Help! PDA un-defined error 120168006 and 134429006. Bad input argument to function.

[rberger]

It looks like my Windows Mobile 5.0 devices crashes right at the Greater Than? primitive.  My comparison involes comparing a string result as the X input with an array of strings as the Y input.  My array of strings has 10 elements, and at the point of crashing, if you probe the array of strings, I have one element with the timestamp string and the other elements as null strings.  The output of Greater Than is set to compare elements.

Attached is a JPEG file of the block diagram where is crashes.  I have setpoint at the Greater Than? primitve to highlight the troubled area.

Can anybody else confirm?

NI, please, please have this issue be fixed before releasing PDA V8.2  With all of the bugs uncovered by me with v7.1 v8.0, v8.01, I should be getting an NI paycheck or at least a free upgrade to v8.2

Thanks

Robert

[rberger]

In my previous post I forgot to mention my X input to the Greater Than? primitive is the string: 08/29/2006 15:20-D7

My Y Input is an array of strings with the first element containing the string: 08/29/2006 15:35-D12.  The rest of the elements are null strings.

This works on the desktop but consistently crashes my Windows Mobile 5.0 device.

Robert

[rberger]

The workaround to this bug is to index the array of strings with a For Loop surrounding the Greater Than? primitive.  In that way, Greater Than? is comaring one input with each element in the string array.  Hope NI looks into this bug.

Thanks for reading.

Robert

[JLS]

Hello,

I am just now seeing the new additions to this thread.  First, I am glad you found a workaround to the greater than problem.  I did not find an existing CAR on this so I'll reproduce it (at least try - seems pretty straightforward), and file a CAR.  I'll post back the results including the CAR number if indeed I can reproduce it - just wanted to post here quickly so you knew you weren't alone in this 🙂

Best Regards,

JLS

[JLS]

Hello again,

I have verified that this is a known issue and being addressed by R&D.  You can track it with CAR ID: 40TE6LZ0, and you have been added to the notification list.

Thank you for reporting this!

Best Regards,

JLS

Message Edited by JLS on 08-31-2006 04:15 PM

[rberger]

That great JLS.  Thanks for your response.

Have a nice day.

Robert