Com port problems...again

[richard_saylor]

Ok, it's been 6 years since I've had com port problems.
Now I've been out of business for 2 weeks.
EVERYTHING is grounded just like it has been for 6 years.
Running Buddy on Windows XP...for 6 years...ok, you get the idea.
Now I have the intermittent connection loss problem.
I've tried two other computers, both Windows 10, but they can't find the Buddy. Assuming that's a Windows 10 problem?
Back to the XP machine. Reinstalled control software and drivers. Wiggled everything internally. Blown any dust out. Replaced memory.
I can get anywhere from a full day of cutting to 1 minute before the dreaded yellow screen appears.
Please don't suggest I contact tech help. They gave me the typical set of instructions I've had for 6 years.
Any ideas? :confused:

[Tim Lucas]

Install a new usb hub?

[Chuck Keysor]

Hello Richard, I feel your pain. I have similar, intermittent Com Error problems. I have gotten lots of suggestions over the years, and think my problem is solved, and then it locks up again. I frankly don't trust my machine to run long jobs.

As it has been explained/or as I understand it, packets of data are transferred from you old XP machine over the USB cable to your machine. And those packets/transmissions get corrupted by ESD events, creating the Com Errors and all of your/our woes.

What I don't understand, is with all of the low cost, tiny PCs, why on earth isn't there a simple retrofit of a little PC into the Shopbot's control box. Then once the file gets loaded into the control box, it can run without being corrupted by ESD.

Well, no doubt that is simplistic. But at this rate, I feel like you and I are stuck............. Chuck

[richard_saylor]

Hello Richard, I feel your pain. I have similar, intermittent Com Error problems. I have gotten lots of suggestions over the years, and think my problem is solved, and then it locks up again. I frankly don't trust my machine to run long jobs.

As it has been explained/or as I understand it, packets of data are transferred from you old XP machine over the USB cable to your machine. And those packets/transmissions get corrupted by ESD events, creating the Com Errors and all of your/our woes.

What I don't understand, is with all of the low cost, tiny PCs, why on earth isn't there a simple retrofit of a little PC into the Shopbot's control box. Then once the file gets loaded into the control box, it can run without being corrupted by ESD.

Well, no doubt that is simplistic. But at this rate, I feel like you and I are stuck............. Chuck

A computer within the control box seems like a simple fix. I like it.
As far as the Windows 10 problems, it seems that I had the wrong driver installed. I have a first generation Acer Aspire One running things now and am back in business....for the time being.
All the the grounding being the same over 6 years leads me to believe that the problem must have been with the XP machine.
I am still using the original USB cable.

[scottp55]

Glad your running again:)
Cables DO go bad, and the only way to know is with a multitester, or swap out the cables to check.
Stinks chasing gremlins around.
Sure we'll see more of this, as static season is almost here.
scott

[Gary Campbell]

From above: "They gave me the typical set of instructions I've had for 6 years."

I'm going to guess that the solution was in those instructions.

[richard_saylor]

From above: "They gave me the typical set of instructions I've had for 6 years."

I'm going to guess that the solution was in those instructions.
Uninstalling and reinstalling the software and drivers seemed to do the trick this time. Although, I'm not certain that the problem is solved. I've made changes carefully following the instructions before. Either the problem will immediately persist or eventually come back. In this case, I've made a few hours of cuts without a hitch. There are may variables in 'solving' this problem. Time will tell.

[Gary Campbell]

Richard...
Time will tell, for sure. Assuming the ShopBot controller card has not been zapped by static or a component failure the only items that can cause those issues are from the USB cable on out.

[ron_moorehead]

I have heard that ShopBot is coming out this fall/winter with the FabMo for the big shopbot cnc machines, which will have a micro computer in the the control box and you will be able to access it by WiFi or Ethernet. This was in a news letter I got this summer:

One of the unseen heroes in the ShopBot booth was FabMo, ShopBot’s new CNC software platform. FabMo provides fast, smooth, motion and incredible ease of use because it allows our CNC tools to be run and managed from any device – phone, tablet, PC, Mac, iPad, etc., and to be run wirelessly or wired. Anyone who watched the snappy cabinet-cutting of the PRSalpha ATC saw FabMo in action. FabMo makes CNC more efficient; it makes CNC easier to use; it makes your CNC better. We’re currently shipping FabMo on Handibots and Desktop products and will be moving it to full-size tools this fall. Shortly after that, FabMo will be available as a control card upgrade for all older ShopBot tools.

[Chuck Keysor]

Thanks Ron! I'll look forward to hearing more information about the FabMo. Chuck

[richard_saylor]

Ok, the problem is back. I've replaced the computer, the software, the drivers, the cable. I've redone the grounding, several times.
As far as tech help, I'm back at the beginning with them since they don't read through emails. I'm getting the seemingly bot generated "help" files again.
They won't tell me what the 'proper' grounding is to avoid ground looping problems. For the last six years I've had a copper wire running through the dust collection hose and attached to the dust collector motor housing. The motor housing is grounded to the service entry grounding bus. The Shopbot computer box is grounded to the Shopbot frame and the frame is grounded to the service entry ground bus. This is how it's been ever since I've had the machine and it worked up until recently. I've checked and rechecked all the connections.

[richard_saylor]

Something else I've told Shopbot help several times but haven't gotten an answer...The packet speed can vary from 10.9 ms to 25.9 ms depending on file size. It always seems to fail during longer files. Is this normal?

[Tim Lucas]

Since your packet speed is VERY LOW (should be in 70's) I believe you may have answered your problem.

[richard_saylor]

i was under the impression that faster packet speed is better.

[srwtlc]

Tim is thinking of the old transfer efficiency %, which was 70% or better. SB3.8.XX no longer uses that test and it is now the packet-et value that is looked at. This value is to be referenced after a single move command of 4" with a MX,4 or MY,4 and then UD to see what the value is. 20ms or less is preferred, though usually any value under 40ms indicates that you should not have any problems running your tool.

Have you done any updating to windows lately? Check to see if USB selective suspend is enabled in advanced power settings. If it's a laptop, make sure that any processor throttling is disabled as well and any turning off of the hard drive. In other words, if it's a laptop, make sure that everything in the power scheme is powered up all the time, no power saving settings at all.

Gotta love the 5th season, static season.

[richard_saylor]

Ok, that makes sense.
Yes, I've got a new computer with Windows 10 that's not a laptop. The old one was an XP machine. Both have had no power setting saving features turned on. Both display the same problems, although the Windows 10 machine much less frequently.

[phil_o]

I had a problem with loosing steps recently. Tech support suggested that I run a USB speed test, one of the SB diagnostic tools. The USB port I was using tested at 56%, 75% is needed. I tested another USB port that came in at 80%. Have you tried other USB ports?

Phil