jason_fw
@jasonwhite18 · Joined April 2025
Embedded developer · logistics
- Topics
- 10
- Replies
- 48
- Points
- 0
Forum Replies Created
That’s the scenario I was scared of, thanks David. Called the operator: since our module is already approved, they want a form, the module certificate, and a two week pilot on their network. TAC registration is part of it. Pilot starts next month. Offline rule set to 3,600 s after the Recent message window, with 1,800 x 2 on the profile.
Done. 9 of the contractor’s 12 came back with a single 3 MB app0, so no OTA on those without a visit. The other 3 and all of ours have app0/app1 at 1.25 MB each, which is tight against our 1.4 MB build, so I’m switching our table to the minimal SPIFFS one with 1.9 MB slots before we go further. Good thing we checked first.
That needs USB though. The trailers are out most of the week.
Please don’t expose a Pi to the internet with a “high port”. Your Pi already keeps an outbound connection to the broker, you can send stuff down that.
On Linux you’d just write a udev rule and get /dev/loadcell. On Windows it’s messier.
That’s the argument I couldn’t make. The new-network notices alone kill the Tor idea. Set Allowed networks to our static IP this afternoon, tested with a node on my phone hotspot and it got refused, Log tab showed the reason. Boss is happy, nobody installs Tor.
Can you post a photo of the wiring? Hard to say otherwise.
Careful with Allowed networks on a home connection. Most UK ISPs change your public IP now and then, and the day it changes every sensor gets refused (CONNACK 5, the reason only shows on the device Log tab). Only use it if you pay for a static IP.
For the sockets, a 2 dollar FS1000A 433 MHz transmitter module plus the rpi-rf Python package. Sniff the remote’s codes with the matching receiver first (rpi-rf_receive), then replay them.
I’d want it too, but from what the camera docs say it’s a big change: Hermetry passes the live video through only while someone watches, doesn’t decode or re-encode it, and stores nothing. There’s no frame in the platform to run a model on. So in the meantime it goes at the edge, which is where I’d put it anyway for 9 cameras: no upstream bandwidth for 9 streams all day.
What we run on a logistics yard: a Jetson Orin Nano pulling the cameras’ RTSP streams locally, a person/vehicle model on it, and a small script that sends results to Hermetry as normal telemetry every 10 s:
{"yard.people": 2, "yard.forklifts": 1, "nogo.people": 0}Then alarm rules and charts work as for any device, e.g. nogo.people > 0 with a time-window condition for after hours on a Rules card rule. The cameras stay in Hermetry for live view, so the person who gets the alarm can open the camera.
Cheaper first step: many cameras do their own motion or line-crossing detection. If yours are supported for camera events, switch events on for the endpoint and you get event.motion as 0/1 readings on the camera device, with ready alarm rules on the profile (motion is off by default). Not object detection, but it costs nothing.
Neha’s right, and Emily, on a schematic it’s not mounted. I’ve laid out a few of these TI and Silicon Labs radio boards, and the NM parts each have a reason:
Antenna matching (your two caps and the inductor): the match depends on your PCB, enclosure and antenna, so TI leaves a pi network footprint. You build the board, measure with a VNA, and then fit the values that bring the antenna to 50 Ω. Some designs fit a 0 Ω in series and leave the shunt parts empty until tuning.
32 kHz crystal: optional. The chip has an internal RC oscillator that’s good enough for many applications. If your end node sleeps a lot and needs accurate wake timing, fit the crystal; otherwise leave it.
0 Ω and jumper footprints: alternatives, like choosing between two power paths or connecting a debug interface. The reference design keeps both options.
For your soil probes I’d keep every NM footprint on the layout, fit the crystal (sleepy end nodes benefit), and plan one tuning session with a VNA on the final enclosure before you order a batch. In your BOM, mark them DNP so the assembler doesn’t fit anything there.
That was it, tier and the high impact box. It shows up now. And the duplicate thing is real: during testing we had one double pulse when the depot Wi-Fi dropped right after a press, the door went up and straight back down. Added the request id check and haven’t seen it since.
Yep, door has its own safety edge and photocell, the ESP32 only does the pulse. Kevin, I’d rather not, the command history with who pressed it is half the reason we’re doing this.
BLE tags can’t talk to Hermetry directly anyway, you need something with internet in every building.
All wired with cut Grove cables, everything at 3.3 V except the relay on VIN. Light and loudness on GPIO34 and 35. Noise max is already the most fun chart on the board: you can see every pallet jack pass. Ciaran, yes, my first try was on GPIO4, ADC2, stuck at 4095.