Hello @modaltb @Eric-Katzfey @Alex-Kushleyev
I am trying to send a trigger message from voxl-tflite server to voxl-mapper server.
Once the object is detected an trigger message will be received and identified by the voxl-mapper and a custom marker will be placed in the position.
thank you
@Alex-Kushleyev @Eric-Katzfey
can you check the above mentioned error.
@Eric-Katzfey thank you for sharing the data.
I tried flashing the voxl-io-server you mentioned, but I got the following error.
t@t-MS-7B29:~/git/voxl-io-server-master$ ./deploy_to_voxl.sh
searching for ADB device
checking VOXL for dpkg/opkg
dpkg detected
voxl-io-server_0.0.5-202502191136_arm64.deb: 1 file pushed. 2.1 MB/s (25928 bytes in 0.012s)
dpkg: considering removing voxl-neopixel-manager in favour of voxl-io-server ...
dpkg: warning: ignoring dependency problem with removal of voxl-neopixel-manager:
voxl-suite depends on voxl-neopixel-manager (>= 0.0.3)
voxl-neopixel-manager is to be removed.
dpkg: yes, will remove voxl-neopixel-manager in favour of voxl-io-server
dpkg: regarding .../voxl-io-server_0.0.5-202502191136_arm64.deb containing voxl-io-server:
voxl-io-server conflicts with voxl-mpa-tools (<= 1.2.3)
voxl-mpa-tools (version 1.2.3) is present and installed.
dpkg: error processing archive /data/voxl-io-server_0.0.5-202502191136_arm64.deb (--install):
conflicting packages - not installing voxl-io-server
Errors were encountered while processing:
/data/voxl-io-server_0.0.5-202502191136_arm64.deb
DONE
@Alex-Kushleyev can you check this out
@Alex-Kushleyev , I tested the turtle mode out and it is working fine.
Once the approach for LEDs are shared, I will test it out .
I had an additional query, while we are using Telem for FCV2 and ESC communication. Will the PWM output (8 pinout) still be transmission and can we access the data.
@Alex-Kushleyev I have not tested turtle mode with Voxl2 - FCV2 setup. I have tested with the Voxl2, internal PX4 server.
I will test it out and get back to you.
@Alex-Kushleyev Thanks for the help. I will also test it out and get back with the results as soon as the approach is shared.
Can you also help me with finding clarity whether turtle mode will be affected by this setup.
@Alex-Kushleyev
just a thought, the data from Voxl2 is transfered to FC. so you can convert them to specific msg type and forward it to external FC and External FC already has modal-io-bridge, it can forward the data to ESC. There will be need of conversion of msg types multiple places, for handling and forwarding.
the External Fc has turtle mode running on it, will it setup affect it.
@Alex-Kushleyev ,
Thanks for the clarity, I also went through the same process and was not able to find any way to forward the message to ESC through external FC.
If you could help with a work around this approach it will be really helpful. I can test it out and get back to you.
@Alex-Kushleyev thanks again. can you check this out.
As mentioned the messages needs to be converted to mavlink message. Will mavlink message be handled by VOXL-ESC and will it trigger the voxl-send-neopixel-cmd and turn on the LEDs? I guess multiple conversion of message types might be required.
Also there is voxl-io driver link running in the VOXL FCV2. It should help voxl FCV2 to handle the data from VOXL2 and pass it to the VOXL FPV ESC.
There are 2 PWM outputs link that are independent, can we send a trigger message from VOXL2 Board to the VOXL FCV2 and FC will send the message to VOXL FPV ESC and give PWM output. Using the voxl-send-pwm-cmd command.
@Alex-Kushleyev Thank you for reverting. I tested it out and the ESC is powered. The TELEM1 port is connected to VOXL2 board and TELEM2 port to the Flight Core FCv2 board. I used the PX4 firmware modalai_fc-v2_1.14.0-8.93.1.px4 from the ModalAI build and setup the necessary parameters following documentation. The VOXL ESC is recognising the data from FC autopilot and the LED blinking sequence starts.
I have few more queries,
In the coming days I'll be upgrading to VOXL-FPV ESC. Can I follow the same wiring setup for this as well?
I had an additional query link, you had mentioned not able to run any python tool files, but since voxl-send-neopixel-cmd is in C/C++, it should be working.
Also, will this setup affect the turtle mode implementation.
@KnightHawk you may consider reflashing your SDK image if feasible to mark out things.
Hello @Alex-Kushleyev @tom @Vinny @Eric-Katzfey,
@modaltb @Chad-Sweet
In my setup, I'm having
-> Compute - VOXL2
-> FC - Flight Core V2
-> ESC - VOXL ESC 4-in-1
-> Firmware - PX4 1.15.2
I'm connecting a VOXL2 to external Flight Controller Flight Core V2. My ESC is connected to Flight Core V2 through the M0063 cable setup.
I'm connecting external Flight Core V2 to VOXL2 using the M0054 Cable connector setup but only connected to TELEM1 port at autopilot end.
Also as per the ModalAI Documentation, I have changed the voxl-mavlink-server to enable external autopilot functionality. When I connect to QGC on host computer, I'm able to connect to Flight Core V2 and see parameters on the autopilot.
But when I setup the VOXL ESC parameters also as per the documentation stated here, I still not able to make it clearly if Flight Core is communicating with VOXL ESC or not.
From VOXL2 I'm trying to run VOXL-ESC commands also,
This is the terminal output,
voxl2:/$ voxl-esc
What do you want to do?
1) scan 3) spin 5) upload_params
2) detect 4) upgrade_firmware
#? 1
enabling bridge
detected voxl-px4 is enabled
Removed /etc/systemd/system/multi-user.target.wants/voxl-px4.service.
detected voxl-px4 is running, stopping it now
Sending kill slpi command!
bridge enabled
Detected Python version : 3.6.9 (default, Mar 10 2023, 16:46:00)
[GCC 8.4.0]
Found voxl-esc tools bin version: 1.9
VOXL Platform: M0054
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 2000000
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
WARNING: No ESC(s) detected
VOXL Platform: M0054
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 250000
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
WARNING: No ESC(s) detected
VOXL Platform: M0054
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 921600
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
WARNING: No ESC(s) detected
VOXL Platform: M0054
Detected RB5 Flight, VOXL2 M0054 or M0104!
INFO: Scanning for ESC firmware: /dev/slpi-uart-2, baud: 57600
INFO: Scanning for ESC bootloader: /dev/slpi-uart-2, baud: 230400
Updated baud rate to 230400
WARNING: No ESC(s) detected
ERROR: not all ESCs found
FAILED to ping ESCs when calling scan script
disabling bridge
Sending kill slpi command!
re-enabling voxl-px4
Created symlink /etc/systemd/system/multi-user.target.wants/voxl-px4.service → /etc/systemd/system/voxl-px4.service.
restarting voxl-px4
bridge disabled
DONE
Now how do I confirm if my Flight Core V2 is communicating VOXL ESC?
Also, I'm following the setup from the this documentation from ModalAI.
Also can I check using voxl-esc tools from VOXL2 to check the status of ESC in this setup?
@Jeremy-Frederick Thanks for reverting. In your setup do you have the Radio directly paired or connected with ground unit of the MH carrier without having to any other workarounds?
@Alex-Kushleyev @Eric-Katzfey can you check it out and help with the code.
I am also interested what kind of signal is send to the neopixel LEDs to turn it ON.
And with addition to that what is the command to turn ON only blue lights.
@Eric-Katzfey thank you for reverting.
I was able to run the code in loop and it is working good. now i want to automate this client file. start the file when the system is booted.
I have provided the External FC details in the above posts. @Alex-Kushleyev , can you verify the approach and help me out with the implementation.
@Eric-Katzfey @Vinny @tom Also, I have a doubt regarding the hardware connections between VOXL2 and Doodle Labs Helix Nano module,
As depicted here,
The Helix mini module is connected to VOXL2 through M0078-2 board. In terms of hardware connections its,
1- 5P0V - VCC(1)
2- DATA_M - D-(14)
3- DATA_P - D+(15)
4- GND - GND(3)
In my setup, as mentioned earlier I'm using Nano Module and M00125_A USB3.0 Expander board.
Over here, in M0125_A since there are no direct DATA_M, DATA_N ports on J3, how can I interface this with Nano Module? As per Doodle Labs Nano documentation, there are Ethernet ports which support higher data baud rates. Could I use them for interfacing?
Or would you suggest any specific ports from Nano for interfacing?
@Eric-Katzfey Could you kindly respond for this?
@Alex-Kushleyev thank you for reverting .
I will try out the approach you mentioned.
The VOXL2 board is connected to Flight Core V2 (FC) and the FC connected to modalai FPV ESC .