VVinny
- 16 Jan
- Joined Sep 24, 2023
- 0 best answers
- Edited
Mike v1.12, from my understanding that is the only firmware available. Am I right?
I am attempting to follow the instructions here: https://docs-beta.luxonis.com/hardware/rae/get-started/?v=Advanced+%28manual%29
I cannot ping external internet (8.8.8.8) unless I perform these actions in a particular order, and I have yet to figure out how to do so. I have already factory reset the device once.
Sometimes when I run the wpa_supplicant command I get this
root@keembay:~# wpa_supplicant -B -i wlp1s0 -c /etc/wpa_supplicant.conf Successfully initialized wpa_supplicant nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: kernel reports: Match already configured nl80211: Could not set interface 'p2p-dev-wlp1s0' UP nl80211: deinit ifname=p2p-dev-wlp1s0 disabled_11b_rates=0 p2p-dev-wlp1s0: Failed to initialize driver interface P2P: Failed to enable P2P Device interface
Also, I believe I am missing how to have these settings persist after rebooting.
Hi,
When I use
robohub-ctl stop
on the RAE (through SSH over my home wifi), as suggested in the ROS2 tutorial, the device becomes unresponsive and requires a power reset.https://github.com/luxonis/rae-ros/tree/humble
Is there anything I can do to prevent this behavior, or is this expected?