Hey,
I will try my best to explain the idea I had.
You can use gstreamer to stream your camera to a shared memory sink (shmsink). To implement this I would use cv2 (python) with the video writer class to write the video to a FIFO file location. The location can be set to /temp/[name] which will utilize shared memory. This location can be mapped to both docker containers with the -v / --volume parameter so you can access the stream from the other docker container as well. This is obviously not the easiest nor best solution but probably better than a custom kernel.
All the best
A
Posts made by Arrowtec
-
RE: Duplicating UVC cameraposted in Software Development
-
Error using Voxl-tflite-server on Firmware 3.1.0posted in Ask your questions right here!
Hey there,
I am trying to get the voxl-tflite-server to run on my Voxl. I know it is recommended to use 3.3.0 or greater but I experienced some issues with the newer versions and wanted to make it work on this version. Installing it seems to be going alright, but when trying to configure it this error occurs:voxl-tflite-server: error while loading shared libraries: libmodal_pipe.so: cannot open shared object file: No such file or directoryI ignored it and went on with the configuration. At the end no configuration file was created in the directory as shown here: https://docs.modalai.com/voxl-tflite-server/
Furthermore after looking at the service which would be started this is the output of systemctl:~ # systemctl status voxl-tflite-server -l ā voxl-tflite-server.service - voxl-tflite-server Loaded: loaded (/usr/bin/voxl-tflite-server; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since Thu 1970-01-01 00:00:08 UTC; 52 years 0 months ago Process: 2496 ExecStart=/bin/bash -c /usr/bin/voxl-tflite-server (code=exited, status=127) Main PID: 2496 (code=exited, status=127) Jan 01 00:00:08 apq8096 systemd[1]: voxl-tflite-server.service: Service hold-off time over, scheduling restart. Jan 01 00:00:08 apq8096 systemd[1]: Stopped voxl-tflite-server. Jan 01 00:00:08 apq8096 systemd[1]: voxl-tflite-server.service: Start request repeated too quickly. Jan 01 00:00:08 apq8096 systemd[1]: Failed to start voxl-tflite-server. Jan 01 00:00:08 apq8096 systemd[1]: voxl-tflite-server.service: Unit entered failed state. Jan 01 00:00:08 apq8096 systemd[1]: voxl-tflite-server.service: Failed with result 'start-limit'. Jan 01 00:00:11 apq8096 bash[2260]: /usr/bin/voxl-tflite-server: error while loading shared libraries: libmodal_pipe.so: cannot open shared object file: No such file or directory Jan 01 00:00:11 apq8096 bash[2310]: /usr/bin/voxl-tflite-server: error while loading shared libraries: libmodal_pipe.so: cannot open shared object file: No such file or directory Jan 01 00:00:11 apq8096 bash[2401]: /usr/bin/voxl-tflite-server: error while loading shared libraries: libmodal_pipe.so: cannot open shared object file: No such file or directory Jan 01 00:00:11 apq8096 bash[2496]: /usr/bin/voxl-tflite-server: error while loading shared libraries: libmodal_pipe.so: cannot open shared object file: No such file or directoryHere is the same error present not being able to load the libraries necessary.
Help would be appreciated
-
RE: Voxl stuck in waiting for device after unbrickingposted in Ask your questions right here!
I'm just gonna leave this here if it affects others aswell:
I was stuck on the issue for a while but it was indeed an adb issue. Restarting it didn't fix the issue and I couldn't debug what the problem seems to be. Using another device (laptop) did work tho and I was able to unbrick it.
Thanks for the inputs Chad. -
Voxl stuck in waiting for device after unbrickingposted in Ask your questions right here!
Hey, my voxl is stuck in waiting for device after trying to unbrick it with the addon board. I tried basically everything and followed the instructions precisly and tried power cycling it etc. Some help on what to do would be appreciated
sudo ./install.sh -f [INFO] adb installed [INFO] fastboot installed [INFO] Factory Mode [INFO] Using factory mode [INFO] Rebooting into fastboot... error: no devices/emulators found target reported max download size of 536870912 bytes sending 'aboot' (494 KB)... OKAY [ 0.047s] writing 'aboot'... OKAY [ 0.069s] finished. total time: 0.116s target reported max download size of 536870912 bytes sending 'boot' (56070 KB)... OKAY [ 1.639s] writing 'boot'... OKAY [ 0.416s] finished. total time: 2.055s target reported max download size of 536870912 bytes erasing 'system'... OKAY [ 0.013s] sending sparse 'system' 1/4 (522964 KB)... OKAY [ 17.077s] writing 'system' 1/4... OKAY [ 13.870s] sending sparse 'system' 2/4 (521547 KB)... OKAY [ 21.430s] writing 'system' 2/4... OKAY [ 14.420s] sending sparse 'system' 3/4 (524111 KB)... OKAY [ 21.710s] writing 'system' 3/4... OKAY [ 15.434s] sending sparse 'system' 4/4 (76257 KB)... OKAY [ 3.667s] writing 'system' 4/4... OKAY [ 4.348s] finished. total time: 111.969s target reported max download size of 536870912 bytes erasing 'userdata'... OKAY [ 0.024s] sending 'userdata' (142611 KB)... OKAY [ 4.099s] writing 'userdata'... OKAY [ 1.172s] finished. total time: 5.295s target reported max download size of 536870912 bytes sending 'persist' (4292 KB)... OKAY [ 0.177s] writing 'persist'... OKAY [ 0.070s] finished. total time: 0.247s target reported max download size of 536870912 bytes erasing 'cache'... OKAY [ 0.021s] sending 'cache' (5152 KB)... OKAY [ 0.217s] writing 'cache'... OKAY [ 0.095s] finished. total time: 0.332s target reported max download size of 536870912 bytes sending 'recoveryfs' (126585 KB)... OKAY [ 3.532s] writing 'recoveryfs'... OKAY [ 6.273s] finished. total time: 9.805s [INFO] Done flashing all images. Rebooting device in 2 seconds rebooting... finished. total time: 0.072s [INFO] Waiting for device... -
RE: Bootup after running install.sh script out of fastboot not workingposted in FAQs
I tried everything there was in the tutorial and spent like 1h with different timing. I was able to unbrick other Voxls before but this one doesn't want to. If there is a different method than what you already described please let me know.
-
Bootup after running install.sh script out of fastboot not workingposted in FAQs
So basically the voxl was bricked and I put it into fastboot with the add-on board. Now I wanted to flash the software onto it. After running the script with the -f Flag it is stuck waiting for device. So basically after flashing it goes straight back into the bricked state.
Here is the log:sudo ./install.sh -f [INFO] adb installed [INFO] fastboot installed [INFO] Factory Mode [INFO] Using factory mode [INFO] Rebooting into fastboot... error: no devices/emulators found target reported max download size of 536870912 bytes sending 'aboot' (494 KB)... OKAY [ 0.037s] writing 'aboot'... OKAY [ 0.036s] finished. total time: 0.073s target reported max download size of 536870912 bytes sending 'boot' (56066 KB)... OKAY [ 0.379s] writing 'boot'... OKAY [ 0.450s] finished. total time: 0.829s target reported max download size of 536870912 bytes erasing 'system'... OKAY [ 0.008s] sending sparse 'system' 1/3 (523027 KB)... OKAY [ 4.245s] writing 'system' 1/3... OKAY [ 17.553s] sending sparse 'system' 2/3 (523094 KB)... OKAY [ 3.654s] writing 'system' 2/3... OKAY [ 13.533s] sending sparse 'system' 3/3 (521982 KB)... OKAY [ 4.312s] writing 'system' 3/3... OKAY [ 16.147s] finished. total time: 59.452s target reported max download size of 536870912 bytes erasing 'userdata'... OKAY [ 0.023s] sending 'userdata' (138395 KB)... OKAY [ 0.889s] writing 'userdata'... OKAY [ 1.124s] finished. total time: 2.036s target reported max download size of 536870912 bytes sending 'persist' (4292 KB)... OKAY [ 0.057s] writing 'persist'... OKAY [ 0.072s] finished. total time: 0.129s target reported max download size of 536870912 bytes erasing 'cache'... OKAY [ 0.021s] sending 'cache' (5152 KB)... OKAY [ 0.056s] writing 'cache'... OKAY [ 0.095s] finished. total time: 0.173s target reported max download size of 536870912 bytes sending 'recoveryfs' (126585 KB)... OKAY [ 0.771s] writing 'recoveryfs'... OKAY [ 6.139s] finished. total time: 6.910s [INFO] Done flashing all images. Rebooting device in 2 seconds rebooting... finished. total time: 0.824s [INFO] Waiting for device... -
RE: VOXL can't be forced into fastboot/unbrickedposted in VOXL Flight
Hey sorry for the late reply but I got it to work after some trial and error, not really sure why it wouldn't work in the first place but maybe I just got the timing way off. Thanks anyway
-
Apt-get functionalityposted in Ask your questions right here!
Is there a way to get
apt-getinstalled on the Voxl? I want to develop using certain libraries and cant really get them another way. -
VOXL can't be forced into fastboot/unbrickedposted in VOXL Flight
After buying the debug board for my bricked VOXL and following the unbricking tutorial I still can't seem to let it show up on either
sudo fastboot devicesoradb devices. The LED1 on the VOXL is also only a solid green indicating that it is not in a boot mode. How would I proceed now? -
Voxl doesnt show up in either adb devices or fastboot devicesposted in Ask your questions right here!
I have a problem where my voxl flight showed up in adb devices, I ran the install.sh script and it failed and afterwards it didnt show up on my computer. Is there anything I can do without the debug board to fix this? Below is the code of the installation.
ben@ben-desktop:~/Downloads/modalai-3-1-0$ ./install.sh [INFO] adb installed [INFO] fastboot installed This process will completely wipe your VOXL Would you like to preserve the /data/ partition which contains things like calibration, wifi config, and docker images To preserve files in /data/ answer Y To wipe /data/ for a full factory flash answer N Enter Y or N: y [INFO] Rebooting into fastboot... error: no devices/emulators found target reported max download size of 536870912 bytes sending 'aboot' (494 KB)... OKAY [ 0.037s] writing 'aboot'... OKAY [ 0.031s] finished. total time: 0.069s target reported max download size of 536870912 bytes sending 'boot' (56066 KB)... OKAY [ 0.469s] writing 'boot'... OKAY [ 0.591s] finished. total time: 1.060s target reported max download size of 536870912 bytes erasing 'system'... OKAY [ 0.014s] sending sparse 'system' 1/3 (523027 KB)... FAILED (data write failure (Cannot send after transport endpoint shutdown)) finished. total time: 1.236s -
RE: UVC Camera interfacing in version 3.2.0posted in Ask your questions right here!
@Dean-Fortier personally I use the docker version and it works fine on my end
-
RE: IOT Sim-card integrationposted in Cellular Modems
The
echo -ne "AT+CGDCONT?\r" | busybox microcom -t 1000 /dev/ttyUSB2is btw from when I was using the old APN so dont get confused by that, here is the new one:~ # echo -ne "AT+CGDCONT?\r" | busybox microcom -t 1000 /dev/ttyUSB2 AT+CGDCONT? +CGDCONT: 1,"IP","spe.inet4g.gdsp","0.0.0.0",0,0,0,0 +CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0 +CGDCONT: 3,"IPV4V6","sos","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1 OK -
RE: IOT Sim-card integrationposted in Cellular Modems
@tom
The APN seems to default to "internet" but after thevoxl-configure-modemits set correctly as seen below. After that it is still not working / showing up.Here is
echo -ne "AT+CGDCONT?\r" | busybox microcom -t 1000 /dev/ttyUSB2:~ # echo -ne "AT+CGDCONT?\r" | busybox microcom -t 1000 /dev/ttyUSB2 AT+CGDCONT? +CGDCONT: 1,"IP","web.vodafone.de","0.0.0.0",0,0,0,0 +CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0 +CGDCONT: 3,"IPV4V6","sos","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1 OKHere is the content of
/etc/modalai/voxl-modem.conf:~ # cat /etc/modalai/voxl-modem.conf { "modem_type": "v2", "apn": "spe.inet4g.gdsp", "world": "true", "microhard_ip": "192.168.168.100", "modallink": "false", "placeholder": "hello world" }And here again the
systemctl status -l voxl-modem:~ # 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 Wed 2021-04-07 09:19:38 UTC; 11min ago Process: 4400 ExecStartPre=/bin/sleep 2 (code=exited, status=0/SUCCESS) Main PID: 4401 (voxl-modem-star) CGroup: /system.slice/voxl-modem.service āā4401 /bin/bash /usr/bin/voxl-modem-start.sh āā5666 /usr/bin/python /usr/bin/sierra.py Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: "plmn_mnc": 2, Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: "plmn_description": "vodafone.de", Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: "roaming": true Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: } Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: ] Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: Successfully registered with the network Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: Starting network Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: Checking connection status Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: "disconnected" Apr 07 09:30:38 apq8096 voxl-modem-start.sh[4401]: Connection failedFurthermore here is
ifconfigif that helps:~ # ifconfig docker0 Link encap:Ethernet HWaddr 02:42:DD:11:4A:98 inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 inet6 addr: fe80::42:ddff:fe11:4a98/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:152 (152.0 B) TX bytes:216 (216.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr EC:5C:68:CD:21:5B inet addr:192.168.7.122 Bcast:192.168.7.255 Mask:255.255.255.0 inet6 addr: fe80::ee5c:68ff:fecd:215b/64 Scope:Link inet6 addr: fd48:4c86:10be:e600:ee5c:68ff:fecd:215b/64 Scope:Global inet6 addr: 2a01:598:b00c:e53c:ee5c:68ff:fecd:215b/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:110 errors:0 dropped:0 overruns:0 frame:0 TX packets:104 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3000 RX bytes:11644 (11.3 KiB) TX bytes:15615 (15.2 KiB)Let me know if you can troubleshoot anything off the new information
-
RE: IOT Sim-card integrationposted in Cellular Modems
That should be the name of the Carrier and not the APN but I went through the
voxl-configure-modemmultiple times and it should be set right.
As already mentioned here:@tom Yes exactly it is a new Sim and I went through the
voxl-configure-modemsetup.
The Problem that I think I am having is that in order to figure out if the connection works Voxl tries to ping a server and if it can't reach it it will say it is not connected. With the IOT-Sim it only allows to speak to certain predetermined IPs meaning it cant reach the IP to confirm the connection.I am thinking the Problem is with the restricted access to certain IPs and the checking of one not in those in the startup process. Do you know what happens during the startup of the modem and how it checks to see if its connected to the internet?
-
RE: IOT Sim-card integrationposted in Cellular Modems
I am using the WP7607. The carrier is Vodafone and I am located in Germany.
The APN I am using is: web.vodafone.de
It worked with another Sim-Card so the compatibility shouldn't be the issue here -
RE: IOT Sim-card integrationposted in Cellular Modems
@tom Yes exactly it is a new Sim and I went through the
voxl-configure-modemsetup.
The Problem that I think I am having is that in order to figure out if the connection works Voxl tries to ping a server and if it can't reach it it will say it is not connected. With the IOT-Sim it only allows to speak to certain predetermined IPs meaning it cant reach the IP to confirm the connection. -
IOT Sim-card integrationposted in Cellular Modems
Hey there,
we want to switch from using a normal sim-card to an IOT one which basically only means that certain IP-addresses are valid to connect to and receive a connection from.
I think that this is a problem since the Modem won't boot/show up unless the connection is valid and the means of confirming a valid connection probably have something to do with my issue of the Modem not starting properly.
Any Ideas?~ # 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 Tue 2021-04-06 13:43:08 UTC; 31min ago
Process: 4223 ExecStartPre=/bin/sleep 2 (code=exited, status=0/SUCCESS)
Main PID: 4225 (voxl-modem-star)
CGroup: /system.slice/voxl-modem.service
āā4225 /bin/bash /usr/bin/voxl-modem-start.sh
āā7565 /usr/bin/python /usr/bin/sierra.py
āā7636 uqmi -P -d /dev/cdc-wdm0 --get-msisdnApr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: "plmn_mnc": 2,
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: "plmn_description": "vodafone.de",
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: "roaming": true
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: }
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: ]
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: Successfully registered with the network
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: Starting network
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: Checking connection status
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: "disconnected"
Apr 06 14:14:29 apq8096 voxl-modem-start.sh[4225]: Connection failed -
LTE Modem v2 Registration Errorposted in Cellular Modems
Hey there I have problems with getting my LTE to work I use the v2 version and it seems to fail on the registration part as seen below any Ideas on how to fix that?
(It worked previously with the same configuration)
And when it worked it was like and on-off connection..~ # systemctl status 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:09 UTC; 51 years 3 months ago
Process: 2179 ExecStartPre=/bin/sleep 2 (code=exited, status=0/SUCCESS)
Main PID: 2870 (voxl-modem-star)
CGroup: /system.slice/voxl-modem.service
āā2870 /bin/bash /usr/bin/voxl-modem-start.sh
āā4236 /usr/bin/python /usr/bin/sierra.pyApr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: response: [{
Apr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: "registration": "searching",
Apr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: "plmn_mcc": 262,
Apr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: "plmn_mnc": 3,
Apr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: "plmn_description": ""
Apr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: }
Apr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: ]
Apr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: registration: searching
Apr 06 13:27:19 apq8096 voxl-modem-start.sh[2870]: Giving up on registration
Apr 06 13:27:52 apq8096 voxl-modem-start.sh[2870]: "Not provisioned"
Hint: Some lines were ellipsized, use -l to show in full. -
RE: Speed of LTE-modem recognitionposted in Cellular Modems
@Eric-Katzfey I figured that would be the case. Atm I am just letting it boot on it's own; the systemd service file is an idea that i will test and afterwards I will get back to you.