PR55-34 Basic Configuration Via PR55-17A

Hardware
21

@Bhaskar just wanted to check that ALL sensors on this mesh network would use the same COM channel - including a RS485 wireless converter?

22

yes that is correct.

1 Like
23

I see there is a potential to update the firmware. What do you recommend?

firmware
firmware2572×1946 414 KB

24

@Bhaskar we were able to configure both wireless-to-ethernet modems via XCTU last night.

  1. SM Sleep Mode settings were confirmed to be “No Sleep [0]”
  2. ID Network PAN ID was confirmed to be same on all devices: “7FFF”
  3. EE AES Encryption Enable was confirmed to be “Enabled”
  4. KY Encryption Key was blank. It is now set to 55AA55AA55AA55AA55AA55AA55AA55AA

However the situation has not improved.

Questions:

  1. How do we confirm the Gateway settings as above? It has an outgoing USB-A port. Am I supposed to connect this with a special male-male cable to connect to a PC?
  2. We observed that in msg.payload a “MAC_modem” MAC address. Is this the device that the wireless sensor is first connecting to?
  3. Are we configuring these wireless-to-ethernet modems as simple mesh repeaters? If so, wouldn’t they ignore the ethernet connection?
  4. If they are using the ethernet connection, wouldn’t we configure each wireless-to-ethernet modem to listen on different ports than the COM1 port of the gateway?
25

Also can you confirm baud rate for the modems to talk to each other?

26

firmware update is no necessary.
if you are getting sensor data then gateway and sensor do have correct settings.

The Ethernet modem baudrate does not need to be changed.

can you share screenshots of all the settings ?

27

here ya go - these are from the two wireless-to-ethernet modems

3c_1
3c_11920×1404 142 KB

3c_5
3c_51920×1298 128 KB

3c_4
3c_41920×1026 95.5 KB

3c_3
3c_31920×619 67.5 KB

3c_2
3c_21920×1433 135 KB

3c_6
3c_61920×1656 125 KB

d8_3
d8_31920×1139 113 KB

d8_2
d8_21920×1088 117 KB

d8_1
d8_11920×1093 116 KB

28

The ENY key should be 55AA55AA55AA55AA55AA55AA55AA55AA

Also go to serial terminal in xctu and open port.

image
image714×467 27.6 KB

do you see any packets in the frame log section ( data will only show up when sensor sends it so you might have to wait for a bit)

29

I can only do this at night as factory is on other side of the world. If there are a few steps to do at once, please let me know.

30

that should be it. if you are getting the data in serial terminal it means all the settings are good and this device is also repeating the data.

31

@Bhaskar
update from tonight’s session

  1. we loaded the modem back into USB mode only to find our encryption key was deleted.
  2. after adding it back, we do not see the frames log as you show.

1_8_240507_1
1_8_240507_11920×1350 131 KB

I have the software on and running remotely. can you join me on a zoom to help confirm these settings?

2
21920×1436 101 KB

32

did you open the port ? by looking at the picture looks like its not open.

image
image720×515 63.7 KB

33

oops I misunderstood the graphic and followed your screenshot

XCTU_240508
XCTU_2405083064×1996 303 KB

34

so now we can see that this device is getting data and radio is set a router. it should be repeating the data as well.

35

ok great. So now why do you think the KY AES Encryption Key was deleted when it was powered off?

36

power cycle wont delete the keys. You wont see the key when you power cycle because that will be security violation.

37

so after I power cycle and reload this into XCTU you would expect this field to be blank?

38

yes that is expected. this way nonone who has radio module can read eny key and hijack entire network.

39

ok that makes sense, but that means I am in a circular loop of debugging:

  1. I updated my encryption key and I got reporting through Ethernet
  2. I then had my modem and gateway switch physical places and then nothing worked.
  3. if my encryption key was correct, then there must be another issue?
40

Also would love your thoughts from questions above.