Home › Forums › The libraries hosted on the site › EByte LoRa e220 UART devices LLCC68 › Encryption and EBYTE 220 library
- This topic has 5 replies, 3 voices, and was last updated 1 year, 4 months ago by
Renzo Mischianti.
-
AuthorPosts
-
-
14 April 2022 at 21:00 #20247
Hi
I was trying to understand how the library’s encryption system works.
In the topic, “Basic configuration option”, it says that it would be possible to configure encryption with “CRYPT Encryption to avoid interception 07H”. (link)In the E220 module, is there signal encryption (internal to the LLCC68 module) or just the message (Ebyte220 library)?
Do I need to configure any settings to enable message encryption?
Can I change library encryption keys? How? -
16 April 2022 at 19:08 #20248
Hi George,
Sorry for the late response; I’m not at home these days.E220 has internal encryption managed by two keys,
CRIPT_H
CRIPT_L
; these keys are used for the description. You can change them with configuration.configuration.ADDL = 0x03; // First part of address configuration.ADDH = 0x00; // Second part configuration.CHAN = 23; // Communication channel configuration.SPED.uartBaudRate = UART_BPS_9600; // Serial baud rate configuration.SPED.airDataRate = AIR_DATA_RATE_010_24; // Air baud rate configuration.SPED.uartParity = MODE_00_8N1; // Parity bit configuration.OPTION.subPacketSetting = SPS_200_00; // Packet size configuration.OPTION.RSSIAmbientNoise = RSSI_AMBIENT_NOISE_DISABLED; // Need to send special command configuration.OPTION.transmissionPower = POWER_22; // Device power configuration.TRANSMISSION_MODE.enableRSSI = RSSI_DISABLED; // Enable RSSI info configuration.TRANSMISSION_MODE.fixedTransmission = FT_TRANSPARENT_TRANSMISSION; // Enable repeater mode configuration.TRANSMISSION_MODE.enableLBT = LBT_DISABLED; // Check interference configuration.TRANSMISSION_MODE.WORPeriod = WOR_2000_011; // WOR timing configuration.CRYPT.CRYPT_H = 0x00; configuration.CRYPT.CRYPT_L = 0x01;
The default values are all 0.
I will try to publish the E220 configuration article next few days with some additional information.
Bye Renzo
-
19 December 2023 at 23:08 #28842
Hello
I am testing all the options and the encryption works correctly by configuring it with your library.
But then I try to check the configuration of a module with the Ebyte specific application (E220_V1.0) and it always shows “Key: 0”.
Could you confirm if your library’s encryption settings work better than the manufacturer’s application?
Regards
-
19 December 2023 at 23:23 #28843
update:
There is a more updated version of the application from the manufacturer E220_V1.1, but it is not well translated into English and does not show the encryption key either…
-
19 December 2023 at 23:43 #28844
Well, auto response after reading the manual again:
The encryption key is write-only. The manufacturer’s application cannot read this parameter.
I apologize for dirtying the forum. I hope it helps if anyone searches for this information.
-
21 December 2023 at 15:33 #28853
Thanks for your feedback, JaTo; I often find some bugs in EByte software, and I try to fix Them when I find them.
Bye Renzo
-
-
AuthorPosts
- You must be logged in to reply to this topic.