Hey there! New guy here. I just updated to a version of the index.html.gz that has the Define XY Home press and hold change. Figured I’d drop in and give some feedback on that change in particular.
I’ve been mostly running the Maslow off my phone or a tablet while in the garage, and the default behavior for those devices when you press a button for a prolonged period of time is to select the text on the button and offer to copy it for you. In other words, I can’t set XY home anymore when using a phone or tablet because press and hold doesn’t play well with touch screens. I don’t know if there’s a better way around it, but I guess there’s always a confirmation modal?
I’ve been kinda thinking that change isn’t right. I was thinking instead we might need to implement an “undo” function so it changes location with just one click, but then it can be undone if it was a mistake
Having it display coordinates in fields that can be edited directly would also be a great way to get around issues with this and make it easier to both return to and use custom home locations per cut if necessary.
Here’s a quick interstitial firmware update 0.82.2 with a couple of tweaks. This update adds a double tap behavior to set the home position on touch screens where a long press doesn’t work, and this update downgrades the over current error from an error which will stop the machine while it’s cutting to an error which shows up but doesn’t cause the machine to shut down.
@bar I am assuming this update is to help with the current errors I am experiencing. Just wondering if bypassing this error could cause damage to motors or other negative consequences.
Is there anything I should be monitoring if implementing? Measuring motor temperature perhaps?
The real concern is that it could break a belt. In practice I’m not sure how useful that warning message actually was which is why I feel OK disabling it
I like that you separated the Z stuff from the X-Y stuff. The one outlier is the mm/inch button which is in the X-Y space, but applies to both. I don’t know if that will confuse new users, but I thought I should mention it.
I like it, couple things though, is it possible to make the xy and z numbers look and act like a text box? Make it have a white background with a border around it so it is obvious it is editable? I also don’t feel like it is necessary to have a popup 10 key either, but maybe it is for tablet and phone users. I always have my laptop and would prefer to click a text box, edit the number, and hit enter, but understand tradeoffs are necessary.
The mm does seem a little out of place there, but have no suggestion where it would be better Maybe move the unit definitiion to the setup screen and then just display the unit (unedittable) next to the number?
Also, maybe put the text 'Move" either above or to the left of the numbers.
Move: 100
or
Move
100
Yes! In fact that change will already be in today’s firmware update. The inches/mm was actually already updating, but the distance to move wasn’t which meant that suddenly jog would move 100 inches instead of 100mm. Now that distance to move gets divided by 25 when the machine is switched to inches so it will automatically become 4 inches.
Excellent suggestions!
You are spot on, it’s needed for tablet and phone users, but there is no reason that we can’t take keyboard input too so that typing a number and pressing enter has the expected effect. Great idea!
Version 0.82 has only been out for a few minutes, but here is 0.82.1 which adds a couple things that we would like to start testing for the next release.
0.82.1 adds in @ronlawrence3’s excellent logging system to make it easier to track down bugs (although there is not a UI to turn it on yet) and also brings back the over current alarm but with a much higher threshold hopefully giving us the protection that it brings without the false alarms, although we will need to get feedback on that to see if it works right.
Here is 0.82.2 which is a part of investigating the 15mm error. This update gives you the option to adjust the timeout on the I2C line which seems like the source of the issue. It’s a bit crude at the moment, but pressing the “Test” button will lower the timeout from 50ms down to 10. (You will see some text printed in the console which confirms that)
Restarting the machine will reset it back to the default of 50ms.
I think that the reason that we were seeing the error happen less on older versions of the firmware is that earlier versions have less going on which leaves more processor overhead making the machine less susceptible to these timeouts leading to issues.
I would be very grateful if someone who is seeing the issue would be willing to run the following test.
Power the machine up
Press the test button and confirm that it says in the console that the timeout has been lowered to 10
Retract All → Extend…etc and run normally
See if the behavior of the 15mm error is any different
@bar, no join for me with 82.2. All I attempted to do after Rectract/Extend/Tension was move to Home (which spooled out a ton of extract slack on the trailing belts) then Tension again (because of the extra slack). It through the error as soon as the Tension was complete.
Index.html Version: 0.82
[MSG:INFO: Firmware Version: 0.82]
[MSG:INFO: I2C timeout: ]
[MSG:INFO: 10]
[MSG:INFO: I2C timeout: ]
[MSG:INFO: 10]
[MSG:INFO: Motor detected on Top Left]
[MSG:INFO: Encoder connected on Top Left]
[MSG:INFO: Magnet detected on Top Left]
[MSG:INFO: Motor detected on Top Right]
[MSG:INFO: Encoder connected on Top Right]
[MSG:INFO: Magnet detected on Top Right]
[MSG:INFO: Motor detected on Bottom Left]
[MSG:INFO: Encoder connected on Bottom Left]
[MSG:INFO: Magnet detected on Bottom Left]
[MSG:INFO: Motor detected on Bottom Right]
[MSG:INFO: Encoder connected on Bottom Right]
[MSG:INFO: Magnet detected on Bottom Right]
[MSG:INFO: Retracting all belts]
[MSG:INFO: Bottom Right pulled tight with offset -0.011]
[MSG:INFO: Top Right pulled tight with offset -0.032]
[MSG:INFO: Top Left pulled tight with offset -0.064]
[MSG:INFO: Bottom Left pulled tight with offset -0.011]
[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.126 TR: 0.104 BL: -7.233 BR: -12.482]
[MSG:INFO: Center point deviation: TL: 0.126 TR: 0.104 BL: -7.233 BR: -12.482]
[MSG:INFO: Center point deviation within 15.000mm, your coordinate system is accurate]
[MSG:VRB: Mount_sd]
[MSG:DBG: /SD/Paddleboard Lift-2.nc found]
[MSG:DBG: path /SD/Paddleboard Lift-2.nc CT text/html hash ]
[MSG:VRB: Unmount_sd]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.054 TR: 180.787 BL: -199.283 BR: 12.536]
[MSG:ERR: Center point deviation over 100.000mmm, your coordinate system is not accurate, adjust your frame dimensions and restart.]
[MSG:ERR: Emergency stop! Stopping all motors]
[MSG:WARN: The machine will not respond until turned off and back on again]
[MSG:INFO: Center point deviation: TL: 0.054 TR: 180.787 BL: -199.283 BR: 12.536]
[MSG:ERR: Center point deviation over 15.000mmm, your coordinate system is not accurate, maybe try running calibration again?]
I should note that I ran a calibration last week successfully with ~0.75 fitness and haven’t used it since.
Maybe move the unit definitiion to the setup screen and then just display the unit (unedittable) next to the number?
