applciation does not display correctly

[Kenny_K]

I built an application that reads the data off an Extech Thermocouple module through RS232 using the VISA vi's.  the applcation works on my computer that has the labview environment on it running Windows XP, and a computer that has windows 2k on it with only the runtime, VISA and DAQmx on it.  It does not work on the computer that I need it to work on, another windows 2k machine with the runtime, VISA and DAQmx on it (even though I am not using DAQmx in my program).  The only difference I can see in the installed software between the 2k machines, is that the one in which it works has the runtime for 7.0 and 7.1.1, and the one where it does not work has 7.1.1 and 8.0 runtimes on it (I developed the program in LV8.0)

Ok, I guess I should define "does not work'.  On the 2k machine that works, I get a display of the temp every 2 secs on a graph and in a multicolumn listbox, 75.5, 75.6, 75.7 etc.  On the machine that does not work, I get 0.00, 0.00, 0.00 etc.  If I unplug the serial cable, the program tells me that it is unplugged (through custom error codes).  So I am pretty sure that it is communicating with the computer (also I do not get a VISA read error when I start the program).

I checked in MAX, and initally it said that there was a port conflict.  So I had to change th settings in MAX to make sure that the Windows and VISA settings were the same.  But I still get the same results.  I checked to make sure that I have the latest drviers for the serial card.  I have MAX version 4.0.  I have also been getting error BFFF0015 when trying to communicate using VISA in MAX (the thermocouple module uses a nn standard communication protocol so ti doesnt surprise me) but again, I have it working on 2 other computers and just not the computer I need it to work on.

I will try uninstalling and reinstalling everything, and post back , but in the mean time, anyone get any ideas???

[Dennis_Knutson]

I'm curious about the port conflict message you had. What was the conflict between and how did you resolve it? Could the pc where it doesn't work have additional serial ports or a modem? Are you sure that you resolved the conflict so that the com port you think is connected to the instrument is really the correct one? If you get a timeout error in MAX, your LabVIEW program is probably as well. They are both using VISA so if you can talk to the instrument with LabVIEW, you can certainly talk to it in MAX with the same commands. Have you tried using Hyperterminal on the offending pc? If you can't talk there, then I'd say you have a problem with the port itself or the cable you are using.

Also, I don't understand your comment about the pc that is working has 7.0 and 7.1.1 runtime but you developed in LabVIEW 8.0. Running an 8.0 program without the 8.0 run-time is not possible.

[Kenny_K]

The port conflict was that windows had the port configured for 9600-8-N-1-N and the VISA wanted to have it configured for 2600-7-E-1-N (baud rate, data bits, parity, stop bits, flow control), which I found under MAX.  I am trying to use COM3 (COM1 is hooked up to a different device, using a non-LabView program, although I tried to run the thermocouple program through COM1 as well and with no success).  I have it in my program that you can select the COM port (I have tried to select COM1 with the cable attached to COM3 (and visa versa) and it gives me an error that it is the wrong device, so I am using the correct COM port).   Also under Device Manager it says that COM3 is a SIIG serial card, which is the add-on serial card that I am connected to.

I tried using the test panel in MAX, but forgot what number Even was for parity, so that is why I was having issues trying to get data (you have to go through and set everything manually in the test panel).  I will try it again and see what happens.

I was looking at the runtimes as well.  My installer says that it installed the runtime 8.0.1, but I do not see it in the list under my programs (you select National Instruments Software> Change to see all the software) and it lists Runtime 7.0 and 7.1.1 (this is on my computer that I have the development environment as well).  Does it not list the runtime in this spot anymore for LV 8.0??

I have tried uninstalling and reinstalling the software as well and that did not work either.  The IT dept is going to get me a PC with the exact same hardware and same image to see if it is the computer itself or the software.

I have not tried hyperterminal yet, I will go do that and see what happens.  I am sure that the cable is fine (since I used it on my computer and the other 2k machine that works).  It is an optical RS232 to DB-9 cable, jsut an FYI.

I will post again in a bit with the results of the hyperterminal test.

[Kenny_K]

Sorry, I was typing too fast.  For the port it is 2400 not 2600.

[Dennis_Knutson]

From your description, it sounds like you've configured everything correctly. I'll be curious to see what happens when you try Hyperterminal and MAX again.

You're right about the run-time not showing up the same way as 7.0 and 7.1. Never noticed that before. I only have an expired evaluation copy of 8.0 and it does get listed when you select 8.0 to change and it also shows up in MAX.

[Kenny_K]

I seemed to have narrowed it down to the other software that I mentioned in my first post.  It seems to be causing problems with the serial communication. 

I got another computer from the IT dept that was an exact copy of the one that does not work, except for that software (which is non'-labview based).  And I installed my software and it ran right away out of the box, no problems.  Exact same setup, same add-on serial card, same mobo manucatorer, etc.

I will ahve to contact that manufactorer or get another PC out there.

Thanks for the ideas Dennis.

Kenny

[Kenny_K]

I forgot to mention that initally I thought it was the drivers for the serial card.  Regarding the 2 computers that were identical, the one that was working (that I got from IT) installed the drivers off the cd that I had.  The one that was not working was installing the driver from msports.inf instead of from the cd.  So I thought that that was the issue.

But then I forced it to use the ones on the cd (my moving the msports.inf so it couldnt "find" it) and it still did not work, giving me the same results.

Then the last thing that was different was the extra software.

Kenny

[Dennis_Knutson]

I'm glad you got it working. If another applications is doing something with a port, you usually get a resource is being used type of error. That would have made isolating the problem easier. Hopefully, the vendor can provide some clues as to what their software might be doing.

[Kenny_K]

Ok.  Finally got it to work.  Turns out that the serial card that I was told was in the computer (the newest version of the serial card) was actually false.  The card that was in the non-working computer was a MUCH older version of the new card, that IT put in the copy computer.  The one in the non-working computer had thru hole parts on it, many which were socketed (obviously not NEW or anything made recently).

Anyway, I swapped out the old card for the new card and it worked right away.

I guess I cant assume "exactly the same" means exactly the same....

thanks again.