hexagon logo
Register Sign in
  • Replies 28 replies
  • Subscribers 23 subscribers
  • Views 597 views
  • Users 0 members are here
Options
Related

Offline Program with an Online Seat

KamikazeKonrad
I know this isn't news to many currently using the forum, but for those interested in offline programming when all they have is an online seat (dongle's married to a CMM), there was in the past a workaround to programming offline, that may still work for you.

Download and install PCDmis version 3.5 or earlier on a computer you want to offline program from. Locate the file interfac.dll in the install folder and rename it to anything other than interfac.dll. Plug your dongle into the USB port, and you're good to go. You may not be programming in the latest version, but any newer version will open the older versions saves, and furthermore, with a program like UltraVNC, you can remote access the computer you've set up and program from anywhere.

The only issue is that you can't run your CMM while you have the dongle in another computer.
Parents
  • When our management learned of this "Background Editor," they took this up as the torch for why we did not need an offline seat. "We can program while we run production!"

    Try programming a part while another is running. That is, if you do not have any objections to accepting bad parts or crashing expensive equipment. If a program ends with you still in the background editor, it screws up the printing of the report royally. On top of that, I have had it put in autofeatures, movepoints, etc, into the currently running program, not the background program, and vice-versa. After wiping a TP200 and accepting bad parts twice because of this problem, we no longer have more than one program open at a time.
    There are a couple of tricks to using the background editor while running parts.

    1) NEVER have 2 programs open that use the same probe file.
    2) Save the stats without the automatic update command at the end of the program, for every progam you run while using the BGE, this makes it "pause", thus allowing you to change to the ONLINE to finish the program.
    3) Open the BGE program BEFORE you cycle the running program.
    4) Do NOT "execute" the BGE program while the running program is running.

    I've never had it add things to the running program. BUT, with the advent of V3.7, some of the "things" stayed visable on the monitor for the program you were NOT seeing. For example, the SEARCH pop-up. You could start running a program, then switch to the BGE program, do a search for something, leave the window open for your next search, then go back to the running program and the stupid SEARCH window is still there. You can still type stuff in it, but it is "working" in the BGE program. If the BGE program is NOT the visable program, NONE of it's command windows of ay kind should be visable, ONLY those that the running program are using should be visable.
Reply
  • When our management learned of this "Background Editor," they took this up as the torch for why we did not need an offline seat. "We can program while we run production!"

    Try programming a part while another is running. That is, if you do not have any objections to accepting bad parts or crashing expensive equipment. If a program ends with you still in the background editor, it screws up the printing of the report royally. On top of that, I have had it put in autofeatures, movepoints, etc, into the currently running program, not the background program, and vice-versa. After wiping a TP200 and accepting bad parts twice because of this problem, we no longer have more than one program open at a time.
    There are a couple of tricks to using the background editor while running parts.

    1) NEVER have 2 programs open that use the same probe file.
    2) Save the stats without the automatic update command at the end of the program, for every progam you run while using the BGE, this makes it "pause", thus allowing you to change to the ONLINE to finish the program.
    3) Open the BGE program BEFORE you cycle the running program.
    4) Do NOT "execute" the BGE program while the running program is running.

    I've never had it add things to the running program. BUT, with the advent of V3.7, some of the "things" stayed visable on the monitor for the program you were NOT seeing. For example, the SEARCH pop-up. You could start running a program, then switch to the BGE program, do a search for something, leave the window open for your next search, then go back to the running program and the stupid SEARCH window is still there. You can still type stuff in it, but it is "working" in the BGE program. If the BGE program is NOT the visable program, NONE of it's command windows of ay kind should be visable, ONLY those that the running program are using should be visable.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement