|
|
558bbfded9
|
Avoided setup-dependent error (file structuring). Implemented TNMR application search and re-open if it closes. This will not fix any particularly odd situations, but it will recover the majority of TNMR crashes and user error.
|
2025-08-15 11:15:10 +02:00 |
|
|
|
b3d243d831
|
safety
|
2025-08-05 10:33:59 +02:00 |
|
|
|
1777e4b7b1
|
debug
|
2025-07-24 10:41:02 +02:00 |
|
|
|
1990f906a3
|
debug
|
2025-07-24 10:39:03 +02:00 |
|
|
|
c2f4df30eb
|
debug
|
2025-07-24 10:27:42 +02:00 |
|
|
|
1ded495e4a
|
debug
|
2025-07-24 10:25:59 +02:00 |
|
|
|
7adf4bf452
|
on the fly
|
2025-07-21 17:10:50 +02:00 |
|
|
|
730aa61789
|
Cleaned up
|
2025-07-21 10:12:47 +02:00 |
|
|
|
10acd4a188
|
TNMR updates: workaround for the hardware module error. Added more dashboard support. Added class definition auto-generated by pycom (NTNMR.py)
|
2025-06-30 13:55:21 +02:00 |
|
|
|
388748c995
|
Fixed hardware issue?
|
2025-06-24 11:35:32 +02:00 |
|
|
|
2fce39c381
|
frappy_psi: Added support for changing the observation frequency & number of scans. Further, added an automatic dashboard load on file setup, and a template dashboard for the Scout device.
|
2025-06-13 07:58:25 +02:00 |
|
|
|
365f0a2374
|
A few things: 1. Got it working again; 2. Renamed files to make more sense; 3. Replaced template tmp.tnt with an emptied out file that previously took data, now data is collected correctly (bug, I'm not sure where this need comes from but this is, as far as I know, a permanent workaround); 4. Added automatic COM interface restart on errors compiling; 5. Implemented variable acquisition times.
|
2025-06-12 11:04:57 +02:00 |
|
