07-12-2013 09:16 AM
Hi plist,
Thank you!
07-23-2013 08:53 AM
Sorry for the confusion, that was worried a bit poorly.
I'm currently working with a system with 1 cRIO chassis (Custom FPGA, no scan engine) and 2 EtherCAT chassis. The power to the system is removed every time the stand is shut down. Whenever I come in first time in the morning I power on the system. I then deploy the VeriStand configuration which results in either one or both of the ethercat chassis in error states (blinking red LED on the chassis). The problem with this is that VeriStand is unaware of the error states, and the system still deploys.
This results in none of the controls on those stands operating, but with no indication as to why. I then undeploy / redeploy the system and everything works fine. Even if the system errored the first time it would be much more appealing that having to go through the whole deploy / undeploy procedure as it isn't exactly a speedy process.
My question was referring to how is it that the system can error while a chassis isn't seen, but not when the chassis is not responding to commands? If there is a way to recover the system from an error state, that is one thing, but if not, why not just fail the deploy process all together?
So I guess I actually have several questions.
1. Can an errored chassis be recovered when an error is detected without re-deploying?
2. Can the custom device be changed such that a chassis showing an error can result in a failed deploy?
3. Any ideas as to what is causing these chassis to error every time the power is applied to them for the first time?
Thanks for the help.
07-24-2013 04:24 PM
Hi plist,
Hmm. Thanks for the description. I havent seen this before.
can you attach your system definition so I can take a look at some settings?
Thanks.
08-06-2013 07:35 AM
I have attached the system definition.
08-08-2013 10:08 AM
Hi,
I would like to confirm whether "DataRate" property is accessible for some modules supporting it? I don't see it, for instance for NI-9239, NI-9237 module when I add them manually to my System-Definition.
My understanding is that it would allow customers to configure Anti-aliasing filter for these modules.
If confirmed, any plan to add it?
Regards
Vincent
08-12-2013 10:35 AM
Hi Vincent,
It looks like "Data Rate" is indeed a property we can set for thoese modules. I don't recall seeing it as an option before, so I wonder whether this option was recently exposed by RIO for the modules' scan support. Even looking at the module configuration pages from LabVIEW, this setting isn't visible (see below).
It shouldn't take much work to add it, so I can start looking into that now. When do you need it by? Is there anything else besieds the 9237 and 9239 that need updating?
Thanks,
Devin
08-12-2013 10:47 AM
plist,
Next time this happens, can you open Distributed Systems Manager (from the start menu) and browse to the remote target? I want to see what error fault it is throwining to cause the red lights to blink.
Thanks!
08-12-2013 10:47 AM
So, it looks like the "Data Rate" property should be added to the following modules:
9229, 9233, 9234, 9235, 9236, 9237, 9239
In addition, the 9235 needs shunt calibration added, and the 9478 has a number of properties that need to be added.
Is there anything else I'm missing?
Thanks,
Devin
08-13-2013 10:48 AM
Devin, it seems like this is applicable for all the C series module that feature a delta-sigma ADC with built-in filtering at half ot the sampling rate. If the "Data Rate" property is user configurable through System Explorer and on the Workspace, does that mean that the sampling rate of these devices can be different that the main loop rate of the EtherCAT slave even though the modules are still working in Scan Mode (i.e. no custom FPGA code)? Example, I have a 9237 and a 9239 in my system, and the main EtherCAT loop rate is 1KHz. If I decide to sample the 9239 at 25 KS/s will the "Data Rate" property help me accomplish that?
Thanks,
Kalin
08-13-2013 11:01 AM
Yes exactly.