Libelium Waspmote Smart Parking v2, Technical Manual

Page: 20 / 155

Smart Parking node
In the next video-clip you can see how the "magnet start-up" is performed: Magnet start-up
After fi nishing the "magnet start-up", the node starts working normally for the rest of the time. No more three-time
"magnet resets" are needed in order to reset the device properly. So if a 4th magnet reset or software reset is
applied, the device will reset and continue working normally again.
Important :
The "magnet start-up" is only mandatory when the node is powered from a power-off state. In other words, when
the device is set to a "ready to install" state.
3.6. How the node works
3.6.1. Frame types
The Smart Parking architecture manages different uplink and downlink frames.
The next table shows the Uplink frames:
Frame type #num Description
Start frame 1 4 First frame sent by the node when starting (with params settings)
Start frame 2 5 Second frame sent by the node when starting (with params settings)
I nfo frame 0 Used to inform a Parking Status change
Keep-alive frame 1 Used to inform the device keeps working since last reported status
Con fi guration uplink 2 Used to con fi rm a "Con fi guration downlink" was applied or not
RTC update request 7 Used to request for an RTC sync once every day
The next table shows the Downlink frames:
Frame type #num Description
Con fi guration downlink 3
Used to update the node parameters. After the customer sets up a new
node con
fi guration in the Remote Con fi guration Form a new "Con fi guration
downlink" frame is enqueued into the LoRaWAN network server ’ s downlink
queue.
RTC sync frame 6
Used to sync the node ’ s RTC to the server ’ s timestamp. I t is the mandatory
response to "Start frame 1" and "RTC update request" uplink frames.
The uplink frames are 11-byte long to always comply with the LoRaWAN datarate worst case scenario. Their
structure consists on 2 parts: header and payload. The "header" format is always the same for all uplink frame
types. On the other hand, the "payload" format may be di
ff erent for each frame type.
Header Payload
2 bytes 9 bytes
Regarding the downlink frames, they have variable length and its format is private to the customer. The "RTC sync
frame" is the mandatory response for both "Start Frame 1" and "RTC update request" frames. The "RTC sync frame"
provides the server time to the nodes in order to keep the RTC updated. Also, the "Con
fi guration downlink" is an
asynchronous frame sent by the server when the Remote Con fi guration Form is managed by the customer.
You must keep in mind that when a downlink packet is requested there are usually some issues related to LoRaWAN
- 19 - v7.5