Well I've toasted my RTX4140 module while probing it to find out why it randomly reset. I'm giving up on this beast for my gateway and looking for suggestions as alternative.
General structure is going to be Moteino Mega (was Moteino R4) handling the Moteino wireless & gateway function end of things and I need a WiFi module with a TCP/IP stack that will support both TCP Client and TCP Server simultaneously. I'm not planning on providing an HTTP server at the gateway so this is not a requirement.
I'm looking at the RN-XV module. This seems like it should do the job, at an acceptable price, and from a reputable supplier (Microchip & Sparkfun for the XBee packaging). I don't necessarily need XBee package, I just want something pluggable so I can breadboard before making my next PCB... u.fl connector is preferred but RP-SMA would be usable.
Please let me know what experience you have with anything you propose. I can DAGS the module, I need real world experience...
Thanks in advance
Tom
I've always used an ethernet-wired Pi as a gateway and never had an issue.
I know there's the overhead of having a full OS running on it, imaging/reimaging/keeping it updated. I just really haven't found reasons to move away from it. This is just to say that the Pi works great for what I need it to (as a gateway from my Moteino network, and a server to the world to my automation stuff). So it's all contained in the Pi, very compact and nothing else needed. I looked up the RN-XV and the price is near that of a Pi, but maybe you have your own reasons why you'd want this instead of something like a Pi. So .. sorry but I am not able to suggest a better alternative.
Quote from: Felix on January 08, 2015, 03:31:03 PM
I've always used an ethernet-wired Pi as a gateway and never had an issue.
I know there's the overhead of having a full OS running on it, imaging/reimaging/keeping it updated. I just really haven't found reasons to move away from it. This is just to say that the Pi works great for what I need it to (as a gateway from my Moteino network, and a server to the world to my automation stuff). So it's all contained in the Pi, very compact and nothing else needed. I looked up the RN-XV and the price is near that of a Pi, but maybe you have your own reasons why you'd want this instead of something like a Pi. So .. sorry but I am not able to suggest a better alternative.
You're absolutely right about using the Pi if I was creating a wired gateway (best ethernet/usb/gpio bargain around!). In my case, however, of the 4 or so gateways that I'm implementing, only one is even within line of sight to a hot RJ45... I need wireless IP. The gateways, by the way, will be posting to a BBB home server running Ubuntu :D
Tom
I use a Pi with wireless dongle that was something like $2 in quantity. Based on the RTL8188 IIRC. Super-reliable. It used to drop out every few months until I set up a netconfig watchdog. Online 24/7 since. I don't even have access to my wired ethernet port in my enclosures ... http://www.cupidcontrols.com/2014/02/making-of-a-cupid/
Colin
Quote from: ColinR on January 08, 2015, 05:28:44 PM
I use a Pi with wireless dongle that was something like $2 in quantity. Based on the RTL8188 IIRC. Super-reliable. It used to drop out every few months until I set up a netconfig watchdog. Online 24/7 since. I don't even have access to my wired ethernet port in my enclosures ... http://www.cupidcontrols.com/2014/02/making-of-a-cupid/
Colin
Thanks. I did find some of these with RP-SMA connectors. While not as convenient as the u.fl, it would still be usable.
With this setup I could have distributed servers rather than simple gateways. Hmmmm, something to ponder over a Lagvulin or two tonight.
Thanks again,
Tom
BTW, was the watchdog an existing package or something you created? Recoverable dropouts I can deal with (if they don't occur too often). Hangs are totally unacceptable.
Quote from: TomWS on January 08, 2015, 06:16:42 PM
Thanks. I did find some of these with RP-SMA connectors. While not as convenient as the u.fl, it would still be usable.
With this setup I could have distributed servers rather than simple gateways. Hmmmm, something to ponder over a Lagvulin or two tonight.
Thanks again,
Tom
BTW, was the watchdog an existing package or something you created? Recoverable dropouts I can deal with (if they don't occur too often). Hangs are totally unacceptable.
Ah - skimmed over the connector requirement.
Watchdog was homebrew. It's in here: https://github.com/iinnovations/iicontrollibs/blob/master/cupid/systemstatus.py
Look for 'wpaconnected'. It parses wpa supplicant status. I also have it test WAN connection and latency, and it uses pyiface to parse configuration ... some other random stuff in there. Code could use a woman's touch, but what couldn't?
Assuming that I went with RPi as my Gateway/DistributedServer, I'd also want to use that as a locally located Arduino IDE for the atached Mote.
I did a bit of research on RPi and was surprised to find that it only had one serial port available on the GPIO connector. Since I'd need this for my Moteino/RPi gateway interface, I'm thinking that I should be able to use a USB Serial Cable (AKA FTDI cable) attached to one of RPi's USB connectors to talk to the Mote's debug/upload serial port (assuming I use a Mega with two ports).
Have you tried this (ie, running Arduino IDE & FTDI cable) from RPi?
Tom
I've not. I use my unimote sketch so just pass parameters to the gateway moteino and other motes by RF.
Using a USB adapter is quite popular for level reasons as well, and since the B+ has four USB it's less painful to give one up if you see fit. That said, why can't you use the one serial port for everything? You need more than one? I feel I'm missing something.
Quote from: ColinR on January 08, 2015, 10:13:22 PM
<...snip> That said, why can't you use the one serial port for everything? You need more than one? I feel I'm missing something.
The app I'd be debugging would be using the serial port for 'conversation' between to the gateway/server - don't want to mix the two, totally different content.
Tom
But there is no gateway server convo during programming. When I'm programming I pretend I'm the Pi. Same thing.
Quote from: ColinR on January 09, 2015, 12:46:39 AM
But there is no gateway server convo during programming. When I'm programming I pretend I'm the Pi. Same thing.
Aha, yes, you have a point. I'm still stuck on the totally separate processor paradigm. Hmmmm, more to think about. Perhaps another Lagvulin...
Tom
I cheers a Balvenie Doublewood to you, good sir.
I've definitely considered IDE through Pi before, but my overarching idea is to program, deploy, and then just set parameters where needed. The one place I'm really interested, though, is the remote reprogram of the gateway and remote sketches for 'firmware update', so I'm tuned in to the idea for sure.
Quote from: TomWS on January 09, 2015, 12:50:35 AM
Quote from: ColinR on January 09, 2015, 12:46:39 AM
But there is no gateway server convo during programming. When I'm programming I pretend I'm the Pi. Same thing.
Aha, yes, you have a point. I'm still stuck on the totally separate processor paradigm. Hmmmm, more to think about. Perhaps another Lagvulin...
Tom
<as he comes out of his Scotch induced fog, he says...>No! That's not the point! The point is to be able to simultaneously run the program AND use the
antiquated 'Classic' Arduino PRINT Trace debug technique that we used back in the 70s before In Circuit Debuggers were invented.
Additionally, while the notion of having distributed servers is esoterically appealing, having the gateway low enough power that I can keep it running for a day or so with LiPo backup should we lose power (ie, the wind is above 5MPH and it's been raining a bit) is more appealing.
Tom
Re reprogramming the gateway and the motes via the gateway is in the plan... that's a post for another day (gotta get the bloomin' gateway running first!).
I don't know if it helps, but I'm using the com0com driver + config util on Win7 driver and the ser2net daemon on my gateway VM on a linux virtualisation host (my home server + NAS). It's working fine for uploading sketches, terminal, etc., since the mentioned SW components fully implement the RFC 2217 / Telnet Com Port Control Option protocol. I believe the Linux daemon is available for the rPi too. The newest Windows com0com driver is not digitally signed for x64 so you need to use an older one. I have the relevant configs or binaries if anyone is interested. I see no reason why it woudn't work on the Mega.
Hi, Tom.
I'll confess to not reading this entire thread, but I'll toss out a suggestion for the path I'm currently on... Intel Edison.
At $50 a pop it's mildly more expensive than many add-on WiFi Arduino modules, but it comes with WiFi (up to 802.11n, I believe), Bluetooth, a fast processor, and loads of flash and RAM. My current thinking is to use it as the WiFi gateway device, or the main board in applications that require direct WiFi.
For serial-only, you could explore the low-cost ($4) ESP8266, which comes in many flavors but is not FCC certified, the supply chain is questionable (usually eBay), and it's still very much in the hacker / experimental space.
FWIW,
Richard
Quote from: Richard on January 25, 2015, 01:49:35 PM
Hi, Tom.
I'll confess to not reading this entire thread, but I'll toss out a suggestion for the path I'm currently on... Intel Edison.
At $50 a pop it's mildly more expensive than many add-on WiFi Arduino modules, but it comes with WiFi (up to 802.11n, I believe), Bluetooth, a fast processor, and loads of flash and RAM. My current thinking is to use it as the WiFi gateway device, or the main board in applications that require direct WiFi.
For serial-only, you could explore the low-cost ($4) ESP8266, which comes in many flavors but is not FCC certified, the supply chain is questionable (usually eBay), and it's still very much in the hacker / experimental space.
FWIW,
Richard
Richard, thanks for the suggestion. I've looked at the Edison and the cost was a real turnoff, not to mention the connectorization sucks IMO. Definitely not home fab friendly.
I've decided my next attempt will be the RN-XV module. I've had good results with Microchip products (I can not say the same for Intel Wireless products) and the price/feature/power mix meets my needs. I'll let you know how it works out.
Tom