Posts made by Matthew Wellner

@Vinny - I apologize for not seeing your response until now! I was wondering whether or not I could use the LTE carrier board attached to USB, but without being connected using the VOXL2's main connector. I thought there was some reference to using the carrier board like this in some older documentation, but I'm guessing it isn't possible with the current hardware.

It looked like there used to be a way (or maybe a different module) to run the LTE carrier board in "USB mode". Is that still something that exists and are there directions for doing so?

Thanks!

@Moderator thanks for letting me know. I have a here 2 laying around. I'll just use that instead.

@Vinny - I could, but how would this work? We'd need the board in NC by Monday afternoon. Is that even feasible?

Thanks,
Matt

@Vinny - We have a demo for a government customer next week that I was hoping we didn't have to cancel. Is there anything short of an RMA that we can try? We can't use the Q
Quectel modem since it's not NDAA compliant. Also - how do I get enough reputation points so that I can post faster than every 2 minutes?

@Vinny - both carrier board have their respective modems installed.

@Vinny - Quick update. The old VOXL2 that wasn't working is working when not setup with the Sierra wireless carrier board. It also works when hooked up to the Quectel carrier board. I haven't tried hooking up the Sierra wireless board to it again yet, but I have a feeling something wonky is going on with the Sierra wireless board / modem.

Hi @Vinny - We had a new board that we purchased this week to replace the board that wouldn't boot. I tested the board before we added that new board into the rest of the system and I was able to adb to it. After adding the 5G carrier board (Sierra wireless), I went to set the board up and now it won't show up with adb anymore. Any ideas?

Thanks,
Matt

I wasn't able to determine whether or not I can use a Here3 GPS over the CAN port on the Flight Core V2. Is CAN supported on the Flight Core v2?

Thanks!
Matt

@Vinny - I definitely didn't see that. Thanks for taking a look. Realizing that it would be impossible for you to really know, is there anything that we could have done to avoid the crack in the connector? We didn't crash / forcefully insert the carrier board into the VOXL2.

Do you think the cracked connector caused some sort of other HW failure? I'm only asking because I tried getting ADB to come up after I removed the carrier board and I was having the same issue.

Do we just need to buy a new board or will the RMA process be a less expensive approach?

Matt

Hi @Vinny

Here are the close up pics of the connectors - https://photos.app.goo.gl/mU3oUiArJ6j3WisL6

Thanks!
Matt

@Moderator I used the Sierra wireless carrier and modem that came preassembled. Previously we used a Quectel modem in a carrier made by you guys for the Quectel modem and the VOXL 2. Both of those setups worked as expected previously.

@tom said in Failed Unbricking:

@Stefan-Amundarain Okay if you have a QRB5165-based VOXL 2 then it looks like you're flashing the correct image through QDL. After the unbricking procedure try powering off your VOXL 2, turning the SW2 switch off, and powering the board back on.

Then connect VOXL 2 to your host PC via. usb and run lsusb on your host machine and post the output here. It may take some time for the board to boot.

@tom - I'm sorry to jump on this thread, but I think I am having a similar issue where I go through the QDL procedures, switch SW2 off and I can't successfully make it through an installation of the SDK (I tried 1.1.3 & 1.2.0 with and without the -w command). My lsusb command shows the VOXL2 connected as a Qualcomm bulk device (the exact output is on another computer).

Again - sorry to hijack this thread, but I seem to be having a similar issue.

Thanks!
Matt

Our VOXL2 stopped responding over adb after we installed our new 5G carrier board, but we still had access through tailscale. I went to update from 1.1.3 to 1.2.0 and after going through the unbricking procedure and using fastboot to reflash the SDK, I can't get adb to see the VOXL2. I get stuck at the waiting for ADB portion of the flashing sequence.

Please let me know if there is anything I can try.

Thanks!
Matt

Hi,

Has anyone used the Hadron 640r with the VOXL2 with or without the Gremsy gimbal that was produced for the Pixhawk / Herelink and RB5 board? https://gremsy.com/products/product-gimbals/tiny-gimbals/g-hadron

Thanks!
Matt

Hi,

I had this working last week, but since the beginning of this week I am no longer able to get GPS information to display within QGC. I am able to get the GPS status from "px4-listener sensor_gps" command. I am running a VOXL2 / M0054 voxl suite 1.1.3-1.

Has anyone run into this issue?
Thanks!
Matt

@Alex-Kushleyev thanks! I responded. The ESC parameters file were exactly as you example except for the calibration parameters (the 3 numbers we need from the calibration routine). I averaged the numbers I collected from running the calibration on each ESC.

@Alex-Kushleyev Is there a way to share it privately? Otherwise I can send it to the link you already shared.

@Alex-Kushleyev I'm sorry to have to ask this, but is there a way to upload the logs via this interface? When I try and upload a file I get a permissions error.

@Alex-Kushleyev sorry for the slow response. I never actually test flew the setup outside of a few quick lift offs because we were making some housing changes. I thought the platform just needed to be tuned.

I have run 3 different motors with similar behaviors - sunnysky 4004 (400kv), tmotor 4004 (400kv) and tmotor 4006 (380kv) all at 6s voltage with 11" props. I also tried 10" master airscrew props with the 4006s.

I swapped the 0134-6 ESC with a 0138 ESC yesterday after the the 0134-6 got hot enough that, I think, one of the motor wires desoldered itself.

Thanks again for the help!
Matt