Sensor (temp) does not store encryption key

cesararaujo · February 17, 2025, 6:19pm

Hello i have bought 10 units of Industrial IoT Wireless RTD Temperature Sensor Brochure - NCD.io and using alpha station i can program the devices but the encryption key on the device is never used, it always keeps the default encryption key 55AA… and not my key that i use in other sensors.

What am i missing?

Eduardo_Mtz · February 17, 2025, 6:37pm

Hi @cesararaujo The sensor comes with the default encryption key 55AA....

You can set a new encryption key using Alpha Station or XCTU software. The encryption key change command can be found in the API Overview documentation under the “Set Wireless Sensor Encryption Key” section:

Remember: Only devices with the same key will be able to communicate with each other.

Take a look at this and feel free to let us know if you have any questions.
Thank you,
Eduardo M.

cesararaujo · February 18, 2025, 9:11am

Hello, thanks for the help, we already know that this is not our first order.

I have two receivers, one with default key that I use to program new devices and another one with my key so i can pick them up and confirm they are ready. On this new devices (board totaly different from the older ones) I program all that i need with alpha station and all stays ok except the encryption key, that is always reverted to the default one. What is wrong here? Does this hardware have different requirements?

Thanks in advance

cesararaujo · February 18, 2025, 3:27pm

I have used xctu to program the zigbee and set the encryption and other parameters as i always have done and always have worked but:
1 - If i place the zigbee card on the new sensor it reports with default key, don’t know why
2 - If i place the zigbee on older sensor it reports with my encryption key (used in xctu).

After placing the zigbee card on the new sensor it keeps the default key and if i want to use on old sensors have to reprogram the encryption key again.

I have reasons to believe that the board may be changing the zigbee card.

Bhaskar · February 18, 2025, 5:15pm

Hi Cesar,
Its good to hear from you.
if you change the key by plugin the radio in the xctu , the mcu will revert it. MCU is the master device.

The command to encryption key is slightly diff in the new devices.
new command – 7E 00 23 10 00 00 00 00 00 00 00 FF FF FF FE 00 00 F2 03 00 00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF FF FF 09
Command – F2 03 00 00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF FF FF
ENY key – 00 00 00 00 00 00 FF FF FF FF FF FF FF FF FF FF

You can configure using XCTU.
This is how you can do it

Add the command in XCTU frame list
press reset on sensor
sensor will send RUN packet, Data packet and then a FLY packet
as soon as you receive the 3rd packet send the ENY set command
reset again and it will store the key

We will make a chance in firmware and make is same old command. apologies for the delay.

cesararaujo · February 18, 2025, 5:34pm

Hi Bhaskar, thanks for the response.

I did not get it, I am not that expert yet :). What is the mcu? the motherboard?
Also when you change the firmware how do i flash that firmware in the mcu?

What more changes do i have to be aware?

I will try to use xctu but i would need the firmware and use the alpha station, again.

Thanks in advance

Eduardo_Mtz · February 18, 2025, 6:22pm

Hi @cesararaujo The MCU (Microcontroller) is the CPU of the sensor, and it uses the Radio Module to transmit sensor data.

No, you do not need to flash the firmware at this time.
No, the firmware is not required to configure the encryption key.

The command to set a new encryption key is slightly different in the newer sensors, like the one you have. You can use XCTU to configure your new encryption key, as Bhaskar mentioned.

You can download the XCTU tool here:

Then, you can follow Bhaskar’s instructions. I’m also sharing a manual, and we have a video tutorial available for additional support:

ncd-enck-key-config-xctu.pdf (145.6 KB)

Please take a look at this and feel free to let us know if you have any questions.
Thank you,
Eduardo M.

cesararaujo · February 19, 2025, 9:16am

Thanks for the time to help. From the Bhaskar I got the procedure instructions, the pdf fails in step 15 saying i will have a response, but i guess it would be in mode PGM (network id 7BCD).

I have tried the method that you both describe without success as you can see in video attached.

What am i doing wrong?

