NI VeriStand Add-Ons Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Scan Engine & EtherCAT Custom Device Feedback

The custom device now supports Specialty Mode, but only when used on a local chassis.  You're correct though that using the 9411 over EtherCAT will require a bitfile.

capture.jpg

0 Kudos
Message 231 of 676
(731 Views)

I am on a local chassis.

0 Kudos
Message 232 of 676
(731 Views)

Yep, so when you set your module into the "quadrature" specialty mode, you should see the I/O change from the 6 digital channels into 2 position and 2 velocity channels like in this picture.

capture.jpg

If you're still seeing DIO 0, 1, 2 after selecting this option, that's not supposed to happen...is that what you're seeing?

0 Kudos
Message 233 of 676
(731 Views)

Thanks Th0r. 

For some reason when I selected Quadrature the DI channels were still showing up.  I had to shut down and resetart Veristand, then select NONE for specialty mode, then back to Quadrature.  Now everything looks like it is working ok.  It was very confusing with the DI channels still showing, the Pos labels make much more sense. 

Thanks for everyones support.

0 Kudos
Message 234 of 676
(731 Views)

Does this custom device have a system definition API created for it?

0 Kudos
Message 235 of 676
(731 Views)

Unfortunately nothing official. There is an old unofficial one that may or may not work anymore if you really need it I can hunt it down, but no promises on if it works anymore

Stephen B
0 Kudos
Message 236 of 676
(731 Views)

I would appreciate it if you can find it as a starting point for me.

Thanks

0 Kudos
Message 237 of 676
(731 Views)

Here is what I have. good luck

Stephen B
0 Kudos
Message 238 of 676
(731 Views)

Hello everybody,

i am doing my master thesis and have to use VeriStand to read PWM Signals, use CAN-Communication and so on with cRIO Hardware. I already used the way with VeriStand FPGA-Based I/O Interface Tools (https://decibel.ni.com/content/docs/DOC-13815) but is this the best way? The tests should be generated in Teststand 2013.

So I tried to use the Scan Engine and EtherCAT custom device (https://decibel.ni.com/content/docs/DOC-15510)

I use the following software:

  • Windows 7 64bit
  • LabVIEW 2013 English 32Bit (without SP1)
  • LabVIEW 2013 Real Time Module (without SP1)
  • LabVIEW 2013 FPGA Module (without SP1)
  • NI-RIO 13.0
  • NI-Industrial Communications for EtherCAT 2.7
  • NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4
  • VeriStand 2013 (without SP1)
  • TestStand 2013
  • NI Device Drivers 2013.02

These are all components on the cRIO:

  • CompactRIO Support 13.0
  • DataSocket for LabVIEW Real-Time 5.1.0
  • EPICS Server I/O Server 13.0.0
  • HTTP Client 13.0.0
  • HTTP Client with SSL Support 13.0.0
  • Hardware Configuration Web Support 5.5.0
  • I/O Variable Remote Configuration Web Service 1.2
  • LabVIEW PID and Fuzzy Logic Toolkit 13.0.0
  • LabVIEW Real-Time 13.0.0
  • Language Support for LabVIEW RT 1.0.0.5
  • Modbus I/O Server 13.0.0
  • NI Application Web Server 13.0.0
  • NI Scan Engine 4.2
  • NI System Configuration 5.5.0
  • NI System Configuration Remote Support 5.5.0
  • NI VeriStand Engine 2013.0
  • NI Web-based Configuration and Monitoring 13.0.0
  • NI-RIO 13.0
  • NI-RIO IO Scan 13.0.1
  • NI-Serial RT 4.0.0
  • NI-VISA 5.4.0
  • NI-VISA ENET Passport 5.4.0
  • NI-VISA ENET-ASRL Passport 5.4.0
  • NI-VISA PXI Passport 5.4.0
  • NI-VISA Remote Passport 5.4.0
  • NI-VISA Server 5.4.0
  • NI-VISA USB Passport 5.4.0
  • NI-Watchdog 5.3.0
  • Network Configuration Web Support 5.5.0
  • Network Variable Engine 13.0.0
  • Remote Panel Server for LabVIEW RT 13.0.0
  • Run-Time Engine for Web Services 13.0.0
  • SSL Support for LabVIEW RT 13.0.0
  • Software Management Web Support 5.5.0
  • System State Publisher 3.1.0
  • Time Configuration Web Support 5.5.0
  • Variable Client Support for LabVIEW RT 13.0.0
  • Variable Legacy Protocol Support 5.5.0

Hardware of the cRIO

  • cRIO 9024
  • FPGA 9116
  • NI 9401 (TTL)
  • NI 9425 (DI)
  • NI 9205 (AI)
  • NI 9853 (CAN)

My Problems:

If I generate a new VeriStand Project and go into the System Explorer to “Auto-Detect Modules” nothing is detected.

If I add a local chassis manually I get an Error if I try to Select a FPGA Bitfile like this: Error -2632 occurred at Eigenschaftsknoten (arg 1) in niECATGetCustomIOVNodeArrayFrom2010Bitfile.vi->Scan Engine Custom Device.lvlib:Get FPGA Info.vi->Scan Engine Custom Device.lvlib:Add FPGA.vi->Scan Engine Custom Device.lvlib:FPGA - Select Bitfile (Local).vi

What am I doing wrong?

Thank you very much!

0 Kudos
Message 239 of 676
(731 Views)

Hi Hans,

Can you post your bitfile for me to test with?

You also may not be able to detect modules for 1 or 2 reasons:

  1. Make sure the IP address is set on the controller page
  2. You have to set the controller to 'scan mode' before you can detect anything. Set this on the controller page and then deploy an empty system definition. Then undeploy and go back and try to detect again.

Thanks,

Stephen B
0 Kudos
Message 240 of 676
(731 Views)