Wifi module for R2C2 getting ready

[Jorge Pinto]

This module is very easy to build, only 4 wires to solder. It works as expected.

It needs more development, right now the only piece missing is the
ReplicatorG_R2C2 with Sockets communications instead Serial.
What is done/developed until now:
- R2C2 firmware (edge branch) supports UART for communications with
the module (thanks Bob Cousins)
- The IMX233 Linux board have a software for Serial<->Socket (thanks
to Nelson Neves). There is also a python code I did that does
Serial<->Socket.

bitBOX can help others R2C2 developers who wants to play with this
Wifi module. We can help on getting all the components from market and
build/assembly the module.

--
Jorge Daniel Pinto
+351 927 145 983
jpi...@bitbox.pt

www.bitbox.pt
IEUA - Universidade de Aveiro
Portugal

[Nelson Neves]

Hi Jorge,

nice to see that you are also getting into python and make your own tests, I don't use python that much (already have my hands full), but I've seen ppl doing very nice things with it ;)

I'm currently on vacations (that started in a bad way), but things are now getting better and hope to make some additional tests with Olinuxino Micro board + R2C2 (trying to get my Node.js WebInterface running).

Really looking forward to see the ReplicatorG tcp/ip stuff integrated and get it working with the OlinuxinoMicro/rPi proxy/gateway ;)

[Rui Ribeiro]

Hi all,

 

I was playing around with my arduino and the ethernet shield, and got it to work as a serial<->socket relayer.

 

Looking forward to see ReplicatorG with sockets! I'm ready!

 

Rui

[Jorge Pinto]

2012/8/24 Rui Ribeiro <racri...@gmail.com>:

> Hi all,
>
> I was playing around with my arduino and the ethernet shield, and got it to
> work as a serial<->socket relayer.
>
> Looking forward to see ReplicatorG with sockets! I'm ready!

Let's go!!

Can't you help with ReplicatorG with sockets?

In your case, arduino and the ethernet shield, how your machine can be
indentified on the network? How would the software identify your
machine on the network?

[Rui Ribeiro]

Hi Jorge,

 

Can't you help with ReplicatorG with sockets?

Not until I get my printer printing! It is being an hard fight... that I will win!

 

In your case, arduino and the ethernet shield, how your machine can be
indentified on the network?

The arduino presents on the network as a "raw TCP server" on port 23 on the IP setup by DHCP. At the end the arduino is transparent, just an applicance that on one side has the "raw TCP server", on the other a serial port and it passes the bytes both ways.

 

How would the software identify your machine on the network?

I suppose the same way it finds your wifi ethernet link... Probably by defining a configuration parameter on ReplicatorG for the IP and  port where the printer is.

There are some other tricks to make it plug&play, but I don't think that we are going that way, at least on the first version. 

Rui

[Jorge Pinto]

>> Can't you help with ReplicatorG with sockets?
>
> Not until I get my printer printing! It is being an hard fight... that I
> will win!

May the force be with you :-)

>> How would the software identify your machine on the network?
>
> I suppose the same way it finds your wifi ethernet link... Probably by
> defining a configuration parameter on ReplicatorG for the IP and port where
> the printer is.

Current my Linux wifi board connects to local network/router. I can
connect to board using his hostname that is "R2C2", I don't need to
know which IP it got from the router/network.

> There are some other tricks to make it plug&play, but I don't think that we
> are going that way, at least on the first version.

Other than using hostname?

[Rui Ribeiro]

>> How would the software identify your machine on the network?
>
> I suppose the same way it finds your wifi ethernet link... Probably by
> defining a configuration parameter on ReplicatorG for the IP and  port where
> the printer is.

Current my Linux wifi board connects to local network/router. I can
connect to board using his hostname that is "R2C2", I don't need to
know which IP it got from the router/network.

What happens is that the Linux exposes himself to the LAN using some trickery, like NetBios announcments or similar. I don't have it on the Arduino. It is just a straight plain TCP server with nothing else.

I can set the arduino to a static IP and then configure "hosts" file on windows and then I can call "r2c2" also from ReplicatorG. ;-)

 

> There are some other tricks to make it plug&play, but I don't think that we
> are going that way, at least on the first version.

Other than using hostname?

Option A: LAN discovery

When I say plug&play is make an autodiscover of the service on the LAN. First we must define a few "constants" of the service, like, which port it will run on, or if it runs on something know if there is a specific protocol that should be used to identify that we are talking to a "gcode consumer".

Then we start with a ICMP lan broadcast, then on each response we try the IP and Port until we get some result.

Option B: LAN annoucment

Either (or both) send multicast UDP packets on the network to a specific IP and Port announcing "I'm here with this IP and Port". The printer should respond to the announcment with its IP and Port.  ReplicatorG will then construct a list of devices on the LAN.

...

Rui Ribeiro

racri...@gmail.com

[P Brier]

There is a version of repg with socket support:

https://github.com/spoorloos12/ReplicatorG

May need ti merge it with recent version.

Op 24 aug. 2012 11:50 schreef "Jorge Pinto" <jpi...@bitbox.pt> het volgende: