installation of lookout fails or if it installs lookout doesn't launch

[khalidfaridi]

I have serious problems with lookout 5.0 installations. Until week back all was fine. Now Lookout doesn't install in Win2k adv server and win XP professional. If it does some times, the Service Manager wouldn't launch and hence neither would lookout. I have done a new xp installation just to see it work and it doesn't. While in win2k, if I install ver 4.5 no problems. Haven't tried same in win XP. SOS

[nickf]

khalidfaridi,

Can you post some more detailed information about your system configuration? Are you upgrading a previous installation of Lookout, or installing it from scratch?

You also mentioned that you tried a fresh install of WinXP and then tried to install Lookout. Were you logged in as Administrator when you performed the installation? Did you see the same error this time? Does Lookout return any specific errors, other than the Service Manager not starting?

Regards,

Nick F.
Applications Engineer
National Instruments

[khalidfaridi]

Hi Nick,
Yes indeed I was logged as an administrator in XP, new installation. And yesterday I managed to install Servicepack 4 in Win 2k but same result. However, LO4.5 installs without an ado.

To tell you in detail:- I run setup, select complete installation, the wizard shows only 3 items (program files, documents and ...), upon clicking Next, it says "installation complete" without really doing anything.

To beat the system, I select custom install, select each n every module...., it gives error 1601 or 1602 saying not able to install.

Initially I was able to set up once or twice but then the Service Manager doesn't start, hence errors during Launch about "time service not started".

As mentioned above, the Lookout 4.5 and 4.0 are smooth as silk.

I have used DELL and assembled machines both, same result.

You think any compatibility issues? I heard somebody saying that Lookout is tested only on Win2k Professional and not server/XP et al?

Eager to hear from you..

regards

Khalid Faridi

[nickf]

Khalid,

You are correct about Win2k Server edition; National Instruments has not tested Lookout on this platform and we can not guarntee that it will work. XP and Win2K Professional should work fine.

Did you try to just install Lookout 5.0 on the XP machine, or did you try to install previous verions of Lookout first? There should be an issue with this anyway, but it would be good to try for trouble shooting purposes. (Definitley do not install Lookout 5.0 over Lookout 3.8 versions and earlier. This will not work).

When you started with fresh installations of Windows did you completely re-format the hard drive of said computer, or did you "repair" the Windows installation?

Also, just to make sure you're not having any trouble with registration/actication right?

Regards,

Nick F
Applications Engineer
National Instruments

[khalidfaridi]

(You are correct about Win2k Server edition; National Instruments has not tested Lookout on this platform and we can not guarntee that it will work. XP and Win2K Professional should work fine.)

Thats bad news for me.

((Did you try to just install Lookout 5.0 on the XP machine, or did you try to install previous verions of Lookout first? There should be an issue with this anyway, but it would be good to try for trouble shooting purposes. (Definitley do not install Lookout 5.0 over Lookout 3.8 versions and earlier. This will not work).))

The situation is slightly better now. I installed XP afresh and Lookout 5.0 works great on it. But it doesn't recognize the com ports attached to internal modems. These modems work with Hyperterminal and other diallers but lookout says NO.

Win2k was a REPAIR. Still same problem, 4.5 works good but 5.0 doesn't install. I am formatting tomorrow and shall post the results later. I have several more peculiar issues. With some installation, I am able to use Mitsubishi objects (two with two internal modems) and dial out to RTUs. But can't hangUP due to absence of OffHook member. If I try ASCII object to dial out one modem works, the other doesn't. I tried several internal modems but same result. BEcause of these situations I have ended up struggling to somehow manage to install two internal modems and make lookout 5.0 and ASCII objects to dail out for me.

No registeration issues, the Lookout is licensed. Besides, since it doesn't install, why that can be an issue.

Warm regards

When you started with fresh installations of Windows did you completely re-format the hard drive of said computer, or did you "repair" the Windows installation?

Also, just to make sure you're not having any trouble with registration/actication right?

Regards,

Nick F
Applications Engineer
National Instruments

[nickf]

>>But it doesn't recognize the com ports attached to internal modems. These modems work with Hyperterminal and other diallers but lookout says NO.

Have you configured the modems in the Options>>Serial Ports configuration dialog? If so, is Lookout returning any specific errors when you try to use those serial ports?

>>But can't hangUP due to absence of OffHook member.
The drivers in Lookout are designed to give you a constant-as-possible connection to your device. So this is expected behavior. One thing you can try is to configure both an ASCII object and the Mitsubishi object for the same COM port. As long as the Mitsubishi object is not configured to poll constantly you might be able to disconnect the modem by using the ASCII object.

>>If I try ASCII object to dial out one modem works, the other doesn't. I tried several internal modems but same result. BEcause of these situations I have ended up struggling to somehow manage to install two internal modems and make lookout 5.0 and ASCII objects to dail out for me.
Can you describe this behavior in more detail? Exactly how do the modems "not work". Can you configure one or the other, or only one of them? After configuring the modems in the Serial Ports configuration, do both ports work properly?

Regards,
Nick F.
Applications Engineer
National Instruments

[khalidfaridi]

>>But it doesn't recognize the com ports attached to internal modems. These modems work with Hyperterminal and other diallers but lookout says NO.

>>Have you configured the modems in the Options>>Serial Ports configuration dialog? If so, is Lookout returning any specific errors when you try to use those serial ports?
Yes Nick, Indeed. Lookout says "Unable to Open COMn"

