The SQM was delivered with logging software, “SQM Manager”, but for Win XP 32 bit. NIST is not allowed to use XP operating system computers. We are allowed to keep a few to run obsolete equipment but we cannot connect to the internet or get the machines repaired. I have two – one with a bad screen and the other that still works. SQM Manager as delivered would not operate on my XP machine. After some weeks of contacting Yankee Environmental Systems (YES), they sent us an updated piece of software and this allowed us to run SQM Manager on the XP machine. Issues noted were that the graphics windows did not autoscale, the buttons functionality is not self-evident, and there is an extra column of data in the file that is not described in the manual. It appears to be a temperature.

We asked YES for the original Labview code. After some time, they sent us the software but noted they could no longer open it because it is in an old version of Labview. Tom Larason took these elements (sqm2001.vi, sqm2001.llb, xsample.llb, parse_sqm.vi, SQM – 100 control.llb, and SQM Control Win 95.llb) and updated the 2001 versions to Labview 2013 (not all would update).  Fig. 1 is a screen shot of how the YES program looks in Labview 2013. He had to rewrite the “Parse” vi and he redid the serial VISA. It will run the SQM. We note that a header row is now saved in the data file, but otherwise Tom kept the formatting the same as YES: except for between the time and the first SQM data field, all fields are separated by a blank and a comma, including at the end of the line (we will change this for the NET version). A call is made to the SQM – with one command – and then this string is parsed to get the SQM fields. This does not include date or time – this information is added by Labview to the front of the data stream. An example of the YES SQM on the XP machine data file is attached.

Tom has reworked the SQM logging program. For now, he kept the data file format exactly. He added a table to the front panel to show the data, and is anticipating additional commands related to set up etc.  This leads to Problem 2 – what do we want this program to look like and how to function? NOTE:  The SQM has no on/off switch; when plugged into to AC the electronics are on and you can log data – even with the knob in the “OFF” position. So we plugged it into a power strip and use that for the on/off switch. With AC on, and the SQM switch is moved to “STANDBY”, the temperature controllers come on. The lamps come on when you switch to Hi, Med, or Lo. So, the software must be designed with this in mind, so the metadata is correct as to who did what when.

A next step is Log Sheets, stay tuned. The data stream will be what it is now, but we have freedom on the metadata and operating protocols.

Fig. 1 Screen shot of sqm2001.vi (LabVIEW 5.1 version converted to LabVIEW 2013).

Fig. 2 Screen shot of updated SQM Monitor.vi version 0.0 (LabVIEW 2013).

The SQM logs these variables:
Date and time;
1A set current
1A actual current
1A diagnostic code (we don’t care about this)
3A set current
3A actual current
3A diagnostic code (we don’t care about this)
Photodiode 1 voltage
Photodiode 2 voltage
Photodiode 3 voltage
Temperature 1
Temperature 2
Temperature 3
Temperature 4

 The photodiodes are “blue” “red” and “broadband” but looking at the data so far I think the manual has them mislabeled so I’d just number them for now. The manual mentions 3, not 4 temperatures so for now we’ll call them 1 to 4 since we are not sure what part of the SQM they are attached to.

 Traditionally, the log sheet would be geared to the radiometer measuring the SQM. The SQM is a source, and the source part was in the “header” part of the log sheets. So we need to think about how to record the manual steps related to the SQM described below. I think we’d have a MOBY SQM log sheet and a CAS SQM log sheet to account for the differences in the MOBY and the CAS?

 The log sheet would could have a place to note (occasionally?) the actual SQM currents, photodiodes, and temperatures. The set currents cannot be changed so that can be hardwired onto the form.

The log sheet would have SQM and MOBY/CAS filenames – and we need a convention how about SQM_YYYYMMDD_xxx.txt? (NOTE we plan on the same file format as the Version 2 NPR file).

 Now, the big SQM issue I see is the manual steps, and also what happens when you change output light levels. Here is a typical sequence:

1. The operator either plugs the SQM into the wall socket or turns on the power strip that connects it to the wall. The electronics are on whenever the SQM is plugged in, and I don’t think this is what we want (to leave in on all the time). But, we do want it to be fully warmed up. So, one might turn on the AC hours or even the day before: We need to record the date and time when this happened, and this is a completely manual operation. NOTE here the SQM knob is “off” but the electronics are ON.
2. Next, the operator switches the knob from “off” to “standby”. This turns on the heaters for the photodiodes and shunt resistors. This date/time needs to be recorded, and again, it is a manual operation. At the moment, we don’t know how long it takes to stabilize, and this time may depend on ambient temperature.
3. Housekeeping data logging program. I am not sure about this sequence. We have the option to start logging when the SQM  was plugged in (electronics on), turned from “off” to “standby” (heaters on), or a lamp level initiated (knob from “standby” to “Low” “Med” or “High”. My vote would be when we go from “off” to “standby” we start logging data. This will capture the lamp ramp up.
4. Changing levels. Now, this is completely manual. At the moment, we assume we want to run all three levels (1A on; 3A on, both 1A and 3A on). It might turn out there is a preferred sequence due to thermal effects, but for now we must assume random. Choices:
   1. we don’t parse the file and let the processing programs figure out what happened when; but the log sheet makes a note of the time the setting was changed
   2. we make separate files, copy the header information but allow for revisions, whenever the lamp level is changed.
   3. note that if you start at HIGH, then MED, then LOW, the 1A set is on, off, on and this led to a mess of notes in my logbook. It would also be true for HIGH, LOW, MED sequence the 3A would be on, off, on.
5. Turning off the SQM:  same goes:  Lamps; heaters; electronics  -- there are multiple meanings of “turn off”! When would you stop logging – this is TBD.
6. which instrument and what configuration is looking at the SQM
7. The rows would be the instrument files and TBD fields. Fields could be: the actual SQM currents, photodiodes, and temperatures; temperature and RH; CAS/MOBY instrument settings (integration time/bin factors); etc. and a Remarks section
8. Location and or Lat and Long
9. purpose of experiment