Scan Engine & EtherCAT Custom Device Feedback

[JeKo]

Yes, we had a ini key setup as described here:

https://decibel.ni.com/content/projects/ni-timesync-ni-sync-hardware-support

We can try to add everything else except the time sync and see if it is still stable (NI Switch, NI-XNET).

[StephenB]

OK sounds like a good plan. I'll do the Sync stuff and we can meet in the middle.

[StephenB]

Few more questions

1) What mode did you have the 6683 in? 1588 mode, GPS, default?

2) What time sync settings did you have configured on the "time settings" page in MAX?

3) What settings did you have for the Ethernet adapter?

[StephenB]

Nevermind. Just reproduced!

[StephenB]

I'm going to try uninstalling NI-TimeSync 1.2 and the NI-TimeSync Plugin for NI-Sync and seeing if the issue still reproduces. Once I have that narrowed down, I will work with R&D to find the root cause.

[StephenB]

Just reproduced without NI-TimeSync and with NI-Sync

[JeKo]

I'm glad to hear that you are able to reproduce that.

We run the system with everything except time sync and it is working stable (ca. 24h), so I think we now know which software is causing the problem.

Any idea how we can fix it? Or when we can expect some patch/fix from Your side?

Sorry that I'm pushing so much, but for our client it is a show stopper and we have some deadlines till end of August.

[StephenB]

without NI-TimeSync, but with NI-Sync, it was not stable for me. So I believe the problem is with NI-Sync, not NI-TimeSync.

I'm working with R&D on the issue now. I cannot promise any time frame as we don't know the exact issue yet. Can you tell me your service request number and name of the support contact at your branch?

[StephenB]

Nevermind I found it, SR 1444290

[StephenB]

JeKo,

I've figured out a few things. With the NI-Sync card and driver installed, the EtherCAT read/write API calls sometimes return error -2147138393. The custom device catches this error and filters it out as a 'late count'. However, not before the error is internally passed through our Fixed Point UDV read/write code which will set the UDV reference to blank if it is passed an error. So next iteration, the custom device throws error -1950678941.

I've fixed the Fixed Point UDV read/write code to no longer set the UDV reference to blank if it was passed an error. Therefore, the system will not error shut down after seeing error -2147138393, it will simply count that iteration as 'late' as it is supposed to. This will allow you to run without shutting down.

I am posting a new version right now, 4.1.4, with this fix. However, this does not explain why we are getting error -2147138393 intermittently when NI-Sync is installed in the first place. Our R&D team is looking into that now.