CDM64 won't receive or send audio, network port won't work

I need some help with my Dlive C3500 and CDM64. The C3500 could not detect the CDM64 which we bypassed it and switched to the Just CDM64 we turned the mixrack on a few hours ago the mixrack was not detecting audio neither will the network work, the light on the network ports were not blinking as well. Please, what could be the problem.

What does “not detecting audio” mean?

What did you plug into the network port?

The DLive C3500 Surface needs to be connected to the built in GigaAce port on the DLive CDM64 Mixrack using the built in GigaAce port on the C3500. That is all that is required to send audio and data between the two devices. If you are making this connection and nothing works, something is broken. I would suggest trying the connection with a different network cable to ensure it is not a cable issue. It is recommended that you use shielded Cat5e cables for this connection.

EDIT - the two devices also need to be on the same firmware version. If this is a problem, the Surface will display a message on the screen that explains that the Surface firmware doesn’t match the Mixrack’s firmware. You’ll have to upgrade (or downgrade) one of the device’s firmware so that the firmware matches on both the Surface and Mixrack.

Additionally, to connect the system to a local data network, you only want to use the network ports on either the Surface OR the Mixrack. Never plug both devices into the same local network however because it causes a network loop which can bring down the entire network if your switches aren’t set up to use the Spanning Tree Protocols correctly.

If nothing is connected, how would you find out that the mixrack is not working?

With a laptop or tablet connected for example.

Then, there is something connected.

What makes you think there was nothing connected? :person_shrugging:

It’s a bit confusing… but switched to the just CDM64

And it was a question, btw… Still not answered. The OP didn’t come back after it’s initial question.

Yes, we have to wait. Probably it resolved itself. :winking_face_with_tongue: