Scan Engine & EtherCAT Custom Device Feedback

[StephenB]

Hello,

Can you add support for the 9220 please?

Thank you

[Vincent_R.]

Hi Stephen,

What is the FPGA target you want to use with the NI-9220?

Regards

Vincent

[StephenB]

Hey Vincent,

We haven't selected one yet but probably one of the new Linux cRIOs

[Vincent_R.]

Hi Stephen,

No Ethercat chassis involved?

Regards

Vincent

[StephenB]

At the moment we are not planning on one. Curious- why?

[Vincent_R.]

Hi Stephen,

I just re-checked the SW support details, per module, here is what I got:

I'm going to confirm internally that information related to Ethercat (Scan Interface) for 9220 is still correct.

Regards

Vincent

[Vincent_R.]

Hi Stephen,

I checked with our technical support and the information I used is not correct. A CAR has been created to fix that source of information.

I have been confirmed by technical support that NI-9220 is supported in a NI-9144 (Scan-Mode) but Slots 1-4 only.

http://digital.ni.com/public.nsf/allkb/D03CD7A8F899F86C86257EF200500667

We are going to put your module support request the whish-list for new features.

Take care.

Vincent

[emallett]

I am working to add a third party EtherCAT instrument to the Scan Engine and EtherCAT custom device. I have done this successfully in the past. However my needs are more complex this time. I have written a purely LabVIEW based application using the instrument XML file to familarize myself with the instruments capabilites. This application uses the SLAVE methods "IndComECAT Slave.ReadSDO" and "IndComECAT Slave.WriteSDO" to accomplish the tasks I require. This functionality is used because the property "IndComECAT Slave.Children[]" does not return IO Variables to all the needed values. Use of the SDO read and write methods requires knowledge of the Object Dictionary, Index and SubIndex. I think LabVIEW obtains this information from the XML file. Since the Scan Engine and EtherCAT custom device does not use the XML file, will the two required methods function properly?

[AndreasStark]

We implemented a version that supports 3rd party slaves, but only PDOs so far (SDOs yet to come). If you're interested in that please contact me or your local NI representative.

[Damian_S]

EtherCAT 9144 chassis, NI9212 FPGA, Scaling Issue in VeriStand.

I'm having some issues figuring out the scaling for c-series 9212 module in FPGA mode on the 9144 EtherCAT chassis. My plan was to import the value into a model to convert the FPGA value into readable temperature value. I'm currently doing this with two cards on the main cRIO 9081 chassis and due to the test stand's setup the 3rd 9212 card needs to be added on the 9144 EtherCat chassis.

The issue is that the value reported into Veristand is approximately 7495. The scaled value from the 9212 card on the main chassis has a value of 0.0001065. I would expect the 9212 from the 9144 would give a simlar result after scaling the raw value. I'm not sure how to scale the 7495 value to a value similar to the values from the cRIO 9212 cards. Could you provide some insight on how to do this? I tried to use the scale maps, but i didn't see the option for the 9212. When using the 9213 scale it did not give expected results.

Just a bit more information, the 0.0001065 value runs through a model in VeriStand that runs the code from the cRIO 9212 example. This

gives a temperature value in degrees C with K type TC. In this case the temperature is approximately 30C. I checked the scalinig value for a simliar TC card, the 9213 and it uses 0.25. I'm actually using this for the XML file for the main chassis FPGA and it's giving me expected resutls.

I tired to use the equations below, but the values seems way off. This might be due to the large range of a U32 bit number. I'm not really sure.

9144 FPGA project for NI 9212 card