I was curious so I looked at the 1.1 module. It does use MVMAX to provide a volume gauge. The volume text is whatever was sent back in MV (displayed in db), BUT the volume gauge is computed using the last value of MVMAX than it saw (which would be the MVMAX from the previous MV response). So based on the data you sent: For MV values between 0 and 410 you would likely see a gauge where 665 (or 670) is 100%, e.g. 400 would be about 60%. For MV = 880 you might see 100%, or close to it. If the MV value goes above 880 you will see a gauge that¡¯s wrapped around to 0, e.g. For MV=900 it could show about 2%. And all of this depends on which direction MV has been moving since it uses the last MVMAX it saw, e.g. you could see the same gauge wrap-around when turning down the volume and crossing over from something in the 700 range to the 400 range.
If that looks something like the ¡°weirdness¡± you¡¯re seeing, then it appears to be a result of the AVR sending back incorrect values for MVMAX
Hi h2oskr2001 This module definitely handles the MVMAX command (Although there's no indication of it in the '21 protocol). Clearly it is causing issues, perhaps that the MV processing is getting confused. But I even tried eliminating the variable and it still seems that things aren't working correctly.? I just seems that there's something different about the AVR or CP4 FW that's causing this as I've used this module in the same way for years without issue...
