Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems New Meridian Control app version, can't connect to 271 anymore

An update on my plight. I found that one of my iPads was set not to accept updates automatically. Although its IOS is version is 18.2 (I accepted that) the M Control App has not been changed. Whoopee, it works perfectly, finding my 271 quickly and reliably and allowing me to control my 271.

In case anyone is wondering why, with an RTI control system talking directly to my 271, I need the M Control app, it is because the RTI wakes up the 271 and my speakers but the long standing flaw in the 271 firmware means the level from standby is 65, despite settings being set so that it should be 87 (which gets sound levels right for the Trinnov). I find the easiest way to get from 65 to 87 is to use the M Control app. My excellent RTI programming person may be able to add a second instruction to the 271, after a suitable delay, to adjust the 271 sound level yet again to 87 (there is one already but perhaps it comes too soon for the 271 after its initial arousal) which would avoid any use of M Control, but that is something to be addressed in the new year. I would like to think that M will fix the app flaw soon, but it is a relief to know that there is a workaround, if you do not always allow updates. Actually, I am normally not an early adopter of app updates so I must be more careful with new kit (it was a recent iPad that I had left on automatic - very foolish).

If you need the command to set the 271 to 87 from the RTI let me know.

Bruce, That is a very kind offer, but my RTI programmer has incorporated a command (I explained the problem from the beginning of his work) and he knew he needed to incorporate steps to overcome the level-setting problem. I suspect the issue is one of timing in the control sequence as it only happens if my speakers have been just powered on from no power (as opposed to Standby) by me - I keep them off, mostly, to save energy and, sometimes, things work despite this. He will be coming to see me soon to put a new RTI processor in so we will check and tweak things then.

However, I have better news. Thanks to the magnificent Rick Weldon of Audio Images, my problem is solved. The exact cause cannot be identified with logical certainty because I have not done enough alternative testing, but it is something to do with the firmware version of the 271 and/or whether your controlling IOS device has been used with your 271 before.

I had discovered by messing around that my iPad Mini 5 did work as an M controller. I thought it was still on an earlier app version, but it turned out it wasn't. Yet the cinema iPad didn't work whereas the Mini 5 did. Puzzling.

Then Rick advised a firmware update for the 271. Mine was on 221 but the latest is 249. The update was done and the Cinema iPad still didn't work. So I did the obvious thing and deleted the app and re-downloaded and installed it. Everything then worked. I should add that I had already tried this before on the Cinema iPad and, at that point, it didn't help.

The Mini 5 continues to work.

So, it could well be the 271 Firmware. But perhaps whether the device you are using has been connected to a 271 before makes a difference (even uninstalling the app may leave some network settings behind). For sure, check you have the latest version (249) of the 271 firmware AND re-download and install the app again.