piwolf

Im having trouble wrapping my head around the translations between hex and ints and ascii involved inherently in some max objects and how that relates to formatting command info to send out the serial object.

I have tried writing out some simple ints and lists of ints that are translations from hex data supplied by the manufacturer with no luck. I also feel like the developer info from blackmagic is a bit sparse and I was hoping for some help with message format.

Ive attached screenshots from the blackmagic support of command data info.

Would I be sending the max serial object a message that is a string of ints which are translations of the Hex data specified in these screenshots?

How much data is the max serial object already supplying and formatting that I dont need to include in the message box?

Finding after years of advanced gl work that I am such a noob with serial packets.

Hello forums!
Im having trouble wrapping my head around the translations between hex and ints and ascii involved inherently in some max objects and how that relates to formatting command info to send out the serial object.

Would I be sending the max serial object a message that is a string of ints which are translations of the Hex data specified in these screenshots?
How much data is the max serial object already supplying and formatting that I dont need to include in the message box?

formatting-serial-422-command-messages-for-hyperdeck

The main thing to remember is that hex, octal, binary, and decimal are just different ways of representing same integers. So, yes, you need to send the decimal values of the integers to the serial object and everything should work.

That said, the documentation you posted does take a bit of figuring out which bits need to be set how, and from thence converting them to integer values. Also, a possible trap may be making sure you send bytes to the [serial] object in the order your device expects to receive them.

Also make sure you've got the bit rate, parity, etc. matching.

Serial can be a bit of a PITA to set up, but once it works it's fairly straightforward.

That said, the documentation you posted does take a bit of figuring out which bits need to be set how, and from thence converting them to integer values. Also, a possible trap may be making sure you send bytes to the [serial] object in the order your device expects to receive them. 

Serial can be a bit of a PITA to set up, but once it works it's fairly straightforward.


does the serial object send out binary or ASCII bytes to devices?

so finally found a pinout issue with the setup and everything works like a charm now.

the serial object obviously sprays out binary.

controlling ki pros and hyperdecks currently

i love that message boxes auto translate hex to integers, makes it easy to do checksum.

so finally found a pinout issue with the setup and everything works like a charm now.
the serial object obviously sprays out binary.
controlling ki pros and hyperdecks currently
doing some frame sync testing today.

i love that message boxes auto translate hex to integers, makes it easy to do checksum.


I bet you're the one who would know this. I'm trying to send some commands with RS232 but I can't seem to get it working. What objects did you end up using for your serial 422 set-up? I'm really struggling. - all best.

I bet you're the one who would know this.  I'm trying to send some commands with RS232 but I can't seem to get it working.   What objects did you end up using for your serial 422 set-up? I'm really struggling.  - all best.


I have a suggestion: create Macros with the ATEM software and then trigger the Macros using the atemOSC utility. It is very stable and there are examples to get started on the site. This will give you Max control over most of the commands you are trying to trigger using serial. And by the way, the atemOSC programmers are currently working on more direct control of the Hyperdecks.

atemOSC
http://danielbuechele.github.io/atemOSC/

Formatting Serial 422 command messages for Hyperdeck