Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Announcement of the discontinuation of the LSV2 protocol #60

Open
CuriousCrook opened this issue Mar 26, 2024 · 2 comments
Open

Announcement of the discontinuation of the LSV2 protocol #60

CuriousCrook opened this issue Mar 26, 2024 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@CuriousCrook
Copy link

CuriousCrook commented Mar 26, 2024

Apologies if this enquiry is a little off-topic, but I suspect I've found the right specialists here.

I have been told that the LSV2 protocol has been discontinued and will no longer be available on newer CNCs in about 2-3 years.
The successor is the RemoTools protocol, but that seems to be a crappy Microsoft COM+ component.

Then there is an OPC UA server. It seems really intuitive, but it is only available for newer cnc. With this python opc ua toolkit I have already made first experiences in controlling a heidenhain CNC via OPC UA.

As far as I understood, I have two options:

  1. build a separate connection for old and new controls respectively:
    1a) old cnc = LSV2
    2b) new cnc = OPC UA
  2. write a Python wrapper for the RemoTools COM component and connect all controllers via it.

Does anyone have experience of using com components in python?
It seems incredibly complicated to me.

I am grateful for any tips.

@drunsinn drunsinn added the help wanted Extra attention is needed label Mar 27, 2024
@drunsinn
Copy link
Owner

Hi @CuriousCrook!

Personally I would go for your option 1. It might be a bit more work during implementation to get the same data via both protocols but probably still less of a hassle than option 2.

Another thing to consider is the OS you want your application to run on. If you want to support anything other than Windows, the COM solution won't work without something like wine which adds another layer of complexity. This was also the reason for me to focus on LSV2 since I needed a solution that can run on MacOS.

In the end I am also skeptical of the time frame for the final discontinuation of the LSV2 interface. The latest software version of the TNC7 still supports LSV2. The only "limitation" is the requirement to use a SSH tunnel for the connection. In earlier versions this was optional, now you have to change a machine parameter (see manual page 2318 under notes) to allow connections without SSH. I also think that there are too many applications like tool setters out there that only support LSV2 since it doesn't require a software option on the control. People would be very unhappy if the had to by a new tool setter because the bought a new machine.

@Andreas-strg
Copy link

Andreas-strg commented Jun 19, 2024

Heidenhain tools from TNCremo and all the OEM tools still work with LSV2, there will be a change in a future Version from LSV2 to DNC Connection for the new Maschines (there are no plans for OPC UA to come to orginal Heidenhain programms)

The DNC connection will not be replaced but also not actively developed, only bug fixes ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants