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.....
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.
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.
