Livox Converter 2.0 Is really mandatory? #249
Assignees
eeeck (Erick)
Clear assignees
eeeck (Erick)
No Assignees
No due date set.
Dependencies
No dependencies set.
Reference: mmr/Livox-SDK#249
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello.
I saw this cable on Aliexpress:
https://ae-pic-a1.aliexpress-media.com/kf/S7d975ffdc935445eabe7739f2eb41652K.jpg
So makes me wonder if my battery which already has a voltage regulator, supplies stable 12V DC if I could get rid of the box stage and use a cable like the one in the picture.
If only voltage rgulation is taking place, I would say yes since there is the power cable, the 3cable sync cable and the ethernet part...
I made my own PCB to interface directly with the Livox Avia replacing the heavy cable and convert box and providing a ethernet connection that can be plugged directly into a Raspberry Pi. If you need some help let me know. I'm considering releasing the design (kicad PCB) as an open source repo soon.
Sorry I meant to post from this account. This is a test PCB for a future larger PCB board for the Livox Avia lidar. I wanted to make sure the M12 12 pin aviation connector footprint was correct and that it was just a matter of connecting two twisted pairs from the ethernet cable without any magnetics in between. It worked. In this case power is provided by a USB-C PD trigger board set to trigger 12V. (Note if you're bypassing the converter box the allowed power voltage range is lower that what the converter box will accept). Also note that not all PD power supplies will supply 12V and may fall back to 9V which is below specification. Also note there are subtle difference in some of the pins across the various Livox lidars. So even though the connector is the same, each device model will require a custom board (an unfortunate design decision).
(Also this is not my finest work. The M12 female socket is deliberately not fully soldered because I only had one and need to make it as easy as possible to remove it again :-) Those connectors are hard to source. They are currently available in the DJI store at EUR 11 each.
NEAT!
On my end I purchased the cable I posted originally. I've to check first each cable is mapped as the livox spects, as I fear power cables may not be properly mapped :D
I agree not mantaining an standard even with same pin number is wild.
Someone decided that it would be nice to put the cable section instead of the pinout... So I'm scared to use the cable I got on Aliexpress... The avia pinout on the automotive connector seems the same tho.
On DJI store, the M12 extension cable is sold as compatible for 3 models hence, seem safe to asume the pinout in the Horizon and Avia are the same:
Looks like the calble claims are legit, The pinout in the connector is the same as in the Avia. And the Extension Avia cable woks aswell for the Horizon as per DJI store, hence have same pinout.
Since the Pinout id from the mid 360 and Avia are the same and the functions of each are same too, we can conclude the breakout cable from Aliexpress claiming compatibility for Horizon-Avia & Mid 360 is legit.
I only need to add the RS485 to convert the PPS TTL in between the GPS and breakout cable.
Pigtail on the Livox Horizon was a terrible choice btw, wish had a clean connector like the Avia. But no one in Livox seem to give a **it about anything anyway.
I don't have detailed notes to hand, but I have two Livox types: the Avia and the Mid-360 which I had concluded are sufficiently different that I would not dare to try to interchange the adapter cables. In particular take a careful look at the inner ring of the M12 connector: pins 10, 11, 12. They have different functions but more worryingly may have different signal voltages.
It is very unfortunate that Livox did not release a reference design for the interface electronics for each model. Something happened to that company: in 2020 it was a hive of github activity. Now it's crickets. Which is such a pity because they are excellently engineered products and a great price point.
You're right!!. Dang!
I rushed my mid360 checking. Wishfull thinking betrayed me I guess. Will check again the aliexpress cableble pinout vs the Avia. Since Avia cable sold by DJI Claims AVIA and Horizon compatibility, and being from same era, deems somewhat safe asumption...
OK, so I gave a look to this with a bit more of calm.
In one end, there is the doubt wether Avia & horizon cable's/pinouts are equal. My asumption is that yes, heare is why:
The M12 extension cable is compatible with
Livox Avia
Livox Mid-70
Livox Horizon
DJI OFFICIAL EXT CABLE
Plus comparing the pinout of the automotive connector, since the M12 is not avialable in the Horizon manual, they're the same.
The pin numbering is the same in both cases too, no possition swaps.
When comparing the Aliexpress to the mid 360 manual, they match perfectly so the breakout cable is designed for the mdi360
BUT, as you nicely warned,
Between the mid360/aliexpress calbe there are pins that do not match
the pin ID on the conector is 1:1 when comparing the manuals, hence the missmatch is not because of missidentification
HENCE
On my end, I will need to check with voltimeter the continuity of the pins, in my case, if the cable mapping is true, I would need to make sure following pins receive the data
connector pin 10- 11-12 pps +-
Ground
Sync+ Input RS485_A, Pulse Per Second
Sync- Input RS485_B, Pulse Per Second
But now at least I've the vision of what is the problem. I hate to lose time with stuff like this, but at least seems like there is a solution.
edit: Timestamp sync related info as anyone getting rid of the box will need to have a look into this
https://github.com/Livox-SDK/Livox-SDK/wiki/livox-device-time-synchronization-manual
Ok,
so, What I did was to check every loose line and tag the pin where it goes to, with this can now follow the Avia's/Horizon, pin logic, all should work ok.
Thanks for documenting this!