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

Livox on diferent subnets #190

New Issue
Open
opened 2022-11-04 12:36:02 +01:00 by fbzavaleta · 2 comments
fbzavaleta commented 2022-11-04 12:36:02 +01:00 (Migrated from github.com)
Copy Link
Copy Source

Hello,

We are working with two diferent subnets, trying to acess from computer(subnet 1) to the livox(subnet 2). The reason is because we are trying to acess the sensors, conected to the router from a instance EC2.

When we use livox viewer, we ca get the cloud point, but when we are trying to do this using the sdk, the sensor lost conection.

Can you please help with this network issue?

best,

Hello, We are working with two diferent subnets, trying to acess from computer(subnet 1) to the livox(subnet 2). The reason is because we are trying to acess the sensors, conected to the router from a instance EC2. When we use livox viewer, we ca get the cloud point, but when we are trying to do this using the sdk, the sensor lost conection. Can you please help with this network issue? best,
MizzouRobotics commented 2023-02-04 23:43:37 +01:00 (Migrated from github.com)
Copy Link
Copy Source

any insight on this?

any insight on this?
MizzouRobotics commented 2023-02-06 21:29:33 +01:00 (Migrated from github.com)
Copy Link
Copy Source

One interesting thing I found in the docs is that while the activation udp is 65000 and 55000 respectively. The sdk sets a random ip to be the received data for pointcloud and imu... With this in mind, it's likely that networking issues are implicit networking issues. At least, this was my issue, I was able to solve it be opening all ports for a cheap hack, but I'd love a more programmatic approach in the future.

One interesting thing I found in the docs is that while the activation udp is 65000 and 55000 respectively. The sdk sets a random ip to be the received data for pointcloud and imu... With this in mind, it's likely that networking issues are implicit networking issues. At least, this was my issue, I was able to solve it be opening all ports for a cheap hack, but I'd love a more programmatic approach in the future.
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#190
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?