LabView CANOpen Library ("CANopen SDO Write Object"), General error (COE_SDO_GENERAL, 134217728)

[Captain_Julz]

Hi,

I've just started using labview2017 so if I'm missing something really obvious I apologise now!

I'm evaluating LV2017 with our application which is using LV8.5.1 - it used CANopen which wouldn't migrate as it seems all the CANOpen libraries are different!

I am using the NICANopenSW1700 download to add the CANOpen

with an evaluation version of LV2017 64bit

So to get myself going I opened the example and tried to compile / run but I just get bombarded with errors. It appears LV is trying to update the VI's and llbs but hasn't got permission - it is asking for a password to verify.

Am I missing something with LV?

Its the same if I use these vis/llb in my code too.

[GerdW · Accepted solution]

Hi Julz,

I'm evaluating LV2017 with our application which is using LV8.5.1 - it used CANopen which wouldn't migrate as it seems all the CANOpen libraries are different!

So you want to replace this old CANopen library with a modern CANopen-library dedicated to special devices? (Comment: your NI8473 is NOT mentioned as supported by the modern CANopen lib!)

I don't think this will work (easily)…

You may try this:

- Install NI-CAN for LabVIEW2017

- Install that legacy CANopen library for LV2009

- copy the content of the LV2009 folder (all the stuff of the CANopen library) to your LV2017 folder

This way I can still use the legacy CANopen stuff with LabVIEW - last tested with LV2014!

Keep in mind: the old legacy stuff was only supported until LV2010…

I am using the NICANopenSW1700 download to add the CANOpen with an evaluation version of LV2017 64bit

Why do you use LV2017-64bit? Is there a special reason for?

Why not use the 32bit version?

[Captain_Julz]

Hi GerdW,

Thanks again for your help.

I have installed the32bit version of LV2017 now,

Installed the NICAN1700

and copied over the CANOpen from my old LabVIEW directories.

My application successfully loaded and compiled.

I have quickly tested the NICAN interface and it works - I'll need to soak test this now to see if this has solved the original problem of loosing the CAN .

I don't have anything in at the moment to test the CANOpen properly but as soon as we do I'll try that.

I have been talking with Tomasz Dziendziel, from your Northern Europe sales team and he has suggested some avenues with new hardware that is fully compatible with LV2017.

Thanks again for your help.