Axcent 2?
TurnipTruck
Posts: 1,485
in AMX Hardware
Greetings,
I am looking at upgrading a system that contains an Axcent 2. I have never worked with one of these before. Do they work like Axcent 3s where you can put them into a slave mode and give them a starting Axlink channel? I would like to leave the Axcent 2 in place and continue to use it for IR controls.
The website seems to have no operating manuals for the unit.
Thanks you.
I am looking at upgrading a system that contains an Axcent 2. I have never worked with one of these before. Do they work like Axcent 3s where you can put them into a slave mode and give them a starting Axlink channel? I would like to leave the Axcent 2 in place and continue to use it for IR controls.
The website seems to have no operating manuals for the unit.
Thanks you.
0
Comments
Perhaps you could use the the control ports on the Axcent2 with just a little effort.
Write a custom control protocol for the RS232 ports on the two systems that pass button pushes and releases from the NetLinx system to the Axcent 2. Then run some Axcess code in the Axcent2 that decodes the strings and sends IR or pulses relays as necessary.
As I said, it's very strange, but at home, in this way I'm controlling the Volume channels of my AXcent1 with my NetLinx Master....
I don't have an example and protocol here at the office, sorry.
For me at home, an AXB-VOL3 (also a secondhand one) is too expensive. The AXcent1 has cost me 1 hour of repair and about 35EuroCent of spareparts...
I must confess, I recently bought an Axcent2 off eBay for next to nothing. On my ToDo list is the idea of writing a Netlinx module/virtual device which talks to the Axcent2 via the External Control protocol. There seems to be enough info passed back & forth in the protocol to make the Axcent2 still useful, except that it costs 1 serial port on both the Axcent2 & Netlinx. With the virtual device taking care of the External Control messages to & from the Axcent2, you should be able to treat it like any other device in the system.
I'd be inclined to include some code checking that diverts strings/commands to a debug terminal when someone inadvertantly tries to send a string out the Axcent2 port that is occupied by the External Contol link. If you want to get really special, filter out all commands that the Axcent2 does not act on, and report back to the Netlinx master as "The XXX command is unsupported."
But, now that I think about it.... I just couldn't live with it not being Netlinx code.... Bid away
Jeff