Page 1 of 2

Hit * for faults - multi-partition

PostPosted: Wed Aug 18, 2021 9:12 am
by miragejb
I am having problem expanding the faults when I get the "Hit * for faults" message (Honeywell 21ip). If I launch a telnet window and type in "K19*" and hit enter, it seems to have no effect. I am using the "K" command to associate the "*" with keypad 19 in hopes that it will expand the messages.

I have two partitions and need to direct the "*" command to that specific keypad.

I am running firmware version 2.2a.8.8. I have tried the Beta version 2.2a.8.9b-306 as well, but it doesn't seem to help. Has anyone got this to work? I've seen a couple of posts regarding it, but nothing seems to help.

Thanks-in-advance.

Re: Hit * for faults - multi-partition

PostPosted: Tue Sep 07, 2021 10:03 am
by mathewss
Sorry for the late reply. This should work something else must be happening. I am exclusively using the 'K' command on the new C++ IoT embedded API code and it has been working perfectly.

A few things is it possible you are hitting or sending a \r or \n after the K command? The K command persists until it receives a \r\n and then it reverts back to the default address.
https://github.com/nutechsoftware/AlarmDecoder-IoT/blob/zone-tracking/main/ad2_utils.cpp#L1003

Best
Sean M.

Re: Hit * for faults - multi-partition

PostPosted: Tue Sep 07, 2021 10:20 am
by miragejb
Thanks Sean. I am out of town at the moment but will give it a try as soon as I am able.

I'm pretty sure I tried it without the "\r\n". It wasn't working when I sent the command: K19* (K <command> + 19 <keypad address> + *) as follows:

Code: Select all
if(message.ToLower().Contains("hit * for faults"))
{
    Logger.LogDebug("Sending message to display detail fault information");
     var command = $"K{int.Parse(alarmDecoderMessage.Keypads[0]):00}*"; //HERE IS THE COMMAND
     await _socketTransceiver.SendAsync(command.ToAsciiBytes(), CancellationToken.None);
     Task.Delay(500, CancellationToken.None).Wait(CancellationToken.None);
}


I'll let you know how it goes.

Re: Hit * for faults - multi-partition

PostPosted: Tue Sep 07, 2021 11:04 am
by mathewss
Looks correct. Took me a minute to get my brain back into C# mode and interpolation :c)

Looks correct presuming that in the array[0] the int keypad value. It looks to send "K19*"

Stick with the latest firmware. It is possible some issues exist in 8.8

When you dig in again give me a ring or drop an email. One idea is to enable verbose logging on ser2sock. It is a bit noisy but you will see raw bytes received from the client and it may show something. As I recall ANY character not expected by my code on the AD2* will kick it out of the K mode but it would have no issues accepting the initial command "K19*".

Best
SM

Re: Hit * for faults - multi-partition

PostPosted: Wed Sep 08, 2021 9:26 am
by miragejb
What is the latest version of the AD2USB firmware?

Re: Hit * for faults - multi-partition

PostPosted: Wed Sep 08, 2021 1:27 pm
by mathewss
The latest is 2.2a.8.9 here is the link. It has a few small fixes to 8.8

http://www.alarmdecoder.com/downloads/firmware/2.2/ademcoemu_V2-2a-8-9b-306.zip

Best
SM

Re: Hit * for faults - multi-partition

PostPosted: Wed Sep 08, 2021 1:27 pm
by mathewss

Re: Hit * for faults - multi-partition

PostPosted: Thu Sep 09, 2021 4:21 am
by miragejb
Again, Thank you very much.

I'll give it try next week.

Re: Hit * for faults - multi-partition

PostPosted: Mon Sep 13, 2021 9:30 am
by miragejb
Well. I updated the AD2USB to the version you suggested. I still can't get the details of the "Hit * for faults".

The correct Keypad is 19 and I am sending "K19*". I have also tried "K19*\r", "K19*\n" and "K19*\r\n", but it's just not working. I've tried through code and manually using Telnet.

I also tried the AlarmDecoder Keypad App (V2.0.10), but hitting * on it doesn't work as well.

Can you think of anything else that might help?

Thanks-in-advance.

Re: Hit * for faults - multi-partition

PostPosted: Mon Sep 13, 2021 9:49 am
by mathewss
A few ideas yes.

If you can turn on debugging by sending @48 then type your K command and send me 30 or so lines of messages from the AD2* when this is done.

1) Another keypad is at 19
2) 19 is not enabled on the partition that has a fault.

A few lines of messages from the panel so I can see the keypads that are enabled would help and again above the debug dump while sending will show if another keypad is on that same address.

Best
SM

will look something like this. This was me sending K01 to my 50PUL panel.
Code: Select all
[01010001000100003A--],0fc,[f700000000fc804c0c020000202020],"SYSTEM LOBAT                    "
!DBG:<ff><ff><ff><ff><ff>
!DBG:*f7*[f7][07][00][16][00][fc][80][0c][0c][02][00][00][c1][52][4d][45][44][20][2a][2a]
!DBG:[2a][41][57][41][59][2a][2a][2a][2a][2a][20][41][4c][4c][20][53][45][43][55][52][45]
!DBG:[20][2a][2a][77]<ff>
[01010001000000003A--],0fc,[f707001600fc800c0c0200002a2a2a],"ARMED ***AWAY***** ALL SECURE **"
!DBG:<ff><ff><ff><ff><ff><ff><ff>
!DBG:*f7*[f7][00][00][00][00][fc][80][0c][0c][02][00][00][d3][59][53][54][45][4d][20][4c]
!DBG:[4f][42][41][54][20][20][20][20][20][20][20][20][20][20][20][20][20][20][20][20][20]
!DBG:[20][20][20][fc]<ff>
[01010001000000003A--],0fc,[f700000000fc800c0c020000202020],"SYSTEM LOBAT                    "
!DBG:<ff><ff><ff>
!Sending.!DBG:(fd)<ff>
!DBG:*f6*[f6][01](01)(02)(0a)(f3)[01]done
!DBG:<ff>
!DBG:*f7*[f7][07][00][16][00][fc][80][00][0c][02][00][00][c3][4f][4d][4d][2e][20][46][41]
!DBG:[49][4c][55][52][45][20][20][20][20][20][20][20][20][20][20][20][20][20][20][20][20]
!DBG:[20][20][20][00]