>>But can't hangUP due to absence of OffHook member.
>>The drivers in Lookout are designed to give you a constant-as-possible connection to your device. So this is expected behavior. One thing you can try is to configure both an ASCII object and the Mitsubishi object for the same COM port. As long as the Mitsubishi object is not configured to poll constantly you might be able to disconnect the modem by using the ASCII object.

I have exactly the same. The problem is not all my modems, internal ones, work with ASCII object!!!!!!!!! I have spend days and days to somehow manage to use two modems but no way. I reckon there is some command which needs to be modified. But I am at loss to understand that. I tried modify this command- RqV1.txt=>"AT+MS=V32,1,0,4800,0,4800" but no use. Lucky for me that at least one modem works and am able to show some results.


>>If I try ASCII object to dial out one modem works, the other doesn't. I tried several internal modems but same result. BEcause of these situations I have ended up struggling to somehow manage to install two internal modems and make lookout 5.0 and ASCII objects to dail out for me.
>>Can you describe this behavior in more detail? Exactly how do the modems "not work". Can you configure one or the other, or only one of them? After configuring the modems in the Serial Ports configuration, do both ports work properly?

Same as above. Modems do not respond at all. While external modems also do not work at all no matter what cable configuration I use. I tried direct, crossed, 1,6 shorted to 4 at both ends, used only crossed and ground, wherever anything about rs232 i could see on net i tried but no way!!!

I can't really manage with one modem since I need to configure one with dial out and another with dial IN. I really do not know how dialIN will work in lookout 5.0.

I even tried copying the modem profile.....

Regards,
Nick F.
Applications Engineer
National Instruments

[nickf]

khalidfaridi,

>>I have exactly the same. The problem is not all my modems, internal ones, work with ASCII object...
I'm confused. I thought you said your internal modems didn't work? Can you tell me exactly how many modems you are using and what thier expected configuration is?
Modem n:
Manufacturer:
Configuration String:
Internal/External:
COM Port Assigned:
Works Reliably (Yes/No):

Also, make sure you are following the modem configuration settings in the Lookout help file.
Search for "Dial-Up Serial Communication." This document describes how to properly configure the serial cable you use to connect to external modems.

The following DevZONE entry may also help you configure your modems:
http://zone.ni.com/devzone/conceptd.nsf/webmain/108F6FA501DC4A2E86256A6F00519BEF?opendocument

If you can, post the serial diagnostics log file(s) that is/are generated by Lookout. This log file can be enabled per COM port in the Options>Serial Ports dialog box. When I tried to configure an external modem (I don't have one connected), Lookout generated the alarm "No response from local modem [COMn]". The serial log file showed the commands that were sent to the phantom modem.

You will need to reference the documentation for each of your modems to ensure they are correctly configured to work with Lookout as decribed in the documentation.

If you are having trouble with any of your external modems can you verify that the serial ports are properly configured by performing a simple loop-back test, or by connecting two COM ports together and verifying communication?

Regarding using one of your modems in a "dial-in" configuration I don't think this configuration has ever been tested at National Instruments. Also, as far as I know Lookout doesn't support waiting for a connection. If you get this working I'm curious to learn how you configured your system.

[khalidfaridi]

---

@Tychova wrote:
khalidfaridi,

>>I have exactly the same. The problem is not all my modems, internal ones, work with ASCII object...
I'm confused. I thought you said your internal modems didn't work? Can you tell me exactly how many modems you are using and what thier expected configuration is?
Modem n:
Manufacturer:
Configuration String:
Internal/External:
COM Port Assigned:
Works Reliably (Yes/No):

Also, make sure you are following the modem configuration settings in the Lookout help file.
Search for "Dial-Up Serial Communication." This document describes how to properly configure the serial cable you use to connect to external modems.

The following DevZONE entry may also help you configure your modems:
http://zone.ni.com/devzone/conceptd.nsf/webmain/108F6FA501DC4A2E86256A6F00519BEF?opendocument

If you can, post the serial diagnostics log file(s) that is/are generated by Lookout. This log file can be enabled per COM port in the Options>Serial Ports dialog box. When I tried to configure an external modem (I don't have one connected), Lookout generated the alarm "No response from local modem [COMn]". The serial log file showed the commands that were sent to the phantom modem.

You will need to reference the documentation for each of your modems to ensure they are correctly configured to work with Lookout as decribed in the documentation.

If you are having trouble with any of your external modems can you verify that the serial ports are properly configured by performing a simple loop-back test, or by connecting two COM ports together and verifying communication?

Regarding using one of your modems in a "dial-in" configuration I don't think this configuration has ever been tested at National Instruments. Also, as far as I know Lookout doesn't support waiting for a connection. If you get this working I'm curious to learn how you configured your system.

---

Hello,

Finally I have sorted all the issues.
I have handed over my successful project to R&D, Jucao Liang
Yes, lookout wouldn't wait for an incoming call, perhaps. I configured modem to pick up call after one ring, configured COM port as hardware and all is fine.

The Mitsubishi object now has an offHook member. Hence before dialing I remove OffHook, dial, collect data for a duration, Send OffHook, wait for proper hangUP and then dial next number....

I no more use ASCII dialer due to its various shortcoming as compared to Direct Dialing from the driver.

Nevertheless, I was able to use ASCII dialer for more than one modem by removing some commands from it.

My Project, Mercy from Lord, is successful and looks good.

Special thanks to Jucao and Michel Haddad.

If anyone needs the project, he can contact me.