I just got my rae. Tried to set it up with RobotHub according to instructions (QR code): QR code is received, display states "connecting to <my SSID>", device flashes first blue, then red, then turns white - but no connection to my WLAN (device doesn't show up in my WLAN or RobotHub). Tried to set it up manually according to instructions: SSID & password were obviously correctly received, because the correct information is in /etc/wpasupplicant.conf. BTW, there is an error in the instructions, the quotation marks in the example for the passPHRASE are wrong, use only if you use the passWORD. /etc/systemd/network/20-wifi.network has the right content, too. Stopping hostapd was never needed, it is always dead after startup. When trying to connect to my WLAN with wpasupplicant b -i wlp1s0 (…) i start getting lots of error messages - from missing or invalided devices, to already running (or hanging) instances… Error messages seem to depend a bit on the time of day and what I tried before - I can provide them, if there is anyone who can help me. This seems to be the root cause of the issue, because I don't get beyond that step in the manual setup and I guess the "QR code method" is trying to do pretty much the same in the background. I do get wlp1s0 shown in the device list for ifconfig & Co.), but obviously never with a connection to my WLAN. When trying to scan for WLANs with wpa_cli, I don't get any output (and there are plenty of WLANs around), which strikes me as weird, because that should IMO work, even without any WLAN connection. So maybe THIS is the root cause and something is wrong with the WLAN adapter? Last observation, not sure if this might be related: My device gets VERY hot. You need to be quick when picking it up for shutting it down…! I don't think, that it should be that hot. After some time, I started to get kicked out of the ssh session too, so I suspect a bit, the device might freeze/lock-up due to overheating. The display is strange, too: It starts up fine (backlit -> "rae" -> small robot on white background -> "Register…" on white background, but then the display starts to "flicker", constantly changing ist brightness until it's gone. Looks a bit like a "fade out" effect with 0.5 Hz … I doubt very much, that this is as it should be, too. Any ideas, tips or recommendations? Some more info I shall provide? I have no previous experience with Archlinux, but I am otherwise fairly proficient on Linux (Ubuntu/Debian), so fire away! With respect to temperature and display: Might I simply have a HW defect?

DiMa … I can confirm that my Rae gets slightly warm after an hours use and charging but definitely not hot. I suspect a H/W fault ... my Rae's display is constant, no fading etc. Have you tried a hard reset with the reset button and then updating to FW v1.13 (using the USB cable connection) ?

Definetly more than "slightly warm"… 😉 No, I did not try a "hard reset" - how do I do that? And how do I install new FW (and where do I get it) - I guess that's somewhere in the Wiki, but I did not yet stumble upon it… EDITH: Found it - just in case I am not the only one looking in different places… Instructions are here .

DiMa … v1.13 is here https://luxonisos.fra1.digitaloceanspaces.com/index.html?prefix=build/

There are two versions, which one should I pick - the newer one (from October, 2nd)? How does the installation work, when I have no internet connection, i.e. have to scp the files onto the rae? I did find instructions for pulling the FW via mender only.

Got one step further after hard resetting: QR scan method etc. works, I triple checked that. I now get a proper "Couldn't connect" message with the red blinking, too. With the "fresh" device, I can now see all my local WLAN APs, too, so the WLAN interface does seem to work, too: wpa_cli v2.9 Copyright (c) 2004-2019, Jouni Malinen <j@w1.fi> and contributors This software may be distributed under the terms of the BSD license. See README for more details. Selected interface 'p2p-dev-wlp1s0' Interactive mode <3>CTRL-EVENT-SCAN-RESULTS scan_results > bssid / frequency / signal level / flags / ssid 82:a7:41:ec:80:f1 5220 -41 [WPA2-PSK-CCMP][ESS] lannisport_iot 76:a7:41:ec:80:f1 5220 -77 [WPA2-PSK-CCMP][ESS] lannisport 7e:a7:41:ec:80:f1 5220 -77 [WPA2-PSK-CCMP][ESS] lannisport_restricted 7e:a7:41:ec:80:f0 2462 -83 [WPA2-PSK-CCMP][ESS] lannisport_iot 7a:a7:41:ec:80:f0 2462 -44 [WPA2-PSK-CCMP][ESS] lannisport_restricted 7a:a7:41:ec:80:f1 5220 -77 [ESS] eighteenguests 76:a7:41:ec:80:f0 2462 -43 [ESS] eighteenguests 86:a7:41:ec:80:f0 2462 -83 [WPA2-PSK-CCMP][ESS] 70:a7:41:ec:80:f0 2462 -44 [WPA2-PSK-CCMP][ESS] lannisport 82:a7:41:ec:80:f0 2462 -83 [WPA2-PSK-CCMP][ESS] ea:63:da:a4:f3:fb 2462 -79 [WPA2-PSK-CCMP][ESS] lannisport_restricted ee:63:da:a4:f3:fb 2462 -80 [WPA2-PSK-CCMP][ESS] lannisport_iot e0:63:da:a4:f3:fb 2462 -82 [WPA2-PSK-CCMP][ESS] lannisport e6:63:da:a4:f3:fb 2462 -79 [ESS] eighteenguests I have three APs, all providing the same four SSIDs (lannisport_iot, lannisport:restricted, lannisport, and eighteenguests). Could this be the issue, that the rae doesn't support any roaming or fails to connect to an SSID, when multiple APs are available to connect to it? It seems to "see" the nearest AP with both 2.4 & 5 GHz bands plus one other with 2.4 GHz only. According to the documentation , wpa_supplicant should support roaming, though.

Hah! Found it! hostapd is blocking wlp1s0! After stopping the service, the link to my WLAN comes up. This is reproducible, since hostapd is running after each reboot… I am not too familiar with systemd and not at all with hostapd: Quick hint or pointer on how to disable the automatic start on reboot? @Mike Do you have any hint which 1.13 to pick? Running on 1.12. And which URL do I need to provide to mender: To the directory, to the *.mender file…(I guess: the latter)? Sorry if these are stupid questions, but "mender -install <link_to_firmware>" isn't that conclusive with respect to what the link should point to 😉 BTW: I just measured the surface tempratire (just on the top of the rae): 54°C after ca. 30-45min fighting with the WLAN config, see above. Doesn't sound right to me. I am now starting to get kicked out of the ssh session again and can't reconnect… root@keembay:~# wpa_supplicant -i wlp1s0 -c /etc/wpa_supplicant.conf -B Successfully initialized wpa_supplicant root@keembay:~# client_loop: send disconnect: Connection reset Shutdown via double click stopped working, too, only hard shutdown will work then.

DiMa … Good to hear you are connected … 54degC is hot … something is wrong … I'd reach out to support. See here for the firmware upgrade entry … https://discuss.luxonis.com/d/2328-newbee-quick-starter-to-get-code/5

Don't get further, the device is mostly dead. When starting up, I got the logo and then the LEDs where "blinking" white, but not in a good way. Looked more like something was wrong with the process controlling the RGB-LEDs. Devices doesn't react to power button at all - neither double-click, nor pressing 8s (or longer). Had to wait until the battery died… Sent a mail to support, let's see how they react. So far, rae is a very frustrating experience…

Hi DiMa Very likely it's a hardware issue. Thanks for emailing support and sorry for the inconvenience. Regards, Jaka

I can confirm the RAE becomes hot while running the ROS stack. It's "slightly warm" only in idle mode.

No chance in getting a WLAN connection & device gets VERY hot

jakaskerl

Hi DiMa
This looks like the device's system clock is incorrect, leading it to believe that the certificate is not yet valid.
Re-setting the internal clock should fix the error.

Thanks,
Jaka

DiMa

And that is done how? And do I need to do this after each reboot manually, like the systemd stuff? Maybe it's even documented somewhere, and I missed it?

Any thoughts about the systemd nightmares I am having? I mean, can't be that I have to restart systemd-networkd after each reboot, right?

jakaskerl

Hi DiMa
sudo timedatectl set-ntp true will enable NTP which should persist between reboots.

Thanks

DiMa

OK, that did the trick, although I don't fully understand why. After activating ntp, rebooting, restarting systemd-networkd the conenction via QR code did work. Now this is persistent - I shudtown/restarted multiple times, and the rae comes up fine, connects to the WLAN etc.

What I did ultimately need to do to make this happen:

disable hostapd
enable ntp
reboot
restart systemd-networkd
run QR-code setup from RH

So I can now start experimenting - but I still have no clue, why this worked in the end. Getting rid of the certificate issue via setting the correct time I dig, but why this addressed the "rae does not connect to WLAN issue"???

Video streams work, remote control work, so for the moment I am happy 😀 No more experiments today, can only get worse 😉 Thanks @jakaskerl , I hope at least the basics are now sorted out. I'd still be curious what exactly happend…!

« Previous Page