What do think about storing a persistent counter that is incrimented each bootup and display is periodically so we can idtentify if resets are occuring?
1 Like
You guys are going to hate me but I got āautocorrectedā. My ssid name got changed and I just now noticed it. The software thought that TMOBILE was the same as T-MOBILE. So now I am connected to home WiFi network and have a blinking blue light 
1 Like
So now on to why I have no motion?
Canāt remember if I did an e-stop or not. What are some of the other possible scenarios ??
If you are on the current 0.74 firmware, you can go to the first tab in the ui and send $MINFO in the serial connection and it will spit out some info . look for āhomedā and if that is not true then you are in the state where you have to take the maslow off the frame, retract/extend/re-hang/apply tension before you can move.
Edit: I will be adding things to the interface soon that will detect this condition and notify you on the maslow tab.
Alright. So here is where Iām at right now.
Got connected to home WiFi.
Still could not jog
Updated to 0.74
Was able to move z axis but not jog. Again when the command is given the numbers change and it sounds like something is moving but no physical motion.
1 Like
Every time you restart or power cycle at this point in time, you will have to do the āre-hangā dance I mention above: take the maslow off the frame, retract/extend/re-hang/apply tension. We will eventually have saving of belt sizes but right now, the maslow starts up in a mode where it does not know āhomeā and it canāt move until it gets the belt lenghts via the above process.
1 Like
Iām starting to understand. New issue tho- retract all does not actually retract all. My top right stops with about 7ā of belt hanging out. The others have retracted all the way to the stops/ anchor points.
Tried faking it by only extending a little on each belt but it seems pretty consistent that one belt does now retract all the way.
I assume that this will throw off the calibration as it thinks the frame is different than it actually is??
1 Like
You need all the bets to fully retract so they can zero out in software. Extend them and retract while retracting apply tension so the belts wind tight. It may take several tries until the belts are wind tightly then they should go in all the way
1 Like
I think I need to slow down a little. Really excited tho.
My config still had the āoldā values in it. From the last calibration. Iām assuming that it was hanging on to that info and would not fully retract that top right belt?
I changed the config values and re-saved. Was then able to extend and retract fully.
I think I could be a decent Guinea pig- just tell me what you need.
1 Like
Donavan Rekstis wrote:
Iām starting to understand. New issue tho- retract all does not actually retract all. My top right stops with about 7ā of belt hanging out. The others have retracted all the way to the stops/ anchor points.
Tried faking it by only extending a little on each belt but it seems pretty consistent that one belt does now retract all the way.
I assume that this will throw off the calibration as it thinks the frame is different than it actually is??
it thinks the belt is shorter than it actually is, yes this is a problem
most people have been able to get things to fully retract by increasing the
current limit (default 1300, bump it up 100-200 per attampt) until you can
reliably extend/retract the belts.
Some people have found that when they mounted the motors, they mounted them just
a hair closer to the idler than they should have, and disassembling things to
move them further out makes things move more easily, but that requires
disassembling everything.
David Lang
1 Like
This is the key I think, or just press retract again 