When I use CM’s rapids I’m crashing into my X limits.
**Edit/Add: I am running CM on Win 10, and my machine is a SO XL
I tried re-sending config data and it looks like CM, when set to Shapeoko XL, is sending the wrong configs:
(2264270): <- ok
(2264269): -> $132=150
(2264268): <- ok
(2264267): -> $131=850 <-- should be 840 for SO XL
(2264266): <- ok
(2264265): -> $130=845 <-- should be 430 for SO XL
I also tried to send the config from a fresh install of Win 10 CM 5.37
Anyone else ever see this issue?
When you go onto config you pick your machine type and z type. Then go to second tab and pick BitSetter and/or BitRunner. Then go back to first tab and send config. You are prompted for z type again. Some forget to go to first tab and hit send config. If you do not send config and just hit “ok” so whatever was in config is persistent from previous send. Did you “Send Config”.
Thank you for the replu. Unfortunately it didn’t work and yes, I do send config. This has me stymied. If I set it up as a S3, it goes to the correct X.
By the way, I even put in the 103 and 140 parameters using /$131=830 and it still goes too far. The log shows the correct x limit but the machine just goes off.
You guys have been terrific. You even are sending out a new PCB. I am not going to open it when it arrives because I don’t think it is a PCB problem. This reeks of software
I have also used the /$ command to input with no luck. By the way, If I tell it that it is a Shapeoko 3, the parameters do the same thing on the log 845 and 850 but the machine will travel about 711mm on the x axis rather than crashing beyond the x limit
Hmm. no mater what I do this machine thinks it is a XXL regardless of what the log has in it