Dumping the database using the ISY994, it does it one record at a time. #233
Comments
|
Here's a log of the ISY994 restoring the same device. I am unable to pair this device using insteon-mqtt. Thu 11/26/2020 04:01:00 PM : [ 29 53 46 1] Preparing Device 'MB Chandelier KP.1' for Restore |
|
I am not sure all that logging text is necessary. My preference would be to continue using the single command for these reasons:
That said, I see that jon is having issues. At the end of this comment is a relevant excerpt from an attempt by him to refresh a device. In short it has a lot of craziness. The process goes well for about 6 entries. Then it looks like messages are being dropped on his network. A number of entries never make it through but then a number of entries show up multiple times likely because the device is resending messages. I also note that a number of times the message handler times out. This means that a full 5 seconds elapsed without a message coming in from the device. In a patch I provided to him, the handler re-sends the initial request. But I see now that is not a good idea nor the correct want to handle this, as this is only adding unnecessary traffic to the network. Quite possibly the only way to fix jon's problem is to query each address one by one. My concern is that this may cause issues for other users as the increased messaging traffic may result in more failures. |
|
One possible interesting idea would be to increase the message timeout on the devicerefresh handler from 5 to say 10 seconds. Since the retry number should be 0 for this routine, that may at least help in some cases. |
|
OK #237 may provide some mild improvement, but I doubt it will solve all of your issues. Also it is probably best to keep all of the issues here in one repo. I thought about this a bit more. I am still of the mindset that the current system using the single request is preferable. However, I thought of a way to add in support for individual requests as a fallback. The process would look like:
Basically, the separate handler is patching up the holes of what was missed. The two downsides to this are:
|
|
I can get further... (venv) jonsmirl@ares:~/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 Device 29.53.46 received model information: DIMMABLE_LIGHTING (0x01): '2334-232' (0x42) 'Keypad Dimmer Dual-Band, 6 Button' firmware: 0x43 ------------- tail of debug ------------------ 2020-12-10 15:38:38 DEBUG Protocol: Passing msg to write handler: ExtendedCmdResponse handler |
|
Ok, so this line:
Is unrecoverable for us. That is a message from your device basically saying "No, I won't add that entry to my database." It shouldn't respond like that. I can only assume this is a quirk where it is "busy" but isn't saying it is. Eitherway, it is a valid response and our only course of action is to stop. That said, it looks like you got through the refresh this time. I would hope that running pair again would not require getting the entire database again, and that adding the new entry would work since the device would be a bit "calmer" now. |
|
it's been sitting there a couple of hours and I just reran the command.... (venv) jonsmirl@ares:/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 ---- debug ----- 020-12-10 21:28:58 DEBUG KeypadLinc: Btn 7 old: 1 new 1 |
|
Above I attached the ISY99 log of it updating this device. The ISY developer has insider connections with the Insteon devs so he knows how to deal with all of the bugs. Does the ISY log show anything interesting? |
|
So something is getting written if the database delta is changing. So
there is that.
Fixing the bug with the database delta may help you.
No the isy isn't doing anything special. Just hammering away at it. I
have been doing this for 8+ years now and have collected all the insteon
documentation that exists. It isn't a failure of documentation but a
failure of design.
…On Thu, Dec 10, 2020, 6:38 PM Jon Smirl ***@***.***> wrote:
Above I attached the ISY99 log of it updating this device. The ISY
developer has insider connections with the Insteon devs so he knows how to
deal with all of the bugs. Does the ISY log show anything interesting?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#233 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXHXK4IIDUMXQXBAT2YMMDSUGAZJANCNFSM4UEE3ZQQ>
.
|
|
Do you know what the ISY is doing with those PEEK/POKES to alter bytes in memory? |
|
Note that after it fails, I have to PAIR the device again. The fail during JOIN seems to cause it to forget that it was PAIRed. Does the PAIR write something? |
|
As to the peeks pokes, I would have to check but it is likely setting some of the flags on the keypadlinc. Could be the button light level, radio button style, detached load. With older KPLs you can only change these values with the old peek/poke. Newer models work with the get_extended_flags feature. Sorry, your last comment isn't clear to me. Are you saying after the Pair command fails, you have to run Join again? The pair command does try to write new database entries, that seems to be where things are failing at the moment for you. But it shouldn't delete the Join entry. |
|
Yes, when the PAIR fails with this message... Pairing may fail if the modem db is out of date. Try running It forgets the JOIN |
|
That language by itself doesn't mean if forgot the Join. Join - Adds a link from the modem on the device. Without this link the device won't respond to the modem. So if the device is responding at all, then the join is still fine. Pair - Adds links from the device to the modem for each button on the device. This is complicated in your case because we can't add these links without knowing the contents of the database on the device. The warning you posted, just says the pairing failed (in your case because it isn't adding all of the 8 required links). |
|
I just tried it again. What does this mean? (venv) jonsmirl@ares:/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 |
|
That is the modem refusing to add an entry. Let's try refreshing the modem, I suspect this is because this link is already on the device. That is a nice typo we seem to have in the command line. Anyways, try running
Then you can try pairing that device again. |
|
(venv) jonsmirl@ares:/aosp/insteon-mqtt$ insteon-mqtt config.yaml refresh modem --- debug ---- |
|
Well now you get the error from the device. In this case, the device is rejecting adding the entry. |
|
I can't say why you have so many issues Jon. |
|
It is a 9,000sf house over four floors, three electrical boxes and 200 Insteon devices. Plus I have a mix of dual band and old power line. I am slowly working my way though replacing the oldest devices. I think I have about five I1 devices left. Then I will start replacing the power-line devices. I would really love to convert to a wifi based system, but nothing exists that can replace my system. The central problem is getting replacements for keypads. I have about ten keypads and they are essential to running the system. |
Many messages still come from the device after the command as errored out. here is a full debug capture.... (venv) jonsmirl@ares:~/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 ------------- debug -------- 2020-12-11 21:25:46 INFO Mqtt: MQTT message insteon/command/29.53.46 b'{"cmd": "pair", "session": "4067905342"}' |
|
BTW, I am also software developer. When I get some free time I can try to debug what is going on, but right now I am way overloaded with work. I was hoping for a quick and painless source of real-world MQTT sample data for a demo system I am building. BTW, the free levels on an AWS account are enough to run IOT, database and front end system. So if I can sort this stuff out it is possible to make a project that each person can clone into their free AWS quota and have a web/ios/android front-end for their system. |
|
As I have said, the Insteon protocol isn't very robust. Your devices are sending NAKs for no reason randomly. This isn't all that uncommon, but with the size of your network and the number of links, it becomes a lot for you. In this most recent case, this NAK Was in response to the dump the database request. They device said, no I don't want to do that. But then proceeded to do it. Which is why you see so many messages coming in after it. I will continue to patch bugs as as I see them and make fixes where I can. Perhaps this error would have been saved from the more elaborate refresh command I proposed on one of your other issues. But at some point, the only thing that can be done about these errors is just to repeat the process again. |
|
A couple other ideas... Maybe there is a retransmission issue happening. Because of the delays, the two nodes are out of sync in where they thing the protocol state machine it. Fall back to an item by items dump request loop if the dump_all consistently fails. |
|
I am using branch, keegan/DB_Retry_Timeout Isn't this NAK a pre-NAK? |
|
Let's have you stay on the krkeegan/Pre_NAK branch. There a number of changes that might help you. This is how things should work I am interested to see how that goes. In addition, the database delta value is being incremented in our cache now, so some of your failed pair commands may not require a full refresh anymore which should make things more tolerable. |
|
git checkout keegan/Pre_NAK scratch that, I forgot to copy into the venv pip install . same result... (venv) jonsmirl@ares:/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 --- debug ---- 2020-12-12 18:49:09 INFO Mqtt: MQTT message insteon/command/29.53.46 b'{"cmd": "pair", "session": "2101796308"}' |
|
Sometimes it gets further.... (venv) jonsmirl@ares:~/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 ERROR: 29.53.46 device NAK error: , Message: Std: 29.53.46->53.bf.6b Type.DIRECT_NAK cmd: 2e 00 ----- debug ------ ta: 0xff 0x1f 0x01\n 0fc7: 3c.48.88 grp: 72 type: RESP data: 0xd8 0x1c 0x01\n 0fcf: 3c.48.88 grp: 61 type: RESP data: 0xff 0x1f 0x04\n 0fd7: 3c.48.88 grp: 62 type: RESP data: 0xff 0x1f 0x03\n 0fdf: 3c.48.88 grp: 63 type: RESP data: 0xff 0x1f 0x06\n 0fe7: 3c.48.88 grp: 72 type: RESP data: 0xff 0x1f 0x03\n 0fef: 3c.48.88 grp: 72 type: RESP data: 0xff 0x1f 0x04\n 0ff7: 3c.48.88 grp: 72 type: RESP data: 0xff 0x1f 0x05\n 0fff: 3c.48.88 grp: 72 type: RESP data: 0xff 0x1f 0x06\nUnused:\nLast:\n 0eff: 53.bf.6b grp: 1 type: RESP data: 0x00 0x1c 0x01 (UNUSED) (LAST)\nGroupMap\n 1 -> ['3c.48.88', '44.85.11']\n 3 -> ['12.de.b9', '3c.48.88', '50.d0.2c', '50.d0.7e', '52.76.08', '52.d6.cc']\n 4 -> ['13.3a.7a', '3c.48.88', '52.7b.53']\n 5 -> ['3c.48.88']\n 6 -> ['12.de.b9', '13.3a.7a', '13.3e.10', '3c.48.88', '50.d0.7e', '52.d6.cc']\n"} qos=0 ret=False |
|
What is going on in this failure? Isn't 0EF7 past the end of the database? Modem add db already exists for 29.53.46 grp 1 CTRL --- Debug ----- 2020-12-12 19:11:02 DEBUG Protocol: Write handler finished |
|
Does it show the entry twice? |
|
(venv) jonsmirl@ares:~/aosp/insteon-mqtt$ insteon-mqtt config.yaml refresh 29.53.46 --force Device 29.53.46 received model information: DIMMABLE_LIGHTING (0x01): '2334-232' (0x42) 'Keypad Dimmer Dual-Band, 6 Button' firmware: 0x43 |
|
strange, now nothing matches. For some reason ISY and we are reading that last entry different. |
|
Nothing matches because I did that test where I removed the self-referencing links and then readded them. That caused the ISY to reorder the database. |
|
ok well run pair on that device again now and let's see what entry it fails on. |
|
The failing one is a 5-button keypad, the other ones are 8-button. |
|
That's fine. I might have a guess at a solution, but it would be nice to confirm the error. |
|
(venv) jonsmirl@ares:~/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 ERROR: 29.53.46 db mod NAK: , Message: Std: 29.53.46->53.bf.6b Type.DIRECT_NAK cmd: 2f 00 --- debug ---- |
|
ok, do one more thing for me. Try and run pair again. It may cause the full refresh to happen in the process. I wonder if we get one step farther each time. |
|
It goes back into the quick fail mode... now I refreshed the modem... (venv) jonsmirl@ares:~/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 Handler timed out 1 of 3 sent: Ext: 29.53.46, Type.DIRECT ext, 2e 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 --- debug ---- 2020-12-13 15:46:26 DEBUG Mqtt: MQTT writing |
|
OK, I have a guess that this could be related to #250. I am grabbing some food. But I should have a branch for you to try in an hour or so? |
|
Sure. I have to run out to Home Depot probably be back about same time. |
|
Alright, checkout this branch krkeegan/Jon_Branch It has a minor change wherein we are writing the new last entry in the database as all 0s rather than copying the existing last entry. There could be a few things at play here:
|
|
Hold off for a minute, I just realized one more thing. |
|
OK, now that is better. I hope I solved your issue. I think it has to do with how the ISY uses the database. |
|
If I am right, the ISY uses the last mem_loc in the database. This is different from how we do it and how insteon devices seem to do it. The code in this branch should now deal with this. I 'think' it is possible that the device as sending a NAK because we were writing a used entry below the last entry. Although it isn't clear why this worked sometimes for you. Perhaps the firmware on this device is just new enough to cause the issue. |
|
No change.... ERROR: 29.53.46 db mod NAK: , Message: Std: 29.53.46->53.bf.6b Type.DIRECT_NAK cmd: 2f 00 0-12-13 19:56:35 DEBUG Protocol: Passing msg to write handler: ExtendedCmdResponse handler |
|
(venv) jonsmirl@ares:~/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 29.53.46 ERROR: 29.53.46 db mod NAK: , Message: Std: 29.53.46->53.bf.6b Type.DIRECT_NAK cmd: 2f 00 |
|
Here are my keypads.... 9 -> ['53.bf.6b'] pairs 9 -> ['53.bf.6b'] Device 25.0e.3c add db already exists for 44.85.11 grp 1 RESP 25.0e.48 Pre-NAK: Pre NAK in case database search takes too long, Message: Std: 25.0e.48->53.bf.6b Type.DIRECT_NAK cmd: 2e fc ERROR: 29.53.46 device NAK error: , Message: Std: 29.53.46->53.bf.6b Type.DIRECT_NAK cmd: 2e 00 pairs ERROR: 2a.17.1b device NAK error: , Message: Std: 2a.17.1b->53.bf.6b Type.DIRECT_NAK cmd: 2e 00 pairs ------ Now I unplugged ISY.... pairs now So I am finally able to pair all of the keypads.
or it is saying -- Wait for a while, updating the EEPROM is really slow? Device 2a.17.1b db out of date (got 4 vs 3), refreshing |
|
It doesn't look like you are running the branch that I asked you to. |
|
Please run branch krkeegan/Jon_Branch |
|
I am on it.... if I am not on it I can't pair at all. and I added a githook to run pip install . when I check out. (venv) jonsmirl@ares:~/aosp/insteon-mqtt$ git log --pretty=format:"%h%x09%an%x09%ad%x09%s" |
|
Check this out... this is all of my keypads running the PAIR command and none of them failed... (venv) jonsmirl@ares:/aosp/insteon-mqtt$ insteon-mqtt config.yaml pair 25.0b.1a |
|
Well that is a good sign. |
|
I have 55 on-switches added now without any abnormal errors. A few I had to try twice to pair, but they paired on the second try. I am starting the dimmers, 105 of them. What was going on before? Was the ISY994 fighting with insteon-mqtt? |
|
I think so. At least in what I could see from your logs, I don't have an ISY myself. I am making an assumption about how the ISYs work here, but it is possible that this all happened for other reasons caused by other errors. Insteon SpecEach link entry in a device database has two flags, USED and LAST. Any entry can have the USED flag set to 0 or 1. Imagine you remove a device in your house, rather than reorganize the database, that entry just gets marked as 0, or unused. However, there should only be one entry marked LAST. Or at least starting from the highest memory address working down, the first entry encountered that has the LAST flag set is where the device stops reading entries. Devices have tens or hundreds of memory locations for storing entries and reading a bunch of empty addresses would slow things down. How Insteon Writes LinksWhen you manually pair Insteon devices, use the Insteon Hub, or the old Houselinc software the entry marked LAST is also unUSED. So if you read the database you will see that the entry at the lowest memory location looks like 0x00 0x00 0x00 (Unused)(Last) In my opinion, this happens because Insteon never marks an entry as LAST. It relies on the fact that a factory reset device has all of its entries zeroed out and marked LAST. So when it writes a new entry at the top of the memory addresses it writes that entry as unUSED and notLAST. And it relies on the default state that the next memory location will be marked LAST. But this is not described as a guarantee in the spec, nothing says you can rely on unseen memory locations to be marked LAST or even UNUSED. Insteon-mqttWriting new entries in Insteon-mqtt works like this, in this order 1) Mark the memory location just below the current last_entry as LAST, 2) Write the new entry in the previous last_entry location marking this entry as USED and notLAST. It is making one more write to the database than is necessary to mimic how insteon did things, but it is a cautious approach because it doesn't rely on the unstated feature that unseen memory locations are empty and marked LAST. So, it is probably worth keeping. Where things got weirdIt appears to me that you can mark an entry as LAST and USED, which is what I think ISY is doing. So the last entry in a database had a valid USED entry for the link table. And obviously things work on that device. I don't see anything wrong with this per the spec. It should be allowed. But nothing does that, except ISY. This caused 2 issues for Insteon-mqtt. Issue 1) Insteon-mqtt previously did a silly thing where were when writing the new last entry it didn't write it as all 0x00s, instead it copied the previous last entry including the state of the USED flag. This is where I think your generic NAK was happening. If the existing last_entry was marked as USED, then when we copied it and tried to write it back at a lower address, we were writing a USED entry below an entry marked LAST. Remember we write the new last entry first before altering the original last entry. It isn't clear why we were copying the prior last_entry. It may have been a conservative approach since we don't always understand what Insteon is doing. This works fine, in most environments, because the entry marked LAST on a device is also unUSED. So when copying the entry, we were generally writing an unUSED entry below the LAST entry, the devices didn't care about this. Issue 2) There was also a subtle error in that we were always assuming a LAST entry to be UNUSED in part of the code. I wasn't able to figure out what exact error this caused, but it could have also created an issue. The SolutionThe easy part, is properly treat an entry as USED if it is marked used. The more fundamental problem was how to write entries to the database when it is full. I think ISY's approach is wrong. When adding a new entry, they need to re-write the existing last_entry first and mark it not LAST, before adding a new entry below it marked LAST. There is no way to only write the flags on i2 devices, so this requires writing the full entry again, which could result in an error. I think it is preferable not to touch existing links if it can be avoided, otherwise a user adds a new link and then discovers that some other link they believe to be unrelated is not working. The resulting error isn't very intuitive. So I stuck with our approach of the LAST entry also being unUSED. This means that if we encounter a USED LAST entry we first have to mark it last. Then add 2 more entries (a new entry and a new last entry). So we have to make 3 writes the first time we encounter this. But after that, everything is how we expect it and future adds only require 2 writes. The write process is also reorganized now, we write to the current last_entry location and then write the new all 0x00 unUSED LAST entry to the new last entry location. The risk here, is if the process fails before we write that new last entry we may have inadvertently enabled a bunch of previously hidden entries. But I think this is extremely unlikely to occur. The resulting database is fully compatible with ISY. It won't care. Again, I only think this is how ISY is doing things, this could have been caused by some other error along the way. Anyways, that is more words than were necessary to fix the code, sorry for the long winded explanation. |
|
So far I am 0/4 on getting I1 protocol devices to work. I am just replacing them with new Dual Band devices when I encounter them. I need to go replace #4 now, I might have one or two more to replace. I1 support shouldn't be critical, how many people have Insteon devices over 10 years old that still function besides me? Other than no luck with I1 devices I am proceeding without significant issues. I do get the occasional retransmit failure, but it has always worked on the second try. 57 dimmers left to check. Thanks for the work, the Jon_Branch appears to be functioning pretty well --- way, way better than my initial problems. I'd say check it into the main app and get more people testing it. The only weird Insteon device I have is a leak sensor so I don't have any way to test the unusual devices. (venv) jonsmirl@ares:~/aosp/insteon-mqtt$ insteon-mqtt config.yaml join 08.09.e3 ERROR: Serial read error from /dev/insteon |
|
the And it did. I pushed a new commit to the branch that fixes it for you. |
Note that the ISY994 reads the database one record at a time and does not use the DUMP ALL option.
I am unable to pair this device using insteon-mqtt. It is a fairly recent 2334-2 KeypadLinc Dimmer 5 Buttons v.43
Thu 11/26/2020 03:52:27 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2
Thu 11/26/2020 03:52:27 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00)
Thu 11/26/2020 03:52:28 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:28 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:28 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:28 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:28 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F FF 20 A2 48 3C 48 88 FF 1F 06 88
Thu 11/26/2020 03:52:28 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:28 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA
Thu 11/26/2020 03:52:28 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06 (00)
Thu 11/26/2020 03:52:29 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:29 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:29 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:29 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:29 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 15 2F 00 00 01 0F F7 20 A2 48 3C 48 88 FF 1F 05 91
Thu 11/26/2020 03:52:29 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Thu 11/26/2020 03:52:29 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2
Thu 11/26/2020 03:52:29 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00)
Thu 11/26/2020 03:52:32 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:32 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:32 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:32 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:32 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F EF 20 A2 48 3C 48 88 FF 1F 04 9A
Thu 11/26/2020 03:52:32 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:32 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA
Thu 11/26/2020 03:52:32 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00)
Thu 11/26/2020 03:52:32 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 16 2F 00 00 01 0F EF 20 A2 48 3C 48 88 FF 1F 04 9A
Thu 11/26/2020 03:52:32 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=2, Hops Left=1
Thu 11/26/2020 03:52:32 PM : [Ext MH ] Unexpected Response (i.e. DB range): ignored
Thu 11/26/2020 03:52:33 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:33 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:34 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F E7 20 A2 48 3C 48 88 FF 1F 03 A3
Thu 11/26/2020 03:52:34 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:34 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2
Thu 11/26/2020 03:52:34 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00)
Thu 11/26/2020 03:52:34 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:34 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:35 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:35 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:35 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F DF 20 A2 3F 3C 48 88 FF 1F 06 B1
Thu 11/26/2020 03:52:35 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:35 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F D7 01 00 00 00 00 00 00 00 00 EA
Thu 11/26/2020 03:52:35 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F D7 01 00 00 00 00 00 00 00 00 EA 06 (00)
Thu 11/26/2020 03:52:35 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:35 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:36 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F D7 20 A2 3E 3C 48 88 FF 1F 03 BD
Thu 11/26/2020 03:52:36 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:36 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F CF 01 00 00 00 00 00 00 00 00 F2
Thu 11/26/2020 03:52:36 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F CF 01 00 00 00 00 00 00 00 00 F2 06 (00)
Thu 11/26/2020 03:52:36 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:36 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:37 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F CF 20 A2 3D 3C 48 88 FF 1F 04 C5
Thu 11/26/2020 03:52:37 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:37 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F C7 01 00 00 00 00 00 00 00 00 FA
Thu 11/26/2020 03:52:37 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F C7 01 00 00 00 00 00 00 00 00 FA 06 (00)
Thu 11/26/2020 03:52:37 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 16 2F 00 00 01 0F CF 20 A2 3D 3C 48 88 FF 1F 04 C5
Thu 11/26/2020 03:52:37 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=2, Hops Left=1
Thu 11/26/2020 03:52:37 PM : [Ext MH ] Unexpected Response (i.e. DB range): ignored
Thu 11/26/2020 03:52:38 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:38 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:38 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:38 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:38 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 15 2F 00 00 01 0F C7 20 A2 3F 3C 48 88 FF 1F 01 CE
Thu 11/26/2020 03:52:38 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Thu 11/26/2020 03:52:38 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F BF 01 00 00 00 00 00 00 00 00 02
Thu 11/26/2020 03:52:38 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F BF 01 00 00 00 00 00 00 00 00 02 06 (00)
Thu 11/26/2020 03:52:39 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:39 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:39 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F BF 20 A2 48 3C 48 88 D8 1C 01 F7
Thu 11/26/2020 03:52:39 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:39 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F B7 01 00 00 00 00 00 00 00 00 0A
Thu 11/26/2020 03:52:40 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F B7 01 00 00 00 00 00 00 00 00 0A 06 (00)
Thu 11/26/2020 03:52:40 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:40 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:41 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F B7 20 A2 3E 3C 48 88 FF 1F 01 DF
Thu 11/26/2020 03:52:41 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:41 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F AF 01 00 00 00 00 00 00 00 00 12
Thu 11/26/2020 03:52:41 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F AF 01 00 00 00 00 00 00 00 00 12 06 (00)
Thu 11/26/2020 03:52:41 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:41 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:42 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F AF 20 A2 3D 3C 48 88 FF 1F 01 E8
Thu 11/26/2020 03:52:42 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:42 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F A7 01 00 00 00 00 00 00 00 00 1A
Thu 11/26/2020 03:52:42 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F A7 01 00 00 00 00 00 00 00 00 1A 06 (00)
Thu 11/26/2020 03:52:42 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:42 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:43 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F A7 20 A2 00 3C 48 88 FF 1F 01 2D
Thu 11/26/2020 03:52:43 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:43 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 9F 01 00 00 00 00 00 00 00 00 22
Thu 11/26/2020 03:52:43 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 9F 01 00 00 00 00 00 00 00 00 22 06 (00)
Thu 11/26/2020 03:52:43 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:43 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:44 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:44 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:44 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 9F 20 E2 01 3C 48 88 FF 1F 01 F4
Thu 11/26/2020 03:52:44 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:44 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 97 01 00 00 00 00 00 00 00 00 2A
Thu 11/26/2020 03:52:44 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 97 01 00 00 00 00 00 00 00 00 2A 06 (00)
Thu 11/26/2020 03:52:46 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:46 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:46 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:46 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:47 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 15 2F 00 00 01 0F 97 20 E2 03 12 DE B9 01 00 03 78
Thu 11/26/2020 03:52:47 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Thu 11/26/2020 03:52:47 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 8F 01 00 00 00 00 00 00 00 00 32
Thu 11/26/2020 03:52:47 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 8F 01 00 00 00 00 00 00 00 00 32 06 (00)
Thu 11/26/2020 03:52:47 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:47 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:47 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:47 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:48 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 16 2F 00 00 01 0F 8F 20 E2 03 3C 48 88 FF 1F 03 00
Thu 11/26/2020 03:52:48 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=2, Hops Left=1
Thu 11/26/2020 03:52:48 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 87 01 00 00 00 00 00 00 00 00 3A
Thu 11/26/2020 03:52:48 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 87 01 00 00 00 00 00 00 00 00 3A 06 (00)
Thu 11/26/2020 03:52:49 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:49 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:49 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:49 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:49 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 1A 2F 00 00 01 0F 87 20 E2 03 50 D0 2C 01 00 03 E5
Thu 11/26/2020 03:52:49 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=2, Hops Left=2
Thu 11/26/2020 03:52:49 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 7F 01 00 00 00 00 00 00 00 00 42
Thu 11/26/2020 03:52:50 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 7F 01 00 00 00 00 00 00 00 00 42 06 (00)
Thu 11/26/2020 03:52:50 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:50 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:51 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 7F 20 E2 03 50 D0 7E 01 00 03 9B
Thu 11/26/2020 03:52:51 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:51 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 77 01 00 00 00 00 00 00 00 00 4A
Thu 11/26/2020 03:52:51 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 77 01 00 00 00 00 00 00 00 00 4A 06 (00)
Thu 11/26/2020 03:52:51 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:51 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:52 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 77 20 E2 03 52 76 08 01 00 03 71
Thu 11/26/2020 03:52:52 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:52 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 6F 01 00 00 00 00 00 00 00 00 52
Thu 11/26/2020 03:52:52 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 6F 01 00 00 00 00 00 00 00 00 52 06 (00)
Thu 11/26/2020 03:52:52 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:52:52 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:52:53 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:52:53 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:52:53 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 6F 20 E2 03 52 D6 CC 01 00 03 55
Thu 11/26/2020 03:52:53 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:53 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 67 01 00 00 00 00 00 00 00 00 5A
Thu 11/26/2020 03:52:53 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 67 01 00 00 00 00 00 00 00 00 5A 06 (00)
Thu 11/26/2020 03:52:54 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:54 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:54 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 16 2F 00 00 01 0F 67 20 E2 04 13 3A 7A 01 00 04 88
Thu 11/26/2020 03:52:54 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=2, Hops Left=1
Thu 11/26/2020 03:52:54 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 5F 01 00 00 00 00 00 00 00 00 62
Thu 11/26/2020 03:52:54 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 5F 01 00 00 00 00 00 00 00 00 62 06 (00)
Thu 11/26/2020 03:52:55 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:52:55 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:52:56 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 5F 20 E2 04 3C 48 88 FF 1F 04 2E
Thu 11/26/2020 03:52:56 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:52:56 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 57 01 00 00 00 00 00 00 00 00 6A
Thu 11/26/2020 03:52:56 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 57 01 00 00 00 00 00 00 00 00 6A 06 (00)
Thu 11/26/2020 03:52:57 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 17 2F 00 00 01 0F 5F 20 E2 04 3C 48 88 FF 1F 04 2E
Thu 11/26/2020 03:52:57 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Thu 11/26/2020 03:52:57 PM : [Ext MH ] Unexpected Response (i.e. DB range): ignored
Thu 11/26/2020 03:53:06 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 57 01 00 00 00 00 00 00 00 00 6A
Thu 11/26/2020 03:53:06 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 57 01 00 00 00 00 00 00 00 00 6A 06 (00)
Thu 11/26/2020 03:53:06 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:53:06 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:53:07 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 57 20 E2 04 52 7B 53 01 00 04 3F
Thu 11/26/2020 03:53:07 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:53:07 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 4F 01 00 00 00 00 00 00 00 00 72
Thu 11/26/2020 03:53:07 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 4F 01 00 00 00 00 00 00 00 00 72 06 (00)
Thu 11/26/2020 03:53:08 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:53:08 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:53:08 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 4F 20 E2 05 3C 48 88 FF 1F 05 3C
Thu 11/26/2020 03:53:08 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:53:08 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 47 01 00 00 00 00 00 00 00 00 7A
Thu 11/26/2020 03:53:08 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 47 01 00 00 00 00 00 00 00 00 7A 06 (00)
Thu 11/26/2020 03:53:08 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:53:08 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:53:09 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:53:09 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:53:09 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 47 20 E2 06 12 DE B9 01 00 06 C2
Thu 11/26/2020 03:53:09 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:53:09 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 3F 01 00 00 00 00 00 00 00 00 82
Thu 11/26/2020 03:53:09 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 3F 01 00 00 00 00 00 00 00 00 82 06 (00)
Thu 11/26/2020 03:53:10 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:53:10 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:53:10 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 3F 20 E2 06 13 3A 7A 01 00 06 AC
Thu 11/26/2020 03:53:10 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:53:10 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 37 01 00 00 00 00 00 00 00 00 8A
Thu 11/26/2020 03:53:10 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 37 01 00 00 00 00 00 00 00 00 8A 06 (00)
Thu 11/26/2020 03:53:11 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:53:11 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:53:11 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:53:11 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:53:11 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 37 20 E2 06 13 3E 10 01 00 06 1A
Thu 11/26/2020 03:53:11 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:53:11 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 2F 01 00 00 00 00 00 00 00 00 92
Thu 11/26/2020 03:53:11 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 2F 01 00 00 00 00 00 00 00 00 92 06 (00)
Thu 11/26/2020 03:53:12 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:53:12 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:53:12 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:53:12 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:53:12 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 2F 20 E2 06 3C 48 88 FF 1F 06 5A
Thu 11/26/2020 03:53:12 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:53:12 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 27 01 00 00 00 00 00 00 00 00 9A
Thu 11/26/2020 03:53:12 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 27 01 00 00 00 00 00 00 00 00 9A 06 (00)
Thu 11/26/2020 03:53:13 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:53:13 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:53:13 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 27 20 E2 06 50 D0 7E 01 00 06 ED
Thu 11/26/2020 03:53:13 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:53:13 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 1F 01 00 00 00 00 00 00 00 00 A2
Thu 11/26/2020 03:53:13 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 1F 01 00 00 00 00 00 00 00 00 A2 06 (00)
Thu 11/26/2020 03:53:14 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:53:14 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:53:14 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 15 2F 00 00 01 0F 1F 20 E2 06 52 D6 CC 01 00 06 9F
Thu 11/26/2020 03:53:14 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Thu 11/26/2020 03:53:14 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 17 01 00 00 00 00 00 00 00 00 AA
Thu 11/26/2020 03:53:14 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 17 01 00 00 00 00 00 00 00 00 AA 06 (00)
Thu 11/26/2020 03:53:15 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:53:15 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:53:15 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 1A D0 C0 00 01 0F 17 20 AA 01 53 BF 6B 00 1C 01 45
Thu 11/26/2020 03:53:15 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=2, Hops Left=2
Thu 11/26/2020 03:53:24 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 17 01 00 00 00 00 00 00 00 00 AA
Thu 11/26/2020 03:53:24 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 17 01 00 00 00 00 00 00 00 00 AA 06 (00)
Thu 11/26/2020 03:53:25 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2B 2F 00 (00)
Thu 11/26/2020 03:53:25 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Thu 11/26/2020 03:53:25 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 11 2F 00 00 01 0F 17 20 AA 01 53 BF 6B 00 1C 01 45
Thu 11/26/2020 03:53:25 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Thu 11/26/2020 03:53:25 PM : [INST-TX-I2CS] 02 62 29 53 46 1F 2F 00 00 00 0F 0F 01 00 00 00 00 00 00 00 00 B2
Thu 11/26/2020 03:53:25 PM : [INST-ACK ] 02 62 29.53.46 1F 2F 00 00 00 0F 0F 01 00 00 00 00 00 00 00 00 B2 06 (00)
Thu 11/26/2020 03:53:26 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 2F 2F 00 (00)
Thu 11/26/2020 03:53:26 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Thu 11/26/2020 03:53:26 PM : [INST-SRX ] 02 50 29.53.46 3C.48.88 23 2F 00 (00)
Thu 11/26/2020 03:53:26 PM : [Std-Direct Ack] 29.53.46-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Thu 11/26/2020 03:53:27 PM : [INST-ERX ] 02 51 29 53 46 3C 48 88 16 2F 00 00 01 0F 0F 20 00 01 53 BF 6B 00 1C 01 F7
Thu 11/26/2020 03:53:27 PM : [Ext-Direct ] 29.53.46-->ISY/PLM Group=0, Max Hops=2, Hops Left=1
Thu 11/26/2020 03:53:27 PM : [All ] Writing 0 bytes to devices
Thu 11/26/2020 03:53:27 PM : [All ] Writing 0 bytes to devices
Thu 11/26/2020 03:55:31 PM : [ Time] 15:55:32 11(0)
The text was updated successfully, but these errors were encountered: