Have a M-MMO in port B of a RAB2 card in my 144 surface. (Port A is ACE.) All seems to work fine except that I can’t see/configure the MMO card in the OUTPUTS screen.
The RAB2 is fitted right below the CPU card.
Any ideas?
Follow up: To my dismay, I found the following in the Hardware Reference (v1.7), "part 1-34":
"Surface Port B and firmware version V1.7. It is possible to fit the M-MMO option and assign its outputs, but note the following:
The Status screen does not recognise the Port B option even if one is fitted. Use the TouchScreen or Editor OUTPUTS screen ACE Link or ESA tab to assign signals to the M-MMO option fitted in Port B. Use CH33 and higher. These are permanently mapped to the M-MMO output sockets according to the table below."
The “table” shows AVIOM (the object of this little adventure) “Not Used”.
Any idea how I can support Aviom? via the Surface…? Maybe a second RAB2 in the IDR10 and move the M-MMO there?
Been through something like this before, but don’t remember all the details on it. I ended up with the full size aviom card in the iDr10 and used Dante in the mini card slot.
Have you thought about switching from the mini to full size card?
… “As gil has pointed out the best way would be to fit the Digital Multi output module to either your surface or …”
Thanks, both Gil and Sam.
At the moment, my plan is now to put a Digital Multi Out in the A/B slots of the Surface, remove the M-MMO from the RAB2, and move an existing Dual Mic/Line module from slot A to Slot C or D.
Is that an approved configuration?
Any concerns?
Thanks!!
Ray
PS. Would anyone like to comment on potential latency issues that may arise from the fact that this Dual-rack system has the 144 Surface (& Aviom out) attached to an iDR-32 (master) at FOH with the iDR10 (slave) roughly 130 feet of CAT5E away from the iDR-32. My concern is that band members onstage will hear Aviom IEM signals only after they’ve made the trip from the stage (iDR10 slave) to FOH (iDR-32 master) and then back down another 130’ CAT5E cable to the Aviom hub onstage.
Would like to revisit this thread to see if the following is still true:
Follow up: To my dismay, I found the following in the Hardware Reference (v1.7), “part 1-34”:
"Surface Port B and firmware version V1.7. It is possible to fit the M-MMO option and assign its outputs, but note the following:
The Status screen does not recognise the Port B option even if one is fitted. Use the TouchScreen or Editor OUTPUTS screen ACE Link or ESA tab to assign signals to the M-MMO option fitted in Port B. Use CH33 and higher. These are permanently mapped to the M-MMO output sockets according to the table below."
The “table” shows AVIOM (the object of this little adventure) “Not Used”</font id=“red”>.
AviomTM now available at Surface MMO: The MMO (Mini Multi Out) option is the only Port B option supported at the modular Surface. The AviomTM output socket can now be assigned (they duplicate the assignments to the MMO ADAT outputs).
Outstanding!! I just received my CPU upgrade for the iDR10 a few days ago.
Since I’m running a dual-rack configuration, I’d really appreciate someone from A&H reviewing how things are set up today and give me an indication of whether changes are needed before I upgrade to v1.9.
Current configuration:
144 surface (RAB2 w/ACE, M-MMO in port B, and fullsize MMO card in A/B slots because I was going to have to deal with this in v1.83),
(1) The Dante card is used to feed a nearly full complement of 64 channels from a combination of the two racks. Any concerns over Dante firmware version vs. v1.9?
(2) My ideal world would be to upgrade to v1.9 and then use both MMO cards in the surface for dual Aviom (or A&H ME!!) systems.
Thanks for the encouragement, Nicola! Eager to get v1.9 installed!