-
-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm getting soft limit errors within the prescribed distances but can jog normally #1127
Comments
Please supply all the startup message as shown by $SS, not just the one signon line. |
Also what is "fluidwifi"? Do you mean WebUI? Did you home the machine first? We need complete information including everything that you did after starting the machine. |
Thanks Mitch. I do home the machine after every startup and firmware change because otherwise it wont function. Yes I meant webui using wifi (tried to designate that it wasnt bluetooth) I simply home the machine, enter a g91 code and get the error. Reset, and it jogs perfectly. Tell it another code like g91x-50 while its at the 1240mm positive home postion, or 1200 etc. and the soft limit error pops up. This is new after I fixed the speed_map because it had 0% and 0-25%. But this occurs without powering up the VFD |
I am going to guess that you have a work coordinate offset that is outside the machine range. But I can't tell for sure because you have still not provided enough data for me to evaluate the situation. I would like to see the complete startup messages, and a complete list of exactly what you did. |
$G |
$X Heres what happens when I try to move along the x axis |
Thanks, now type ? several times until you see a status report with a WCO: field and tell me what is in that field. |
Can you explain how to do that? I'm pressing "?" and enter over and over and I've tried pressing "?????????" and enter. lol. I hope i'm not the king of amateur hour over here |
Hit enter or send after each one if you are in the WebUI console |
Do you have verbose enabled in the WebUI console? Support is much easier with FluidTerm because there is less in the way. |
oh.. finally got it <Alarm|MPos:1240.000,1240.000,150.001|FS:0,0|WCO:0.000,0.000,0.001> |
Looks like there is a 0.001 offset on the Z axis |
Is there a way to fix that? I'm not sure why that would happen |
We might be seeing a rounding error problem. Internally, positions are held in integer units of steps. Your Z axis steps_per_mm is 799.43. Multiply that by 150 mm and you get 11914.5 , which is not an exact integer so when it gets converted to an integer it is rounded up to 11915 . Convert that back to floating point by dividing by 799.43 and that gives 150.000625 which is closer to 150.001 . |
I really feel like I botched the file for the Z stepspermm. I used a calculator to correct the movement but I feel like it shouldnt be so far off the 320 of the other two. I'm pretty sure its the same ball drive and pitch on the ultimate bee 1515 |
I suspect that it would work if the z steps_per_mm were 800. The closest value to 799.43 that doesn't cause rounding problems at 150 mm is 799.42 |
Mitch, youre a god amongst plebs with hobby interests outside of their skill level. Thank you! I'm ready to test the VFD for EMI now (which hasnt been a problem from before this started) I haven't changed the z steps_per_mm for days so I would have never caught that and I'm not sure why it started becoming an issue. Maybe running the VFD started the error? Its on a 220 circuit and the steppers are on a separate 110. I've heard people having less issues when theyre both on the same 220 circuit so if it crops up again i might try that Thanks again! |
It seems unlikely that VFD interference would cause this particular problem. If it were me I would jog off the Z and set the work coordinate zero somewhere away from the limits of travel. |
Do you mean to initially jog it and then set zero with the zero button? I'm having issues with seeing the work position to the updated current value. I incrementally moved X axis over the entire 1240mm but it only showed it to be 640 away. Once I home the z, it updated the x position |
I'm sorry, I don't want to think about this anymore right now. Got other stuff on my mind. |
No problem, Mitch. Appreciate the speedy help. I'll do some research. Thanks again |
Wiki Search Terms
Soft limit error. ALARM:2 Soft limit alarm.
Controller Board
Xpro V5
Machine Description
Ultimate Bee 1515 220v 2.2kw water cooled spindle.
Input Circuits
No response
Configuration file
Startup Messages
User Interface Software
Fluidwifi
What happened?
I've had success with this yaml file in homing and giving g91 codes but all of a sudden its stopped. I get a soft limit error even when I ask it to move 5mm and the spindle is in the middle of the table. The work position is often incorrect. The machine jogs fine after initializing and going through homing on all axes.
This file has worked fine before and I've attempted to remove soft limits with false but it still gives the same error. This occurs even if the VFD is unplugged from the unit although in previous files the vfd functioned well without interrupting the machine. It didn't like how my speed % was set up so I fixed that but I'm still not able to position the tool head correctly.
GCode File
No response
Other Information
ALARM:2
Soft limit alarm. G-code motion target exceeds machine travel. Machine position retained. Alarm may be safely unlocked, click the Reset Button.
[MSG:ERR: Reset to continue]
g90x-30
[MSG:INFO: Soft limit on Z target:150.001]
ok
[MSG:INFO: ALARM: Soft Limit]
ALARM:2
Soft limit alarm. G-code motion target exceeds machine travel. Machine position retained. Alarm may be safely unlocked, click the Reset Button.
[MSG:ERR: Reset to continue]
g90y-30
[MSG:INFO: Soft limit on Z target:150.001]
ok
[MSG:INFO: ALARM: Soft Limit]
ALARM:2
Soft limit alarm. G-code motion target exceeds machine travel. Machine position retained. Alarm may be safely unlocked, click the Reset Button.
[MSG:ERR: Reset to continue]
g90z-20
ok
g90z-40
ok
All of those "ok's" are ignored by the mahine.
The text was updated successfully, but these errors were encountered: