No, we don't have an EU marking label.

@JP-Drone In my case, I was using the rb5 so the correct service was voxl-px4-imu-server, which was already running. The qvio, vison-px4 takes imu from imu_px4 not imu0. This is specific for the rb5.

@Alex-Gardner Great, thanks.

@Alex-Gardner Will we be notified when the new version is available?

@m1baldwin I think things will work as you expect if you first run voxl-send_command hires stop_ae. You may also need an update to the voxl-camera-server code, refer to this post.

@mirasul This is most likely a hardware issue in which the WiFi chip on the VOXL has either failed or the solder connection between it and the board has failed. I would recommend sending it in for an RMA: https://www.modalai.com/pages/rma

@modaltb What do you suggest I should do then? Do I need to flash the board? Or take it down a version?

@Vinny Just re-reading my last reply to you. The wording of the first sentence may be confusing, so rewritten... ... I'm not claiming that the "ModalAI USB-expansion add-on board" is doing anything wrong....

@Alex-Gardner I installed the 0.8 on the voxl, and mow I'm trying to configure the voxl flight deck for a new drone, but it seems to not work at all. I chose the frame type and once applying the modification, the system restart as normal. Once restarted, it ask again to chose the frame type, it doesn't keep the previous settings. Have you any idea what can be?

it's not possible for a flight controller to have PID parameters for an unknown drone. Every drone has different tuning parameters. We sell the VOXL m500, pre-tuned and flight tested, just for this purpose.

@Chad-Sweet What is the "basic drone bring up process"? I can fly it in manual mode, it's not easy to fly, but I felt like its more due to my skill level as its behavior from virtual joystick was somewhat similar to when I tried virtual joystick with your RB5 drone. It does drift noticeably. I think this drift is excessive but again, I'm not sure if it's an issue with the drone or my skill level using virtual joystick. It didn't seem to respond to virtual joystick inputs in position mode but I didn't extensively enough test that mode. I'll test that mode again and see what happens.

The best place to start would be try to reinstall the Flight Core firmware. It sounds like the VOXL side of things is OK. The most common failure mode for Flight Core is plugging USB into the R/C port. Any chance that happened?

I haven't tried it but I was just able to publish to /mavros/setpoint_velocity/cmd_vel_unstamped and the motor speed appeared to respond as expected when testing without propellers. This only works if the drone is set to offboard mode.

Thanks. I got it working and it appears to be calibrated. It also appears to be responding as intended with MAVROS when I publish to /mavros/setpoint_velocity/cmd_vel_unstamped I tested with props off and powered via battery. I published 0,0,1,0 corresponding with vertical speed of 1 m/s up and the motors sped up. I then published 0,0,-1,0 and the motors slowed down as expected.

The hires channel was renamed to hires_preview, it's identical otherwise

@Gyeongmin-Kim if the board is too hot to touch, then that is an issue. Did anything change between now and ten days ago? Can you send a couple of close up, high-resolution photos of both sides of the board?