Hi @Matthew-Wellner
Yes, we sell some modem products as "stand-alone" which can be connected to any USB host.
We have not offered our popular M0090 5G modem in that mode, but we have offered it for the older Microhard and Sierra 4G modules, but right now we only offer it on Microhard:
https://www.modalai.com/collections/modems/products/mdk-m0048-2

Thank you @ben-grocholsky! I should be more clear, when I ran px4-listener sensor_gps I received something along the lines of "GPS never published". I just went to go get the verbatim output but everything seems to be working. I do indeed see the uorb now. Puzzling

@groupo Yes, we have used px4-listener <topic name> for external monitoring of PX4 topic data in other applications.

Hi @wouter the reason this is happening is recently docker depricated their api v1 version and are only using v2 api calls now. Meaning the original voxl is not able to pull down pre made docker images. The solution around this is to build the docker image on a parent computer, tar it up via docker save, then push that to the voxl and run a docker load -i on the tar file.

You can follow similar to what we do in voxl-docker-mavsdk:

https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk/-/blob/main/Dockerfile?ref_type=heads

Please verify the PC data in rviz2. What you see in rviz2 should look exactly alike to what is shown in voxal portal for tof_pc. Note that the point step size is 12. See this guide for more info on pointcloud data message data

Point cloud data will look very different from image data, since the data field is constructed very different from BGR image formats.

I have replicated these results in a starling2 as well, with voxl-mpa-to-ros2 dev branch:rospc_.png

Note that you may need to spin up a static transform to see the pointcloud data in ROS:

ros2 run tf2_ros static_transform_publisher 0 0 0 0 0 0 map world

@jonathankampia Yes, it would require modifying the "tones" in whichever esc param file you're using. For example for starling 2 it is defined here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-params/D0014_starling_1504_3000kv_ms_props/D0014_starling_1504_3000kv_ms_props.xml?ref_type=heads#L90

@wetherbeej ,

VOXL2 does not have ability to un-invert the SBUS signal, so you cannot plug in a standard SBUS receiver directly into VOXL2. However, we offer VOXL2_IO board, which supports standard SBUS input and will send the SBUS data to PX4 using standard UART.

https://docs.modalai.com/voxl2-io-user-guide/

If you don't want to add another board and if you find a receiver that is capable of outputting "inverted SBUS", which is actually using standard UART levels, you may be able to use the PX4 standard sbus driver. However the PX4 sbus driver is not currently built for VOXL2 because it is requires some support of UART port, which VOXL2 does not support (specifically inverted signal level and maybe some other options).

Long story short, if you want a solution that will just work, it is better to use our VOXL2 IO board, but if you absolutely do not want to add another board to the drone, then you will need a rx with inverted SBUS + modify PX4 sbus rc driver to work on VOXL2.

Alex

Hi @Jeremy-Frederick
Can you please provide some pictures?
It almost sounds as if you have a faulty RJ45 jack, but these are tested in factory before shipping.
If you can get some close ups of the non-working RJ45 and the LAN7500 chip, that may help.

And, can you clarify that you have Qty-2 M0062's and one works, yet one doesn't? Did the faulty one ever work for you? Was the faulty one in any type of handling mishap (like an accidental drop/fall)?
The RJ45 has integrated magnetics to save space (which is why it is so tall), but that makes them more vulnerable to shock failure than typical RJ45's.

One thing I do know that may also occur is the jack can be installed slightly tilted, making it hard to seat the RJ45 cable in firmly. There is an odd feature on the connector that sometimes allows it to seat at an off-angle, slightly pointing down making the cable slightly interfere with the PCB (but still ok to insert, since as I mentioned, we tested at the factory). Also, the metal along the sides of the RJ5 may also be stiff, preventing a smooth insertion, so sometimes just inserting the RJ45 cable a few times making sure you get that nice tactile "click" may be what is needed to ensure the contacts are engaged and kinda "breaking in" the stiff connector.

@Bernhard , you may be missing a step, if you want to stream the encoded stream using RTSP protocol, please take a look at voxl-streamer, which is our standard package : https://docs.modalai.com/voxl-streamer/

voxl-streamer can perform the following functions:

receive unencoded yuv (or raw8 monochrome) images from camera server and encode them using VOXL2's hardware encoder (using gstreamer + OMX api) and serve the encoded video as rtsp service receive encoded video stream from camera server and serve the encoded video directly

To play the h264 / h265 stream you can use VLC as Zach mentioned, or ffmpeg / ffplay:

ffplay rtsp://<board-ip>:port/live

port number is printed when you run voxl-streamer (port can be modified with a command line argument)

Alex

Hi @Alessandro-Voltolina
Not quite. Close.
We use the 0.9mm mate height on the ToF side (that mates with M0178) to ensure clearance to the caps at the connector.
https://docs.modalai.com/M0178/#pin-out-p1

Note on that page, we show over 1.2A of current draws at times (and it can be more if you adjust exposure ), so your solution needs very thick copper for power and return. Hence why our flexes are very rigid. They are nearly 95% copper density on all layers, with more than 65% of the copper for power feeds.

If you wish to design your own, feel free to let us review your design. Just tag me again if you want that, and we can reach out to you using the info you provided to register on the forum.

Also of note, we DO have another solution (it is a flex too) that is longer, but wider. It is M0170 Rev B. We have not released it yet since it was for internal dev to support all use cases with these new Molex connectors, but we may have it listed for sale soon. You are not alone in needing longer lengths. But, the length here is not something that can be extended indefinitely. Due to the power draw, plus MIPI traces, you still want to keep the distance as short as possible <100mm or so. M0170 is ~75mm long, so it adds about 20-ish mm more than M0177, but it also blocks one of the mounting holes on M0173 (it was designed first for dev as I mentioned).
Here is an example picture (M0180 is a "sample" run we did with a different vendor and is the same, but M0170B will be the product):
ef14de75-5d9b-4834-bc08-e4bcb5bc43b5-image.png

Hope this helps.

@Alex-Kushleyev I never uploaded any parameters, just used both escs out of the box. maybe that caused the issue?

@Moderator I am aware. I've been using this drone for research purposes and I always make sure to follow safety guidelines. Thanks, I'll follow these instructions.

@jonathankampia can you go into voxl-vision-hub.conf in /etc/modalai and ensure you have offboard_figure_eight set to off - I have a feeling these offboard setpoints are interfering with your code.

LMK if this fixes it.

Zach

@itsnav, can you please clarify whether the alternate camera you testes is the same IMX678 or it is a camera of different type?

I would recommend trying a different extension flex, which connects the camera to VOXL2.

Alex