search

mfassler / eFirmata

Connecting the real world to the digital world.
Other
5 stars 0 forks source link

firmata compatibility. #2

Open monteslu opened 9 years ago

monteslu commented 9 years ago

I like the idea of this project. Any reason to not strive for 100% firmata compatibility? I've done some remoting of firmata on top of arduino and other Johnny-Five compatible hardware: http://blog.iceddev.com/2014-12-05-remotebots-cutting-the-cord-with-remote-io.html

mfassler commented 9 years ago

Hello,

Thank you for your interest in eFirmata. IIRC, the "regular" firmata protocol is 3 bytes per one action, whereas I'm putting things directly on UDP. One UDP packet is up to about 1400 bytes on normal ethernet -- so that allows me to, in principle, set up to 1400 or so PWMs in one, single packet. In principle, I could also set ~11200 GPIO bits in one, single packet.

I would be perfectly happy to make a "firmata over UDP" protocol (and/or "MIDI over UDP") if there was some interest in that. I think that that would allow for some backwards-compatibility, I suppose... (it is rather inefficient to use an entire UDP/IP packet for only 3 bytes, though...)

(I would also have some use for async serial over UDP. And I've got some SPI-over-UDP... but that still needs some more work.)

(I'm going to look at your webpage some more later this afternoon... it looks pretty interesting.)

-Mark

On Sun, Jan 4, 2015 at 3:33 AM, Luis Montes notifications@github.com wrote:

I like the idea of this project. Any reason to not strive for 100% firmata compatibility? I've done some remoting of firmata on top of arduino and other Johnny-Five compatible hardware: http://blog.iceddev.com/2014-12-05-remotebots-cutting-the-cord-with-remote-io.html

— Reply to this email directly or view it on GitHub https://github.com/mfassler/eFirmata/issues/2.