mmr/Livox-SDK
Archived
1
0
Fork 0
Code Issues 105 Pull Requests 11 Actions Packages Projects Releases 9 Wiki Activity

Connection issues #250

New Issue
Closed
opened 2026-01-07 01:23:12 +01:00 by jeremy-rutman · 1 comment
jeremy-rutman commented 2026-01-07 01:23:12 +01:00 (Migrated from github.com)
Copy Link
Copy Source

Hi
I have a livox avia to which I have connected with no problems using linux and livox viewer 0.1 in the past. I used an openpylivox fork to get point data entirely in python which was great.
However now I have problems connecting both from Linux and Windows.
I switched ethernet cables to no effect.
I don't have an extra thick black cable going from little grey livox box to camera so I can't check if that is the problem.
I did have my power supply set on current limitation for a few minutes , causing it to spin up then down a few times, would this cause damage?
Once I discovered the current limitation I allowed full current of course and now the device spins up no problem.

I should add, I am able to ping the lidar but even if I set the IP info manually in the viewer, the device is not seen (previously, the device is seen without needed any ip info to be input). I set a manual interface IP, netmask and default gateway as recommended in the manual, both when attempting from linux and when attempting from windows. Hopefully the log files will allow some light to be shed.

Any help appreciated -
JR

LivoxViewer2.log
LivoxViewer2-backup-2026.01.07-06.12.23.log

Hi I have a livox avia to which I have connected with no problems using linux and livox viewer 0.1 in the past. I used an openpylivox fork to get point data entirely in python which was great. However now I have problems connecting both from Linux and Windows. I switched ethernet cables to no effect. I don't have an extra thick black cable going from little grey livox box to camera so I can't check if that is the problem. I did have my power supply set on current limitation for a few minutes , causing it to spin up then down a few times, would this cause damage? Once I discovered the current limitation I allowed full current of course and now the device spins up no problem. I should add, I am able to ping the lidar but even if I set the IP info manually in the viewer, the device is not seen (previously, the device is seen without needed any ip info to be input). I set a manual interface IP, netmask and default gateway as recommended in the manual, both when attempting from linux and when attempting from windows. Hopefully the log files will allow some light to be shed. Any help appreciated - JR [LivoxViewer2.log](https://github.com/user-attachments/files/24461825/LivoxViewer2.log) [LivoxViewer2-backup-2026.01.07-06.12.23.log](https://github.com/user-attachments/files/24461824/LivoxViewer2-backup-2026.01.07-06.12.23.log)
jeremy-rutman commented 2026-01-07 22:54:20 +01:00 (Migrated from github.com)
Copy Link
Copy Source

It seems the livox viewer 0.11 is the only one supporting livox avia. That does work on windows, but 0.10 on linux does not seem to work (although I seem to have had it working in the past). Version 2.0 does not support the avia for whatever reason.

It seems the livox viewer 0.11 is the only one supporting livox avia. That does work on windows, but 0.10 on linux does not seem to work (although I seem to have had it working in the past). Version 2.0 does not support the avia for whatever reason.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
eeeck (Erick)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mmr/Livox-SDK#250
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?