Network Stream On PXI W/RTOS works in debug but not deployed

[DogOnWood]

I have a new problem, recently my network streams have decided to not work.

I have a PXI with a 8102 controller running the NI RTOS, If I run the program on the PXI from in the development environment they work as expected, however if I build the exe and run as startup the communicating program times out, the target (PXI) is unresponsive.

This has work previously, we had a power outage and I had to re-format the PXI HD and re-install the RTOS, I do believe it is back to the original state before the power issue software wise, but as stated my network streams seem to be unresponsive as an app

Networks Streams 1.1 loaded according to MAX

any ideas?  The fact that it work like a champ in debug, but not as an exe is very frustrating, especially since it was all working beautifully before the power outage.

oh yeah, using REAL-TIME 11.0.1 and labview 2011 SP1

TIA

[DogOnWood]

I've created another project and made a simple app the creates one netstream and that's it, seems to work fine.

If I try simplifying the original program  - still doesn't work - did a clean build - no go

created a new RT build - no go.

Going o try adding piece by piece and see if I can find what is breaking it.

Once again, this code worked for months(over a year actually in slightly differnet forms), and works if run from the development environment

[DogOnWood]

Well after lots of hair pulling and cussing (and a few visits from HR about said cussing) I've narrowed the problem down a bit, seems a subvi that hasn't even been executed yet is the culprit, not sure why yet but I have an idea.

[Kilometers]

What is this subVI doing? Can you attach it or a screenshot of it so we can have a look? 

Just to double check the subVI is running in interactive mode, but when you build the executable you can tell it's not executing? How did you discover this?

[DogOnWood]

The Sub VI is setting up and controlling the 2536 Switch and 6133 capture cards based on the command recieved by the Vi from the host program.

It also talks with the 7811

I thought that I was using slot numbers to reference the cards before the corruption, but now it is device numbers,.

I was playing around in MAX and it caused labview to crash if I tried to view the block diagram of the subvi.

I changed everything back in MAX and now the App is running - that is I can now establish a network stream with it and comunicate with the 7811, my data captures however seems to not be working and cause the PXI to go off in the weeds, the CPU loads go up and stay up and I can't re-establish the network streams without a reboot.

I just took a look at MAX while the PXI is in lala land, it has little red x's next to the 6133's and 2536

[DogOnWood]

I was able run it with some probes, seems something is still trying to address the the 2536 with a slot ID i.e.  PXI1Slot5 instead of the current Dev4 that the MAX shows and I used in the beginning of the VI

just realised why, all my routing is using the old  PXI1SlotX stuff, is that an alias I can set in MAX?  I don't recall having to do that before - but it has been several years.......

[Kilometers]

It looks like the slot detection is done through NI VISA. This KnowledgeBase and its related links talk a lot about identifying PXI cards in their slots, http://digital.ni.com/public.nsf/allkb/2342900AED02975A86256BD800764C8B?OpenDocument. I hope those are helpful.

[DogOnWood]

thanks, but I get and error when I click on the link

[Kilometers]

I think it's because the period at the end of the sentence got attached to the hyperlink. Sorry about that. Try this, http://digital.ni.com/public.nsf/allkb/2342900AED02975A86256BD800764C8B , or just try editting the old link.