Posts made by Vinny

Hi @VictorG
Our team went back and quarantined all units again and we have some working.
I'll request they get shipped today, otherwise very soon!!
Again apologies for all the delays, distractions, and stress on this!!
Thanks for your patience.

Hi @jonathankampia
Hate to hand you off but this is out of my realm now.... I think @tom is more suited for helping on this front if we are sure it is no longer a HW issue.

Hi @jonathankampia
Yes, 7.5W will certainly brown out the 5V.
An external splice is a great way to go/try.

By chance, to rule out SW concerns, do you have a normal VOXL 2 ("classic") M0154 board and USB expansion with M0130? That M0130 design will supply 2A of VBUS on the 10-pin USB connector.

Keep us posted.
Thanks!

Hi @VictorG ,
That is unacceptable of us. I worked directly with operations to screen 100% of these units so I need to dig in and find out what happened.
So sorry and we'll get this sorted out.
FYI @Moderator

Hi @TomP
Looking pretty grim...
That specific signal is all buried at least 3-7 layers deep directly from that pad and it hits other BGA devices right in the pad.... no exposed traces, no exposed pins at all...
You'll have to find a different UART port or some other plan B.... sorry.

Hi @TomP
I'll look right now, but can you please also send me a zoom in clearer picture of that area?
I think I see other damaged parts, so I want to double check and advise what else could be impacted.

Thanks!

Hi @jonathankampia
Can you please post some pics of your setups?
I cannot tell exactly how you are using J3, and which version of VOXL 2 Mini do you have? M0104 or the new rounded corner M0204 with fixed SS lines?

Do you have a spec of the SSD you are trying to use? What other 5V peripherals are you using. We could be pulling too much current, since V2 Mini only has 900mA TOTAL 5V support so other 5V peripherals will eat into that budget.

Thanks!
Vinny

Hi @salman3141
I'm not sure of all the details of which kits/skus are no longer available.
Please feel free to start a new forum post asking about SKU availability and the appropriate folks will respond.

I do know our team is working on improving GPS performance across our entire fleet and are planning on better and more tightly integrated custom designs in the future. I cannot however promise any availability dates but we are aware of some performance inconsistencies and have not ignored it.

Hi @salman3141
We are tailored for Sierra wireless EM9291, but also some of the older EM919X (the spec we designed to is 919x), so the EM9291 was considered a drop-in replacement to the EM919X.

You risk damaging your modules if you install other than the above EM919x or compatible units.

It would take a considerable effort by our team (several weeks), assuming we had all the hardware integration docs, to validate if other modules can work (even with HW mods) and be supported by our SDK.

Thanks

@Jaroslav-Richters
Yes, we are aware there is a component on our ESC assemblies and other circuit card assemblies (CCAs), specifically, the Vishay IHLP series inductor, that is at risk of visible oxidation.

We’ve looked into it closely and want to provide a clear update for everyone:

Performance: Vishay, the inductor manufacturer, has confirmed in a published white paper that this oxidation does not affect electrical performance or reliability. There is no need for concern or an RMA, functionality is not impacted. If desired, you may clean any visible rust using your preferred cleaning agent suitable for your production or maintenance process. For full details, you can review their white paper here:
Vishay IHLP Oxidation White Paper (PDF):

Root Cause: The visible oxidation is most likely related to our use of a water-soluble flux during assembly, which requires steam cleaning to remove residue. However, given Vishay’s acknowledgment of the issue, there may be other factors at play and not just our processing steps.

Mitigation: We have already begun including desiccant in all ESD shield bags for ESC assemblies and any other CCAs with the IHLP inductor. If further action is needed, we are prepared to implement additional measures, such as extended baking of the boards after cleaning or applying protective coatings to the inductors.

Commitment: You can expect improvement in upcoming shipments. We take cosmetic quality seriously and will continue to monitor and enhance our process as needed.

We appreciate all customer feedback; clear communication about issues like this help us get better. Thanks for helping us raise the bar.

Hi @Manoj-Kashyap
As per that thread, we EOL'd M0169, so support should move to M0171.

However, if you already have some M0169's, then this cable which will replace your normal MCBL-00001 will do the trick:
https://docs.modalai.com/cable-datasheets/#mcbl-00095

