patricktokeeffe/rpi-ebam-plus

Metadata to log

Opened this issue · 1 comments

patricktokeeffe commented

The entire settings report can be a <pre> block at the bottom of status page. But how often to update?

  1. hourly: Best case for display, because matches data update frequency, but hard to save hourly because requires tabulation.
  2. daily: Pretty slow for display but easier to handle daily settings report files since data is already daily binned.
  3. in between: update hourly, but only retain most recent file as the daily (e.g. 23:00 report)

Which params make sense to highlight up front?:

  • Serial Number
  • Location
  • RealTime Period
  • Conc Type
  • Background
  • PM Inlet type

And to make into statistics for plotting?:

  • Location?
  • Data Average?
  • RealTime Period?
  • K?
  • Background
  • Usw?
  • Audit span
  • Time Zone, as UTC hour offset? (requires separate numeric parser)
  • slope/offset values from sensor table at the end

Example settings report (w/ checksums)

E-BAM PLUS Settings Report*02227                                                                                                                                                                                                      [1/1490]
2019-06-18 14:39:02*00956                           
   
      Firmware, 82102, R1.1.3*01749
          CPLD, 81699, R1.0.0*01355
       Display, 82451, R1.0*01587
 Digital Sen 1, 597, 10503-01, R01.0.0*02292
*02612
 Serial Number, W15096*01713
      Location, 1*01142
     Baud Rate, 9600*01251
Ethernet FlowControl, NONE*02388
        AIRSIS, OFF*01010
  Data Average, 1 HR*01484
RealTime Period, 15*01608
   Tape Period, 1 HR*01444
 Tape Pressure, 250*01542
 Standard Temp, 25 C*01565
 PM Inlet Type, PM2.5*01561
     Conc Type, STANDARD*01666
             K, 1.012*00809
    Background, 0.0010*01515
           Usw, 0.325*00995
    Audit Span, 0.771*01394
    Conc Units, ug/m3*01581
      USB Days, 120*01082
     USB Files, USER*01320
Analog Range 1, 0-5.0 V*01634
Analog Range 2, 0-5.0 V*01635
     Conc Span, 1000 ug/m3*01709
   Conc Offset, 0 ug/m3*01713
Hourly Timestamp, ENDING*02136
  FT Set Point, 45.0*01379
     FT P-Gain, 0.500*01173
     FT I-Gain, 0.300*01164
RealTime Alpha, 0.2316*01679
RealTime Gamma, 0.1500*01670
   Beep Volume, 10*01313
ModBus Address, 1*01453
    Byte Order, 512*01300
  Factory Mode, OFF*01508
 Flow 1 P-Gain, 10000.000*01568
 Flow 1 I-Gain, 5000.000*01517
 Flow 2 P-Gain, 10000.000*01569
 Flow 2 I-Gain, 5000.000*01518
   Cloud Modem, NONE*01509
     Time Zone, UTC -08:00*01650
    Clock Sync, NONE*01445

  Name, Offset,  Slope*01763
 FLOW1, -0.153,  1.030*01111
 FLOW2, -0.255,  0.991*01130
    AT,  0.940*00636
    BP, -0.220*00637
    FT,  0.037*00638
 UPPER, -0.889*00812
 LOWER, -1.279*00803
   FRH,  0.000*00666
*00000

     DAC Cal 1, 0.0,21,5.0,52729*01606
     DAC Cal 2, 0.0,-21,5.0,52732*01646
*00000
patricktokeeffe commented

Deciding to just concatenate reports into long daily files for storage and to keep latest report only for consumers.

Which params make sense to highlight up front?:

[x] Serial Number
[x] Location
[x] RealTime Period
[ ] Conc Type viewable in reports
[ ] Background added to rpimonitor stats only
[ ] PM Inlet type viewable in reports

And to make into statistics for plotting?:

[x] Location?
[ ] Data Average? can review reports
[x] RealTime Period?
[ ] K? " "
[x] Background
[ ] Usw? cannot find documentation
[x] Audit span
[ ] Time Zone, as UTC hour offset? (requires separate numeric parser) text is enough
[ ] slope/offset values from sensor table at the end maybe later
[x] filter temperature setpoint