Too quiet...

has it been.

I recently found a neat way to control regular servos.
PCB designed to replace the internal electronics of reqular hobby servo, controllable over i2c bus: "Openservo" from SparkFun.

So now the instrument control "chain" looks like this:

It is a mes... I mean a mix of ethernet, CAN-bus and i2c-bus.

Why? Because of mentioned "Openservo" controller.

I found it quite difficult to control several servos at the same time using timers to create PWM signals while CAN-bus was sending/receiving data.

Now CAN is handled by interrupt routines and servos (gauges) are handled with dedicated MCU located in Openservo PCB listening the i2c bus.

Why I am not using i2c to control all the instruments via USB-i2c-adapter? I don't know, perhaps I do not like i2c that much (and I already have couple of other projects designed around CAN nodes...).

Why ethernet