Visual Productions forum

Author Topic: CueCore2 UDP Messages  (Read 132 times)

October 09, 2017, 07:30:10 AM
Read 132 times

danit

  • Member
  • *
  • Posts: 9
Hello everybody

Since the last update of my CueCore2 I noticed that the CueCore sends new UDP messages.

Such as:

core-pb-2-active=Off

core-pb-2-cue=1

core-pb-2-intensity=0.50

core-pb-2-active=On


This is great, but where can I set this?
The messages are sent to any port and always four times.

Have the new update also included new UDP messages that the CueCore understands?

Is it possible to have a list with all UDP messages that the CueCore understands?

I use my CueCore exclusively via UDP messages.

Thanks for your help.

regards
danit

October 09, 2017, 03:40:10 PM
Reply #1

Guido Visser

  • Administrator
  • Member
  • *****
  • Posts: 122
    • Visual Productions
Hello Danit,

The messages you are receiving are part of the API. We have added the API for things which where use most frequently using UDP and OSC. All messages related to the API can be found in the manual.

The CueCore2 will send the API feedback messages to any device who has send a message to the CueCore2. It will remember the last 4 connections which where created.

However it should not send message to all ports. I am guising that you have some network analyses tool for reading messages from the CueCore2. And noticed that the CueCore2 was sending you messages. 4 messages to different targets. A target is an IP address and port combination.

I hope that this information was helpful.

Best regards,
Guido
Guido Visser
Visual Productions BV

October 10, 2017, 01:33:08 PM
Reply #2

danit

  • Member
  • *
  • Posts: 9
Hello Guido

Thank you for your reply.

This is super with the reply UPD.
But in the actual user manual on your homepage is unfortunately still nothing of the new Messages over UDP.
The user manual is from december 2016.

Unfortunately, my HomeServer, which is responsible for communicating with the CueCore2, always sends the UDP messages from a different random port.

The HomeServer can only receive messages on one port UDP.

This is set to port 56000.

And the CueCore2 always returns the answers to the last four ports.
These ports are not considered for incoming UDP messages.

Is it possible to set the send port fixed?

Sorry is a bit complicated written but I hope you understand it.

I'll send you a PrintScreen to make it more understandable.

Thank you for your answer.

regards
danit

October 10, 2017, 02:28:38 PM
Reply #3

Guido Visser

  • Administrator
  • Member
  • *****
  • Posts: 122
    • Visual Productions
Hello Danit,

Appendix D.2 of the manual will describe the UDP message used by the API. You are right that the API Feedback messages are not described in the manual at this moment.

core-hello a feedback echo message.
core-pb-1-intensity=0.50 playback intensity feedback.
core-pb-intensity=0.50 master playback intensity feedback.
core-pb-1-rate=0.50 playback rate feedback.
core-pb-rate=0.50 master playback intensity feedback
core-pb-fade=0.50 master playback fade feedback
core-pb-1-active=On/Off playback active same
core-pb-1-cue=5 the active cue of a playback.

The API has been made for easy setup. Which will require almost no setup on the unit. The only thing you can change about the API is the port which the CueCore2 listens to. Which is the same port as for other UDP messages. Unfortunately you can not change the destination port of the API. The API will send messages back to the source.

If you want to send messages to your HomeServer you will have to set it up using show control.

Best regards,
Guido
Guido Visser
Visual Productions BV