Possible issue with AxLink Device
ericmedley
Posts: 4,177
Here's a little problem I ran into that I haven't seen before.
the master is an old ME-260
The short versin is that I was using an AXB television manager box to flash IR to a TV. I then wanted to use the built-in I/O sensor and an AMX power/current sensor to determine the power state of the thing. (no descrete on/off ir commands)
The box uses channel 255 as the I/O port's state.
So, I configure the box, etc.... wrote the new code and no workie.
banged around for quite a while on it with no success. I could see the channel turning on and off in diagnostics but the code would not fire.
I've seen before on other devices the need to put in a set_virtual_channel_count to get channels above 255 to work in code. I've never seen them with axlink devices. I tried putting that in. set_virtual_channel_count(dv_Axlink_Box,255)
Still no workie. Called AMX, but baffled them too.
I tried all kinds of code methods with no luck.
What eventually did work was to put in
set_virtual_channel_count(dv_Axlink_Box,512)
Why this works is somewhat baffling to me.
This smacks of some kind of odd firmware/compiler problem to me. Perhaps it's not a problem in that the master is old skool and the newer ones are not a issue.
But, I just thought I'd throw it out there in case anyone else runs into this.
e
the master is an old ME-260
The short versin is that I was using an AXB television manager box to flash IR to a TV. I then wanted to use the built-in I/O sensor and an AMX power/current sensor to determine the power state of the thing. (no descrete on/off ir commands)
The box uses channel 255 as the I/O port's state.
So, I configure the box, etc.... wrote the new code and no workie.
banged around for quite a while on it with no success. I could see the channel turning on and off in diagnostics but the code would not fire.
I've seen before on other devices the need to put in a set_virtual_channel_count to get channels above 255 to work in code. I've never seen them with axlink devices. I tried putting that in. set_virtual_channel_count(dv_Axlink_Box,255)
Still no workie. Called AMX, but baffled them too.
I tried all kinds of code methods with no luck.
What eventually did work was to put in
set_virtual_channel_count(dv_Axlink_Box,512)
Why this works is somewhat baffling to me.
This smacks of some kind of odd firmware/compiler problem to me. Perhaps it's not a problem in that the master is old skool and the newer ones are not a issue.
But, I just thought I'd throw it out there in case anyone else runs into this.
e
0
Comments
You say this is an old ME-260...by that, you don't mean an ME260-64? So I'm assuming it is not running Duet firmware? I have a vague recollection of a bug that was fixed long ago as part of Duet firmware that revolved around the boundary condition for channel numbers. (ex. 1023 vs 1024). This fix would have been after Duet firmware was introduced and sustaining support for pre-Duet firmware had been discontinued. So it wouldn't have been available to the old ME-260, which doesn't have enough memory to run Duet firmware.