Scan Engine & EtherCAT Custom Device Feedback

[JeKo]

Hello Stephen,

First - thanks for very quick fix! 🙂

We downloaded the new version, install all the software (including all time sync releted things) and will check if the system is running stable. We will also take a look what's the 'late count" after - let's say 24h to verify how often it happens.

Second - Could it be that the problem with NI-Sync is caused by this:

http://www.ni.com/product-documentation/52347/en/#438783_by_Date ?

If You can - please keep my posted about results of Your investigation.

[StephenB]

That absolutely could be it... nice find. I'll bring this up with R&D.

Thanks!

[UsmanKhan]

Hello Stephen, I have a question regarding the daqmx plugin you gave me. I am updating the test cells to 2013 sp1 from 2012. Do I need to recompile those plugins? If yes would i be able to do that? I know this is a different forum but I did not know where to post this question.

Regards

[UsmanKhan]

I upgraded from VeriStand 2012 to 2013 SP1. I am using NI Industrial Comm. version 2.6 and Scan Engine custom device version for 2013 sp1. On deployment of VeriStand I get the following error. I have only EtherCAT Master and no slaves. Everything was working fine before upgrade.

The VeriStand Gateway encountered an error while deploying the System Definition file.

Details:
Error -2147138516 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi

Possible reason(s):

The NI Scan Engine could not be changed to Active mode because one or more slave devices failed to enter Operational state.
=========================
The NI Scan Engine could not be changed to Active mode because one or more slave devices failed to enter Operational state.
=========================
NI VeriStand:  NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi >> NI VeriStand Engine.lvlib:VeriStand Engine.vi >> NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi >> NI VeriStand Engine.lvlib:Initialize Inline Custom Devices.vi >> Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi

[StephenB]

Hi Usman,

Which DAQ plugins are you needing? I have several and I don't remember which ones you are using specifically.

That error is curious. My best guess is we need to update your EtherCAT slave firmware. You can do so by visiting C:\Program Files (x86)\National Instruments\NI-IndCom for EtherCAT

Opening the user guide PDF and going to page 12

Follow the steps there to update your firmware with LabVIEW. If this works, I think I need to add an update firmware button to the Custom Device (for those without LabVIEW)

Thanks

[UsmanKhan]

The data plugins were for scaled voltage inside the system definition when we selected Waveform as the method. I am trying the method you told me to update firmware, if not I will let you know.

[UsmanKhan]

Stephen,

I do not have any EtherCAT project as such. Do I use the source code of the Scan Engine to download the firmware?

[StephenB]

UsmanKhan wrote:

The data plugins were for scaled voltage inside the system definition when we selected Waveform as the method.

Here you go

[StephenB]

UsmanKhan wrote:

Stephen,

I do not have any EtherCAT project as such. Do I use the source code of the Scan Engine to download the firmware?

You can just make a new project.

1. Click create project from getting started window
2. Double click blank project
3. Right click the top node of the project and select new-> targets and devices
4. Expand the real-time compact RIO section
5. Select your controller
6. If prompted, select scan interface and select continue
7. If prompted, select do not discover C series modules
8. Right click the newly added compact rio node and select new -> targets and devices
9. Expand the EtherCAT master section
10. You should be about where the tutorial in the user guide takes over for updating the firmware

[UsmanKhan]

Stephen,

I was not able to flash it because when I create the project, I can select new --> targets and devices, but I see PXI option and not the Ethercat RIO option. I must be missing something here.