@tom I checked wire harness going from the VOXL 2 to the Doodle Labs. Everything seems in check there. Haven't noticed anything wrong with the connector or solder joints on the pcb located on top of the Doodle Labs. Would you recommend getting a RMA going for this radio?
Posts made by Chase Riley
-
RE: Doodle Labs Not Connecting to QGC
-
RE: Doodle Labs Not Connecting to QGC
@tom I am not able to ping the Doodle Labs Radio from the VOXL2 that is connected to it.
-
Doodle Labs Not Connecting to QGC
I received a Doodle Labs Radio in my last shipment that I believe to have an issue. After programming the VOXL2 I am unable to get connection over QGC. I have multiple VOXL2 and Doodle Labs set up in house that I have been able to use to help troubleshoot this issue.
The Doodle Labs Radio that is in question is in the air vehicle. I am able to ping the IP of the Air radio from my Laptop which is connected to a Doodle Labs radio. I am also able to pull up the Web interface for the Air Radio as well. I am not able to ping the VOXL2 or open VOXL Portal. I have tried to reset the radio to factory defaults and also flash a backup file from a known working radio with no luck. I was also able to test out different harnesses and even plugged the Radio in question to a known working VOXL2 setup with the same issue. I was able to plug the VOXL2 that is in the same vehicle with the questionable Doodle Labs radio to another Doodle Labs Radio and it linked up to QGC with no Issues.
With my troubleshooting it seems I have narrowed it down to this Doodle Labs Radio. I am not sure how to continue troubleshooting the issue. I guess it could be something wrong with the actual hardware of the radio.
Any information to help me solve this issue will be appreciated. Thanks!
-
RE: VOXL ESC with Cube running PX4
@Alex-Kushleyev Are you saying run this in the Mavlink Console in QGC? If so I receive "command not found"
-
RE: VOXL ESC with Cube running PX4
@Eric-Katzfey I am waiting for a order from you all now that will allow me to test with the ESC. Once I get that in I will be able to connect it to the cube and see if it works.
I was able to load the mainline PX4 on a cube I have here. I looked in the parameters and did not see any of the
VOXL_ESC_xxxx
parameters listed. Is this something that should only appear when the VOXL ESC is connected? -
VOXL ESC with Cube running PX4
I currently have a VOXL2 running SDK 1.1 with a VOXL ESC (MDK-M0134-6-01). I am looking to add a Cube running PX4 instead of having PX4 running on the VOXL2. What would be the best way to accomplish this? Am I able to run the latest dev version of PX4 1.15 or would I need to run the VOXL Branch of PX4 to be able to talk to the ESC?
-
RE: IMX412 for camera configuration 11 on SDK 1.1.2
@Alex-Kushleyev Awesome! That got it working. Now one last thing on this. How can I flip the image of the imx412? Would it still be a driver that said
flip
after it? -
RE: IMX412 for camera configuration 11 on SDK 1.1.2
@Alex-Kushleyev yes. Exactly. My configuration is c11 just with s 412 instead of the 214.
-
RE: IMX412 for camera configuration 11 on SDK 1.1.2
@Alex-Kushleyev I followed the connection diagram for C-11. Which shows a different configuration than the C-17 you sent here. I am connecting the longest part of the dual flex to the hires camera. This configuration worked in SDK 1.0.
-
IMX412 for camera configuration 11 on SDK 1.1.2
I am trying to get the VOXL2 running SDK 1.1.2 and camera configuration 11 to use the IMX412 instead of the IMX214. I had this functioning in SDK 1.0, however when I try to run the command
voxl-configure-cameras 11 --imx412
like I did in SDK 1.0 it tells me that it is and invalid command. I can runvoxl-configure-cameras 11
with no issues.When I pull up
voxl-portal
in my web browser it does not show the option to view the hires camera. I have the modified thevoxl-camera-server.conf
to set the resolution of the IMX412 to 1920x1080 and I also tried to change imx214 to imx412 and that yielded the same results.When running
voxl-camera-server
I see a error that say failure to find hires stream at 1920x1080. -
RE: Voxl2 Spektrum Receiver error
@Alex-Kushleyev and @Eric-Katzfey Thanks for your help on this. Flight testing went well. I was able to test with the Spektrum DX8 and DX6e and saw no difference between the two while running the custom Debian file that was sent over.
-
RE: Voxl2 Spektrum Receiver error
@Alex-Kushleyev Do you have a rough idea of what this value should be set to? If you need to know my motor and prop combo send me an email. I would rather not disclose on the forums.
-
RE: Voxl2 Spektrum Receiver error
@Alex-Kushleyev I went and checked my .xml file and verified it was correct and re uploaded it to the ESC just to make sure. I had already run the calibration and updated the A0, A1, and A2.
I did find that my
min_rpm
andmax rpm
were different in the xml file than I had them set in px4. That may have been the issue because control seems to be working fine now. Between re flashing the xml and changing the values one or both of the solutions solved the issue. I will contnue testing and report back with any issues. Thanks for jumping in and helping out.@Eric-Katzfey you said this morning that the DX6e data I sent over did not look correct. Is there something else we want to look into there. As I said before after looking at the logs the DX8 and the DX6e seem to behave the same way.
-
RE: Voxl2 Spektrum Receiver error
@Eric-Katzfey Please let me know what you or your team find. This seems to be the last hurdle to getting me to flight testing. I have a shipping deadline to make on Friday with this system.
-
RE: Voxl2 Spektrum Receiver error
@Eric-Katzfey I have tried to spin the motors in manual mode as well with no change. I have included a drop box link with the px4 flight log you requested.
-
RE: Voxl2 Spektrum Receiver error
@Eric-Katzfey
RC_MAP_THROTTLE
is set to Channel 3,RC_MAP_YAW
is set to Channel 4,RC_MAP_ROLL
is set to Channel 1, andRC_MAP_PITCH
is set to Channel 2.Moving the Throttle and Yaw stick while running
listener manual_control_setpoint
shows Throttle and Yaw changing values as it should. It also shows that Stick movement goes TRUE. -
RE: Voxl2 Spektrum Receiver error
@Eric-Katzfey yes, each stick moves correctly in QGC.
listener input_rc
shows all sticks move correctly. I have tested withCOM_RC_IN_MODE
set to 0 and 2 and both yield the same results. -
RE: Voxl2 Spektrum Receiver error
@Eric-Katzfey Here is a
voxl-px4
log while testing with a DX6e this morning. I was able to bind and calibrate no problem. I am just not able to control the motors. Flight mode and kill switch seem to be working fine. So seems to have the same behavior as the DX8 with a error in the log for 32 bytes and 0x00.INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 ERROR [muorb] SLPI: Spektrum RC: Invalid DSM frame. 32 bytes. Protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf5 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Armed by external command INFO [logger] Start file log (type: full) INFO [logger] [logger] /data/px4/log/2024-01-24/19_14_37.ulg INFO [logger] Opened full log file: /data/px4/log/2024-01-24/19_14_37.ulg WARN [mavlink] Event dropped (297, 65527) WARN [mavlink] Event dropped (297, 65527) WARN [mavlink] Dropped 65230 events (seq=65527) WARN [mavlink] Dropped 65230 events (seq=65527) INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00 INFO [muorb] SLPI: Spektrum RC: DSM message parsed successfully INFO [muorb] SLPI: Spektrum RC: Publishing input_rc INFO [muorb] SLPI: 0x00 0x00 0x8c 0x05 0x01 0x56 0x14 0x00 INFO [muorb] SLPI: 0x1b 0xf6 0x2e 0xaa 0x3c 0x00 0x34 0x00 INFO [muorb] SLPI: Spektrum RC: 16 bytes from UART, protocol byte 0x00
-
RE: Voxl2 Spektrum Receiver error
@Eric-Katzfey I have tried all of the options in the DX8. 11, 22 and DSM2, DSMX. They all seemed to produce the same results in the logs.
-
RE: Voxl2 Spektrum Receiver error
@Eric-Katzfey I am also getting my hands on a DX6e for me to test. I should be able to try that in the morning. I still would like to figure out the DX8 as well though since we already have a bunch on hand in our lab.