08-03-2010 03:37 PM
This error began to appear on multiple machines with an older (version 5, Win98) .vi that we would still like to use (and not have to re-write). We have tried reinstalling LabView (versions 6 and 7), and NiDaq - including the legacy download. We are now trying all of the above on a Win 2000 machine. The problem may have begun to appear after a newer version of Max was run on the machines
This is the message that appears:
NI-DAQ LV: An error was detected in the input string; the arrangement or ordering of the characters in the string is not consistent with the expected ordering.
It's not clear (to me) what the exact nature of the complaint is. It seems such a simple error that I'm reluctant to re-write the entire program without exhausting all oher remedies first. Please help.
Thanks.
Solved! Go to Solution.
08-03-2010 05:57 PM
What is the input string? Is it a list of channels, a list of device names? Give us more information. Which DAQ device? Some input strings require comma separation and some allow a colon to indicate a range, like 0:5, and some require a dash, like 0-5.
08-03-2010 07:25 PM
The input string is simply a name for the channel. The channel is configured as a 2 bit wide digital input, there is in addition, a list of names which map to each of the 4 possible inputs. The device is as PCI-MIO-16E-1 that runs perfectly on the NI-DAQ test panels.
Sure hope you've got some ideas about this. Thank you!
08-04-2010 11:25 AM
@Musant wrote:
The input string is simply a name for the channel.
What I meant was, what do you have in your input string? What is the actual string? What are the characters? Is it "1,2,3,4" or "1-4" or "1:4" or what?
It would be better if you just posted your code. Then I can see all the settings.
08-04-2010 04:53 PM
The string is "HV Status", without quotes. But the .vi itself has run flawlessly for years under version 5, and hasn't been changed. What seems to have prompted this problem was running Ni-DAQ Test Panels - perhaps a newer version. The error first appeared after that.
Thank you!
08-04-2010 06:00 PM
I think the space between HV and Status is what is causing the problem. Maybe it was allowed in an older version of LV or DAQ, but it is now not allowed. Change the device name to not have any spaces.
08-04-2010 06:42 PM
I still get the error with no spaces. But I think it's being generated in one of the sub-vi's that the Digital Port function calls internally. The inputs to the sub vi called Port Config are wired differently, and the channel name seems to be a default name, 0. It's not tied to the local variable. That might work for configuring the port. But I think the problem may be that every time a Digital Port Read is encountered, it runs the Port Config sub vi. Nothing is wired to the Dig Port Iteration input, so it always assumes zero. I experimented with it by tying the input to the iteration key, but other problems arose. I'll keep experimenting. Any suggestions are welcomed. Thanks.
08-04-2010 06:47 PM
Attach your code along with all subiv's. Make it into an LLB, and attach the LLB. Then I can play with the whole thing. That will be the only way I could give advice.
09-30-2010 02:59 PM
I wanted to report that we fixed the problem. Believe it or not, somehow, the 'Digital Channel' input to the Digital I/O Config function changed color, which required that the input now be rewired with a box having the same color - fushia. The only thing we could find with that color is a Traditional DAQ box that says 'I/O'. There are evidently differences between some of the original functions and their 'Traditional' counterparts.