I access a RS485 programmable controller via a RS232 converter.I wrote LabView routines that work efficiently on my laptop (WinMe) and on another computer (Win98se) (one at a time, of course), but NOT on a third PC (win98se), wich is required to control my device because other hardware is installed on it.The diagnostic is the following: Proprietary program from the constructor is working on that computer; Com port is seen by NI-MAX; I can write on the port (bytes written output is non-zero) My device doesn't see anything, and doesn't respond.I checked again with the proprietary program, no settings were changed on the controller.I tried again on other computers: it works under LabView and the proprietary prog.I tried after restarting the computer, and with LabView running alone: doesn't work.O tried to install a card with additionnal COM ports: the card is installed, proprietary program runs on any of the new ports, wich are seen by NI-MAX, but nothing encouraging under LabView...Any idea, anyone?

Instrument Control (GPIB, Serial, VISA, IVI)

LabView COM acess problem

Author

!*$à##&;?

I should have tried long before! I used the repair utility in the add/remove programs. And... it repaired my rs-232 routines.
Now, it's fine (in fact, my own program was fine since... wow!).

It is so often THAT stupid, that you don't even think about it.

Message 11 of 11

(848 Views)

Instrument Control (GPIB, Serial, VISA, IVI)

LabView COM acess problem

Re: LabView COM acess problem