Metreau MET-6N!
Spire_Jeff
Posts: 1,917
Wow, I got a VERY nice surprise (depending on how you look at it) when I (and by I, I mean one of the other guys here) connected the MET-6N keypads to a processor for an upcoming job. He was fairly confused because there were twice as many Axlink devices showing in the online tree as we have. I came over to the build area and I saw what he was talking about. It appeared that each keypad had two addresses, the second one was 1 higher than the set address. I automatically thought that there might be a second device built into the keypads that I had overlooked. I zipped over to amx.com and grabbed the Instruction Manual. Buried in the programming section I found this:
I also verified that the IR receiver does respond to the standard AMX IR codes.
Am I the only one that did not realize that the 6N included an IR receiver?
Jeff
MET-6N Instruction Manual wrote:The MET-6N will appear as two devices in the Devices frame, because it?s built-in IR Receiver, is
recognized as a separate online device.
The Device Address of the IR Receiver is always one number higher than the device number of the
keypad itself (to which the firmware is uploaded).
I also verified that the IR receiver does respond to the standard AMX IR codes.
Am I the only one that did not realize that the 6N included an IR receiver?
Jeff
0
Comments
But interesting it has an IR receiver built in. Though I thought on the manual it also said one of those connectors is reserved for future usage. I think we'll have to wait and see.
The IR receiver is documented, it's just not what I would call well documented. The really opens up some options for room based control. Also, be careful as the IR receivers seem to be very good at picking up signal, so be careful when putting two receivers in the same room for different areas... even if they are on different walls. (This great reception may also be because I only have the keypads setup in a test area and they are not mounted in a wall.)
Jeff
- It's buttons are Engraved, or Printed?
The buttons are silk screened or something. I did take my finger and try to scratch the label off and it did not show any signs of distress. I would guess that heavy use would eventually wear the buttons down, but, they seem to be easy enough to replace.
- Do these buttons has a backlight, like the Mio Elite series, so that buttons text is quite visible in the dark?
No, there is a blue LED on the top center of each button, but it does not seem to illuminate the text very well (Put my head under a blanket and looked
- Does these buttons can provide channel feedback.
The LEDs are set according to channel feedback.
- Anything else you can share?
The 6N keypads have a built in IR receiver that accepts standard AMX IR codes (such as from the R1). Be careful tho, the IR receiver has it's own AXLINK address and it can not be disabled.
Hope this helps,
Jeff
The MET-6N is my favorite keypad since the MSP8. I think it?s one of the biggest bangs for the buck as you get a 13 button keypad, an LED display for volume level, AND an IR receiver for less than the cost of an MVP kickstand.
If anyone has problems with the channel feedback not working correctly you may want to check out the following thread. AFAIK the firmware bug has not been fixed yet.
http://www.amxforums.com/showthread.php?t=3924
Sales rep is going to check again why you can order every button available cheaper individually then in the kit.
Kevin D.
I always laugh when people say "MVP Kickstand"
Funniest, Joke EVER.
how do I know what the level limits are? is it documented somewhere?
Can you send the keypad a send_level command to have it match a volume level for that zone?
Is this level #1 for the keypad device ID?
Frank Krauch
MIW Integration
Correct.
Thanks!
By the way the metreau keypads show up as an unknown device in the online tree and in a debug session, although I assume that does not matter.
Remember, the MET-6N uses two AxLink addresses. If the first one is 128, the second one is 129.
No problem. Did the same thing myself!
It's normal. Since the keypads are newer (by about a decade) than the Axcent3, the Axcent3 master does not recognize the Device IDs the keypads report. All it affects is the info shown in the terminal. And as stated before, make sure there is no overlap between any device numbers on Axlink. The Metreau keypads use the device number they are set to by the DIP switch for the buttons and wheel, AND the next sequential address for the IR receiver.
The pair of numbers used depends on the DIP SWITCHES of course. But whatever you set, that's the number for the BUTTONS... the IR pickup follows at the next higher number. Don't try to use that number for another unit, skip over it when addressing the next keypad.
Note also that the AMX DIPSWITCH application that shows you the number for each setting... is UPSIDE DOWN from the way the METREAU addresses. So always check in NetLinx Studio when the keypad is attached to see for SURE where you addressed it.