Sounds good, thanks!
S
Posts made by scottesicdrone
-
RE: LTE Modem "Feather is Disabled"posted in Cellular Modems
Love the Lore and good thing to note! Last last thing, here is the link to an instance of me running
dmesgif that's of any use.
output here
I'm going to keep trying to figure this out because this is a time-sensitive situation but if we will know for sure if it's a hardware issue once we get another modem to test it on. Thanks for the help thus far! Anything else I should try on here? -
RE: LTE Modem "Feather is Disabled"posted in Cellular Modems
This makes a lot of sense. I have seen this working before but now it just says feather is DISABLED until it power cycles and repeats. So if I understand correctly, after a few seconds,
/dev/ttyUSB0will be created and then the feather is enabled? Also random question: what is a feather exactly? I haven't heard of this before and I tried to look into it but I'm still confused! -
RE: LTE Modem "Feather is Disabled"posted in Cellular Modems
Here is what I get when I run
voxl-version:yocto:/# voxl-version -------------------------------------------------------------------------------- system-image: ModalAI 3.1.0 BUILDER: ekatzfey BUILD_TIME: 2020-12-23_19:41 kernel: #1 SMP PREEMPT Wed Dec 23 19:50:23 UTC 2020 3.18.71-perf factory-bundle: 1.0.1 (Yocto installation) -------------------------------------------------------------------------------- architecture: aarch64 processor: apq8096 os: GNU/Linux -------------------------------------------------------------------------------- voxl-suite: Package: voxl-suite Version: 0.3.4 Depends: voxl-utils (>= 0.6.0), libmodal_json (>= 0.3.4), libmodal_pipe (>= 1.7.8), librc_math (>= 1.1.4), libvoxl_io (>= 0.5.4), mavlink-camera-manager (>= 0.0.1), opencv (>= 4.5.1), openmp (>= 10.0.1), voxl-camera-server (>= 0.5.6), voxl-dfs-server (>= 0.0.7), voxl-docker-support (>= 1.1.1), voxl-gphoto2 (>= 0.0.5), voxl-hal3-tof-cam-ros (>= 0.0.5), voxl-imu-server (>= 0.7.8), voxl-modem (>= 0.11.0), voxl-mpa-tflite-server (>= 0.0.2), voxl-mpa-tools (>= 0.1.6), voxl-nodes (>= 0.1.3), voxl-qvio-server (>= 0.2.1), voxl-rtsp (>= 1.0.3), voxl-streamer (>= 0.2.1), voxl-vision-px4 (>= 0.8.1), voxl-vpn (>= 0.0.3) Status: unknown ok not-installed Section: base Architecture: all Maintainer: james@modalai.com MD5Sum: e1e5bf1a125affe5036099f6ce895bed Size: 1818 Filename: voxl-suite_0.3.4.ipk Description: meta-package for voxl-suite stable release Package: voxl-suite Version: 0.2.0 Depends: docker, imu_app (= 0.0.6), libvoxl_io (= 0.5.2), voxl-cam-manager (= 0.2.2), voxl-docker-support (= 1.1.1), voxl-hal3-tof-cam-ros (= 0.0.2), voxl-modem (= 0.10.0), voxl-nodes (= 0.0.8), voxl-rtsp (= 1.0.2), voxl-utils (= 0.5.2), voxl-vision-px4 (= 0.6.8), voxl_imu (= 0.0.4), voxl-time-sync (= 0.0.1), voxl-vpn (= 0.0.2), librc_math (= 1.1.2), libmodal_pipe (= 1.2.2), modalai-vl (= 0.1.3) Status: install user installed Section: base Architecture: armv7a Maintainer: james@modalai.com MD5Sum: af706cd3c1ea59f274f2ed9b93141f1d Size: 870 Filename: voxl-suite_0.2.0.ipk Description: meta-package to install all of the voxl-suite Installed-Time: 689 -------------------------------------------------------------------------------- -
RE: LTE Modem "Feather is Disabled"posted in Cellular Modems
Nothing physically changed that I can recall, and unfortunately, we don't have extra modems though we ordered more modems. Last potential useful bit of info: when I ran dmesg, I saw errors relating to qmi pop up but I don't know what to make of them:
yocto:/# dmesg | grep "qmi" [ 1.186410] usbcore: registered new interface driver qmi_wwan [ 1.187419] msm_sharedmem: sharedmem_register_qmi: qmi init successful [ 5.741357] sysmon_send_event_no_qmi: Message sending failed -19 [ 5.890086] type=1130 audit(7.556:61): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0-s15:c0.c1023 msg='unit=qmi_shutdown_modemd comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.903844] sysmon_send_event_no_qmi: Message sending failed -19 [ 5.903850] sysmon_send_event_no_qmi: Message sending failed -19 [ 5.908564] sysmon-qmi: sysmon_clnt_svc_arrive: Connection established between QMI handle and slpi's SSCTL service [ 5.914578] sysmon_send_event_no_qmi: Message sending failed -19 [ 6.039513] sysmon-qmi: sysmon_clnt_svc_arrive: Connection established between QMI handle and adsp's SSCTL service [ 6.523379] sysmon-qmi: sysmon_clnt_svc_arrive: Connection established between QMI handle and modem's SSCTL service [ 6.543970] msm_slim_qmi_send_power_request: QMI request failed 0x1 (Unknown error) [ 7.045169] msm_slim_qmi_send_power_request: QMI request failed 0x1 (Unknown error) [ 7.546548] msm_slim_qmi_send_power_request: QMI request failed 0x1 (Unknown error) [ 8.049225] msm_slim_qmi_send_power_request: QMI request failed 0x1 (Unknown error) -
RE: LTE Modem "Feather is Disabled"posted in Cellular Modems
Thanks, Tom, for the help! I really appreciate it! Is it possible that the serial port and the ports got renamed from
/dev/ttyACM0and/dev/ttyUSB0? I'm not too familiar with how these devices are generated or normal behavior for these devices. We have also noticed that this happened on two different VOXLs with the same v1 modem, so this problem seems to be with the modem and not the VOXL (though this is not something I am 100% certain about). -
RE: LTE Modem "Feather is Disabled"posted in Cellular Modems
I disabled the service and ran
voxl-modem --feather_configureand got this:Configuring GPIO pins Setting defaults: GPIO_PIN_WWAN_WAKEUP_IN = 1 GPIO_PIN_WWAN_POWER_ON_N = 1 GPIO_PIN_WWAN_RESET_N = 1 feather is DISABLED ENABLE WNC feather module feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED WARNING: feather state transtion failed. enable failed, try again 0 retries remaining ENABLE WNC feather module feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED WARNING: feather state transtion failed. enable failed, try again 1 retries remaining ENABLE WNC feather module feather is DISABLED feather is DISABLEDAnd this will keep going if I let it, I'm pretty sure. In the
/devfolder,/dev/qcqmi0exists but/dev/ttyUSB0doesn't exist. -
RE: LTE Modem "Feather is Disabled"posted in Cellular Modems
Here is my
voxl-modem.conffile:{ "modem_type": "v1", "apn": "broadband", "world": "false", "microhard_ip": "192.168.168.100", "modallink": "false", "placeholder": "hello world" }I'm watching the service right now and here is where it is at currently
● voxl-modem.service - Modem Initialization Loaded: loaded (/etc/systemd/system/voxl-modem.service; enabled; vendor preset: enabled) Active: active (running) since Thu 1970-01-01 00:01:23 UTC; 51 years 3 months ago Process: 2129 ExecStartPre=/bin/sleep 2 (code=exited, status=0/SUCCESS) Main PID: 2853 (voxl-modem-star) CGroup: /system.slice/voxl-modem.service ├─2853 /bin/bash /usr/bin/voxl-modem-start.sh └─3364 /usr/bin/python /usr/bin/voxl-modem --connect_to_network Apr 02 17:13:49 apq8096 voxl-modem-start.sh[2853]: Setting network preference to LTE Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: Failed to open device Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: Finished setting network preference Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: Disabling band 5... Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: configband starting Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: Band mask 1 to 32: 0x0000080a 0x0a 0x08 0x00 0x00 Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: Band mask 33 to 64: 0x00000000 0x00 0x00 0x00 0x00 Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: Band mask 65 to 96: 0x00000000 0x00 0x00 0x00 0x00 Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: Error opening /dev/ttyUSB0: No such file or directory Apr 02 17:13:59 apq8096 voxl-modem-start.sh[2853]: Initalizing cellular connection... -
RE: LTE Modem "Feather is Disabled"posted in Cellular Modems
Thanks for the quick response! We are using a v1 modem.
We ranvoxl-configure-modempreviously so that definitely could be the case. Here is the output forsystemctl status -l voxl-modem:yocto:/# systemctl status -l voxl-modem ● voxl-modem.service - Modem Initialization Loaded: loaded (/etc/systemd/system/voxl-modem.service; enabled; vendor preset: enabled) Active: active (running) since Thu 1970-01-01 00:00:08 UTC; 51 years 3 months ago Process: 2041 ExecStartPre=/bin/sleep 2 (code=exited, status=0/SUCCESS) Main PID: 2824 (voxl-modem-star) CGroup: /system.slice/voxl-modem.service ├─2824 /bin/bash /usr/bin/voxl-modem-start.sh └─2907 /usr/bin/python /usr/bin/voxl-modem --feather_configure Jan 01 00:00:06 apq8096 systemd[1]: Starting Modem Initialization... Jan 01 00:00:08 apq8096 systemd[1]: Started Modem Initialization. Jan 01 00:00:09 apq8096 voxl-modem-start.sh[2824]: Initializing v1 modem...Should I disable this service and try configuring and connecting?
-
LTE Modem "Feather is Disabled"posted in Cellular Modems
Hi Guys,
I was working on setting up the LTE modem add-on with the VOXL. I configured the modem properly and even connected to our VPN, and used QGC on the VPN server. However, when I rebooted the VOXL and went through the process of connecting the modem usingvoxl-modem --connect_to_network, I wasn't able to connect and got this as output:Configuring GPIO pins Setting defaults: GPIO_PIN_WWAN_WAKEUP_IN = 1 GPIO_PIN_WWAN_POWER_ON_N = 1 GPIO_PIN_WWAN_RESET_N = 1 feather is DISABLED ENABLE WNC feather module feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED WARNING: feather state transtion failed. enable failed, try again 0 retries remaining ENABLE WNC feather module feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED WARNING: feather state transtion failed. enable failed, try again 1 retries remaining ENABLE WNC feather module feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLED feather is DISABLEDI know people previously have had this issue and the solution was that they improperly answered the
voxl-configure-modemprompts. But I'm almost certain that this isn't the case because I was able to connect with no problems previously with no issues. What seems to be the problem from my view is that the devices/dev/ttyUSB0and/dev/ttyACM0, which are supposedly the serial port and AT command port respectively, do not exist! I'm not sure if this is normal or if they are suppose to generate, but they do not show up whenls -la /devis run:total 4 drwxr-xr-x. 16 root root 5660 Jan 1 1970 . drwxr-xr-x. 29 root root 4096 Jan 1 1970 .. crw-rw-rw-. 1 root root 224, 0 Jan 1 1970 adsprpc-smd crw-------. 1 root root 10, 37 Jan 1 1970 android_mbim crw-------. 1 root root 10, 28 Jan 1 1970 android_rndis_qc crw-------. 1 root root 244, 3 Jan 1 1970 apr_apps2 crw-------. 1 root root 10, 53 Jan 1 1970 ashmem crw-------. 1 root root 248, 0 Jan 1 1970 at_mdm0 crw-------. 1 root root 234, 0 Jan 1 1970 at_usb0 crw-------. 1 root root 234, 1 Jan 1 1970 at_usb1 crw-------. 1 root root 228, 0 Jan 1 1970 avtimer crw-------. 1 root root 10, 56 Jan 1 1970 binder drwxr-xr-x. 3 root root 1680 Jan 1 1970 block drwxr-xr-x. 2 root root 220 Jan 1 1970 bsg drwxr-xr-x. 3 root root 60 Jan 1 1970 bus crw-------. 1 root root 10, 30 Jan 1 1970 ccid_bulk crw-------. 1 root root 10, 31 Jan 1 1970 ccid_ctrl drwxr-xr-x. 2 root root 4020 Jan 1 1970 char crw-------. 1 root root 5, 1 Jan 1 1970 console crw-------. 1 root root 10, 49 Jan 1 1970 coresight-stm crw-------. 1 root root 10, 50 Jan 1 1970 coresight-tmc-etf crw-------. 1 root root 10, 51 Jan 1 1970 coresight-tmc-etr crw-------. 1 root root 227, 0 Jan 1 1970 coresight-tmc-etr-stream crw-------. 1 root root 10, 43 Jan 1 1970 cpu_dma_latency crw-rw----. 1 root diag 243, 0 Jan 1 1970 diag drwxr-xr-x. 8 root root 160 Jan 1 1970 disk crw-------. 1 root root 10, 32 Jan 1 1970 dpl_ctrl lrwxrwxrwx. 1 root root 13 Jan 1 1970 fd -> /proc/self/fd crw-rw-rw-. 1 root root 1, 7 Jan 1 1970 full crw-rw-rw-. 1 root root 10, 229 Jan 1 1970 fuse crw-------. 1 root root 248, 2 Jan 1 1970 glink_pkt_loopback crw-------. 1 root root 248, 1 Jan 1 1970 glink_pkt_loopback_ctrl crw-------. 1 root root 10, 59 Jan 1 1970 hbtp_input crw-------. 1 root root 10, 58 Jan 1 1970 hbtp_vm crw-------. 1 root root 10, 55 Jan 1 1970 hwbinder crw-------. 1 root root 10, 183 Jan 1 1970 hwrng crw-------. 1 root root 239, 0 Jan 1 1970 icesdcc crw-------. 1 root root 240, 0 Jan 1 1970 iceufs lrwxrwxrwx. 1 root root 25 Jan 1 1970 initctl -> /run/systemd/initctl/fifo drwxr-xr-x. 2 root root 160 Jan 1 1970 input crw-rw-r--. 1 root root 10, 94 Jan 1 1970 ion crw-------. 1 root root 233, 0 Jan 1 1970 jpeg0 crw-------. 1 root root 232, 0 Jan 1 1970 jpeg2 crw-------. 1 root root 231, 0 Jan 1 1970 jpeg3 crw-------. 1 root root 10, 57 Jan 1 1970 keychord crw-------. 1 root root 242, 0 Jan 1 1970 kgsl-3d0 crw-r--r--. 1 root root 1, 11 Jan 1 1970 kmsg lrwxrwxrwx. 1 root root 28 Jan 1 1970 log -> /run/systemd/journal/dev-log crw-rw----. 1 root disk 10, 237 Jan 1 1970 loop-control brw-rw----. 1 root disk 7, 0 Jan 1 1970 loop0 brw-rw----. 1 root disk 7, 1 Jan 1 1970 loop1 brw-rw----. 1 root disk 7, 2 Jan 1 1970 loop2 brw-rw----. 1 root disk 7, 3 Jan 1 1970 loop3 brw-rw----. 1 root disk 7, 4 Jan 1 1970 loop4 brw-rw----. 1 root disk 7, 5 Jan 1 1970 loop5 brw-rw----. 1 root disk 7, 6 Jan 1 1970 loop6 brw-rw----. 1 root disk 7, 7 Jan 1 1970 loop7 drwxr-xr-x. 2 root root 60 Jan 1 1970 mapper crw-------. 1 root root 224, 2 Jan 1 1970 mdsprpc-smd crw-------. 1 root root 251, 0 Jan 1 1970 media0 crw-------. 1 root root 251, 1 Jan 1 1970 media1 crw-------. 1 root root 251, 2 Jan 1 1970 media2 crw-------. 1 root root 251, 3 Jan 1 1970 media3 crw-------. 1 root root 10, 40 Jan 1 1970 memory_bandwidth drwxrwxrwt. 2 root root 40 Jan 1 1970 mqueue crw-------. 1 root root 256, 0 Jan 1 1970 msm-rng crw-------. 1 root root 10, 75 Jan 1 1970 msm_aac crw-------. 1 root root 10, 83 Jan 1 1970 msm_aac_in crw-------. 1 root root 10, 73 Jan 1 1970 msm_alac crw-------. 1 root root 10, 68 Jan 1 1970 msm_amrnb crw-------. 1 root root 10, 80 Jan 1 1970 msm_amrnb_in crw-------. 1 root root 10, 67 Jan 1 1970 msm_amrwb crw-------. 1 root root 10, 63 Jan 1 1970 msm_amrwb_in crw-------. 1 root root 10, 66 Jan 1 1970 msm_amrwbplus crw-------. 1 root root 10, 72 Jan 1 1970 msm_ape crw-------. 1 root root 10, 93 Jan 1 1970 msm_audio_cal crw-------. 1 root root 10, 65 Jan 1 1970 msm_evrc crw-------. 1 root root 10, 81 Jan 1 1970 msm_evrc_in crw-------. 1 root root 10, 70 Jan 1 1970 msm_g711alaw crw-------. 1 root root 10, 78 Jan 1 1970 msm_g711alaw_in crw-------. 1 root root 10, 71 Jan 1 1970 msm_g711mlaw crw-------. 1 root root 10, 79 Jan 1 1970 msm_g711mlaw_in crw-------. 1 root root 10, 62 Jan 1 1970 msm_hweffects crw-------. 1 root root 10, 69 Jan 1 1970 msm_mp3 crw-------. 1 root root 10, 74 Jan 1 1970 msm_multi_aac crw-------. 1 root root 10, 64 Jan 1 1970 msm_qcelp crw-------. 1 root root 10, 82 Jan 1 1970 msm_qcelp_in crw-------. 1 root root 10, 48 Jan 1 1970 msm_rtac crw-------. 1 root root 254, 0 Jan 1 1970 msm_sps crw-------. 1 root root 253, 0 Jan 1 1970 msm_thermal_query crw-------. 1 root root 10, 77 Jan 1 1970 msm_wma crw-------. 1 root root 10, 76 Jan 1 1970 msm_wmapro crw-------. 1 root root 10, 29 Jan 1 1970 mtp_usb drwxr-xr-x. 2 root root 60 Jan 1 1970 net crw-------. 1 root root 10, 42 Jan 1 1970 network_latency crw-------. 1 root root 10, 41 Jan 1 1970 network_throughput crw-rw-rw-. 1 root root 1, 3 Jan 1 1970 null crw-------. 1 root root 108, 0 Jan 1 1970 ppp crw-------. 1 root root 10, 1 Jan 1 1970 psaux crw-------. 1 root root 10, 26 Jan 1 1970 pta crw-rw-rw-. 1 root tty 5, 2 Apr 2 16:31 ptmx drwxr-xr-x. 2 root root 0 Jan 1 1970 pts crw-------. 1 root root 247, 0 Jan 1 1970 qbt1000 crw-------. 1 root root 10, 60 Jan 1 1970 qce crw-------. 1 root root 238, 0 Jan 1 1970 qcqmi0 crw-------. 1 root root 238, 1 Jan 1 1970 qcqmi1 crw-------. 1 root root 238, 2 Jan 1 1970 qcqmi2 crw-------. 1 root root 238, 3 Jan 1 1970 qcqmi3 crw-rw-rw-. 1 root root 241, 0 Jan 1 1970 qseecom brw-rw----. 1 root disk 1, 0 Jan 1 1970 ram0 brw-rw----. 1 root disk 1, 1 Jan 1 1970 ram1 brw-rw----. 1 root disk 1, 10 Jan 1 1970 ram10 brw-rw----. 1 root disk 1, 11 Jan 1 1970 ram11 brw-rw----. 1 root disk 1, 12 Jan 1 1970 ram12 brw-rw----. 1 root disk 1, 13 Jan 1 1970 ram13 brw-rw----. 1 root disk 1, 14 Jan 1 1970 ram14 brw-rw----. 1 root disk 1, 15 Jan 1 1970 ram15 brw-rw----. 1 root disk 1, 2 Jan 1 1970 ram2 brw-rw----. 1 root disk 1, 3 Jan 1 1970 ram3 brw-rw----. 1 root disk 1, 4 Jan 1 1970 ram4 brw-rw----. 1 root disk 1, 5 Jan 1 1970 ram5 brw-rw----. 1 root disk 1, 6 Jan 1 1970 ram6 brw-rw----. 1 root disk 1, 7 Jan 1 1970 ram7 brw-rw----. 1 root disk 1, 8 Jan 1 1970 ram8 brw-rw----. 1 root disk 1, 9 Jan 1 1970 ram9 crw-------. 1 root root 10, 91 Jan 1 1970 ramdump_AR6320 crw-------. 1 root root 10, 85 Jan 1 1970 ramdump_a530_zap crw-------. 1 root root 10, 46 Jan 1 1970 ramdump_adsp crw-------. 1 root root 10, 38 Jan 1 1970 ramdump_adsp_rh crw-------. 1 root root 10, 87 Jan 1 1970 ramdump_memshare_DIAG crw-------. 1 root root 10, 88 Jan 1 1970 ramdump_memshare_FTM crw-------. 1 root root 10, 89 Jan 1 1970 ramdump_memshare_GPS crw-------. 1 root root 10, 44 Jan 1 1970 ramdump_modem crw-------. 1 root root 10, 45 Jan 1 1970 ramdump_slpi crw-------. 1 root root 10, 39 Jan 1 1970 ramdump_smem crw-------. 1 root root 10, 86 Jan 1 1970 ramdump_venus crw-rw-rw-. 1 root root 1, 8 Jan 1 1970 random prw--w----. 1 root rebooters 0 Jan 1 1970 rebooterdev crw-rw-r--. 1 root root 10, 92 Jan 1 1970 rfkill crw-------. 1 root root 10, 36 Jan 1 1970 rmnet_ctrl crw-------. 1 root root 10, 35 Jan 1 1970 rmnet_ctrl1 crw-------. 1 root root 10, 34 Jan 1 1970 rmnet_ctrl2 crw-------. 1 root root 10, 33 Jan 1 1970 rmnet_ctrl3 lrwxrwxrwx. 1 root root 4 Jan 1 1970 rtc -> rtc0 crw-------. 1 root root 252, 0 Jan 1 1970 rtc0 brw-rw----. 1 root disk 8, 0 Jan 1 1970 sda brw-rw----. 1 root disk 8, 1 Jan 1 1970 sda1 brw-rw----. 1 root disk 8, 2 Jan 1 1970 sda2 brw-rw----. 1 root disk 8, 3 Jan 1 1970 sda3 brw-rw----. 1 root disk 8, 4 Jan 1 1970 sda4 brw-rw----. 1 root disk 8, 5 Jan 1 1970 sda5 brw-rw----. 1 root disk 8, 6 Jan 1 1970 sda6 brw-rw----. 1 root disk 8, 7 Jan 1 1970 sda7 brw-rw----. 1 root disk 8, 8 Jan 1 1970 sda8 brw-rw----. 1 root disk 8, 9 Jan 1 1970 sda9 brw-rw----. 1 root disk 8, 16 Jan 1 1970 sdb brw-rw----. 1 root disk 8, 17 Jan 1 1970 sdb1 brw-rw----. 1 root disk 8, 32 Jan 1 1970 sdc brw-rw----. 1 root disk 8, 33 Jan 1 1970 sdc1 brw-rw----. 1 root disk 8, 48 Jan 1 1970 sdd brw-rw----. 1 root disk 8, 49 Jan 1 1970 sdd1 brw-rw----. 1 root disk 8, 50 Jan 1 1970 sdd2 brw-rw----. 1 root disk 8, 51 Jan 1 1970 sdd3 brw-rw----. 1 root disk 8, 64 Jan 1 1970 sde brw-rw----. 1 root disk 8, 65 Jan 1 1970 sde1 brw-rw----. 1 root disk 8, 74 Jan 1 1970 sde10 brw-rw----. 1 root disk 8, 75 Jan 1 1970 sde11 brw-rw----. 1 root disk 8, 76 Jan 1 1970 sde12 brw-rw----. 1 root disk 8, 77 Jan 1 1970 sde13 brw-rw----. 1 root disk 8, 78 Jan 1 1970 sde14 brw-rw----. 1 root disk 8, 79 Jan 1 1970 sde15 brw-rw----. 1 root disk 259, 0 Jan 1 1970 sde16 brw-rw----. 1 root disk 259, 1 Jan 1 1970 sde17 brw-rw----. 1 root disk 259, 2 Jan 1 1970 sde18 brw-rw----. 1 root disk 259, 3 Jan 1 1970 sde19 brw-rw----. 1 root disk 8, 66 Jan 1 1970 sde2 brw-rw-r--. 1 root disk 259, 4 Jan 1 1970 sde20 brw-rw----. 1 root disk 259, 5 Jan 1 1970 sde21 brw-rw----. 1 root disk 259, 6 Jan 1 1970 sde22 brw-rw----. 1 root disk 259, 7 Jan 1 1970 sde23 brw-rw----. 1 root disk 259, 8 Jan 1 1970 sde24 brw-rw----. 1 root disk 259, 9 Jan 1 1970 sde25 brw-rw----. 1 root disk 259, 10 Jan 1 1970 sde26 brw-rw----. 1 root disk 259, 11 Jan 1 1970 sde27 brw-rw----. 1 root disk 259, 12 Jan 1 1970 sde28 brw-rw----. 1 root disk 259, 13 Jan 1 1970 sde29 brw-rw----. 1 root disk 8, 67 Jan 1 1970 sde3 brw-rw----. 1 root disk 259, 14 Jan 1 1970 sde30 brw-rw----. 1 root disk 259, 15 Jan 1 1970 sde31 brw-rw----. 1 root disk 259, 16 Jan 1 1970 sde32 brw-rw----. 1 root disk 259, 17 Jan 1 1970 sde33 brw-rw----. 1 root disk 8, 68 Jan 1 1970 sde4 brw-rw----. 1 root disk 8, 69 Jan 1 1970 sde5 brw-rw----. 1 root disk 8, 70 Jan 1 1970 sde6 brw-rw----. 1 root disk 8, 71 Jan 1 1970 sde7 brw-rw----. 1 root disk 8, 72 Jan 1 1970 sde8 brw-rw----. 1 root disk 8, 73 Jan 1 1970 sde9 brw-rw----. 1 root disk 8, 80 Jan 1 1970 sdf brw-rw----. 1 root disk 8, 81 Jan 1 1970 sdf1 brw-rw----. 1 root disk 8, 82 Jan 1 1970 sdf2 brw-rw----. 1 root disk 8, 83 Jan 1 1970 sdf3 crw-------. 1 root root 224, 1 Jan 1 1970 sdsprpc-smd crw-------. 1 root root 229, 0 Jan 1 1970 seemplog crw-------. 1 root root 225, 0 Jan 1 1970 sensors crw-------. 1 root root 21, 0 Jan 1 1970 sg0 crw-------. 1 root root 21, 1 Jan 1 1970 sg1 crw-------. 1 system system 21, 2 Jan 1 1970 sg2 crw-rw----. 1 root disk 21, 3 Jan 1 1970 sg3 crw-rw----. 1 root disk 21, 4 Jan 1 1970 sg4 crw-rw----. 1 root disk 21, 5 Jan 1 1970 sg5 crw-rw----. 1 root disk 21, 6 Jan 1 1970 sg6 crw-rw----. 1 root disk 21, 7 Jan 1 1970 sg7 crw-rw----. 1 root disk 21, 8 Jan 1 1970 sg8 drwxrwxrwt. 2 root root 40 Jan 1 1970 shm crw-------. 1 root root 10, 84 Jan 1 1970 smcinvoke crw-------. 1 root root 245, 11 Jan 1 1970 smd11 crw-------. 1 root root 245, 21 Jan 1 1970 smd21 crw-------. 1 root root 244, 1 Jan 1 1970 smd22 crw-------. 1 root root 245, 36 Jan 1 1970 smd36 crw-------. 1 root root 245, 7 Jan 1 1970 smd7 crw-------. 1 root root 245, 8 Jan 1 1970 smd8 crw-------. 1 root root 244, 4 Jan 1 1970 smd_pkt_loopback crw-------. 1 root root 244, 0 Jan 1 1970 smdcntl0 crw-------. 1 root root 244, 2 Jan 1 1970 smdcntl8 crw-------. 1 root root 10, 90 Jan 1 1970 smem_log drwxr-xr-x. 2 root root 60 Jan 1 1970 snd drwxrwxrwx. 2 root root 200 Jan 1 1970 socket lrwxrwxrwx. 1 root root 15 Jan 1 1970 stderr -> /proc/self/fd/2 lrwxrwxrwx. 1 root root 15 Jan 1 1970 stdin -> /proc/self/fd/0 lrwxrwxrwx. 1 root root 15 Jan 1 1970 stdout -> /proc/self/fd/1 crw-------. 1 root root 250, 0 Jan 1 1970 subsys_AR6320 crw-------. 1 root root 250, 2 Jan 1 1970 subsys_a530_zap crw-------. 1 root root 250, 3 Jan 1 1970 subsys_adsp crw-------. 1 root root 250, 5 Jan 1 1970 subsys_modem crw-------. 1 root root 250, 4 Jan 1 1970 subsys_slpi crw-------. 1 root root 250, 1 Jan 1 1970 subsys_venus crw-------. 1 root root 10, 52 Jan 1 1970 sw_sync crw-rw-rw-. 1 root tty 5, 0 Jan 1 1970 tty crw-rw----. 1 root dialout 246, 0 Jan 1 1970 ttyHS0 crw-------. 1 root root 10, 239 Jan 1 1970 uhid crw-------. 1 root root 10, 223 Jan 1 1970 uinput crw-------. 1 root root 237, 0 Jan 1 1970 uio0 crw-------. 1 root root 237, 1 Jan 1 1970 uio1 crw-------. 1 root root 237, 2 Jan 1 1970 uio2 crw-rw-rw-. 1 root root 1, 9 Jan 1 1970 urandom drwxr-xr-x. 3 root root 60 Jan 1 1970 usb-ffs crw-------. 1 root root 10, 27 Jan 1 1970 usb_accessory crw-------. 1 root root 236, 0 Jan 1 1970 usbmon0 crw-------. 1 root root 236, 1 Jan 1 1970 usbmon1 crw-------. 1 root root 236, 2 Jan 1 1970 usbmon2 crw-------. 1 root root 10, 61 Jan 1 1970 usf1 crw-rw----. 1 root video 81, 3 Jan 1 1970 v4l-subdev0 crw-rw----. 1 root video 81, 4 Jan 1 1970 v4l-subdev1 crw-rw----. 1 root video 81, 13 Jan 1 1970 v4l-subdev10 crw-rw----. 1 root video 81, 14 Jan 1 1970 v4l-subdev11 crw-rw----. 1 root video 81, 15 Jan 1 1970 v4l-subdev12 crw-rw----. 1 root video 81, 16 Jan 1 1970 v4l-subdev13 crw-rw----. 1 root video 81, 17 Jan 1 1970 v4l-subdev14 crw-rw----. 1 root video 81, 18 Jan 1 1970 v4l-subdev15 crw-rw----. 1 root video 81, 21 Jan 1 1970 v4l-subdev16 crw-rw----. 1 root video 81, 23 Jan 1 1970 v4l-subdev17 crw-rw----. 1 root video 81, 24 Jan 1 1970 v4l-subdev18 crw-rw----. 1 root video 81, 26 Jan 1 1970 v4l-subdev19 crw-rw----. 1 root video 81, 5 Jan 1 1970 v4l-subdev2 crw-rw----. 1 root video 81, 6 Jan 1 1970 v4l-subdev3 crw-rw----. 1 root video 81, 7 Jan 1 1970 v4l-subdev4 crw-rw----. 1 root video 81, 8 Jan 1 1970 v4l-subdev5 crw-rw----. 1 root video 81, 9 Jan 1 1970 v4l-subdev6 crw-rw----. 1 root video 81, 10 Jan 1 1970 v4l-subdev7 crw-rw----. 1 root video 81, 11 Jan 1 1970 v4l-subdev8 crw-rw----. 1 root video 81, 12 Jan 1 1970 v4l-subdev9 crw-------. 1 root root 10, 95 Jan 1 1970 vga_arbiter crw-rw----. 1 root video 81, 2 Jan 1 1970 video0 crw-rw----. 1 root video 81, 19 Jan 1 1970 video1 crw-rw----. 1 root video 81, 20 Jan 1 1970 video2 crw-rw----. 1 root video 81, 22 Jan 1 1970 video3 crw-rw----. 1 root video 81, 0 Jan 1 1970 video32 crw-rw----. 1 root video 81, 1 Jan 1 1970 video33 crw-rw----. 1 root video 81, 25 Jan 1 1970 video4 crw-------. 1 root root 10, 54 Jan 1 1970 vndbinder crw-------. 1 root root 10, 47 Jan 1 1970 xt_qtaguid crw-rw-rw-. 1 root root 1, 5 Jan 1 1970 zero brw-rw----. 1 root disk 253, 0 Jan 1 1970 zram0Some more useful info for debugging this (I ran this with the modem in):
yocto:/# lsusb -v Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 3.18 iManufacturer 3 Linux 3.18.71-perf xhci-hcd iProduct 2 xHCI Host Controller iSerial 1 xhci-hcd.0.auto bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 Hub Descriptor: bLength 12 bDescriptorType 42 nNbrPorts 0 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere bHubDecLat 0.0 micro seconds wHubDelay 0 nano seconds DeviceRemovable 0x00 Hub Port Status: Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 15 bNumDeviceCaps 1 SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x02 Latency Tolerance Messages (LTM) Supported wSpeedsSupported 0x0008 Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 3 Lowest fully-functional device speed is SuperSpeed (5Gbps) bU1DevExitLat 0 micro seconds bU2DevExitLat 0 micro seconds can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0001 Self Powered Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 2 TT per port bMaxPacketSize0 64 idVendor 0x0424 Standard Microsystems Corp. idProduct 0x2514 USB 2.0 Hub bcdDevice b.b3 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 41 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 1 Single TT iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 2 TT per port iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 3 wHubCharacteristic 0x0009 Per-port power switching Per-port overcurrent protection TT think time 8 FS bits bPwrOn2PwrGood 50 * 2 milli seconds bHubContrCurrent 1 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0xff Hub Port Status: Port 1: 0000.0100 power Port 2: 0000.0100 power Port 3: 0000.0100 power Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 bNumConfigurations 1 can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0001 Self Powered Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 Single TT bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 3.18 iManufacturer 3 Linux 3.18.71-perf xhci-hcd iProduct 2 xHCI Host Controller iSerial 1 xhci-hcd.0.auto bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 1 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection TT think time 8 FS bits bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0xff Hub Port Status: Port 1: 0000.0507 highspeed power suspend enable connect can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0001 Self PoweredThe last thing to note is that all the lights on the modem seem to be on, even the WWAN light when trying to run
voxl-modem. Any help on this as soon as possible would be greatly appreciated! -
RE: Implementing PX4 avoidance in mission mode using the voxl and QGCposted in Ask your questions right here!
Thank you for your help, the UDP connection seems to be working for the most part! The connection is initiated and the ROS connections seem to be connected but it seems like the pointcloud isn't being updated fast enough. I checked the pointcloud topic made by the snap_dfs manager and that was being updated at around 2Hz at most and the avoidance algorithm requires the pointcloud to updated at least 10Hz. I also opened up the pointcloud in rviz and saw that the pointcloud was updating at that rate. Is this normal behavior or is something else going on here? I apologize that I keep encountering roadblocks but I do think I am close to getting this!
-
RE: Implementing PX4 avoidance in mission mode using the voxl and QGCposted in Ask your questions right here!
I've been working on this more but I'm still stuck at this point. I've tried using a stripped-down version of voxl-vision-px4 to essential just initiate the UART connection but this still doesn't help set up the serial connection for the avoidance repo. I have this running on the yocto base layer and I want to try running the voxl-vision-px4 or libvoxl_io functions in the docker image to initiate the UART connection and see if that does the trick. I've been having tons of problems trying to build these libraries on the roskinetic docker image, is their anyway to build the libvoxl_io library or voxl-vision-px4 on the roskinetic-xenial docker image?
-
Building voxl-suite on Docker Image on VOXLposted in Software Development
I am trying to use a function in the voxl-io library on the VOXL and wanted to do this on an Ubuntu image on the VOXL. I was trying to install the package using opkg but I keep getting an error saying that both 0.2.0 and 0.1.1 are both can't be installed due to incompatible architecture. Is it possible to install these packages on the Ubuntu docker image or should anything that needs to be done using these libraries be done outside the docker image?
-
RE: Implementing PX4 avoidance in mission mode using the voxl and QGCposted in Ask your questions right here!
Another roadblock! I decided to go straight to trying to run it in hardware as opposed to the simulator and I have been running into issues setting up the serial connection between the flight controller and VOXL. How do I specify the fcu_url on a serial port, specifically UART_J10 if I cannot talk to the ports with read and writes? I would not like to use udp and just use a serial connection but I'm confused about how to set up the fcu_url for a serial connection.
-
RE: VOXL Flight will not flash imageposted in Ask your questions right here!
This solved the flashing issue, I thought i did this all as root but I didn't! Thank you!
-
RE: VOXL Flight will not flash imageposted in Ask your questions right here!
The flashing process doesn't seem to really start. My guess is that the problem lies within the bootloader because our team was also having issues with updating the firmware both through and USB and when the process was done through USB, the upload.sh script was stalled on "waiting for the bootloader...", at which point I aborted the upload. My colleague @gus will be around at 4PM EST to discuss our issues; I have to attend to another project but he is just as informed on our issues as I am, if not more. You can reach him at gus@sicdrone.com. Thank you for being so responsive!
-
VOXL Flight will not flash imageposted in Ask your questions right here!
When attempting to flash the VOXL Flight, the VOXL would go into flashboot mode but it never got out of flashboot mode, even after several minutes. The ./install.sh script was stuck on <waiting for devices> as well. I attempted to flash without the Debug Add-on and with it as well (even though we had shell access to the VOXL) and both methods did not work. This was attempted both with the 2.5.2 and 3.1.0 images. Though we have access to this current image, it would be nice to be able to reflash the system image, especially as newer images come out. Any help on this would be appreciated, thanks!
-
RE: Implementing PX4 avoidance in mission mode using the voxl and QGCposted in Ask your questions right here!
Sounds easy enough, thanks for the quick reply!
-
RE: Implementing PX4 avoidance in mission mode using the voxl and QGCposted in Ask your questions right here!
Alright, my first roadblock! I was able to set up a docker image running ubuntu and I have installed voxl-cam-ros, snap_vio, and the dfs node and have built the catkin workspace with no problems seemingly. My problem comes with what to do next exactly: I could continue with the PX4 avoidance README and try SITL but I'm not sure about that because that involves installing PX4's firmware and running a gazebo simulation, which seems too cumbersome both in space and graphics for the VOXL to do. The second option would be to run in hardware. Part of the process of running the PX4 local planner requires specifying the camera serial number along with the company name before running "generate_launchfile.sh" which adds several parameters to launch a specific launch file for the camera specified. The second option seems like the more likely option but I'm not sure.
So my question is two-fold: Should I try to run this in SITL at all or just run it in hardware and if so, what parameters/launch files do I need to include so I could run with this in hardware? Do I even need to set up the node for the stereo camera in the same way it is done for the Realsense or Occipital cameras (For reference, I'm specifically referring to the Run on Hardware section of the PX4 avoidance repo).
Thanks for the help already! Hopefully, I won't have too many more issues that I'll need more insight on.
-
RE: Implementing PX4 avoidance in mission mode using the voxl and QGCposted in Ask your questions right here!
Thank you, I'll follow this and will let you know if I do it successfully or if there are any roadblocks in the way!