Strange Real time target desktop reboots??

[JP205]

Thanks for your response, Soeren.

I'm running a few R-series FPGAs with my realtime target.  Right now I'm basically just sampling digital and analog data on the FPGAs and doing a DMA transfer to the RT, as well as shared variable communication with the windows host computer. 

Justin

[rchangek]

HI,

92: Connector::close h 94, no handler

I am seeing very similar error message on my RT systems. I have seen it on my desktop RTs as well as PXI RTs using NI 8110 embedded controller. In any given system I am only using one PC and one RT communicating with eachother using TCP and network shared variables.

I have typically seen that when this error shows up, my connection between PC and RT is lost and system is down.

At times I have seen this error popping up again and again one below the other.

[soeren]

Hi rchangek

Yeah that sounds about right. Although my systems do not always shut down even with the errors there, that only happens in rare occations. And this is really the problem, because these unwanted shutdowns can do a lot of damage and potentially cause more serious problems, so it would be nice if it was possible to know what caused them, so they could be corrected............NI.........please.....

best regards

soeren

[rchangek]

I talked with NI support as well, but they don't think their VIs use Adaptive Communication Environment (ACE) at all. They think it has to be third party drivers. What kind of third party drivers are you using in your application, in terms of communication protocols?

[soeren]

Actually I don't think I use any at all (could you give an example). I think the most exotic thing I am using is some legacy drivers and ancient subvis for temperature measurements using NI PCI 4351. All other stuff is pretty standard Labview stuff.

/soeren

[sls__]

Hello!

I'm getting the same error as you have described. It started when I moved the shared network variables from my RT-desktop to the host computer. Labview produces the error 1950679027 whenever I tried to read or write them. Then, a message like " 57: Connector : close h 42 ; no handler " appears in the target's screen. Don't know if this have the same cause as your problem, but perhaps there is also a common solution.

Cheers!