next topic »

[on:]

A while back I posted a note to this forum (http://arduino.cc/forum/index.php/topic,75189.0.html) asking for a volunteer to help implement a TCP/IP protocol (http://www.icanprogram.com/simpl/tclSurrogate.html) for the Arduino.   Lots of people read the post,  but no volunteer stepped forward to contribute the code.

We still believe that the Arduino is a natural fit with the SIMPL toolkit and would love to publish an Arduino interface in our next SIMPL release.    If anyone is interested don't hesitate to contact us on the SIMPL project mailing list and we'd be glad to provide whatever testing support is required to make this code a reality including access to a Linode cloud running the SIMPL toolkit.

bob
facilitator for the SIMPL open source project

[Reply #1 on:]

too busy for all interesting projects to volunteer for this one (life is full of choices

Still I think you should find a student / contact a school to implement this in computer class.

[Reply #2 on:]

That is still a valid suggestion,  however most of the local schools teach only web programming and not embedded stuff.   I'll keep searching.

However, since I'm not an Arduino programmer myself,  what hardware would be required?  how big an effort (hours) would this be for an "experienced" Arduino programmer?  beginner?

Thanks.

bob

[Reply #3 on:]

YOu must search for an electronics school no computer science i guess.

owever, since I'm not an Arduino programmer myself,  what hardware would be required?  how big an effort (hours) would this be for an "experienced" Arduino programmer?  beginner?

minimal 1 arduino 1 ethernetshield (better make it 2 of each) and two SIMPL reference devices and a networksniffer preferably one that recognizes SIMPL (2nd project?)
The last 3 as test/debug/reference  environment .

hours? => to complete work out a networkprotocol, test and debug it.. 200-500 hours (I don;t know the complexity) for an experienced programmer. Beginners should not implement network protocols imho, if you want to build something e.g. on top of tcp/ip you must understand the behavior of tcp/ip (my opinion)

why so "many" hours
1) time to learn the merites of the SIMPL protocol, reference and test devices -  50 hours (or is it really really really simple?
2) time to design layered architecture (OSI model alike, responsibilities in the right layer, etc)  - 30 hours
3) defining tests and write these - 50 hours
4) implement the protocol and test it - 10-20 hours per iteration  (expect 5-10 iterations)
5) refactor code 20 hours
6) optimizations optional

As I don't know the merites of the protocol the numbers above are only educated guestimates.

Hope this helpes,