Where was the workpiece Z zero set? What did the digital readout say during each of these steps?
1 Like
Correct.
It looks as if the Quick Action doesn’t trigger a Z-axis measurement and the application of the tool length offset.
Tod1d, I didn’t think to look at the readout when this was going on, so I started the machine again to duplicate it and take notes.
One probable flaw on my part, on a previous power up I set 0s using the corner position on Bit zero (V1) while just setting it on the spoil board as opposed to setting Z 0 on top surface, but I did it a second time today and the same thing happened, just the Z number was different.
Here’s what I noticed: On initial power up through initialization the Z position was Z -0.312, When I moved the spindle to 0 X&Y then tried to move to one inch above Z it moves up, chatters, and the Z position counted up to Z + 1.00. I watched the Z numbers moving as it was chattering and it stopped when it reached 0 Z.
I then zeroed Z on the top of Bit zero and on power up the Z position was -0.078. But it still chattered when moved as before.
If I understand it correctly, Z zero position is a combination of spindle height and tool stick out length.
So, it appears that the machine does retain spindle XYZ position but not the length of the tool on power up, since it doesn’t know if the tool was changed since the last trip to the bit setter.
Suggestions:
1, Maybe the program could be changed to retain tool length. Or
2, Add popup box asking if tool has been changed since last trip to bit setter. or
3, Grey out the selection “Plunge to 1 inch above current Z zero” until a trip to Bit setter or
4, Just tell me I’m doing the whole startup wrong, I’m good with any of those.
A trip to the bit setter during power up was a good thing.
I’ll go back and reread Rob’s posts about the new start up process and try and wrap my brain around the new flow of things.
It probably should check that the workpiece Z zero is at least 1" below the machine Z zero before trying to go there.
I never use the “Rapid to 1” above Z zero". I rapid to XY zero, then jog down to my part.
You can also look at the machine coordinates by clicking on the “Position” word. It will toggle between machine CSYS (G53) & workpiece CSYS (G54).
I just got done with troubleshooting the same problem on my machine. (CM 6.22 worked, Beta release didn’t) After a few exchanges with support they asked me to disable my Blue Tooth driver. After I did that the new Beta Version connected and ran. I have two older Dell PC running Windows 10. Both showed the same problem
1 Like
Wonder if C3D are finally adding Bluetooth support for the ESP32 in the S5 Pro’s Warthog electronics.
Good to know! I’ll give that a try later on today. Thanks
No, we’re not moving to Bluetooth at this point. Support has noticed that some PC’s with serial port troubles can be fixed by disabling bluetooth.
Dell, in particular, seems to have more driver trouble than any other manufacturer. We’ve spent weeks on problems that turned out to be bad drivers from Dell. (We had an early Shapeoko user that worked for Dell, and he mentioned that they frequently ship outdated drivers.)
3 Likes
That did it! Disabled the bluetooth driver and immediately got connection, and the setup wizard is running nice and fast.
2 Likes
Not surprised by this at all. I have done IT work for 20+ years and have all sorts of Dell horror stories. Dell has a history of making horrible Windows drivers. Their Dell RAID cards which were based off LSI Logic chipsets had custom firmware / drivers. The LSI Windows drivers for the LSI manufactured cards were multi threaded. The Dell Windows drivers were single threaded. This caused major performance issues on Windows in comparison to the LSI cards. If you installed Linux on the server they would use the same driver and would get great performance… for a few minutes. The Dell card would overheat because they did not include a heatsink in comparison to the LSI cards. It honestly seemed that the Dell driver was designed to under perform so they could save $2 on a heat sink. I ended up having to epoxy heatsinks to 24 Dell servers at one point because of this.
2 Likes
This topic was automatically closed after 17 days. New replies are no longer allowed.
635 is now on the main download page. Thanks to everyone who tried out the beta!
10 Likes