NIS-TR Temperature Sensor (RTD) - Revision history

Lcs: Abandon de l'extension Widgets : {{#widget:Iframe}} remplace par du HTML brut

2026-09-28T09:41:00Z

Abandon de l'extension Widgets : {{#widget:Iframe}} remplace par du HTML brut

← Older revision		Revision as of 09:41, 28 September 2026
Line 213:		Line 213:


	~~{{#widget:Iframe\|param~~=https://jscalc.io/calc/D3upefvYafJ0EQ7i\|width=100%\|height=800}}		<html><iframe src="https://jscalc.io/calc/D3upefvYafJ0EQ7i" width="100%" height="800" frameborder="0"></iframe></html>

Lcs: /* Uplink data Frame format */

2021-03-17T14:43:44Z

Uplink data Frame format

← Older revision		Revision as of 14:43, 17 March 2021
Line 77:		Line 77:
	bit 1 : indicates the presence of <rtd_temp> field.		bit 1 : indicates the presence of <rtd_temp> field.

	bit 2 : indicates the presence of <voltage> field.		bit 2 : indicates the presence of <voltage> field. <span style="color:red">Only available for versions before 19W03</span>

	bit 3 : indicates the presence of <internal_temp> field.		bit 3 : indicates the presence of <internal_temp> field. <span style="color:red">Only available for versions before 19W03</span>

	bit 4 : is reserved.		bit 4 : is reserved.

Lcs: /* Downlink Frame format */

2018-11-30T14:19:56Z

Downlink Frame format

← Older revision		Revision as of 14:19, 30 November 2018
Line 134:		Line 134:
	<sensor_type>: identifies the type of sensor (PT100/PT1000 and 2/3/4 wires)		<sensor_type>: identifies the type of sensor (PT100/PT1000 and 2/3/4 wires)

	It is possible to change the sensor configuration using the Nemeus downlink protocol. The downlink frame must be sent on the MS008 LoRaWAN port (10).		It is possible to change the sensor configuration using the Nemeus downlink protocol.<br>
			'''The downlink frame must be sent on the MS008 LoRaWAN port (10).'''

	The downlink frame has the following format:		The downlink frame has the following format:

Arl: /* Power consumption */

2017-11-28T11:17:44Z

Power consumption

← Older revision		Revision as of 11:17, 28 November 2017
Line 209:		Line 209:


	~~Please find below a tool to calculate power~~ consumption vs number of ~~measures~~ and transmissions.		Power consumption calculator based on the number of measurements and transmissions.


	{{#widget:Iframe\|param=https://jscalc.io/calc/D3upefvYafJ0EQ7i\|width=100%\|height=800}}		{{#widget:Iframe\|param=https://jscalc.io/calc/D3upefvYafJ0EQ7i\|width=100%\|height=800}}

Arl: /* RTD Temperature sensor properties */

2017-09-08T14:11:32Z

RTD Temperature sensor properties

← Older revision		Revision as of 14:11, 8 September 2017
Line 15:		Line 15:
	* Handles 100Ω to 1kΩ (at 0°C) Platinum RTDs (PT100 to PT1000)		* Handles 100Ω to 1kΩ (at 0°C) Platinum RTDs (PT100 to PT1000)

	* 2-wires, 3-~~wire~~ or 4-~~wire~~ connection		* 2-wires, 3-wires or 4-wires connection

	* 15-Bit ADC Resolution; Nominal Temperature Resolution 0.03125°C (Varies Due to RTD Nonlinearity)		* 15-Bit ADC Resolution; Nominal Temperature Resolution 0.03125°C (Varies Due to RTD Nonlinearity)

Lcs at 08:38, 8 September 2017

2017-09-08T08:38:20Z

← Older revision		Revision as of 08:38, 8 September 2017
Line 3:		Line 3:

	= General information =		= General information =
	{{:~~MSxxx~~ Overview}}		{{:NIS Overview}}

	= Mechanics =		= Mechanics =
Line 64:		Line 64:

	= Magnetic Switch Protocol description =		= Magnetic Switch Protocol description =
	{{:~~MSxxx~~ Generic Magnetic Switch Protocol}}		{{:NIS Generic Magnetic Switch Protocol}}

	= Radio frames description =		= Radio frames description =
	{{:~~MSxxx~~ Generic Application Protocol}}		{{:NIS Generic Application Protocol}}

	== Uplink data Frame format ==		== Uplink data Frame format ==

Lcs: Lcs moved page RTD Temperature Sensor to NIS-TR Temperature Sensor (RTD) without leaving a redirect

2017-09-05T14:54:27Z

Lcs moved page RTD Temperature Sensor to NIS-TR Temperature Sensor (RTD) without leaving a redirect

← Older revision		Revision as of 14:54, 5 September 2017
(No difference)

Arl: /* Power consumption */

2017-07-18T12:38:08Z

Power consumption

← Older revision		Revision as of 12:38, 18 July 2017
Line 210:		Line 210:

	Please find below a tool to calculate power consumption vs number of measures and transmissions.		Please find below a tool to calculate power consumption vs number of measures and transmissions.


			{{#widget:Iframe\|param=https://jscalc.io/calc/D3upefvYafJ0EQ7i\|width=100%\|height=800}}

Arl: /* Downlink Frame format */

2017-07-17T13:25:26Z

Downlink Frame format

← Older revision		Revision as of 13:25, 17 July 2017
Line 162:		Line 162:
	If (mask.bit1 == 1):		If (mask.bit1 == 1):

	<nb_meas_for_tx>: 1 byte containing the number of ~~measures~~ required to trigger a transmission		<nb_meas_for_tx>: 1 byte containing the number of measurements required to trigger a transmission

	If (mask.bit2 == 1):		If (mask.bit2 == 1):

	<meas_period>: 2 bytes in little endian (LSB first) containing the period of ~~measures~~ in <period_unit> seconds		<meas_period>: 2 bytes in little endian (LSB first) containing the period of measurements in <period_unit> seconds
	<period_unit>: 1 byte containing the unit of <meas_period> in seconds (default value is 1 second)		<period_unit>: 1 byte containing the unit of <meas_period> in seconds (default value is 1 second)

Line 204:		Line 204:

	“028182”: set the <up_frame_mask> to 0x82 => the next uplink frames will include the <rtd_temp> field only		“028182”: set the <up_frame_mask> to 0x82 => the next uplink frames will include the <rtd_temp> field only
	“028E04605401100100”: set <nb_meas_for_tx> to 4, <meas_period> to 21600*<period_unit> seconds, <period_unit> to 1 second and enable periodic ~~measures~~ only with subperiod to 1 => one ~~measure~~ every 6 hours and one transmission every 4 measures (every day). Each uplink frame will include 4 ~~measures~~		“028E04605401100100”: set <nb_meas_for_tx> to 4, <meas_period> to 21600*<period_unit> seconds, <period_unit> to 1 second and enable periodic measurements only with subperiod to 1 => one measurement every 6 hours and one transmission every 4 measures (every day). Each uplink frame will include 4 measurements

	== Power consumption ==		== Power consumption ==

Elc: /* Downlink Frame format */

2017-07-17T13:23:55Z

Downlink Frame format

← Older revision		Revision as of 13:23, 17 July 2017
Line 204:		Line 204:

	“028182”: set the <up_frame_mask> to 0x82 => the next uplink frames will include the <rtd_temp> field only		“028182”: set the <up_frame_mask> to 0x82 => the next uplink frames will include the <rtd_temp> field only
	~~“028E0460540110”~~: set <nb_meas_for_tx> to 4, <meas_period> to 21600*<period_unit> seconds, <period_unit> to 1 second and enable periodic measures only => one measure every 6 hours and one transmission every 4 measures (every day). Each uplink frame will include 4 measures		“028E04605401100100”: set <nb_meas_for_tx> to 4, <meas_period> to 21600*<period_unit> seconds, <period_unit> to 1 second and enable periodic measures only with subperiod to 1 => one measure every 6 hours and one transmission every 4 measures (every day). Each uplink frame will include 4 measures

	== Power consumption ==		== Power consumption ==