Nanostation Serial Port
Serial Port Wiki
Hi, I am interested in the Nanostation 2 and NS2 Loco, and would like to use it`s serial port to read in data from a weather station connected to it, disabling the default kernel console (possible, disabling the kernel config option?) and the listening shell (spawned by init?). The software listener/transmitter might be a cross-compiled binary, or even a simple shell or PHP script. I`ll see what`s best. However, I`m not sure if I inderstand the wiki entry right. Do I need the TTL converter even if I would like to connect other RS232 devices (weather station, Palm, PC serial port), or only when using a RS232-USB converter cable? If needed, what TTL converter is advicable to use, in order to avoid the described hang on bootup?
That would be inacceptable for such an application. If, as I read in another topic, a MAX232 has to be used, has anyone a wiring diagram for this use? In the NS2 and Loco cases, is there any space left to put a 2.5mm stereo jack under the cable cover (carrying the RS232 port out of the inner case)? I suppose however that disabling the console will render the unit unusable when something`s messed up, right? Does anyone have experience using such serial applications? Other uses could be a Palm device (to see console output in the field), reading other external sensors and transmitting the data, or listening to and transmitting GPS NMEA sentences in mobile use.
With some hacking, the Nanostation could be converted in a a real killer appliance. THX & regards, Hans. Hans, you're not the first to have this concept of re-creating a NanoStation as a data access device. But I haven't seen any success stories yet. Let me at least explain about the data connection.
A NanoStation doesn't have a 'true' RS-232 port; that requires a bi-polar (+/-) voltage on the pins for both input and output. Instead, it has a TTL (unipolar 0 to 5v) port with the same data signals as an RS-232 port. The article you cite describes how to connect a USB to TTL serial data converter to the NanoStation. This is merely connecting the proper pins. Only data in and out are used-none of the other control/status pins. This approach requires a PC or other USB host device and a driver. That 'other' topic you found shows a MAX232 device which converts TTL signals to RS-232 signals, using level converters and generating the proper bipolar voltage internally.
That would be used if you choose to connect a NanoStation to a standard RS-232 serial port. You can buy such devices ready-made. I'm sure you could add a 3-circuit connector to the NS case; that would end the warranty. That sequence issue that may hang up the NS isn't well defined.
Ubiquiti mPort-S อุปกรณ์เชื่อมต่อกับ mFi Sensor เป็นเครือข่าย TCP/IP กับ Serial Port. How to recover a Bricked Ubiquiti NanoStation2. Preparing the serial connection. Identifying the com port on both windows and linix is rather.
Ubiquiti Nanostation M5
I can't help you with that. I hope this is some help. Hi Dave, Hans, you're not the first to have this concept of re-creating a NanoStation as a data access device. But I haven't seen any success stories yet. Let me at least explain about the data connection. A NanoStation doesn't have 'true' RS-232 port; that requires a bi-polar (+/-) voltage on the pins for both input and output. Instead, it has a TTL (unipolar 0 to 5v) port with the same data signals as an RS-232 port.
Nanostation Loco M5 Firmware
The article you cite describes how to connect a USB to TTL serial data converter to the NanoStation. This is merely connecting the proper pins. Only data in and out are used-none of the other control/status pins. This approach requires a PC or other USB host device and a driver. That 'other' topic you found shows a MAX232 device which converts TTL signals to RS-232 signals, using level converters and generating the proper bipolar voltage internally. That would be used if you choose to connect a NanoStation to a standard RS-232 serial port.
You can buy such devices ready-made. Good explanation, thank you! So I need that TTL converter. I found them already ready made (the hardest thing figuring out the right term in german). As there are SMD versions, there should be enough space to implement a RS232/TTL converter (without the SUB-D connector, a stereo headphone jack should be better suited). Now that I understand what it does, I remember that the serial cable for my old cell phone did right the same thing - I ran into a similar problem when trying to connect a Palm to the cell phone over a decade ago.
I should have this cable still lying around somewhere, it might be even glad to get a new job. Hint @ UBNT: A NS2 with a converter known not to cause the the unit to hang and a jack could be a nice 'Happy Hacker Special Edition' I'm sure you could add a 3-circuit connector to the NS case; that would end the warranty. That sequence issue that may hang up the NS isn't well defined.
I can't help you with that. That could definitely be a problem. Some googling brought up that the NS isn`t the only device showing this behavior, some other Atheros based units seem to do the same thing. Would be interesting to see what the Redboot guys think about that - if it`s a software or hardware bug, or even a feature. Voiding the warranty shouldn`t be a problem, as a properly installed jack with 3 cables routed to the serial port shouldn`t interfere with the main PCB at all. Then, the NS2 isn`t that expensive, a nice hack could be worth the risk.
However, as I will have to wait some time before building this WLAN and buying the NSwhatever and choose a weather station, in the meantime I will see if I get a used guinea-fonera pig off ebay for testing I hope this is some help. Dave It definitely is - thank you! Best regards from Germany, Hans. Hi Dave, mine is a serial cable, so no driver should be needed, just a terminal emulator. However, I suppose it won`t probably be suitable to connect to any other device than a computer (I think it is getting it`s power fed by the PC serial port). Regarding USB adapters, probably a cable with a Prolific chipset will be a good choice, as it is supported by most Linux distributions out of the box and AFAIK by Win XP as well, so no additional driver is needed (at least from a user`s point of view).
I think I`ll get a used Fonera (about €12 here, who cares if bricked.) for testing and a TTL 3.3V converter, to get it fed by the Fonera itself. Then I`ll try to read in some data (GPS maybe) and ftp it to another location, a simple shell script should do the basic job. Other serial devices may get more complicated, as weather stations for example love to get queried before sending any data, so maybe a driver has to be cross-compiled. In the meantime I hope to have 2 NS2 running my future WLAN bridge (no access to location yet). Regards, Hans.
I've read some post about existing serial port inside the NS2 and certainly others as well. According to other forums and CPE, it could be possible to re-flash the firmware, including the boot-loader, using the serial port (JTAG). Anyone have any info on how to do this on a NS2 on which the LAN is not coming up anymore? I'm sure that would help lots of others in my situation that ended up with a dead NS2 due to a flash problem. What i need is the serial cable configuration, hopefully to a USB/Serial adapter.
And a procedure on how to reload the firmware. Hopefully a proper firmware, but that I assume it can be downloaded from another NS2 or from the OSWAVE website. Any help on this would be appreciated and I'm sure that lot more consumer will feel safer knowing that a solution is available to recover those 'dead' units.
Thanks Andre.