CUE to wall lights does not seem to work on a Jnior 410 on a GDC SR-1000 server.

[Rafael Barbosa]

In the attached photo, is this the correct way to do the CUE to connect the wall lights? Can you tell me the correct way to do it?
.
Important notes, using Jnior 410 (OS Version v1.0.6)
I find it strange that on the device page, the Jnior 410 model does not appear, only the a310 and 412 (second image). Or does this have nothing to do with it?

[Dave Macaulay]

I'm not familiar with SR1000 cues, so can't help with that. I've never seen that screen. Usually there's a choice for each relay to switch on, switch off, or pulse on with other servers.
The model number doesn't really matter. Commands are the same regardless. The number is related to the number of output relays and inputs - 310 and 410 have 8 of each, 312 and 412 have 12 outputs and four inputs. Telling a 410 to close relays the nonexistent 9-12 won't do anything.
If a cue is correct, the LED beside the desired output relay will flash (for pulse on) or just go on or off (for switch on/off). Switch on/off are never, in my experience, used with a dimmer as they use a pulse command. I've only used on/off for magnetic door holders to have the doors held open on changes but close themselves during a show.

[Rafael Barbosa]

This one uses pulses. I couldn't find in either the Jnior manual or the GDC manual how to make the CUE structure, I only have this picture of the CUE to turn on the light but I don't know if it's correct.

[Dave Macaulay]

In the SR1000 user manual it says how to add a Jnior IO device. I don't see anything about a 310, 312, 410 0r 412. But it's an older manual (2019) I have and this may have changed. Doremi/Dolby and Barco servers have device managers that work about the same, you select a device and fill in some details (port # and login) then in add cue the functions are easily available. Probably the SR1000 is the same but GDC does things a bit differently (all brands do).
If you really want to send raw commands, the Jnior Support Tool has a hex command builder (tools/advanced) but that should not be needed.
These Jnior IO devices are used A LOT in cinemas so GDC should have a simple way to send a cue to one. Maybe a GDC familiar tech here can help you out?

[Rafael Barbosa]

I have the 2022 manual, It explains how to add a device, this now I believe is added correctly.
But now I need to know what is the CUE structure that I need to create to send the pulses correctly. The manual does not show this.

[Shibu Paul]

GDC does not require any automation device. All GDC servers come with an inbuilt relay and support GPIO > Coil functionality.

[Steve Guttag]

I'm reasonably certain that GDC servers do not have actual dry-contact relays (do you hear a click/clack when they fire?). They are bound to be an open-collector type output transistor...likely part of an opto-isolator to protect the server electronics.

As to the JNIOR...I have none in my service as we went with Eprad's eCNA line long ago (no regrets there either...the most reliable automation on the market). It is entirely possible that you have a configuration issue. I don't know what the options are. Perhaps "Level" is not the right one. JNIORs often have a user/pw that need to be configured.

Bruce Cloutier often cruises these forums and provides outstanding support for the JNIOR line. He, likely, can advise you on the SR1000/JNIOR integration and what must be done for things to work. If you haven't done so already, it might be worth searching to see if this sort of question has come up in the past. Bruce has started a couple threads on the JNIOR.

[Rafael Barbosa]

I'm reasonably certain that GDC servers do not have actual dry-contact relays (do you hear a click/clack when they fire?). They are bound to be an open-collector type output transistor...likely part of an opto-isolator to protect the server electronics.

As to the JNIOR...I have none in my service as we went with Eprad's eCNA line long ago (no regrets there either...the most reliable automation on the market). It is entirely possible that you have a configuration issue. I don't know what the options are. Perhaps "Level" is not the right one. JNIORs often have a user/pw that need to be configured.

Bruce Cloutier often cruises these forums and provides outstanding support for the JNIOR line. He, likely, can advise you on the SR1000/JNIOR integration and what must be done for things to work. If you haven't done so already, it might be worth searching to see if this sort of question has come up in the past. Bruce has started a couple threads on the JNIOR.

This Junior already worked here with GDC, but it stopped working some time ago. In some attempts to make it work again I ended up deleting the CUE structure and I don't remember what it was like anymore. I only have that photo from the first post.

[Carsten Kurz]

Contact INTEG about the JNIOR directly, their support is excellent!

support@integpg.com

[Bruce Cloutier]

There you go. While it is good sometimes to spend the time to figure things out for yourself, in this case just contact INTEG to expedite things. Everyone is supported for free directly by the technical staff sitting right here amongst the engineering and production activity. None of this is subcontracted out.

With things today if anything stops working there are just too many points of failure for it to be literally something simple that you might trip upon. The JNIOR provides enough diagnostic capability that the guys can usually pinpoint the issue pretty quickly.

Thanks guys for helping.

[Rafael Barbosa]

There you go. While it is good sometimes to spend the time to figure things out for yourself, in this case just contact INTEG to expedite things. Everyone is supported for free directly by the technical staff sitting right here amongst the engineering and production activity. None of this is subcontracted out.

With things today if anything stops working there are just too many points of failure for it to be literally something simple that you might trip upon. The JNIOR provides enough diagnostic capability that the guys can usually pinpoint the issue pretty quickly.

Thanks guys for helping.

Ok. I contacted support by email, but I haven't had time to follow the first support tips yet. But I will continue by email, thank you very much for your attention.

[Bruce Cloutier]

If you are interested in what each component does on the JNIOR PCB, the inner workings of the Rensas RX MCU, or any fine detail as to the JANOS operating system, then I am your man. I am not so much up on media servers and their configuration. It is best to handle that through tech support as they can correlate your issue with anything that we've seen before and properly track the resolution.

It is unfortunate that technical support can be a frustration with practically any of the larger companies. I also don't jump at trying to contact other companies. So I get it.

The Series 4 JNIOR monitors interconnections. If the SR-1000 communicates via the network we can use NETSTAT -S to watch the network real time (like Wireshark) to actually see if the media server connects and does anything. If you use a serial connection via the AUX port you can use the IOLOG to see the full exchange of data over the port. The IOLOG also lets you see each and every relay closure or input state change (to the millisecond). On the application side with the cinema software there are debug logs continuously generated which the guys can review (part of a snapshot) and figure out what to do.

Um, if you have Series 3 there are limited diagnostics available.

Operation can be interrupted by changes/updates on the media server, changes made on the JNIOR, and/or some odd situation occurring on the network side. Wiring can become disconnected. Lightning strikes occasionally, literally. So it is best to let the guys pour over the snapshot and help you out. They will! And, quickly.

Most documentation sucks anyway. The Book of JANOS (JNIOR User Manual) probably has too much information. Most don't even know how much help information your JNIOR has available. It is just faster to get our ear.