Wrong temperature parameter

iotfun
Posts: 40
Joined: Tue Sep 20, 2016 11:26 am

Wrong temperature parameter

Post by iotfun » Tue May 02, 2017 10:28 am

Dear Support,

we bought some smart parking sensors this January.
Then we bought some new smart parking sensors last month.
According to the documentation of smart parking system, the Info frames and Keep-alive frames contain their internal temperature parameter.

The sensors bought in January send believable values (5 to 40 celsius degree).
The new sensors send very strange values e.g. 921, -487 etc.

The new sensor were sent with the newest firmware (2.0.0 EU). The old sensors have 1.04 EU firmware.

Has the content of the frames changed?

There are some keep-alive messages from one of the new sensors (S/N 1AF937):

01a609001b001bf3ed04ef00 — 889 Celsius degree
01a7091e1c0046f3de051000 — 921 Celsius degree
01a80a001c0040f3d004ea00 — 921 Celsius degree

There are some keep-alive messages from one of the new sensors (S/N 1AFA0A):

81381001f4f9b50654fae500 — -327 Celsius degree
81391201f4f9b00638faf300 — -327 Celsius degree
813a1501f3f9820678fa8600 — -359 Celsius degree

How can we decode these strange temperature values sent by the new sensors?

Best regards,

Ferenc

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Wrong temperature parameter

Post by libelium-dev » Tue May 02, 2017 3:34 pm

Hi,

The frames are a little different in the new firmware. We are going to upload the Smart Parking guide in the next few days. Sorry for the inconveniences.

Now, the way to convert the temperature is simpler than the above version. The byte 5 is the temperature (1b and f4 in your case). You should convert from signed hexadecimal to decimal. For example, 1b is 27ºC and f4 is -12ºC.

Don't hesitate to ask if you have more doubts.
Regards

iotfun
Posts: 40
Joined: Tue Sep 20, 2016 11:26 am

Re: Wrong temperature parameter

Post by iotfun » Thu May 04, 2017 12:39 pm

Dear Support,

I guess the Start frame 1 also contains the temperature in the new formula.
But when our back-end software receives the start frame 1 from a node it does not know about its firmware version. So the parsing of message Start frame 1 may fail.
The software will be notified about firmware version in Start frame 2 only. Of course when the node is restarted again, the back-end software will know its firmware version. Except at the first start.

I am looking forward to reading the new Smart Parking guide.

Best regards,

Ferenc

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Wrong temperature parameter

Post by libelium-dev » Fri May 05, 2017 11:25 am

Hi,

Yes, the Start Frame 1 also changed the temperature bytes, now it is in the byte 2. This change has been made to improve the stability of LoRaWAN communication. Now the frames have 11 bytes instead of 12 bytes. You could check the firmware version according the frame size.

Sorry for the inconveniences, hope the new guide will be available in a few days.

Regards

Ensamine
Posts: 48
Joined: Wed Jan 04, 2017 9:48 am

Re: Wrong temperature parameter

Post by Ensamine » Mon May 08, 2017 8:08 am

Hi

When will the guide be released?

This is an important change and if you dont notify us in advance this can make our applications instable!

Is there any release management process in place so you can notify all your customers of new releases and upgrades?

Regards

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Wrong temperature parameter

Post by libelium-dev » Mon May 08, 2017 12:56 pm

Hi,

We hope the Smart Parking guide will be available this week. Sorry for the inconveniences.

Usually we announce new release with a post in the forum, such as these posts for new APIs or new software upgrade for Meshlium.
viewtopic.php?f=51&t=23134
viewtopic.php?f=61&t=24127

Surely when the Smart Parking guide is available, we will announce the release of the new parking firmware in the forum(although it is already available in the Smart Device App) .

Don't hesitate to ask if you have any doubt about the new firmware.

Regards

irtaza123
Posts: 26
Joined: Tue Jul 17, 2018 9:13 pm
Company: CONURE TS

Wrong Temperature Reading - Parking Sensor

Post by irtaza123 » Mon Dec 10, 2018 4:09 pm

Hi Libelium Support,

We have been monitoring temperature through Keepalive frame byte 4 as per the guideline butthe temperature reading does not go with the outside temperature. Sensors are placed in he parking lot though.

Looking for your advise.

Thank you,

Irtaza

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Wrong temperature parameter

Post by libelium-dev » Tue Dec 11, 2018 9:13 am

Hi,

What temperature values are you getting?

Could you please also share the frames for each temperature value? So we will check if the conversion is correct.

Regards

jluengo83
Posts: 30
Joined: Tue Sep 18, 2018 10:04 pm
Company: Conure Telecom

Re: Wrong temperature parameter

Post by jluengo83 » Tue Apr 23, 2019 5:08 pm

Hello,

Could you tell me what is the temperature from the following payload:

01 03 0e 32 22 f8 40 f8 71 05 4e


Thank You.


Jorge Luengo

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Wrong temperature parameter

Post by libelium-dev » Wed Apr 24, 2019 1:33 pm

Hi,

In keep alive frames, the byte 4 indicates the temperature. It is a signed integer
01 03 0e 32 22 f8 40 f8 71 05 4e

You can check the frame structure in the technical guide
http://www.libelium.com/downloads/docum ... df#page=15

Regards

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest