bclswl0827
commented
1 week ago If you have read the code of AnyShake Explorer (master or next branch), you will find that whenever the data collected by the sensor is sent to AnyShake Observer, instead of "only sending when abnormal data occurs", this is because the AnyShake Observer need to stream and archive data in a timely manner so that users can access it at any time.
LoRa is theoretically possible, but after my testing (I'm using AS32-DTU-100), at a sampling rate of 100 sps, the actual sampling rate calculated by AnyShake Observer is only 80 sps. I would rather recommend transmitting data wirelessly via TCP over 4G network, otherwise, RS485 would be a better choice.
You mentioned firmware updates, if I understand correctly, do you mean OTA?
hey @bclswl0827
thanks for this hardware . It looks like what I need for an EU Science project I am working with .
the next branch looks good.
https://github.com/simpleiot/simpleiot Is what I use for field sensors like the hardware in question. It’s based on nats.
So when you have hundreds of sensors you can ensure data gets to your servers and it will use a store and forward pattern . I don’t know if you’re only sending when abnormal data occurs on the hardware ?
I have used Lora which is perfectly fine for seismic data at the baud rates your using.
Lora nodes are run by most Universities too to allow large spans of geography .
it’s low power and hardware that works with tinygo exists.
Your base board is an arduino , and so tinygo will do nats works fine there.
https://tinygo.org/docs/reference/microcontrollers/lorae5/
https://pkg.go.dev/tinygo.org/x/drivers/lora
https://github.com/hybridgroup/tinyglobo has code but links to the global Things Network for Lora.
I was also wondering if you have designed for firmware updates yet ? Nats is often used to do that too .
if any of this sounds useful let me know ..