You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some things are specific to manufacturers. For example, it has been complained
that percentual timing quality is useless. Manufacturers could add their own
specific timing quality info.
One more thing that would be nice to have is an optional "instrument ID"
that unambiguously identifies the response. Could have separate IDs for
sensor and datalogger that are manufacturer-specific or refer to NRL.
+1 on a standard key-value to identify logger and sensor type and serial numbers. Although getting the sensor correct is unlikely to be automatic as the logger that builds the records may only know that it has voltages on pins and have no idea of the sensor connected to it. You probably want a "model" and a "serial number" as model is often sufficient to get nominal response while serial helps with calibrated response and with inventory control.
+1 on a standard key-value to identify logger and sensor type and serial numbers. Although getting the sensor correct is unlikely to be automatic as the logger that builds the records may only know that it has voltages on pins and have no idea of the sensor connected to it.
There can be a plug-and-play protocol, like VGA monitors were recognized by the graphics card using I2C.
You probably want a "model" and a "serial number" as model is often sufficient to get nominal response while serial helps with calibrated response and with inventory control.
Indeed, I forgot the serial number.
The text was updated successfully, but these errors were encountered:
Discussion branched off #2. Concerns DRAFT20170622.
@andres-h
@crotwell
@andres-h
The text was updated successfully, but these errors were encountered: