types of logging?

[IVI]

hi all,

                we planned to create a new ATE station!!!

                can any one please suggest what are all the diffrent kinds of logging we can provide to application developer????

thanks

bharathi

[Dennis_Knutson]

Your question is extremely vague. There are physical locations for log files such as local/network, hard drive, floppy drive, flash drive, tape, etc. There are different file formats such as html, xml, text, excel, binary, database, etc. How much data do you want to log, how often, what do you want to do with the logged data afterward, etc.

Since this appears to be a software question, you should re-post this with additional details to the appropriate board (i.e. LabVIEW, LabWindows, etc.).

[IVI]

hi,

thanks for ur reply

am just asking a sugestion for logging in our new ATE?

wht are all the things can be logged?(like event logging,data logging etc)

can any one suggest

some more kinds of logging types for an ATE for instruments??

thanks

bharathi

[Anna_M]

Hi bharathi,

What programming environment will you be logging data from?  Just about any data you get back from your instrument can be stored to a file, etc, likewise with events.  The data you can retrieve from your instrument will be dependent on the type of instrument.  But I think an important question for you would be to ask, what all information would you ideally like to store?

[Dennis_Knutson]

bharathi,

It sounds like you are very new to ATE and instrument programming. If that''s the case, you should seriously consider NI's TestStand. This is a test executive that comes with a complete set of tools. This includes an operator interface, report generation, and data logging. This is what I use. For each test run, it logs UUT serial number, date/time, operator name, name of the test sequence, name of the test machine, and overal status. For each test, it logs test name, test type (numeric limit/string limit/Pass-Fail), test duration, test limits, comparison type (EQ, LE, GE, GELE, etc), and test status. You can also customize it to anything else you might want. A huge advantage of TestStand is that you can concentrate on writing the actual tests and not spend a huge amount of time on the interface/reporting/logging part.

[IVI]

thanks for ur response

        we planned to use .net environment for logging

        we need errors,warnings,status,bus info and Instrument info need to be logged

        how to get the bus details in .net environment because we use diversified bus(GPIB,RS232,USB etc)?

thanks

bharathi

[IVI]

hi all,

These are all the levels we have identified

The logging basically classified as Six Levels

1)      Warning

2)      Information

3)      Debug

4)      Trace

5)      Success Audits

6)      Failed Audits

can u please help me with grouping the information in the related levels

 i can't actually diffrentiate between the Trace level and Debug level?

can any one please suggest what data can be loggeed under these two levels?

thanks

bharathi

[Dennis_Knutson]

Where or how did you 'identify' these 6 levels? I have no idea what debug or trace might refer to either. Instead of asking about what types of logging might be possible, sit down with your quality department and decide what type of data is required for your process control.