LNX triggered by an encoder, Y-axis resolution acquired from Mech-Eye API matches the trigger interval, differs from Y-axis resolution in Mech-Eye Viewer

Mech-Eye SDK Development
1

Problem

As shown in the figure, when the LNX laser profiler is triggered using an encoder, the Y-axis resolution parameter acquired from the Mech-Eye API matches the trigger interval, but differs from the Y-axis resolution parameter in the Mech-Eye Viewer software.

77cbe318d1f1777c1c54b18a966b5df5abf5afa0_2_640x500

Explanation

The situation described above is normal, and the explanation is as follows:

  • Mech-Eye Viewer: For both encoder trigger and fixed-rate trigger, the Y-axis resolution set in the Mech-Eye Viewer software is used as the distance between two spots, which is for convenient display in the Mech-Eye Viewer software.
  • Mech-Eye API: For fixed-rate trigger, the Y-axis resolution acquired from the Mech-Eye API is the Y-axis resolution value set in the Mech-Eye Viewer. However, for encoder trigger, the Y-axis resolution acquired from the Mech-Eye API indicates the actual distance between two lines triggered by the encoder.
  • In other words, when the Mech-Eye API is triggered by an encoder, the value of the Y-axis resolution acquired from the Mech-Eye API is unrelated to the Y-axis resolution set in the Mech-Eye Viewer.