For the weather buoy project we need a way to take data in over our Ministation’s serial port and push it upstream over the network. As the ministation is pretty limited in flash and ram, I assumed a compiled (as opposed to scripted) solution would be best.
I think my ideal system would be store-and-forward, with the serial port as a “push,” something along the lines of:
- Open the serial port.
- Read an buffer the data.
- When you have one “line” of data, try to poke it out over a network interface.
- If you succeed, forget that line of data.
- If you fail, save it to try next time. When you reach some maximum amount of backlog, start dropping the older messages.
Where the other end of the conversation would be a network-to-disk server:
- Open a network port
- As data comes in, write it to a file.
It sounds like a simple brief, but I couldn’t find a canned solution which does the job.
One obvious choice is ser2net, though it’s actually designed the other way around. As a “server,” it listens on a network connection (many, actually), opening serial ports as necessary when a connection comes in.
I’m a bit rusty on Linux network programming, so as an interim, I thought I’d try a serial-to-syslog gateway, operating as above but pushing data to syslog (who can then handle the network forwarding).
It’s not a terrible solution, with a couple of caveats:
- It only really works because our data is read-only, and it’s NMEA-like strings, so it’s ASCII, nicely delimited into lines. Syslog wouldn’t work with binary data, I don’t think.
- The Ministation SDK runs busybox’s syslogd, which only supports UDP forwarding, not TCP. OK, so it would only provide one additional ACK of security, not true store and forward, but it’s would be a start.
On the other end of the connection, I’ll have a full-fat computer running rsyslogd which can handle a bit of store and forward to servers off in the cloud.
In any case, I wrote a ser2syslog. I won’t pretend it’s polished, but works for me. As per the README, I was originally going to build it from the framework of ser2net, but given ser2net is a mature, featureful product, and arranged backwards (as above), I stripped 95% of the ser2net code out. I believe (hope!) the copyright and attribution are correct.
Next up is testing it on a Ministation.
Hm. I just realized I could do the same thing very simply on the command line. Something like:
$ cat /dev/ttyS0 | logger -p local7.info -t “/dev/ttyS0”
And I could probably achieve what I need network-wise with netcat. Sigh….