USB Command Interface

[Jmeyer1292]

All of the Keyence commands can be sent over TCP/IP and USB. We currently do not have an implementation of a keyence::USBClient. For configuration in particular, this would be invaluable.

[robotsorcerer]

How do you set the ip address of the sensor? Did you have to use the Windows ip address setting tool or you configured a random ip address for the sensor? I find that I can communicate with the device from Windows using the profiled executables from the manufacturer but not with the default ip address of 192.168.0.1

[Jmeyer1292]

@lakehanne Currently all of the configuration for the laser is conducted through Keyence's Windows tool. This includes:

1. IP Address & Port
2. Program configurations (e.g. continuous trigger at 500 Hz on program 1).

I only ever created a couple of commands for requesting single profiles or changing program numbers. I theoretically have all of the documentation (assuming its accurate), so we should be able to do anything you want!

I had no idea that anyone else was using this stuff, so I'm excited to push it forward if that's the case. Let me know what you need.

[robotsorcerer]

Thanks for your prompt reply.

I am developing a Linux codebase for the LJ-V7300 scanner. I did a quick search on Github and found your code ( so thanks! 👍 ).

Basically, I want a code that will extract the profile map in a point cloud visualizer window and publish all retrieved points via ROS publisher commands.

After doing this, I will want to integrate an encoder that maps the position of the sensor on a rail it is mounted on to the world such that we can move the sensor along a rail and acquire a 3D profile in real-time through some reconstruction mechanism.

My problem for now is trivial. I cannot communicate with the sensor via the 100BaseT IP executable.

UPDATE (6:26pm ET): Fixed.

[gavanderhoorn]

@lakehanne: there are most likely no differences in how any of the LJ-V series profilometers interface over ethernet/usb.

I'm not sure how this would logistically work, but perhaps it might be an idea to complete the work that was started in this repository?

The only really major missing functionality is the configuration interface. Basic req/reply and high-speed mode streaming are essentially working.