Is there an autonomous MAX config logging capability?

[Bill_Raskob]

Do any of the NI services (e.g. nimxs.exe, nipalsm.exe, etc.) have an option to save a log of the discovered hardware each time they are started?  I am looking for a way of obtaining snapshots of device info (installed slot number, device model/serial no., firmware rev., etc.) in a PXI system.  I don't want to rely on user login to obtain the snapshot, and rather than create my own service am trying to "reinvent the wheel."

[Bill_Raskob]

oops - I mean "not reinvent the wheel"...

[Justin_E]

Hey Bill,

You can create a log file in Measurement and Automation Explorer that provides a detailed listing of all the hardware in your system. To do this, in MAX go to File -> Create Report... In the next window, select Technical Report. These files are reports that customers send to us sometimes when they're having issues with their system, and contain lots of useful information. This process generates a zip file called ni_support.zip. If you extract the contents of this zip file, there is a text document titled ni_pal_report.txt. This document contains information for all of the hardware listed in MAX.

To automate this, there is a function in LabVIEW called MAX Generate Report.VI that generates this zip file. Make sure you create a constant/control and select Technical Report to generate this file.

[Bill_Raskob]

Justin,  Thanks for you reply.  The ni_pal_report.txt has what I'm looking for.  The only issue remaining is how to get this report generated autonously each time the system boots up.  I suppose the LabVIEW function you reference could be coded in an executable and run as a service.  Is this how you would approach this, or are you aware of a more direct method?

[Justin_E]

Bill,

I think coding the LabVIEW function into an executable and running it as a service when your OS boots is how I would do this. You can use a property node for your VI to make your front panel invisible so that all the end user sees is the executable in the taskbar. Information on running a VI when Windows boots can be found here : KnowledgeBase 257EMOSG : Running a VI when Windows Boots

[Bill_Raskob]

Justin, thanks.  I took a look at that knowledge base article, but I think that there is some misused terminology.  I'm fairly sure the method the article uses won't run the vi on boot, but rather when a user logs in.  I need my log to run even if a user does not log in.  That is why I think article

KnowledgeBase 2TJE6Q8E : Running a LabVIEW Application as a Windows NT/2000/XP Service may be what I want.  Any comment on running the MAX function as a service?

[Justin_E]

Hey Bill,

I don't think that KnowledgeBase article is going to solve your problem. In fact, I don't think you'll be able to run a Windows service without having some sort of user login, as the OS won't have anything to run off of. One thing you could do is develop a user account that specifically runs this service, and enable auto-login on Windows. Information on automating the login process can be found in this Microsoft article : http://support.microsoft.com/kb/315231