uh oh in configurator v2.1.0-RC1-33 [current values]
observation in ratos 2.1rc "Uh oh, something went wrong!" ?
Config->Motion->pick driver->delete entry in "current" ->boom
background/intend: ... Not sure which 5160 to pick (got a BTT TMC5160T which is not listed, only PROs) , so thought I'd pick one, set the current really low as precaution then try to figure out in config files next step. On deleting the preset entry to enter a new one it crashes. Seems reproducible. Also UhOhs on other entries, like "1.". And the up-down arrows change in full 1A increments (maybe 0.1A increments are more suitable. Not really a problem, just feedback on the ui since its rc.
background/intend: ... Not sure which 5160 to pick (got a BTT TMC5160T which is not listed, only PROs) , so thought I'd pick one, set the current really low as precaution then try to figure out in config files next step. On deleting the preset entry to enter a new one it crashes. Seems reproducible. Also UhOhs on other entries, like "1.". And the up-down arrows change in full 1A increments (maybe 0.1A increments are more suitable. Not really a problem, just feedback on the ui since its rc.
12 Replies
The config for the pro is the same as for the T. I’m using it since day 1.
Just set the correct current (24 or 48v) and that’s it
🙂 The drivers are from a while ago and had their cooling fins fell off during delivery. The old factory glue hid the "pro" print on the board. Discovered that on cleanup pictures after cleaning... (so ... BTT 5160T pro 1.1 which are covered by the config wizardry)
If you update this stops breaking, was fixed a month ago 😄
You should very much update all the package via the mainsail machine tab before starting the hardware selection part of the wizard (so right after connecting to wifi).
maybe it is time to do another RC release so that people are forced to have all the updates?
Wanted the docs ready
They will have to update once RC2 is released as well, it's just a matter of time.
It would probably be better to build in a self update procedure in the wizard
or at least a check to say "hey you are not on the latest and therefore there might be bugs that have already been fixed"
v2.1.0-RC1-33 was the latest version offered when I opened this thread.
it's also happening with v2.1.0-RC2-0.
the configurator log ends with:
[{"code":"invalid_type","expected":"number","received":"nan","path":["current"],"message":"Expected number, received nan"}],"name":"ZodError"}
I need the debug zip
I've fetched a new SD card, imaged 2.1 rc2 onto it. Booted. Ran update. Then went through config. opened advanced motion config. removed the Current setting. UhOh. Still happens. So not something I messed up playing around everywhere. I'd assume the code for that number box can't deal with (temporary) nothing in it.
I got the debug.zip. How do I get it to you securely? (onedrive link in a pm?)
Okay so the way to reproduce is to remove the input from the current setting, that helps a lot, will get that fixed, it should show you an error that you need to input a number, so just do that in the mean time (don't delete, adjust instead, you can use the up/down arrows) 🙂
(I don't need the debug zip with a clear way to reproduce the error, so no need to bother with that)
yes, I know how to work around. Not an issue for me. Just reporting it to contribute a tiny bit to your great work.
(crashing invalidates all the steps until crash ... unhappy user experience outside RC's).
For up/down: did not check this time, might be fixed already, back on initial check I found increments in 1A too high. 0.1A would be more suitable.
Appreciate it!
I removed the 0.1 stepping because it has some awkward behavior in most browsers if you need more precision than 0.1. I will replace it with a custom number input component.