Scan Engine & EtherCAT Custom Device Feedback

[Damian_S]

I've worked on this issue on and off for a few days before posting, but I finally found a workabe solution. The main cRIO chassis requires the use of U32 for DMA FIFO. The 9144 is using network shred variables. I changed the network shared variables from U32 to FXP 24bit word length -2bit integer work length. This passes the value as expectd into m veritand model.

[JeKo]

Hi,

Can you add support for NI 9437?

It's a new model supported now in EtherCAT 15.0

Thanks in advance!

[imf28]

Hi,

I just recently upgraded to Veristand 2015 SP1 (from straight 2015 version), and now I appear to be having issues with the Scan Engine/EtherCAT custom device.  I cannot seem to deploy any system definition files that were created with the SP1 version and have the Scan Engine custom device configured.  I get the following error in the deployement log:  "The network operation exceeded the user specified or system time limit."

However, if I try to deploy a system definition file that was previously created on the straight 2015 version, the deployment is sucessful.  If I remove the configuration for the Scan Engine Custom Device, I can also sucessfully deploy a system def file created in VS 2015 SP1.

Do you know what might be causing this issue?

Thanks!

[imf28]

I also update Labview from 2015 to 2015 SP1...

I'm running the system definition on a CRIO-9081 with the following software:

Veristand Engine 2015.1.0

Ind. Comm for EtherCAT 15.0

NI-RIO 15.5

Labview RT 15.0.1

[RasmusVistisen]

Hi,

After upgrading from 2015 to 2015 SP1 we get the following error:

Error 74 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> Project Window.lvlib:Connect to System.vi

Possible reason(s):

LabVIEW:  Memory or data structure corrupt.

=========================

NI VeriStand:  Unflatten From String in Server TCP Interface.lvlib:TCP Connection Manager.vi:7430001

Any idea for a solution?

[WhizzWr]

Also having same problem with RasmusVistisen.

Shame to NI, for releasing a Veristand version that breaks compatibillity

[Vincent_R.]

Hi WhizzWr,

Sorry to read that. In order to help you, we need more information about the setup and conditions to reproduce issue.

• Does it happen with an existing Sysdef and/or brand new one?
• If you create a brand new Sysdef, add the Scan-Engine Custom Device, perform modules detection and deploy? Do you get the error?
• What is your HW configuration?

If you cannot communicate all the details, send me a private message.

Best regards

Vincent RUAULT

National Instruments

[WhizzWr]

Hi Vincent_R.

Actually I have a different setup (not Scan Engine & EtherCAT Custom Device Feedback)

I'll answer your question

• Brand new project and sysdef, I tried the example (sinewave delay), empty project and sysdev. Same result
• Unfortunately I do not have " Scan-Engine" in my custom device context menu, I only have "Embedded logger". Most likely because I do not have those setup in the first place
• PXIe-8880 Embedded Controller on PXIe-1071 chassis. Veristand 2015 SP1.
  

Regards

W

[Vincent_R.]

Hi WhizzWr,

Thanks a lot for your quick reply. I have three questions/comments:

• If you deploy on Windows (as NI-VS target) instead of PXIe-8880, does same error happen with a blank Sysdef and/or Sinewave example?
• Did the Windows machine have NI-VS 2015 already installed before you installed NI-VS 2015 SP1?
• Just to confirm, when you upgraded to NI-VS 2015 SP1, have-you upgraded the PXI RT Software (NI-VS Engine) as well?

I'm going to share that information with NI-VeriStand Support team. Can you send me a private message with your email address?

Best regards

Vincent

[RichardvL]

I just installed Veristand 2016 Scan Engine,  EtherCAT custom device - 2015 - v4.1.11, Industrial Comms 16.0, etc. Now I get a VI (too old) compatibility issue in System Eksplorer (sorry the "eks" character in my keyboard packed up:-) when I try to add the custom device to my system configuration.   Is this a known issue? If so, what is the workaround?  Thanks Richard