@MK thanks, yes I saw your time clock gizmo, nice piece of kit. Congratulations. @Lazar-Demin The reason why I think a PoE version would be useful is as @MK mentioned, getting power to devices is often a pain, I think especially in a development of IoT devices I want to test devices in various locations and honestly I prefer to cable my stuff for reliability as WiFi is not often reliable in some locations. Especially when I'm fixing things to walls or up in the ceiling of a building where cables, metal and fluorescent lights may be found. Getting an ethernet cable to some of these locations can be a challenge, but getting power there as well can get really complicated and expensive. I also think a solid reference implementation for use with Omega2S+ would be a bonus, or even better with the Omega3S+

@francisco-vieira I agree with @crispyoz, this sounds like a handshaking issue - my guess is in hardware. To check on this, you can use the devmem command to read the UART0 status registers. I would start with the Line Status and Modem Status registers. See the MT7688 datasheet for more info on the registers, and run devmem --help on the command line to see how to read the registers.

Posting an update on this topic received on our helpdesk: After a lot of investigation, we already identify and solve the problem. The problem was on a cable inside our Gateway that induces electromagnetic signals on the Onion Omega 2+ when the GPRS is in use. We already protect the Onion Omega 2+ from electromagnetic signals and right now we are confident that it is solved.

@crispyoz thank you so much for your suggestion. I think we will follow your suggestion and add some logic on our service to guarantee all the required resources/services are up before we start our service. Thank you so much my friend.

Ohh I see. Thank you for the clarification. It's just sort of distracting after I've already acknowledged it and went through the process.

You wrote: Omega2+, probably 0.1.10 b160 ... [ 28.551976] device eth0.1 entered promiscuous mode [ 28.556855] device eth0 entered promiscuous mode [ 28.588837] br-wlan: port 1(eth0.1) entered forwarding state [ 28.594681] br-wlan: port 1(eth0.1) entered forwarding state [ 30.588807] br-wlan: port 1(eth0.1) entered forwarding state [ 32.028929] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944 [ 32.028929] [ 32.042988] Rebooting in 3 seconds.. I wrote in Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ... and a possible reason on 2017-02-05: Omega2+, 0.1.9 b150 (from 0.1.5 b130 to 0.1.9 b150 several FirmWares), without dock / with Arduino Dock 2 ... [ 20.900878] device eth0.1 entered promiscuous mode [ 20.905758] device eth0 entered promiscuous mode [ 20.940478] br-wlan: port 1(eth0.1) entered forwarding state [ 20.946310] br-wlan: port 1(eth0.1) entered forwarding state [ 22.939289] br-wlan: port 1(eth0.1) entered forwarding state [ 24.809528] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944 [ 24.809528] [ 24.823293] Rebooting in 3 seconds.. This Kernel panic is a known bug of the closed source MediaTek WiFi driver. Now we know it can not manage if there is a WiFi AP in the neighborhood with some Unicode character in its SSID. Onion @administrators deeply kept silent about this bug. It seems Onion's new WARP CORE driver (also closed source ???) can manage this situation. Unfortunately Onion @administrators do not say too much about this bug feature (as usual ;-). Since you did not mount the microSD card it is absolutely invisible for the bootloader (Das U-Boot). @Denys-Makogon said in [SOLVED] Kernel corrupted after factory reset: @György-Farkas kernel was corrupted for sure, that's something I can tell you with honesty. The device was literally dead, only after inserting a microSD card with a new firmware my device was able to update itself and become functional. Well... no one but you should know if this correct (or not

https://community.onion.io/topic/1883/use-the-yellow-blinking-led-to-help-troubleshooting

@davidsi there are variety of ways to check whether you are connected or not, please refer to our solutions of our helpdesk. Also, keep in mind that Omega2 supports only 2.4GHz with AES or mixed mode AES+TKIP. Please take a look at the the post on the Onion Community for an interim, manual fix.

awesome project. I have a similar journey ahead of me. got the max232 chip setup . but needing the proper ncurses term library to work Any clue on getting other terminals to work with it or profiles or is it all strictly vt100 compatibles I require the hz1552 variant (interfacing a Hazeltine Esprit )

@Leif-Bloomquist thanks for the project write-up. it looks very simple yet effective. i also have a leap motion device and would love to put it to use as it has been in a box for over a year now. looking to read the code you have this weekend. good luck on continuing with the vehicle. looks fun. may have to do something similar with a omega on a arduino dock.