TS/OI - problem with globals variable

[pachook]

Hello all,

I am in the middle of developing OI which uses some of our previously developed sequences/teststeps etc.

When I do have sequence running directlly on TS - it performs without any problems;

When I run it on OI I dont get some data i think stored mainly in global vi. I havent developed library, so I am not quite sure how it works, but I belive it is something like this :

there is some .ocx file which handles all that - the handle/reference for that is kept in global vi. using this ocx we are also getting some data from text file (mainly addresses for communication) . Those addresses are then stored in stationglobals for TS to use them. 

The problem is, that when I run that sequence on OI the addresses remain 0x0000, when i want to debug the vi it finds addresses normally. 

Have anyone faced something like this? Or can have sugguestion what check (ie execution options, preload system etc ?)

Thanks for help

[RayFarmer]

Can you expand on the following...

[The problem is, that when I run that sequence on OI the addresses remain 0x0000, when i want to debug the vi it finds addresses normally]

When you say, "when I want to debug the vi....."

How are you doing this are you running in SeqEditor and LabVIEW development system?

or

Running in your OI with labVIEW development system?

When it fails, with your OI are you using the LabVIEW RTE for your labVIEW Adaptor comfiguration or are you still using the LabVIEW development System.

Regards

Ray Farmer

[pachook]

I am debugging wiht OI development system - that is setting a breakpoint and then performing step-into and/or step-over. The thing is, that with step-into it works fine (ie enterring subvi -> run it ->return to caller) and with step-over the behaviour is simmilar to standard execution.

I am not using LV RTE, just development system so far.

Thanks

[RayFarmer]

At a guess, it sounds like you are not allowing enough time. whereas when you step into your code module you are allow enough time by the fact that you are in debug mode. Have you go some parallel code running either in the sequence for in your code module?

regards

Ray Farmer

[pachook]

Hello Ray,

Thanks for your support. Finally we were able to solve the problem. or at least it looks like we did. Thing was, that library we had was inheritted from previous versions of TS (2.1 ) and it used legacy way of returning results. 

We changed the steps from action to pass-fail tests and replaced legacy cluster with standard boolean return value and error cluster.