06-26-2012 05:24 AM
Hi there,
I have some Ploblems with 3 Errors. The guys who worked on this project have left the company, and I am only a physics student who is a noob at this. I was told to use their programs in Labview. Please help me.
I am using a Pc with a NI PCI 6025E Board witch is connected to a NI SCB 100 Connector Block. This SCB 100 is connected to 2 Sensors and an Servo Amplifier. I am also using an RCA-S Control Block witch is connected to a standart 9pin COM Port via an RS232C/RS485 Converter.
Now following Errors occure in Labview 5.1 (info: drivers are all updated):
1) Error 37 occured at Serial Port Initial
Possible reasons:
Labview: Device not found
2) Error -10401 occured at AI Group Config
Possible reasons:
NI-DAQ LV: The specified device is not a product of NI or the driver does not support the device.
3) Error 1 occured at FALSCHE CONTROL BYTE (translated it means WRONG CONTROL BYTE or FALSE CONTROL BYTE)
Possible reasons:
Labview: An output parameter is invalid or NI-488: The command requires that the GBIP-controller is the active controller (Original: Ein Ausgabeparameter ist ungültig oder NI-488: Befehl erfordert, dass der GBIP-Regler der aktive Regler ist.)
I somehow can't figure out how to start debugging. I don't understand the first error because everything is plugged in. I don't know what the second error means cause I have the newest drivers. And I am totally confused about the third error. I'm desperated. Please tell me where to start or where I could learn to debug this errors.
Sincerely Yours Paul
06-26-2012 05:38 AM
Run the code in highlight execution and look at where the error occurs (the light bulb, also retain values is helpful). I'm guessing it's the Open Visa that bugs out, have you changed computer, is COM1 disabled in bios or similar, it sounds like you cant open the port.
I wouldn't be surprised if the other error are follow up errors.
/Y
06-26-2012 06:12 AM
For the DAQ part, i suggest you to look into MAX and make sure, that the device is listed there (and working correctly).
It seems to me, that the application is using traditional DAQ, which complicates things. The device ID should be a simple numeric value there. Make sure that this number within the application matches the number you are seeing when working with the traditional DAQ test panels.
hope this helps,
Norbert
06-26-2012 06:14 AM
HI Paul,
To start debugging the problem first of all check whether the device is connected properly.
2. double check and triple check whether the correct drivers are installed or not. Re install or repair may work sometimes.
3.Check in the software whether parameters required for comunication are provided properly. i.e.
Port name COM1, COM 2 etc.
baud rate
any other parameters in the code etc.
All the best.