ucsd-e4e / asm-rpi-node Goto Github PK

Use Case: as a system admin, it would be helpful to have a command that can be used to ping all systems to get a current status.

Automate setup steps

The Data Server will be run as a systemd service. Debugging and informational output needs to be stored to a file

https://github.com/UCSD-E4E/ASM-rpi-node/tree/logging

Motor Shield library is missing attribution from https://github.com/Alictronix/Raspi-MotorHat

Node probably wants to do an exponential retry - delay about 1 s, retry, delay 2s, retry, delay 4s, retry all the way to 6 hours, then remain at 6 hour intervals. Data streams should fall back to buffered or to on-system backup.

Commit Hash

6979d9d93662690b74daed39d586df915a96683a

Steps to Reproduce?

1. Set up server and node with default settings
2. Check heartbeat log after 1 day

Observed Behavior

lots of heartbeats that drown out everything else

Desired Behavior

fewer heartbeat messages

Component

Server

Relevant Sensor Node log output

No response

Relevant Sensor Node configuration

No response

Relevant Server log output

No response

Relevant Server configuration

No response

Service should start on cold boot. Error was unable to connect to network.

Currently, IR data from the on-box sensor node has large amounts of reflection.

Desired: no reflective rings in the video

Commit Hash

d9237a7

Steps to Reproduce?

1. Run Server
2. Run Sensor Node
3. Compare timestamp of heartbeat

Observed Behavior

Server timestamps are in UTC, Pi timestamps are sometimes in PST, sometimes in GMT

Desired Behavior

Expect the same timezone

Component

On Box Sensor Node

Relevant Sensor Node log output

2021-11-22 15:25:47,795 - RemoteSensorNode - INFO - Queued Packet E4E_Heartbeat(src=a4a5090c-fc41-47d4-a180-e82cf8bfc899, dest=a4a5090c-fc41-47d4-a180-e82cf8bfc899, timestamp=2021-11-22 15:25:47.795814)
2021-11-22 15:25:47,796 - RemoteSensorNode - INFO - Sending Packet E4E_Heartbeat(src=a4a5090c-fc41-47d4-a180-e82cf8bfc899, dest=a4a5090c-fc41-47d4-a180-e82cf8bfc899, timestamp=2021-11-22 15:25:47.795814)

2021-11-22 07:42:23,793 - OnBoxSensorNode - INFO - Queued Packet E4E_Heartbeat(src=a105a7ea-3eae-11ec-8446-a0afbd87594c, dest=a105a7ea-3eae-11ec-8446-a0afbd87594c, timestamp=2021-11-22 07:42:23.793840)
2021-11-22 07:42:23,794 - OnBoxSensorNode - INFO - Sending Packet E4E_Heartbeat(src=a105a7ea-3eae-11ec-8446-a0afbd87594c, dest=a105a7ea-3eae-11ec-8446-a0afbd87594c, timestamp=2021-11-22 07:42:23.793840)

Relevant Sensor Node configuration

No response

Relevant Server log output

2021-11-22 15:42:23,804 - ClientHandler - INFO - Got heartbeat from a105a7ea-3eae-11ec-8446-a0afbd87594c (Auto-registered device) at 2021-11-22 15:42:23.793000
2021-11-22 15:42:47,812 - ClientHandler - INFO - Got heartbeat from a4a5090c-fc41-47d4-a180-e82cf8bfc899 (Auto-registered device) at 2021-11-22 15:42:47.805000

Relevant Server configuration

No response

appdirs is deprecated, switch to platformdirs

Commit Hash

0e2a318

Steps to Reproduce?

1. Configure for IP Camera
2. Run IP Camera
3. Download data
4. Check embedded timestamp against file timestamp

Observed Behavior

File with timestamp 2022-07-26T19:58:08Z has a on-screen timestamp 2022-07-26T13:24:27.

Desired Behavior

On-screen timestamp should either match local timezone or UTC

Component

Remote Sensor Node

Relevant Sensor Node log output

No response

Relevant Sensor Node configuration

uuid: a4a5090c-fc41-47d4-a180-e82cf8bfc899
type: IP_Camera
data_server: 132.249.242.142
#data_server: 132.249.242.235
port: 9000
#data_server_uuid: 33cc5438-3d39-11ec-8957-378c22225c74
data_server_uuid: 33cc5438-3d39-11ec-8957-378c22225c74
heartbeat_period_s: 300

IP_CAMERA:
        address: 192.168.2.65
        port: 554
        user: [redacted]
        password: [redacted]

Relevant Server log output

No response

Relevant Server configuration

No response