GroG's blog

I think I now understand some of the complexity moz4r was trying to deal with in Servo.

setAutoDisable is a great function, and it has saved many Servo lives from blue smoke and 21 gun funeral salutes

But with autoDisable comes a "new" servo State.  

More ServoGui updates, also notice the (save, load, refresh) buttons on the top right.  I got tired of having to start a python service and doing a  :
servo.broadcastState()

Same goes for load & save.

If speed control is selected the regularly disabled speed settings are enabled.  500 is the default max & default start setting.

I have not visited the Servo service for a long time.  It gained functionality, but some of the implementations make it very difficult to extend in the future.  Additionally, there were some problems which made the code unecessarily complicated.

Servo Attach Bug

Thank you Mats for pointing out that a servo controller name should be work as well as a reference
(https://github.com/MyRobotLab/myrobotlab/issues/486)

I caused a bug by removing

servo.attach(name, pin, position)

And I removed it because it was never defined in the ServoControl interface.

I've added (save, save all, load & load all) menu times.  My usuage typically starts from eclipse IDE - so its very different from using the UI all the time.  Gael is helping me with some cleanup (already fixed up Arduino oscope & pins) ..  

(Virtual Arduino Uno)

(Real Arduino Uno)

Kwatters & I have have been pounding together unit tests - in the process I noticed Oscope in Nixie was bork'd - so I fixed in .. and improved it.

kwatters posted this link in the shoutbox - thought I'd re-post (and a few others) to keep it around longer ...

Recently I listened to a podcast about P-Zombies, Zimboes and Artificial Intellegence (the-dilemma-of-machine-consciousness-and-p-zombies).  

Here's gesture/balance.py