Chris Kotelmach wrote:
I didn’t enter into the config as I was following the youtube video and entering directly into the yaml seemed to cause the previous issue. perhaps the videos are out of date.
when you start the config, one of the things it asks you is what your frame size
is.
That’s used as the initial guess, and the error you are reporting is that that
guess is too far off.
David Lang
completed successful calibration, fitness 1.069.
entered values into yaml.
uploaded yaml with calibrated values, restarted machine, retracted, extended, applied tension,
[MSG:INFO: Extending all belts]
[MSG:INFO: All belts extended to center position]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: -0.000 TR: 0.104 BL: 0.137 BR: -5.840]
[MSG:INFO: Center point deviation: TL: -0.000 TR: 0.104 BL: 0.137 BR: -5.840]
[MSG:INFO: Center point deviation within 15.000mm, your coordinate system is accurate]
now I try to jog and instead of moving, it unspooled some and just unlocked all the motors
no error message or indication that anything is wrong:
Jog: X-5
Jog: X-5
Jog: X5
Well, that’s a good improvement at least.
When you calibrated, was there a bit in the router and was the z as low as it would go? It’s not in the instructions (and likely should be added to them) that before calibrating you need to remove any bits from the router and drop the z axis all the way down. Often that can cause spooling issues as it tries compensating for an incorrect z position. That being said, I don’t think that usually prevents things from moving entirely.
no bits in the router and it is all the way down,
It simply unspools some and the motors are then unlocked.
I can reapply tension and it gives another correct coordinate system in the serial message
go to jog and same issue
moving the Z axis also just unspools the xy axis belts
Jog: X-5 // unspooled. then I applied tension
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.236 TR: 0.091 BL: -0.115 BR: -5.690]
[MSG:INFO: Center point deviation: TL: 0.236 TR: 0.091 BL: -0.115 BR: -5.690]
[MSG:INFO: Center point deviation within 15.000mm, your coordinate system is accurate]
Jog: Z5 // unspooled.
Jog: Z5 // unspooled. then I applied tension
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.247 TR: 0.155 BL: -0.053 BR: -4.756]
[MSG:INFO: Center point deviation: TL: 0.247 TR: 0.155 BL: -0.053 BR: -4.756]
[MSG:INFO: Center point deviation within 15.000mm, your coordinate system is accurate]
The unspooling is odd, especially for a z axis move.
It’s like it tells the xy axis motors to turn instead of the z axis
I’ve run out of posts so I’ll have to keep editing this one
I’v solved the calibration issue and followed those steps you lay out in future posts regarding calibration.
The unspooling issue is the problem now.
do you have contact info to send to chris@kotelmach.com
The inputs options are under ‘Config’. It asks you for the Width (x-axis dimensions) and Height (y-axis dimensions) of your frame. Changing them using the Config options will change them in the yaml file without needing to edit anything in the yaml file. I would avoid editing anything in the yaml file directly until after things are up and running smoothly.
Also in Config, it asks for home many points in the calibration grid and for the size of the calibration grid. I suggest starting with something like 3x3 or 5x5 grid. After a successful calibration, the system will update the frame dimensions with the dimensions that it calculates from the calibration. At that point, you can start another calibration with more points in the grid (e.g., 7x7 or 9x9).
The calibration should take more points than just that first point.
The process for calibration should be something like this:
If you get this error, it means that the frame dimensions that were inputted are too far off from the actual dimensions of the frame. In the instructions, it says that you do not need accurate frame dimensions and that calibration will figure them out, but you actually do need the inputted dimensions to be reasonably close (~1" for each axis) to the actual frame dimensions, otherwise this error pops up.
Chris Kotelmach wrote:
now I try to jog and instead of moving, it unspooled some and just unlocked all the motors
until you calibrate, you cannot jog safely because it doesn’t know where the
anchors are.
David Lang
what size frame did you build?
David Lang
I followed the instructions for the default wooden frame
Finally got the Maslow to make a cut, but on second attempt It disconnected, after a minute, then I got the following messages after reconnecting: Maslow does not know belt lengths. Please retract and extend before continuing.
error:152 - Configuration is invalid. Maslow.yaml file may be corrupt. Turning off and back on again can often fix this issue. But if I attempt to retract, I get the same message. Router was plunged into the board, when I did a retract and then release, I tried to adjust the Z access, and all 4 belts retracted significantly even with a small z increment
By default, some browsers will ‘sleep’ a tab when you switch to another one. I ran into a lost connection like you describe before I realized that was happening. I was able to avoid it subsequently by changing a setting for that in the browser. Mentioning this in case you were navigating to other tabs.
You mention doing a retract then release before moving the Z axis. Is this accurate? The release tension should not be pressed after retract all if I understand what you wrote.
I guess I should mention that I started doing the retract all, release tension, then apply tension, in order to get it to work reliably.