Scan engine does not start kMinorFault -65606

[Melchiors]

I´m running a CRIO I hybrid mode and use scan engine to read from two 9205 modules.

Frequently after deploying the application no data is received from the scan engine LV shows kMinorFault -65606 and -65607 using get fault list.vi from the Scan Engine, using NI distributed system manager values are states as "Device error, No known value".

It seems that sometimes a reboot of the controller/ redeployment solves the problem and sometimes not.

Is there something to be aware of regarding synchronization in hybrid mode?

I start my program with a synchronize to scan engine, that executes without indicating any error or warning.

Among solutions to synchronization with scan engine is stated something like; continue to read values, so it seems synchronization issues should not give a permanent problem?  

I´m using LV 8.6.1 and NI-RIO 3.1.0 

I recall seeing a similar problems, where modules was not detected I MAX and LV due to VISA Error -63040, which in my experience is due to controller CPU overload, this is not the case here. 

/Mads

[speleato]

Hello Mads,

Minor faults -65606 and -65607 are defined as

"The project contains a module in slot 1 that does not match the type of the module in slot 1 of the chassis."

and

"The project contains a module in slot 2 that does not match the type of the module in slot 2 of the chassis."

respectively.

I'm not quite sure how that could happen if you are using two 9205s, are there other modules also in your project?

Hopefully that points you towards a solution, if not it would help if you could post your project / code so we can look in to it futher.

Thanks,

Sebastian

[Melchiors]

Hi Sebastian

I have 4 modules in a 9104 chassis 8 slot 3M (controller is 9012) as mentioned two AI 9205 in slot 1-2 a AO 9265 in slot 3 and a DI/DO 9403 in slot 4 Scan Engine communicates with the first three modules a custom FPGA code communicates with the DI/DO module. 

Working along the idea of a synchronization issue between Scan engine/ custom FPGA, I ensured that my call of the FPGA reference was performed after the scan engine synchronization has finalized.

This has resolved the issue for now >10 reboots, but as this was initially a periodic error, I will evaluate it again at a later time. 

If anybody has a insight on the priority of scan engine/custom FPGA during initialization please share 

/Mads

[speleato]

Hi Mads,

I'm glad things appear to be working for you now.  Please post back if that changes, and we'll debug further.

I'm afraid I don't really understand how the changes you made could have resolved those faults.  The synchronize to scan engine VI blocks until the RT Scan Clock expires.  Its purpose is to allow you to synchronize your RT code to updates in the IO Memory Table.  See http://zone.ni.com/devzone/cda/tut/p/id/7338#toc3 for more information.  This is supposed to be quite independent of the RIO Scan Interface (which is where those faults originate from).

If you can provide me with code that reproduces the issue you were having, I'd like to look in to it in more detail.  If you prefer to send it to me directly instead of posting on the forums let me know and we can do that too.

Thanks,

Sebastian