Regarding the firmware we really do need it, otherwise having in production sensors with different behaviors is not desired for us, otherwise we will have to keep track if this firmware is “new” version or “old version” to know how to program it (since the new ones wrongly report as firmware 3, the same as the “old” ones).

When is expected to have new firmware version?

Thanks in advance.

Eduardo_Mtz · February 19, 2025, 9:49pm

Hello @cesararaujo Apologies for the delay. We were testing this locally, and unfortunately, the encryption key cannot be configured using FLY mode. You will need to configure the encryption key using manual mode.

To perform this, I’m sharing a PDF with detailed instructions:

Connect the USB modem to your computer.
Open the XCTU Tool.
Identify the COM port assigned to the USB modem.
Click on “Add a radio module” in XCTU.
Click on the XBee PRO module to load and access its configurations.
Set the Modem’s Network ID to 7BCD (Config Mode).
Switch to Console Working Mode (Alt + C).
Open the serial connection with the radio module.
Put the sensor into config mode:

Every sensor has two buttons: Reset and Configuration.
Press and release the Reset button.
Immediately press and hold the Configuration button.
Hold the Configuration button for about 5–8 seconds.
Release the Configuration button.

Add a new frame with the Encryption Key command.
Send the command.
Switch to Configuration Working Mode.
Set the Modem’s Network ID to 7FFF (Run Mode).
Press the Reset button on the sensor.

ncd-sensor-config-xctu-manual.pdf (387.6 KB)

You can use this tutorial as reference as well.

Please try this and feel free to let us know if you have any questions.
Thank you,
Eduardo M.

cesararaujo · February 20, 2025, 12:47pm

Hello @Eduardo_Mtz and @Bhaskar
Thanks again for the pdf, that was something we had already tried, and also the frame you sent is for setting destination address and not the encryption key. Let’s from now on just focus on the frame.

I have tried the frame:

Bashkar sent,
The frame on the page Industrial IoT Wireless RTD Temperature Sensor API Overview - NCD.io or NCD Wireless Sensor Configuration Commands - NCD.io

Booth of them without luck, this is really frustrating (for booth of us :)).

I will post the frame sent and the response to help us debug the problem.

Bhaskar frame (yes i know it is missing a byte in the firmware, that is probably the error/bug/difference you made)

Sent: 7E 00 23 10 00 00 00 00 00 00 00 FF FF FF FE 00 00 F2 03 00 00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF FF FF 09
Response: 7E 00 13 90 00 13 A2 00 42 61 AC 73 FF FE C2 7C 00 EB 00 27 00 FF AC

If i set the modem to this encryption key or the default key it fails to receive anything.

2 . Documentation frame has a 00 byte extra and also the length changes to 24. I’m totally lost so I had to try it also (knowing that it will not work).

Sent 7E 00 24 10 00 00 00 00 00 00 00 FF FF FF FE 00 00 F2 03 00 00 00 00 55 AA 55 AA 55 AA 55 AA 55 AA 55 AA 55 AA 55 5B 56 ( I swapped the last byte to 5B so i can see any change).
Response 7E 00 13 90 00 13 A2 00 42 61 AC 73 FF FE C2 7C 00 EF 00 27 00 0F 98
If i set the modem to this encryption key or the default it fails to receive anything.

What is missing here, have you tried changing the key to something other than the original
Can i use the debug port to view anything relevant? If so, how?
I have experience in hardware mod, so i may have the right cable around here.

Please help us out since we cannot use this new sensors (and i have at least 10 units).

Eduardo_Mtz · February 20, 2025, 4:28pm

Hi @cesararaujo The PDF manual is for reference, and you only need to replace the command with the following:

Just to confirm, at the end of the procedure, did you set the modem network ID back to 7FFF (Run Mode)?

could you share screenshots of the procedure in order we can take a look?
Note: if you prefer we can schedule a zoom meeting.

Thank you,
Eduardo M.

cesararaujo · February 20, 2025, 4:35pm

We can schedule a zoom meting as i can also record a video showing the problem, and yes i was in run mode.

Eduardo_Mtz · February 20, 2025, 5:40pm

Hi @cesararaujo Thank you for the information, I just sent you an email.