Projects
Development decisions, tests, and lessons from the LoRa project.
6posts
ProjectsLoRaThirty sensors on one shared LoRaWAN gateway, and a node that would not join. With no CRC error to go on, the answer turned out to be the sync word set by a single toggle.
ProjectsLoRaThe radio worked, but the sensors were in the field. A PC program that answers like one turned up four contradictions in the protocol document and a timer bug that split good frames in half.
ProjectsLoRaCalling each device in turn fixed the collisions but cost 42 seconds a round, until we stopped waiting for replies. Plus the uplink monitor and the configuration tool built along the way.
ProjectsLoRaAn automated clearance check that reads 0 mm3 is not the same as a case you can build. Five assembly failures, and the worst was a check that ran perfectly and reached the opposite conclusion.
ProjectsLoRaThree wrong theories built on partial logs, and then a line-by-line comparison of the full record explained all thirteen uploads at once.
ProjectsLoRaFrom cutting the enclosure to data that never reaches the server, five posts on a LoRaWAN sensor network - every one of them starting with a signal that said everything was fine.
