We added QU-5D desk recently to our stock and as we usually connect our former QU-16 and QU-24 to an AR2412 Stage Box using single mode fiber and CAT convertors that always works except this doesn’t work on the QU-5D.
I think this is because the AR2412 usually speaks to the desk and updates its firmware to match the desk but seems like it cannot update to the new QU series.
Anybody have any insight on this issue?
I think you will have done it of course, but since you didn’t mention it, just to be sure: For the expected firmware update of the AR2412, did you connect it to the QU via a CAT cable and waited a while.?
So, did the AR work with the CAT cable, and there’s just a problem with the fiber?
I did connect AR2412 via Cat cable but i dont think it updated or is going to update because I think the firmware release of QU-5D is not set to update AR2412 firmware like the older QU series. The stage box works over cat cable but no update.
I would assume that the stage box only works if it already has a correct firmware and doesn’t require an update.
In that respect, that’s actually a good sign.
But unfortunately, I wouldn’t know why it doesn’t work with the proven fiber system. (
Why should the QU-5(D) not update the firmware of the AR2412?
Do you have set the samplingfrequency of your QU-5D to 48kHz. (I assume you have, otherwise it woukd not have worked with direct CAT connection)
The sampling rate of the console is always 96 kHz and cannot be changed.
The desk automatically sets itself to 48 when it detects slink device at 48. No option to set the desk main sampling, can only set sampling for AES and USB and Dante can be set from Dante controller
Sorry, I tumbled it with the USB settings.
Even with a connected 48 kHz stage box, the console operates internally at 96 kHz.
There is only a sample rate conversion from 48 to 96 kHz for the input signals and vice versa for the outputs.
We are diverting from the main question which is why wouldn’t the QU-5D be able to send Slink through using fiber and cat converters while the predecessors QU-16 were able to do it.
Maybe the frequency is still the problem.
If you have a point-to-point cat connection, both sides can handle out the tx/rx frequency direct.
If you use the converters on both sides, I could imagine each device handles out his own frequency with the converter:
QU-5 with converter 96kHz
AR2412 with converter 48kHz
With Qu-16/32 it was no problem, because both worked with 48kHz from the beginning.
Makes sense but still a theory so hopefully someone from A&H could confirm.
If you’re primarily hoping for a quick answer from A&H, it’s advisable to contact support directly.
https://support.allen-heath.com/hc/en-gb/requests/new?ticket_form_id=360001516878
In any case, it might be helpful to mention which fiber system and converters you’re using.
I did send A&H support a ticket already but thought I would also post here maybe somebody been through same issue and has an answer.
The way the SLink port automatically switches mode/protocol is almost certainly what’s going on here.
It first looks at the network speed to find out whether it’s a gigabit GX/gigaACE connection or a fast ethernet DX/dSnake/ME connection, before everything else (discovery, firmware update, status sync) takes place.
In this case, you want it to be fast ethernet but if the converter is gigabit it will switch instead to GX/gigaACE (you could confirm this on the I/O screen).
So try either setting the converter to 10/100 fast ethernet, or force the connection to this speed (either a dumb 10/100 switch with nothing else connected, or a network cable with only fast ethernet pairs connected).
Hi Keith,
The fiber convertors are 1G and this used to work with QU-16 to AR2412. So you are saying that I have to use a 10/100 Mbps convertors to make this work?
Hi @markwehbeh
Yes, you would need the SLink port to ‘see’ a 10/100 Mbps connection for it to be able to discover dSnake (or DX) expanders.
All A&H protocols are designed for point to point connection, so you’re effectively trying to mimic that with your fibre convertor.
The reason they would have worked with the Qu-16 is because that has a dSnake port that always runs at 10/100.
Thanks,
Keith
Hi Keith, the cheapest way to not negotiate 1G and force 10/100 Mbps was for me to make a CAT cable using only pins 1,2,3,6 and it absolutely worked.
Thank you for the support appreciate it.
That was a clever workaround.