You can recover the firmware on the SBC itself using the phidget22admin command line tool. You'll need to SSH into the SBC and run: phidget22admin -M 592703/0 -U If it fails, remove power and the vint cable from your vint device, then plug it back in and try again. -Patrick Thanks once again Patric...

Now THAT is the kind of answer I was expecting. Thanks very much!

Thanks, I'll give that a try.

It's possible the interface on the SBC doesn't behave the same as the Windows/Mac control panel when it comes to firmware upgrades. Can you plug it into a Windows or Mac machine and see if it resets in the control panel? Thanks for the great suggestion. Unfortunately that's not possible since the S...

mparadis wrote:To reset the firmware upgrade process, disconnect the board completely (including power supply) and reconnect. It should show up as a Stepper again.

@mparadis, anyone? Is there a way to reset the firmware on the Stepper Phidget that works?

I also think that the motor that overheated got damaged. It is this NEMA-11 stepper motor https://www.phidgets.com/?tier=3&catid=24&pcid=21&prodid=341 and it won't rotate faster than som 75000 RPM anymore while the max speed is 115000. When I try a faster speed, the motor stalls and does...

To reset the firmware upgrade process, disconnect the board completely (including power supply) and reconnect. It should show up as a Stepper again. Except that it doesn't. I disconnected the Servo Phidget and didn't reconnect it since I wrote my post here. I just connected it again but the status ...

I kept the Stepper Phidget with a motor connected to the SBC and after a while it started to make noise and rotate slowly. I touched the motor to make sure that is was vibrating and it was so hot that I burnt my finger and it now has a big blister. Any clue?

Wouter

Hi, Today I tried upgrading the firmware on one of my Stepper Phidgets and it looks like the upgrade failed. Both Stepper Phidgets were like the one on port 0 before I tried upgrading the firmware on the Stepper Phidget on port 1. The firmware got downloaded and installation failed the first time so...

It didn't yesterday and it stuck to Etc/UT. But I connected again and now I see America/Santiago. It even survives a reboot. Strange. Anyway, case solved