peterw wrote: > Except that you have to power cycle the AVR?
Not really. The timeout only happens (but rarely) when the AVR is powered off (in standby mode) and I am trying to query its power status (PW?) during player startup. If it's already powered on, there's not a problem. The AVR always returns "PWON". The error routine that is invoked on any TCP write errors, including this one, previously just gave up the ghost and exited the callback. With the code change, if the command was a "PW?" and the error is a timeout, it treats it the same as if the AVR had returned a "PWSTANDBY" status and invokes the appropriate plugin logic (PWON, Quick Select, etc.) > Do you maintain a persistent TCP connection or connect, send, process > responses, and then disconnect? Because my AVR will eventually (usually > pretty soon) respond to normal "?" query and other commands if I just > disconnect my TCP connection to the serial port server. (I have no idea > if the 'ser2net' serial port software maintains a connection to the > RS232 port.) The latter, i.e. connect, send, process responses, and disconnect. Using this method, we don't have to deal with all the extraneous small talk that the AVR likes to engage in with its clients, proudly informing us of the current settings of each and every one of its hundreds of parameters over and over. I almost feel bad for the poor guy, just disconnecting after I get the info I need without even asking how his day is going. ;-) Maybe this occasional refusal to answer is his way of expressing his hurt feelings. I suppose it could be worse... "Turn down the volume from 98dB, Hal..." "HAL!!!" > Don't let that stop you! "Enable Amp Status Polling" is a configurable > option (as is the frequency with which the amp is polled, and the > frequency can be different for active** and inactive modes). Turn amp > status polling off and it will still take action promptly when the LMS > player volume or muting or power state changes -- LMS just won't > recognize when somebody has used a Denon remote or the big volume knob > to change the AVR volume. Okay. I didn't know that. I've actually thought about adding that as an optional feature in AvpControl also. Maybe v5.0. The only method currently in place for handling that situation is the optional "Sync on track change", which only works for the main zone since, as far as I have been able to determine, there is no command analogous to "MV?" for the secondary zones. > ** For my plugin, "active" apparently*** means "has seen a recognized IR > command recently" -- IIRC when I initially wrote this I saw that the SB3 > recognized the raw IR command codes of some other devices (though it had > no mapping so didn't act on any of them), and thought if the SB3 saw > somebody interacting with someting like the TV, then it was pretty > likley that somebody was in the room and more likley than usual that > somebody would turn the AVR volume knob. Now THAT's what I call AI at its finest!! ;-) Sam ------------------------------------------------------------------------ SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495 View this thread: http://forums.slimdevices.com/showthread.php?t=60114 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
