Good morning,

Our team received our newest parts in the mail yesterday evening and we are working on integration today. Parts included a new 4 in 1 ESC and a WiFi Dongle and the M0125 Expansion Board to connect the WiFi dongle to.

After proper installation and applying power, no lights show on the Alfa module and no network is detectable. In the past we had M0078 expansion module and when setting up the WiFi dongle we needed to engage the fast boot button during first power up. Is there a step with this new board I am missing? Should power be flowing natively to this M0125 board? WiFi module works and lights flash when plugged into my computer.

set up below

@rdjarvis @Moderator

Flight log from second flight:https://logs.px4.io/plot_app?log=4bb1781f-abc9-49bc-a713-e03a7629b074

a few screenshots from qvio logger while on the bench. Can get some from the air potentially.

video of QVIO Overly from web portal. This was two flights, one in manual, the second in position. drone becomes uncontrollable in position mode and keeps attempting to climb with no throttle input or extremely little
(https://drive.google.com/file/d/1fBXyT1QNDqnYAGuz7ahqJcGqRUeZFnU-/view?usp=sharing)

I tried the old board from our other aircraft, it worked just fine with both the old and new wifi dongle/Alfa Module.

upon further investigation, it seems the wrong parts have been shipped with my order. As per the ModalAI website, the kit includes the following parts:

"What's Included
Carrier Board with 5G Modem and Antennas

(1) MCCA-M0151-1-00: VOXL / VOXL 2 USB 3.0 Expansion Board with Fastboot v2, Board Only
(1) M10000270: Alfa Network AWUS036ACS 802.11ac AC600 Wi-Fi Wireless Network Adapter, Small
(1) MCBL-00041-1: 4-pin JST GH to USBA Female Cable (150 mm)
(1) MHW-M0030-1: VOXL Modem Add On Hardware Kit"

Why was a part no longer produced shipped instead? It is frustrating to wait a week for the product to arrive only for it to be the wrong part. This is absolutely unacceptable.

Hello, we are working with a Voxl2 board and 4-in-1 55amp Voxl FPV style ESC. we have been flying/building our aircraft with no issues binding and controlling with the Spektrum DSX transmitter. With our most recent build, when we arm the aircraft, it immediately goes into land flight mode as the RC loss failsafe gets triggered and the transmitter no longer communicates with the aircraft. Prior to arming we have full control, able to view our switch and throttle movements on the Radio page of QGC. After arming we have to do a full power cycle of the aircraft before our transmitter will be recognized via QGC and the aircraft again. The orange light on our rx stays on the entire time the transmitter is turned on, indicating that it maintains connection. We thought this might be a heat issue, but this happens from a cold start as well. our aircraft does contain active cooling and our IMU and CPU usually do not reach temps above 60C while on the bench.

@tom just spent about 20 minutes outside with it, no luck. We will try a different GNSS module and see if its the equipment or the setup.

We recently connected a Matek M10Q GNSS/Compass to the J19 port of our voxl2. we have a green light on the GPS, and when in the window a blinking Green to indicate GPS fix. We are able to calibrate the compass in PX4, but no GPS data is being recieved. We have the GPS wired correctly. based in the docs.modalai voxl2 onboard sensor user guide. what other steps can we take to troubleshoot? I have also checked voxl-px4.conf and GPS= AUTODETECT

@Alex-Kushleyev this issue was due to poor amperage out of the shore power module. swapped for a different power source and issue was resolved.

Good day,

Just received a new batch of the 4-in-1 FPV ESC’s and had a weird boot up with the first one I tried.

The power out for the voxl also is not staying at 5v and is fluctuating between 1v and 5v when measured with a multi-meter.

Any fix for this? Is this a boot up sequence? We have not faced this before today. This is a brand new ESC that is on its first power up.

Link to video:
https://drive.google.com/file/d/1BhnvUNBwsZ-l2p2VrkCFHZtQENIuKfLA/view?usp=drivesdk

Good Day,
I am working on calibrating a new motor/prop combo and i am not able to get a good calibration result. I have been following the calibration.md doc and have had success in the past.

We are trying to use Tmotor p2306 1900kv with a Gemfan 5.1" tri-blade. We are using a 4-in-1 FPV Racing ESC from Modalai. i have attached the most recent calibration graph. is there a way to get a better start than just trying to find a matching motor file already made? I have preformed a min rpm and max rpm test and input those figures into my param file as well as double check motor KV, pole pairs, start-up rpm and have tried to "massage" the a0, a1, and a2 with varying results. sometimes POW doesn't surpass 48 and RPM's are stuck at 12000, other times we have gotten up to POW: 62 with RPMs close to 16000. Max RPM is close to 23000 and min is around 2800 based on the values and scripts in the https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md?ref_type=heads .

any help or advice would be greatly appreciated.

Hello, we are working with a Voxl2 board and 4-in-1 55amp Voxl FPV style ESC. we have been flying/building our aircraft with no issues binding and controlling with the Spektrum DSX transmitter. With our most recent build, when we arm the aircraft, it immediately goes into land flight mode as the RC loss failsafe gets triggered and the transmitter no longer communicates with the aircraft. Prior to arming we have full control, able to view our switch and throttle movements on the Radio page of QGC. After arming we have to do a full power cycle of the aircraft before our transmitter will be recognized via QGC and the aircraft again. The orange light on our rx stays on the entire time the transmitter is turned on, indicating that it maintains connection. We thought this might be a heat issue, but this happens from a cold start as well. our aircraft does contain active cooling and our IMU and CPU usually do not reach temps above 60C while on the bench.

@Alex-Kushleyev We had a second ESC that faced this same issue.

Like with the previous board, i performed a voxl-configure-mpa which reset the board. After re-uploading the parameter file i faced the same "ticking" during motor calibration.

I then updated the voxl-esc-firmware as per your previous instructions from v0_39 to v39_20 (the newest available firmware for our M0138 ESC. Video of failed or poor calibration below.

https://drive.google.com/file/d/16_ey6Qj7q49LfWXzKo001pBkz8PH4Ls2/view?usp=drive_link

@Alex-Kushleyev As i mentioned in my original post, i experienced this issue with a different ESC as well. I am going to attempt the same steps (reupload SDK, reconfigure MPA) and see if the issue resolves itself when it updates or re installs the voxl-esc-firmware.

@Alex-Kushleyev update**
While attempting to update the esc-tool-bin our (apt-get install updgrade) our voxl suite was removed. ( voxl suite: [blank])
I went ahead and reuploaded SDK 1.3 and after reconfiguration and a new voxl-configure-mpa the ESC seems to be working fine. I just was able to complete what seemed to be a solid calibration and spin test, results are attached. Still no current reading on id 3, but i will update you if this issue persists. Next steps are finishing calibration and attempting flight. I will update you as our results.

@Alex-Kushleyev With voxl-set-cpu-mode perf. updating voxl-esc-tools now to see if that helps.