Q-Sys Plugin unable to control CueCore2

[IAVLRyan]

Hello,

I am a Q-Sys (v10.4) integrator working to deploy my first CueCore2 (v1.46), and I am running into an issue with version 2.00 (and a prior version) of the official plugin. It seems that I can see the status of the CueCore in the plugin, including which playbacks are active and what cue they are on, but I am unable to send any commands.

The plugin shows the status "OK" and if I change the IP address or port it will say "fault" so it does not seem to be an IP or port config issue.

I never see any messages from the core in monitor>TCP, but if I use PuTTY the commands appear just fine and work. When I emulate the Q-Sys design and monitor with WireShark I can not see any packets being sent to the CueCore IP address other than web traffic from my browser and Art-Net traffic from MagicQ.

In the plugin debug panel I can see the plugin receiving messages from the CueCore, but there are no debug entries when I press any button in the plugin.

Any assistance or troubleshooting ideas would be very appreciated.

Thanks,
Ryan

[Jorge Solano]

Hello Ryan,

Thanks for reaching out and for the very detailed troubleshooting. Your tests have already narrowed this down quite a lot 

From what you describe, the CueCore2 connection itself looks healthy: the plugin connects on TCP port 7000, receives status correctly, and commands sent manually through PuTTY work. The important clue is that pressing controls in the Q-SYS plugin produces neither a debug entry nor any traffic in Wireshark. This suggests the issue is occurring on the Q-SYS/plugin side before a command is actually transmitted.

Could you please check the following for us?

1. The complete Q-SYS Designer 10.4 version/build, Q-SYS Core model and firmware version.
2. Whether the same behaviour occurs on the physical Q-SYS Core, or only in Designer Emulation.
3. With the plugin Debug Output set to the most detailed level, try Identify, Playback Go+ and Release and check whether any debug messages appear.
4. If possible, send us a minimal Q-SYS design containing only the CueCore2 plugin.

As an additional test, you can bypass the plugin and send a direct TCP command from Q-SYS to the CueCore2 on port 7000, for example:

`core-pb-1-go+`

If that works while the plugin itself still generates no traffic, it would isolate the problem very clearly to the plugin/Q-SYS side.

There is no need to factory-reset the CueCore2 at this stage. Based on your PuTTY test and the incoming plugin feedback, its TCP interface appears to be working correctly.

Hope this helps!

[IAVLRyan]

Hi Jorge,

Thanks for your reply.

To answer your questions:
1) Q-Sys designer and core firmware 10.4.0-2606.007. This is on a Core Nano.
2) The behavior is the same whether emulated or on the core itself.
3) The screenshot you see in my initial post is after pressing most if not all of the buttons in the plugin. That is the most detailed level, the "normal" option you see is to render the messages in plaintext rather than hexadecimal, but there is no error/warn/info/debug differentiation in Q-Sys LUA, just console prints.
4)I have emailed the actual Q-Sys design to support@visualproductions.nl for your review.

Using Q-Sys command buttons works perfectly, that has been my workaround, you will see this near the CueCore2 plugin in my design.

Please let me know if you need additional information, and thanks again for the help.

Thanks,
Ryan

[Jorge Solano]

Hello Ryan,

Thanks for the additional information and for sending over the Q-SYS project 

This narrows it down considerably. Since the same behaviour occurs both in Emulation and on the physical Core Nano, while your direct Q-SYS command buttons control the CueCore2 correctly, the CueCore2 TCP connection and network path appear to be working as expected.

The fact that the plugin receives status correctly, but operating its controls produces neither console output nor transmitted commands, points toward an issue within the CueCore2 Q-SYS plugin itself, potentially related to Q-SYS 10.4.

There is no need to make further changes to the CueCore2 configuration at this stage. We will reproduce this on our side using the same Q-SYS version and plugin, first with a minimal project and then compare it with the design you supplied.

In the meantime, your direct Q-SYS command-button method is a perfectly valid workaround.

Thanks again for the detailed testing. It has made the issue much easier to isolate!