Our VOXL2 stopped responding
-
@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 @Matthew-Wellner
To be honest, the outcome will be the same and you'll need a new board. The RMA process will just slow things down and the end cost is the same.
The likely cause of your failure is incorrect "zipper angle" during modem board removal. More likely we'd see it on J5, not J3 (to be frank, I have not seen a damaged J3 in many years... )
If the mating board is not inserted or removed "true" or "plumb", then you add pressure to the sidewalls of the connectors. So, care must be taken in the future to advise all users in your facility to pay attention to the zipper angle during removal and to be graceful with the mating cycles. Doing so will get you years and years of extended use. I have several products that are over 10 years old still using that 60-pin QSH/QTH series that work perfectly. They are rated for 100 cycles, but we get much much more in practice.
Hope this helped. -
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 -
Hi @Matthew-Wellner
I may need to call in the big guns here @tom
He is the modem software expert. -
Hi @Matthew-Wellner
Hopefully Tom can help too, so I tagged him in the last response, but can you let us know if the failure to ADB happens with and without the modem board plugged into the M0090 board?
In other words, can you remove the modem itself from M0090, but leave M0090 plugged in to VOXL 2?
Did you get the Modem from us as well, or just M0090-3-02
Also, to be sure, did you ever buy any Quectel carrier boards from us? M0090-3-01?
If so, please be sure you did not accidentally swap them around since the Sierra modem device will not work properly with the M0090-3-01 board. And, vice versa.(side note: M.2 standard is a very loose standard and many M.2 devices can only work in what they were sold into, especially B-key modems)
-
@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.
-
@Vinny - both carrier board have their respective modems installed.
-
Hi @Matthew-Wellner
That sure sounds like it to me...
Feel free to send in the M0090-03-2 board to us for RMA if you think that is the culprit. I'll get notified when it does and I can inspect it for HW issues and we'll run it through a test routine as well.
Please feel free to ping on me when you get an RMA number (and let me know that number) and I'll alert our production team to notify me when it arrives.
Thanks! -
@Matthew-Wellner
And, FWIW, your VOXL 2 with the cracked J3 will still work normally in most instances. It is just some plug-in boards may be more sensitive to that, so I'd delegate that specific HW to other purposes if you can. -
@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? -
Hi @Matthew-Wellner
I alerted our team to see if anyone has any other ideas. I can't promise production items or turn-around times (but some one might be able to
) -
What exactly is needed? A new M0090-3-02?
-
@Moderator That is what the high level failure description seems to imply.
@Matthew-Wellner Are you able to order another one? My team tells me we have them in-stock, and we can ask for expedite (but I can't assure that). Then we can process the RMA later if that works for you.
-
This post is deleted! -
@Vinny - I could, but how would this work? We'd need the board in NC by Monday afternoon. Is that even feasible?
Thanks,
Matt -
No @Matthew-Wellner , Our shipping dept is already done for the day and we missed UPS/FedEx drop-off times for next day delivery.
I can't offer anything other than consolation that we've had some of our customers be amenable to a demo with non-NDAA compliant stuff with our assurance we have a plan to switch over (especially yours since it is available and in-hand, but just not working at the moment).
I only wish I could probe your board remotely to help you figure this out... sorry.
