ELK OUtput naming 33-64

sandman

Member
Hi ALL

I'm kinda confused with the ELK documentation. If I set the name of output 33 in ELKRP, it shows up fine on KP1/KP2.

If I use the SDK to query the name of output 33, I get:

RECV 23:40:30 -- 1BSD04000 00A2
TR00 23:40:30 -- 09sd04033C6

so there is no name.

ELKRP says before firmware version 4.4.0 you couldnt name the zone. Does this mean you couldn't name it for the keypad or just ELKRP?
The serial doco says no names for 33-208....does this mean no matter what firmware, you wont get the name ? Only reason I ask, some guys in the HS forum tell me they got the name...I cant see it happening here :-)

Using 4.4.10 firmware....

Any advice would be appreciated...
 
Yup, I did see that also...the only reason I ask is that the ELK RP software states you weren't able to name those outputs before version 4.4.0 ?
 
IIRC, the names above 32 were for reference purposes only in RP and they are only stored in the RP database, not the controller.
 
I just tried Output 64 name and it is definately in the M1. Outputs 33 to 64 names are stored in the M1 the same as output names 1 to 32.

RECV 16:52:15 -- 1BSD04064MyOutput 64 0017
TR00 16:52:15 -- 0Bsd040640059

The M1_SDK might not have been updated to pass output names 33 to 64. It also sounds like a documentation error in the manual.

I will have them fixed.

Thanks.
 
I just tried Output 64 name and it is definately in the M1. Outputs 33 to 64 names are stored in the M1 the same as output names 1 to 32.

RECV 16:52:15 -- 1BSD04064MyOutput 64 0017
TR00 16:52:15 -- 0Bsd040640059

The M1_SDK might not have been updated to pass output names 33 to 64. It also sounds like a documentation error in the manual.

I will have them fixed.

Thanks.

Spanky

OK, so it is supposed to send out the name. What I've noticed so far with my SDK for output 64

RECV 16:15:03 -- 1BSD04000 00A2
TR00 16:15:03 -- 09sd04064C2

Note the calculation is not the same as yours ie: 0B v's 09 as start bits.

I send your string to my ELK:

RECV 16:19:24 -- 1BSD04000 00A2
TR00 16:19:24 -- 0Bsd040640059

Is it my SDK thats old ?????? I got it around 4 months ago from Ness Security in Australia. Is there a newer one ? Mine is 1.0.3

This is kinda weird :-(

Pete
 
Back
Top