jpimentel wrote:Hi,
I have worked out most of the issues using this very cool and much needed plugin. With this tool, I see my abilities to use ML somewhat endless!! Very nice feature set and implementation.
So... on to the strange thing. I am writing a device for an Integra Receiver. When I execute a power on, or power off to this unit, it is sending MLServeCmds even though I have none specified for that event.
What appears to be happening is that my mapped commands for power on and power off are being matched when I send a power on or off command. I guess this is sort of expected although it would be better if we could separate outgoing mapped commands from incoming ones. But, then for some strange reason, I see a CAV66 command being generated whenever I send power on or off to the unit. Specifically the comand is:
MLServeCmd.MLCAV66|Keypad~1~1~PowerToggle
Could there be some corruption or crosstalk in the plugins?
This is a complete befuddlement to me. Any suggestions on debugging this would be appreciated.
Thanks,
John
EDIT: I removed the CAV66 plugin and all MLServer Command Maps and the command is still being generated!
I am still having issues with the bug above. I have done some experiments and have found that the command is coming from the erial plugin and hitting MLServer internally (not from a com port). In my testing I disabled all serial ports except the one for the Integra Receiver via Generic Serial. As soon as I recieve a particular daat string from the receiver and the termination character is 26 on the main panel of the device (the only way incoming data will work since this is the termination string for Integra even if the termination string is in the mapped comnmand)
I would really appreciate if someone who has access to the source could have a look at this for me.
My two basic questions are:
1. Whay does this particular string make the plugin generate the totally non-related event?
2. How does this plugin know exactly how to generate an event for a unrelated plugin?
It seems to me that there is a fundamental house keeping issue with this and or the Russound Plugin. I have ask Dave P. to look at it from the Russound side and trust in time he will, but I am really beleaguered by this issue and would appreciate a fix greatly.
As always thank you.