Hello,
I am curious about what I am seeing using TestStand 2013/LabWindows 2013 in regards to initial string values in TestStand when executing the steps in process or an external instance of LabWindows/CVI.
I have a string value test step(CVI) that is used to verify a character array stored in a EEPROM. I pass the Step.Result.String into CVI by reference. I then read the charater array from the EEPROM into the string (Step.Result.String). The string is then compared against the limit as specified withing the test step.
When I run this test step with execute steps in process selected from the LabWindows/CVI Adapter Configuration popup it appears that the memory allocated to the string is filled with null characters. Which is what I would expect.
When I run this test step with execute steps in an external instance of LabWindows/CVI iselected from the LabWindows/CVI Adapter Configuration popup it appears that the memory allocated to the string is filled with something else. Which is not what I would expect. For instance what I see in memory is that the first characher is a null byte but the remaining bytes are some other values as shown below:
00 F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D
F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 ...
In my code I make sure to write a null character in the location following the charater array I just wrote into the string so I have no problems with the test working correctly. I did remove writting the null character from my code and was able to verity that the test passes when executing steps in process and fails when executing steps in an external instance of LabWindows/CVI.
The returned string contains what I wrote to it and then the rest of the string is filled with the values that are in the memory space allocated to the string.
Here is my Question: Is this the expected behavior for initial string values in TestStand between the two types of step executions?
Thanks,
Chris Young