Tolerate misbehaving desks

[DavidVentura]

Hi
I was getting really erratic behavior from this tool, so I added debug info on the _bytes_to_meters_and_speed function and the 2nd byte was always stuck at 0xff, basically reporting my desk was at ~7meters:

$ idasen height
['0x17', '0xff', '0x0', '0x0']
7.150 meters

After lowering my desk all the way to zero, it started reporting proper values and idasen starting behaving well again.
In the meantime, I had asked it to save my position with idasen save stand and it "corrupted" the configuration, by storing a 7m height.

I think that

• there should be a warning by the tool if the second byte is 0xff
• invalid heights shouldn't be saved to the config

[newAM]

For future reference do you have the stock controller or a modded one?

[DavidVentura]

stock

[robindegen]

I have a stock desk and for me the same happened. It tried saving 7 meters. I do use an idasen app on my phone and the heights selected in there worked fine; just not through this program.

[comkieffer]

For future reference, if the desk starts reporting the wrong height, you can reset the control box. Quoting from the LINAK troubleshooting guide.

This procedure resets all columns to the fully retracted position so that the control box knows where they are.
Note: This is the common solution for when a desk will move down but not up.
When a control box requires initialisation, this is how the system is programmed to behave.

1. Hold DOWN button on desk panel to ensure the columns are retracted to their lower limit (whether it is the fully retracted hard stop or a configured lower limit).
2. Briefly release DOWN.
3. Press and hold DOWN for 5 seconds, wait until all desk movement has stopped, then release.
   3.1. If initialisation is successful, columns will do a slight up/down “handshake” movement.
   3.2. If you have a desk panel with display, E01 is displayed during this part of the procedure.