New freak behavior

[jTr]

After completing a part file and reaching the jog home final command, machine instead jogs as if home were 96" the opposite direction, leading to a hard stop crash on the X axis. Program disappears from screen entirely as machine crashes.

Re-boot machine, computer, and SB3. Run next part file. Send report to tech support. As I'm typing, next file ends exactly the same....

Previous 3 sheets ran fine. All part files generated with VCPro this morning in one continuous session.

Clues?

Jeff

[joe]

Yep, I've had the same thing happen. Sounds like a grounding problem. SB has always had static electrical issues.

[Brady Watson]

Jeff - Delete your ShopBot .ini file in the ShopBot3 folder. Then open up SB3 and run UR and pick your machine. See if that clears it up. Most times just running UR will overwrite the .ini, but sometimes you have to manually delete it.

-B

[srwtlc]

Jeff,

Tell us what version of SB3 you're running...Help/About. There have been some issues with early 3.8.XX versions with errant behavior after a JZ and a jog to another location , which is how a file ends. Latest version is 3.8.38.

Also, I'm sure it's pretty dry in SD this time of year and static is your enemy. Is your machine grounded properly? Bare ground wire inside dust collector hose? What were you cutting and was the chip load up the dust collector on the heavy side?

You could edit the last line(s) of the file as a test to see if it's the aforementioned bug, by changing the final J3,0.00,0.00,0.00 to a JH instead.

[jTr]

Static is an issue, as we are at the peak of dry season here. misted around cables and table base to help shunt any free roving static charges. Completed last two sheets yesterday with no further issues.

Frank emailed last night, suggesting a ZT command to zero table base coordinates. I've read the help file on this topic to fully understand, and complied this AM.

Currently running version 3.8.26. Other than this recent development, it's been the most trouble free experience in 4 years of running this machine, but if you insist .38 is likely to cure, I may go ahead with that upgrade.

Brady: Though it's caused no issues in the past, I opened with X/Y in negative values yesterday, as I had run dovetails on opposite corner the previous day. However, those were re-set to positive values, full re-zero routines run plus three parts successful before this issue arose. Are you suggesting it's possible there is a remnant of previous files or adjustments (negative Unit Values in this instance) "sticking" to the Shopbot .ini file that may be the culprit? If so, should I be repeating your suggested remedy each time I invert table ends in this fashion?

Thank you all,

jeff

[Brady Watson]

Jeff,
I've seen the .ini get corrupted for no apparent reason. It won't hurt anything to delete it and recreate it. It is possible that something didn't get cleared out. I think the important thing is to write down whatever you did in your notebook and remember to do it again next time.

-B

[paul_z]

I also get a corrupt .ini about once a year. Doing a "UR" fixes it.

Paul Z

[Davo]

Anything bad about doing a UR each day just to be safe?