hexagon logo
Register Sign in
  • Replies 41 replies
  • Subscribers 31 subscribers
  • Views 1051 views
  • Users 0 members are here
Options
Related

Using PC DMIS that was set up for CMM with a Romer

Mike_B
I have been tasked with setting up a Romer with existing software that currently runs a CMM. Software PC-DMIS V. 4.2 MR1. I have set the Romer up, calibrated it using its utility feature (not with PC-DMIS) and now I need to know how to get PC-DMIS to recognize that there is a Romer attached. The CMM attaches through COM port 1 but the Romer has a USB connection. Do I need to uninstall and reinstall? Or can I manipulate the current version to "know" that there is a Romer attached....? Any and all help is appreciated.....
  • No, I have a portlock for the CMM running on windows 7 with 2012 MR1 SP1. (The new software was the license that I meantioned earlier) I have contacted Hexagon and am awaiting a quote for a new portlock for the Romer. When we recieved the new computer for the CMM I reflashed the old portlock. We have a Romer with XP and a CMM with Win 7. Only one portlock, I had originally thought I could switch the portlock between the two computers and that all I had to do was make the comp with Win XP and PC-DMIS 4.2 recognize that there was a Romer attached... Still can't get PC-DMIS 4.2 to recognize that there is a Romer attached.....
  • No, I have a portlock for the CMM running on windows 7 with 2012 MR1 SP1. (The new software was the license that I meantioned earlier) I have contacted Hexagon and am awaiting a quote for a new portlock for the Romer. When we recieved the new computer for the CMM I reflashed the old portlock. We have a Romer with XP and a CMM with Win 7. Only one portlock, I had originally thought I could switch the portlock between the two computers and that all I had to do was make the comp with Win XP and PC-DMIS 4.2 recognize that there was a Romer attached... Still can't get PC-DMIS 4.2 to recognize that there is a Romer attached.....

    The reflashed portlock originally belongs to the Romer arm? Or the Romer never has had a portlock? Confused
  • Since I have been in the dept. the Romer has not been operational. Somewhere along the line the computer that was assigned to the Romer crashed, taking its hard drive with it. Local IT picked up the comp when it crashed, that is when I think local IT took the portlock that belonged to the Romer, probably without knowing what they were taking. The reflashed portlock belonged to the CMM the whole time I have been here and still belongs to the CMM. Just when I updated the computer and installed the new PC-DMIS I had to flash the portlock in order for it to work with the new software.... Still have only one portlock and it goes with the CMM. Im guessing the portlock tells the computer what type of machine is attached? Is that why the CMM's portlock will not work with the Romer?
  • Yes, if the Romer interface is no listed in the modules list the portlock will not recognize the arm. You should ask to the IT dept. to search for the portlock, could save big money to your company.
  • The arm will not work until the proper settings on the hasp/portlock have been activated. Not only that we/I don't know what arm you have. Depending on the arm that you have it is going to be one of 2 .dll files either the romer.dll or the romerrds.dll. This does make a difference since depending on which one is selected depends on what it is looking for. I am going to guess hexagon will/should quote you for another license for the arm. This makes more sense since there will probably be times in which you are trying to use both at the same time. If you are running a Infinite 2 or older it will be romer.dll, if it is a absolute are it will be romerrds.dll. You will probably be able to tell to by what calibrating software you are using Cimcore WinRDS (romer.dll), or just RDS(romerrds.dll). And I would also suggest running whatever version you are running on the cmm on the arm. This makes it so that you can program parts on either machine and run on the other with little modification. If the arm was bought with software you may be able to report the hasp lost/stolen and get a replacement at a better cost if you cant find it, this is a process to go through but it may work. Let me know if you have any other questions.
  • I also forgot to mention that if you do find the hasp or get a new one do a fresh install it will save you headache because you will not have to find the proper .dll file if you have the arm and the hasp plugged in during the install.
  • The arm will not work until the proper settings on the hasp/portlock have been activated. Not only that we/I don't know what arm you have. Depending on the arm that you have it is going to be one of 2 .dll files either the romer.dll or the romerrds.dll. This does make a difference since depending on which one is selected depends on what it is looking for. I am going to guess hexagon will/should quote you for another license for the arm. This makes more sense since there will probably be times in which you are trying to use both at the same time. If you are running a Infinite 2 or older it will be romer.dll, if it is a absolute are it will be romerrds.dll. You will probably be able to tell to by what calibrating software you are using Cimcore WinRDS (romer.dll), or just RDS(romerrds.dll). And I would also suggest running whatever version you are running on the cmm on the arm. This makes it so that you can program parts on either machine and run on the other with little modification. If the arm was bought with software you may be able to report the hasp lost/stolen and get a replacement at a better cost if you cant find it, this is a process to go through but it may work. Let me know if you have any other questions.


    All good information! I am waiting on Hexagon to respond with a price for the Portlock. Then I will uninstall and reinstall. Thank you all!
  • Again I cant stress enough only do the uninstall reinstall after you have the new hasp key. This will hopefully cut down on any problems you are currently facing. BTW what arm do you have? Supposedly you can run the new RDS depending on the age of the arm. The new RDS is a little cleaner but it is a little harder to find your verification information.
  • Oh and one more thing, if its not in the budget for the key you can use the quickmeasure functions that WinRDS/RDS have built in for very simple checks (ID/OD/distance between) without a pcdmis license. This will also help you get a little more comfortable with the arm for when you do get the new license. Down where the icon is at in the bottom right hand corner, just right click and go to quick measure. Its a nice quick check tool that is free, it doesn't record the data but it is pretty nice otherwise.
  • Happy to report that we found the Portkey! And I looked in one other place after I found it just so it wasn't in the last place I looked LOL! Itll be tomorrow before I can uninstall and reinstall. Ill follow the instrustions here and let yall know how it goes. Any other info is always good... Thank you!
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement