In Lookout 4.0.1 why does launching the L4P tie up the modem when there's no reference to the modem in the file??

[JW_Tech]

Running Lookout 4.0.1 on an NT machine. Lookout launches fine, but when the process file is started the "TR" lamp on the modem lights up. There is no reference to the modem in the L4P; no objects use it. The DL205 object uses Com 1 (configured in Lookout as hardwired)via DB9 serial RS-232 to communicate with the PLC port but computer's modem is on Com2. This anomaly is preventing another application from using the modem to dial-out alarms. What's up with this?

[Khalid]

This is odd indeed. And might very well be a bug. However, I would first check this on different computers -- are you using the built-in COM ports or a serial card? -- because the serial card could be the culprit, as well.

Also, just to be doubly sure, open the LKS file for your process in a text editor and search for the string "COM2".

Regards,

Khalid

[JW_Tech]

Khalid:

We do not supply the computer used by the customer so we cannot control consistency or choice of hardware. That said, we HAVE successfully used Lookout and the other application (the one that's trying to access the modem) many times in other computers without having this "conflict".
The built-in COM port is being used.
I did check the text in the LKS. file before posting: no reference to COM2.
The site is 10 hrs away. They won't allow any VPN connections, so we can't assist remotely.
Unless someone can add another suggestion, I'm resigned to hand this over solely to the customer's IT dept saying it's THEIR problem.

Thanks,
JW_Tech

[GValdes]

JW_Tech,
This is strange. I would have them verify that they don't have serial port conflicts in Windows. For example, if they open a Hyperterminal session for COM1, I wonder if that will also affect COM2. There is one last thing to verify. In Lookout, go to the Options menu and select System... . In there, on the right-side of the screen, make sure that the "Log alarms to:" window is set to none.
Unless we are missing to find an object that tries to open the serial port, I cannot see why it is trying to open COM2.

I hope that helps,

GValdes