DignosticFile= setting in .ini file not working?

[erblock]

When editing Lookout.ini file in Lookout 6.1 and adding setting as follows:

[COM9]

DiagnosticFile=C:\com9.txt

or

[COM3]

DiagnosticFile=C:\Program Files\National Instruments\Lookout 6.1\com3.txt

No logs are created for the named COM port.

I know I used this feature sucessfully back in Lookout 4.5 and earlier, maybe even in Lookout 5.1.

Please confirm and help!

[Ryan.S]

You can configure this in Lookout. Go to Option->Serial ports, select COM9, check "Enable", input the diagnostic file path, "Accept".

Close Lookout, then open lookout.ini. You will see the following codes.

DiagnosticFileEnable=1
DiagnosticFile=c:\test.txt
DiagnosticAllHex=1
DiagnosticTimeStamp=1
DiagnosticTimeStampDateFormat=73

So, you need to add DiagnosticFileEnable=1 to make it active.

I'm not sure how it worked in Lookout 4.

[erblock]

Hi Ryan,

Thanks for the help...

However, Lookout 6.1 will not actually write the file!  I have tried the default path and simple c:\logcom3.txt type of paths with full permissions....No LUCK!

Did you folks break this in LK 6.1 ?

Ed

[Ryan.S]

Hi,

I tried Lookout 6.1. It can log the diagnostic file without any problem.

I just follow the steps I said, select the com port, and enable the log.

Which driver do you use?

[erblock]

Hmmm....

The settings do get added to the .ini file, but the file never appears.  How large is the buffer that is used and will it wait until the buffer is full to open and write the file?  The unsolicited ASCII is only taking in 26 bytes every 4 seconds.  Maybe this is the issue?  Also, there is no outgoing traffic, only unsolicited incoming.

Message Edited by erblock on 12-05-2007 10:16 PM

[Ryan.S]

I think I have reproduced the problem.

Try this example. I'm able to log the file.

http://zone.ni.com/devzone/cda/epd/p/id/3818

But when I use labview on another computer to send Ascii messages to Lookout, the log file won't be generated.

I will look into this.

[Ryan.S]

This seems a bug in Lookout. Lookout is able to log all the data outgoing, and all the response data. But the unsolicited data, which is not recognized as response data, won't be logged.