rs-422 rs-232 to fast ethernet converter
Interesting.
I have also been thinking that it might not be too difficult to
implement using Beaglebone Black, Raspberry PI, or even one or another
flavour of Arduino. Lots of possibilities from simple to not so simple.
cheers, Graham ve3gtc
On 2014-11-23 21:38, Neil Schroeder wrote:
If you feel like building :
http://www.ti.com/tool/tida-00226
You can integrate that further than a cots one
On Sunday, November 23, 2014, Joseph Gray jgray@zianet.com wrote:
Didier has a good suggestion as to the serial to Wifi adapter. I may
order one for my Z3801. Looking on Amazon, I see these two units that
are more reasonably priced:
http://www.amazon.com/Ethernet-Serial-RS232-RS485-Converter/dp/B00ATV2DX2/ref=pd_cp_pc_1
Joe Gray
W5JG
On Sun, Nov 23, 2014 at 11:59 AM, Graham <planophore@aei.ca javascript:;>
wrote:
Thanks Didier,
Good suggestions and I have been considering something similar.
cheers, Graham ve3gtc
On 2014-11-23 13:26, Didier Juges wrote:
Graham,
There are a number of WiFi to serial modules like the one I use on my
Thunderbolt monitor: The Microchip WiFly RN-XV-171. Once configured
(typically using a PC), they will present a TCPIP port (TCP or UDP) from
which you can get and send data directly to the serial port.
Alternately, you can use Digi XBee modules that work like wireless RS232
isolators. I use the XSC Pro 900 MHz for a number of projects, including
data loggers that are out of WiFi range. You can get well over a mile in
open space with those. They are limited to 19200 bauds at the most.
Didier KO4BB
On November 22, 2014 4:47:15 PM CST, Graham <planophore@aei.ca
javascript:;> wrote:
I have been contemplating how I will would like to interface to the
KS-23461 devices using rs-422.
One option is a rs-422 to USB cable. Seems easy enough.
But another option I keep stumbling across is a rs-422/rs-232 to fast
ethernet such as:
Frankly, I have no first hand knowledge or experience with these
devices. First glance suggests that it might just be what I want - easy
access to the KS-23461 ports through a connection to my local network
without having a PC of some sort close by.
So, any first hand experience with such devices? Good idea or bad?
cheers, Graham ve3gtc
time-nuts mailing list -- time-nuts@febo.com javascript:;
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
time-nuts mailing list -- time-nuts@febo.com javascript:;
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
time-nuts mailing list -- time-nuts@febo.com javascript:;
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
On 11/24/14, 2:20 AM, Graham wrote:
Interesting.
I have also been thinking that it might not be too difficult to
implement using Beaglebone Black, Raspberry PI, or even one or another
flavour of Arduino. Lots of possibilities from simple to not so simple.
The challenge is always trying to figure out what sort of protocol to
use for encapsulating serial data in the Ethernet Stream. Do you send
each character in its own UDP or TCP datagram? Do you batch them
together and send a message every TBD milliseconds.
Ideally, you'd like the protocol to match some commonly available client
on the other end. Sure, things like telnet exist, but does software
that expects an actual serial port know how to use telnet instead?
That said, there's plenty of example code out there for, example, the
Arduino Ethernet. There's a telnet server that could easily be modified.
I you are really really dead set on building your own there are lots of
chips available with varying levels of external parts needed.
An economical and versatile solution is to use one of the digi TS-One or
portserver TS terminal servers. They are a little pricey new, but, last time
I needed some there were several on the 'Bay. I bought 5 for $75 last time.
That was an incredible steal.
A few positives for using them:
- several of the models have jumper selection of rs232/rs422 so you don't
need an extrernal level converter. - They have excellent and currently maintained support software for past
and current OS's which among other things provides a 'virtual com
port' driver which makes the ports on the remote terminal server appear as
normal serial ports to the OS. - 2nd generation models provide the capability to use SSH and SSL to
encrypt control and data streams for security. - You don't need to do any development work to start using them. you can
start working on the more interesting aspects of your project instead of
reinventing the wheel for several hours while you figure out the arcana of
serial transmission. (been there, done that)
digi also makes board level product for integration in customer products,
but, I have not seen any for sale on the used market.
Netburner makes pretty economical board level stuff too. don't know if
they have any rs422/485 functionality.
I generally avoid using wifi for anything where failure/unreliability would
cost me time/money.
having said that there are also several wifi and bluetooth modules that
might serve your needs.
the bluetooth serial modules I bought from seeed studios were cheap and seem
to work well. they also have the advantage of maintained OS support of
'virtual com ports' so apps don't need any special knowledge of the serial
hardware.
Also, you shouldn't really need a fast ethernet port on the terminal
server. A fast ethernet switch when connected to a stone-age 'regular'
10Mbps port should (after failing auto-negotiation) fall back to 10Mbps half
duplex which is likely sufficient for a single or even several serial
streams.
Hope this is helpful to someone.
Dale NV8U
-----Original Message-----
From: Jim Lux
Sent: Monday, November 24, 2014 8:42 AM
To: time-nuts@febo.com
Subject: Re: [time-nuts] rs-422 rs-232 to fast ethernet converter
On 11/24/14, 2:20 AM, Graham wrote:
Interesting.
I have also been thinking that it might not be too difficult to
implement using Beaglebone Black, Raspberry PI, or even one or another
flavour of Arduino. Lots of possibilities from simple to not so simple.
The challenge is always trying to figure out what sort of protocol to
use for encapsulating serial data in the Ethernet Stream. Do you send
each character in its own UDP or TCP datagram? Do you batch them
together and send a message every TBD milliseconds.
Ideally, you'd like the protocol to match some commonly available client
on the other end. Sure, things like telnet exist, but does software
that expects an actual serial port know how to use telnet instead?
That said, there's plenty of example code out there for, example, the
Arduino Ethernet. There's a telnet server that could easily be modified.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
I have done a bit of searching and found that what I want to do is
nothing really new and their are several off the shelf applications
which will work just fine - linux and Windows based hence the mention of
the Raspberry PI and Beaglebone Black. Some of the higher end Arduinos
(i.e. Yu) are capable of running linux and Windows as well but it would
be entirely possible to roll you own using the lower end Arduinos as well.
I found some answers rather quickly after I started searching for the
right things, for example Serial to Network Proxy.
On Windows you could use a virtual serial port to do the redirecting
from com port to network and on linux there are several the one I found
often mentioned is socat.
The little serial to fast ethernet boxes which I was finding would work
in the situations where you don't have a computer near the device you
are trying to connect to, they act as the Serial to Network Proxy. In my
case, I have a computer nearby which runs linux and is my GPS
disciplined NTP server. I have purchased a RS422 to USB interface cable
which will connect the KS-24631 to my linux box. Now I just have to sort
through all of the information I have found and figure out just which
app I need on the linux box (likely socat) and which one on any of the
other computers on my network with which I may want to connect to the
KS-24631. And of course, how to configure them.
cheers, Graham ve3gtc
On 2014-11-24 08:42, Jim Lux wrote:
On 11/24/14, 2:20 AM, Graham wrote:
Interesting.
I have also been thinking that it might not be too difficult to
implement using Beaglebone Black, Raspberry PI, or even one or another
flavour of Arduino. Lots of possibilities from simple to not so simple.
The challenge is always trying to figure out what sort of protocol to
use for encapsulating serial data in the Ethernet Stream. Do you send
each character in its own UDP or TCP datagram? Do you batch them
together and send a message every TBD milliseconds.
Ideally, you'd like the protocol to match some commonly available
client on the other end. Sure, things like telnet exist, but does
software that expects an actual serial port know how to use telnet
instead?
That said, there's plenty of example code out there for, example, the
Arduino Ethernet. There's a telnet server that could easily be modified.
There is a protocol for ending serial commands over telnet (tcp): RFC2217
See http://tools.ietf.org/html/rfc2217
A number of command line tools, like ser2net and netcat use the protocol.
Some of the small serial servers support it and it can make using serial
remotely tunneled over tcp seamless.
On Mon, Nov 24, 2014 at 6:23 PM, Graham planophore@aei.ca wrote:
I have done a bit of searching and found that what I want to do is nothing
really new and their are several off the shelf applications which will work
just fine - linux and Windows based hence the mention of the Raspberry PI
and Beaglebone Black. Some of the higher end Arduinos (i.e. Yu) are capable
of running linux and Windows as well but it would be entirely possible to
roll you own using the lower end Arduinos as well.
I found some answers rather quickly after I started searching for the
right things, for example Serial to Network Proxy.
On Windows you could use a virtual serial port to do the redirecting from
com port to network and on linux there are several the one I found often
mentioned is socat.
The little serial to fast ethernet boxes which I was finding would work in
the situations where you don't have a computer near the device you are
trying to connect to, they act as the Serial to Network Proxy. In my case,
I have a computer nearby which runs linux and is my GPS disciplined NTP
server. I have purchased a RS422 to USB interface cable which will connect
the KS-24631 to my linux box. Now I just have to sort through all of the
information I have found and figure out just which app I need on the linux
box (likely socat) and which one on any of the other computers on my
network with which I may want to connect to the KS-24631. And of course,
how to configure them.
cheers, Graham ve3gtc
On 2014-11-24 08:42, Jim Lux wrote:
On 11/24/14, 2:20 AM, Graham wrote:
Interesting.
I have also been thinking that it might not be too difficult to
implement using Beaglebone Black, Raspberry PI, or even one or another
flavour of Arduino. Lots of possibilities from simple to not so simple.
The challenge is always trying to figure out what sort of protocol to use
for encapsulating serial data in the Ethernet Stream. Do you send each
character in its own UDP or TCP datagram? Do you batch them together and
send a message every TBD milliseconds.
Ideally, you'd like the protocol to match some commonly available client
on the other end. Sure, things like telnet exist, but does software that
expects an actual serial port know how to use telnet instead?
That said, there's plenty of example code out there for, example, the
Arduino Ethernet. There's a telnet server that could easily be modified.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/
mailman/listinfo/time-nuts
and follow the instructions there.
Ser2net is the way to go for me.
A hardware solution I have been using for this purpose for quite a while are those tiny USB-powered SoC-based "3G / 4G portable routers" from vendors like TP-Link (good little case designs - TL-MR3020 for instance which I currently use). The "3G" models don't actually have cellular modems, they just have a single USB port - and a Fast Ethernet port, and 802.11. They (can) run Linux.
The newer ones have 4M onboard flash and you can flash them instantly with OpenWRT. You can drop the web UI to trim down flash usage if you want, but out of the box they will fit USB-serial drivers and ser2net. Just add a USB to serial cable (or even go wild and buy a quad one with an USB hub built in) and you are still below the price of a Raspberry Pi, nevermind a dedicated serial to Ethernet box. You can also add a mini USB hub, stick a mini USB key in and use it as storage overlay. OpenWRT has all the tools you need available in the package repositories.
I paired mine with a 12Ah portable USB power bank, clipped on using 3M Command(tm) hook-and-loop straps. It ran on it for 48 hours straight. This setup has proven an invaluable tool in data centre work for emergencies and upgrades. I can hang it in a rack or keep it in my pocket, connect to kit using serial or Ethernet, and work from my smartphone over wifi. File transfers, firmware upgrades, whatever you want. Not sure if ser2net supports X/Zmodem somehow (it's probably down to the telnet client here) but for the times you need it, there's minicom. Naturally, USB-RSxxxx converters are not always the way to go, but the RPi needs one as well, it can only do TTL natively.
With some DYI you can put the router board, USB hub and battery in a neat little box as well and add an antenna, for improved usability.
Regards
Wojciech
Wojciech Owczarek
-----Original Message-----
From: Paul Alfille paul.alfille@gmail.com
Sender: "time-nuts" time-nuts-bounces@febo.comDate: Mon, 24 Nov 2014 22:38:04
To: Discussion of precise time and frequency measurementtime-nuts@febo.com
Reply-To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Subject: Re: [time-nuts] rs-422 rs-232 to fast ethernet converter
There is a protocol for ending serial commands over telnet (tcp): RFC2217
See http://tools.ietf.org/html/rfc2217
A number of command line tools, like ser2net and netcat use the protocol.
Some of the small serial servers support it and it can make using serial
remotely tunneled over tcp seamless.
On Mon, Nov 24, 2014 at 6:23 PM, Graham planophore@aei.ca wrote:
I have done a bit of searching and found that what I want to do is nothing
really new and their are several off the shelf applications which will work
just fine - linux and Windows based hence the mention of the Raspberry PI
and Beaglebone Black. Some of the higher end Arduinos (i.e. Yu) are capable
of running linux and Windows as well but it would be entirely possible to
roll you own using the lower end Arduinos as well.
I found some answers rather quickly after I started searching for the
right things, for example Serial to Network Proxy.
On Windows you could use a virtual serial port to do the redirecting from
com port to network and on linux there are several the one I found often
mentioned is socat.
The little serial to fast ethernet boxes which I was finding would work in
the situations where you don't have a computer near the device you are
trying to connect to, they act as the Serial to Network Proxy. In my case,
I have a computer nearby which runs linux and is my GPS disciplined NTP
server. I have purchased a RS422 to USB interface cable which will connect
the KS-24631 to my linux box. Now I just have to sort through all of the
information I have found and figure out just which app I need on the linux
box (likely socat) and which one on any of the other computers on my
network with which I may want to connect to the KS-24631. And of course,
how to configure them.
cheers, Graham ve3gtc
On 2014-11-24 08:42, Jim Lux wrote:
On 11/24/14, 2:20 AM, Graham wrote:
Interesting.
I have also been thinking that it might not be too difficult to
implement using Beaglebone Black, Raspberry PI, or even one or another
flavour of Arduino. Lots of possibilities from simple to not so simple.
The challenge is always trying to figure out what sort of protocol to use
for encapsulating serial data in the Ethernet Stream. Do you send each
character in its own UDP or TCP datagram? Do you batch them together and
send a message every TBD milliseconds.
Ideally, you'd like the protocol to match some commonly available client
on the other end. Sure, things like telnet exist, but does software that
expects an actual serial port know how to use telnet instead?
That said, there's plenty of example code out there for, example, the
Arduino Ethernet. There's a telnet server that could easily be modified.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/
mailman/listinfo/time-nuts
and follow the instructions there.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.