Show Cue System

Hi Mike and SCS-hivemind; hope all's good - this is more of a networking issue but raises a few SCSuggestions.

11.8.5 on Win10 x64. Am successfully controlling a projector (Hitachi CP-X9110) with Network Control Send cues to a local IP on port 23 - annoyingly, however, the projector automaticaly disconnects the TCP connection after 30secs of inactivity (no way to disable this, and seemingly quite common on projectors from other manufacturers).

Things I have tried include:

• Idea: let's try poking the TCP port outside of SCS to keep it open
  
  Outcome: I believe TCP#23 is/was telnet, but none of the scripts I've scribbled so far are being read as RS232C the other end. I'm trying to loop a(ny) message to the projector via port #23 to act like a keep-alive/heartbeat.
  
  SCS Suggestions: a) a loop option (with #loops, etc.) under Control Send cues, combined with: b) a checkbox for all cues like Exclusive Cue that would protect the triggered cue from being stopped in any way (list movement, StopAlls, etc.) until [other trigger/shortcut].

• Idea: OK, let's do it in SCS - a Ctrl Send cue that fires a string at the port to keep it open, and looping that via an auto-triggered GoTo cue
  
  Outcome: Works great in principle, but breaks in Linear Mode when I change the cue list position (e.g. fire another cue), and auto-firing GoTo cues don't work (obviously) in Non-Linear Mode.
  
  SCS Suggestions: a) GoTo cue that can target sub-cues (potential nightmare?); or b) the ability to segregate cues in a separate-but-simultaneously-playable cue list(s) (with activation/relative-start options like Playlist cues but for all types of cue, or - apologies for the comparison - QLab's Grouping).

• Idea: er I guess just use PJLink
  
  Outcome: IT are blocking that port for some reason so no-go when I get this onto infrastructure, and the projector we have accepts very few PJLink commands - certainly none of the ones I need.
  
  SCS Suggestions: PJLink sucks butts.

• Idea: maybe other people have this problem
  
  Outcome: This appears to be a common issue with multiple projectors, though haven't come across SCS users faced with it yet. Anyone out there?
  
  SCS Suggestions: If it's worth the work, a keep-alive checkbox next to the ctrl send device that nudges the port in question every x secs to check/maintain connectivity?

Any and all help appreciated; will happily take forehead-slapping why-didn't-you-think-of-this solutions too!
Cheers,
Bruce

A possible solution is to modify 'Go To Cue' to include the current cue in the list. If a 'Go To Cue' sub-cue is actioned where the cue label is that of the current cue, then the whole cue would be restarted.

Cheers for the speedy reply, Mike (and for a phenomenal software and excellent service!),

Yep, would be a good solution, but unfortunately the loop breaks when I need to fire another cue, or otherwise move around the list. Not sure if there's any way to have separate cue stacks - one running 'in the background' to handle the looped network send while normal operation continues elsewhere - or (my assumption) is the network keepalive something that'd have to be done outside SCS?

Massive thanks as always,
B