ArchiveSW - Display & Data Archive Storage

looks nice and simple (the good old KISS principle)

Don’t forget some have several stations … is it on the list of things to do ?? Multi station ?

Also keep the config file well documented, some will use it on a system with no apache/nginx (ex a pure db server … and no not e, mine has apache :wink: )

2 Likes

It does not know about stations and it doesn’t care. 1 or 100 stations, it records all UDP packets. It’s smart.

It’s very simple and the install is all handled in a script that asks the user questions. It does not need apache/nginx or anything pre-installed.

It’s magic.

5 Likes

Looks great . . . can’t think of anything else to add!

2 Likes

It is magic, indeed. And being able to use good old SQL queries makes dinosaurs like me very happy!

4 Likes

I thought that dinosaurs wrote COBOL, with line numbers in Roman numerals??? :older_man:

5 Likes

Well, we did, but as my old friend Hollerith said “it’s time to move on, son . . . ‘REM’ is the future for us”. (It is possible that I made that up . . . )

2 Likes

Thats BASIC :thinking:

2 Likes

I haven’t Written COBOL in 40 years. It went the way of Fortran.

3 Likes

I was weaned on COBOL…

2 Likes

Just tossing in a thought, but perhaps you might want to make the observation types or events you save configurable on/off.

Also, why would you want to keep rapid_wind since it seems that the obs_sky every minute observation set wind gust to the max measurement rapid_wind measures during that 1-minute interval already…

Although sure a realtime display showing the needle bouncing is fun for sure…

2 Likes

There will come a time when rapid_wind data may need to be purged. It’s on the list of items I need to handle. This set of applications has grown and is getting very complicated. I am adding new features every week.

I just completed an install script that now does the entire install. I have spent hours testing and debugging and I still think there may be issues. It takes an hour to run a full test as I do a fresh install of the OS on the RPi.

Now the the install script is online, I will continue work on the internal web server for WFArchive. There is so much that I need to add:

  1. viewing and purging log and error files
  2. viewing what Alerts have been sent
  3. resetting IO Alerts on the RPi
  4. exporting data from tables
  5. running a query on a table
  6. checking the status of the Applications

Currently all the web page allows is editing the config.json file and restarting the applications.

If anyone is ready to install this please do so. I am here if there are any issues.

2 Likes

will do once my internet is back, running via my phone for now. 50 km away heavy works have simply blown up a node from the DSL provider … no ETA given for now … :roll_eyes:

3 Likes

No ETA, oh no, that’s quite a bad situation :cry:
I hope they will fix it soon, at least before the weekend. :crossed_fingers:t2:

3 Likes

Backhoe fade???

1 Like

No idea what happened but seems they need to bring the heavy stuff. Not just welding the fibers.

3 Likes

With the new web interface you will be able to Start, Stop and Restart the services.
Capture

5 Likes

slowly growing form a simple script to some full blown archive system with all the bells :slight_smile:

2 Likes

Having archived data is nice but not useful if it can’t maintained and monitored. There has to be an easy way to keep the system updated and ensure it’s working.

Maybe a way for automatic updates when firmware gets updated. I’m still thinking.

5 Likes

Hey, @eric @dan.gealt,

How about this?

Capture

for what I see this is the log section ?

1 Like