briankelly63
Active Member
The M1XRF2G or M1XRF1N Wireless receiver gives you full access to all the GE wireless transmitters including multi button keyfobs. You can write rules to do things with the received transmitter data or place the M1 in to special mode to send the transmitter data out the RS232 serial port.
The sky is the limit!!
Cocoontecher's little known feature in latest M1 software upgrade:
RF received data sent to RS-232 serial port 0 mode:
From the M1's keypad enter installer programming, go to Globals G44, right arrow, enter 55555 into the a: field, press ***.
Every transmitter transmission received will be sent out the RS-232 serial port in this form:
A2-Z21-A29B68-Lb0-B0-L11-L20-R0-Tp1-Tb0-M1-CrB0
A2 = address of receiver on the RS-485 keypad data bus
Z21 = zone number of transmitter enrolled in M1
A29B68 = Serial number of transmitter
LB0 = battery in transmitter is OK, LB1 = battery in transmitter is low
B0 = button data from transmitter, usage will vary according to type of transmitter
L11 = hardwire loop 1 is violated, L10 = OK, usage will vary according to type of transmitter
L20 = hardwire loop 2 is OK, usage will vary according to type of transmitter
R0 = Reed switch in tranmitter is closed, usage will vary according to type of transmitter
Tp1 = tamper switch is violated, usage will vary according to type of transmitter
Tb0 = test button is OK, usage will vary according to type of transmitter
M1 = Manufacturer of transmitter = GE, M2 = manufacturer of transmitter is Ness Security
CrB0 = CRC byte of data received at RF receiver. This is verified by the M1 when the RF data is received by it.
You can view the data with HyperTerminal or the M1SDK program connected to the RS-232 bus or the data coming out of the M1XEP Ethernet connection.
If the M1 is powered down or reset the RF data will stop until the procedure above is repeated.
Have fun!
Hello... Is there a Globals location that can be set to cause the status messages that are put OUT by the M1 (like a single keypress) to be tested via Rules...? ie: route the M1's ascii output through the same buffer that allows one to test and act on general serial traffic... Although this info goes out the serial or ethernet ports it doesn't seem to be testable via Rules as it is going "out" vs. coming "in"..
