Scan Engine & EtherCAT Custom Device Feedback

[NFT]

I began wondering the same thing myself. The report says there's a total of 124 MB, with 38 MB free before attempting deployment. Is this sufficient?

Edit: After rebooting the target, MAX reports 93.3 MB free physical memory. After failing the attempt to deploy, MAX reports 38.0 MB free.

[mdobrosky]

Is Industrial Communications for EtherCAT installed on the target?  I think that needs to be on there too in order for the Scan Engine custom device to run.

[NFT]

I decided to monitor the cRIO through the web-based monitoring utility while deploying the VeriStand project. After the "Initializing inline custom devices..." line, there are a few lines that contain errors mentioning "memPartAlloc: block too big". I'm guessing this means the target is running out of memory during deployment.

I took a screen shot, but the comment editor errored out while trying to post it. I know today is Tuesday, but it's definitely behaving more like a Monday.

[NFT]

I do have the Industrial Communications for EtherCAT package installed on the PC, but there's no option to install it on the cRIO target. The documentation said it's only necessary on EtherCAT devices.

[Ryan_S]

EtherCAT should only need to be installed on the target if you're communicating with EtherCAT slaves. I would have thought 32MB would be enough, but the console messages you're seeing would be indicative of running out of memory. It would depend on what the largest contiguous block was available.

[Sebo91]

Hi Ryan,

thank you very much for these informations. I wondered, because under known issues it says it would work with 9401.

I already tested it with 1x9862 and 1x9401 but it doesn't work.

How do you mean your explanation for solving the problem?

Do i have to add the Module 9401 in Labview under FPGA Target and add User variables connected to the Input-ports of the 9401 or do i have to create an VI for the communication with the module?  

Do i have to Add the user Variables in Veristand as well?

When update to 2015 versions is finished i will try if the XNET modules work without the 9401. I think i already tested them a few days ago, but I will test them again.

Kind Regards

Sebastian

[NFT]

I tried using a cRIO-9024 and 9114 in place of my older 9014 and 9104, but I'm still getting the same error that the RT Driver is broken. I didn't see the "memPartAlloc: block too big" in the console output this time, however.

I've attached the MAX technical report.

[NFT]

I decided that the problem must be linked to the PC I was using (I'll call it the "deployment PC"), so I grabbed my development PC and reinstalled all of the software onto the cRIO from it. The project now deploys successfully on the cRIO-9024 from my develpment PC and from the deployment PC. I haven't tried the 9014 yet.

The technical reports show that there is a software installation difference between the two PCs: one includes "NI-RIO IO Scan 15.0" and the other does not, even though they both include "NI Scan Engine 4.4".

What's the difference between "NI-RIO IO Scan" and "NI Scan Engine", and how do I get "NI-RIO IO Scan" installed on the deployment PC?

[NFT]

I found "NI-RIO IO Scan" in the August 15 drivers distribution. For some reason (maybe because I don't have LabVIEW installed on this PC?), it was unchecked when starting up the installer. I had to manually select it.

[Ryan_S]

Huh, so the culprit was IO Scan (and possibly memory limitations on the 9014), I thought so, but I wasn't aware that it had been separated in the driver install; but yes you will need it for proper operation. To be honest I don't know what functionality is seperated between scan engine and IO scan. Kudos on pairing down the issue.