Purchase link here: https://www.modalai.com/products/mcbl-00095

Hi @VictorG
You should RMA the FlightCore and we should replace it. Just mention this thread or place a link to it in the form:
https://www.modalai.com/pages/rma?_pos=1&_sid=190e46152&_ss=r

We do not yet have a replacement set of cables, under normal circumstances, it takes us 6-8 weeks to get more, so we are trying to see if we have any small batch in our inventory to hold us over and replace every bad cable that we shipped.

If you want to try to re-pin your cable for the interim (you will not need to send it back, we can just replace it when we get more), try this link:
https://docs.modalai.com/cable-userguides/ and at the bottom are tips for re-pinning

or you can just search youtube for s JST GH re-pin tutorial and I'm sure you'll find plenty of good techniques. All that is needed is tweezers.

@Martin-Lukac , @VictorG
Yes, we are working a replacement solution.
Exactly what @Martin-Lukac said is a temporary solution by swapping the conductors until we can source replacement cables. We might need a few weeks honestly.
Any HW that was compromised by this issue is an no-brainer replacement by my standards, and I will help ensure our production and operations team replaces any HW at jeopardy of this issue promptly. We have the HW in stock to replace, just not the USB cables as of yet.

We apologize for this issue. We actually had that batch of cables in stock for over 2 years and our sample lot from a different sealed bag in the same shipment that was tested did not experience this issue, so we were caught flat footed and we will put in better inspection processes to ensure this does not happen again.

Thanks!
Vinny

Hi @hula
YOU ARE CORRECT!
I found a whole bag of mis-wired MCBL-00010's in our inventory.
I'll work with our @Moderator to figure out a plan.
We will likely need to setup an email where any customer can let us know if they have offending cables and we will send replacements promptly.

Hi @hula
Interesting. I will investigate. The cable appears as it should according to our tech docs and every batch is sample tested but I will inspect further and respond tomorrow.
https://docs.modalai.com/cable-datasheets/#mcbl-00010
Thanks
Vinny

HI @Jetson-Nano
Your welcome. Apologies I cannot find anything blatantly wrong with your design at the document and layout level.
If your PCB still does not work after all these reviews and positive affirmations, then you may very well have a fabrication issue with your PCB.
The only way to verify that is to try your own net-by-net buzz-out using a DMM to ensure your netlist matches the expected schematic. If that all matches up, then you may be suffering from poor assembly/soldering. The socket for the lepton does require a reflow oven/line and cannot be hand soldered, unless you have an IR tray/heater and a way to deposit solder paste on the pads.

Any further debugging I could offer would require physical samples of the hardware to validate everything.

Hope that info helps!

Hi @Jetson-Nano I have reviewed your schematic again and your layout files.
I cannot see any reason why your design will not work.
The only suggestion I have is to increase your capacitors here to 1uF:

But, otherwise, your layout is OK (some improvements can be made, but nothing is detrimental):

• Pin 1 correct on connector, socket, LDO, other ICs
• Vias are picking up planes correctly
• Voids where expected
• Generous copper trace thickness

The one issue I think I might have found is your reference designators do not match the schematic between the layout. So, I'm wondering if you are installing parts from the BOM in incorrect locations...
For example, the cap on the output of the LDO is "C6" in the layout, but "C7" in your schematic:

And, your resistors are also not in sync. R1 and R2 in the layout are for the Ic2 expander, but in the SCH, it is for your FLIR module and not R5/R6 as in the SCH:

and there are a few other examples. So, I just think perhaps your layout reference designators are not synced to your design.

J1 should be J2, and R3/R4 on the layout does not exist on the SCH.

So, maybe this is where your issue is. I'd recheck the annotation between SCH and Layout, and be sure you are installing all the correct parts in the correct places.

Hope this helped!
Keep us posted.
Thanks!

Hi @Jetson-Nano
I received your data package and will review it this evening.
Thanks!
Vinny

Hi @Michael-Mortensen
Please see the post to Victor about using the power module instead of just USB.
Let us know if that helps.
Thanks!

Hi @Martin-Lukac
Well that's not good. Your board will not work with that chip busted off like that.
Please use our RMA process and we'll get this assessed for for you:
https://www.modalai.com/pages/rma