Basic Interface

Connexions

Hey Guys,

i am trying to get a basic interface working for the BLU-100,

Basically all I need todo is have the ability to raise and lower the gain on the channels in the project.

I am trying to get this working over the Port 1023,

When I open it in a Telnet Session,
The connection is current and when i Send a command, the unit flashes the 'com' light but nothing happens.

For Example this code works in the DI Tool: (Bumps the Gain up by 5.00)

0x02 0x90 0x51 0x5E 0x1B 0x83 0x00 0x01 0x0F 0x00 0x00 0x00 0x05 0x00 0x00 0x97 0x03

But when i copy and paste it into the session, I get the flashing light but the gain level does not increase.

I have read the third party interface booklet, but i cannot seem to find if there is any particular syntax required for it to accept the command.


Regards,

Nathan

HARMAN_Jerome_King

Telnet is not the mechanism for sending DI messages.
Soundweb devices will only repond to DI mesaages on TCP port 1023.

Connexions

Thanks for the Reply,

in putty I am setting the Connection type ot 'telnet' then changing port to 1023.

I can not connecting on the telnet port.

Cinch

Well, the 0xYY values are hexadecimal values, when you paste those into a putty connection, putty will interpret each character as a ASCII, then the values are corrupted...
What you could try....
Put the 0x values into a hex editor and take a look what you get as ascii there, hopefully, you will have some normal characters, paste those into the putty connection... You get the trick?!

malcolmg

Clinch

nope.. I don't quite get the trick. Can you point in the right direction so I can do some reading? (learning!)

Are we needing a lesson here on creating a HEX string? I thought the BSS needs to receive an ASCII representation of the HEX values over a socket. You get the values from the Direct Inject tool bar, which are an ASCII representation of the HEX values.

I have been trying to connect via a socket (SocketTest.exe) and also hopefully via a PHP socket..

I kind of understand your point, Putty (and I assume SocketTest) are interpreting the characters as ASCII before sending. OK...then how does one send a HEX string via a socket? I certainly cant see this gem of information in the Control interface kit!

Any advice would be greatly appreciated.

HARMAN_Jerome_King

Putty and SocketTest are not the same thing. Forget about Putty.
SocketTest or Hercules works fine using port 1023. Try copying a string from the DI Toolbar in LA and paste it into SocketTest. That should get you going.

malcolmg

OK...getting closer

SocketTest has no ability (that I can see) to send a HEX string.

In Hercules, a 2 digit HEX string, with a space as a separator worked. there is a selector box to send as \"Hex\". Copying the 2 digit HEX string from the DI toolbar, with no separator and no prefix worked. eg \"02 88 4A D3 1B 83 00 00 01 00 05 00 00 00 01 17 03\"

Using either SocketTest or Hercules, no combination of anything I tried, would get the same result using an ASCII string. i tried all combinations of prefix & separator. '0x', '\\x', with a separator ',' and or a space.

I am asking this,as the next step for me is to communicate via PHP. I believe a PHP socket has the same issue of interpreting the characters differently, and cant use HEX directly. The solution I found was to use the \"Decimal\" output string from London A, then in PHP use the chr() commands to interpret into HEX:
ie $message = chr(2).chr(136).chr(74).chr(211).chr(27).chr(131).chr(0).chr(0).chr(1).chr(0).chr(5).chr(0).chr(0).chr(0).chr(1).chr(23).chr(3);

This works (yay!)... but I still don't understand why. Am I asking the wrong question - 'what is the ASCII representation, of a hex string with the correct prefixes & separators to send to the device?\"

Why does the manual tell you to copy the \"HEX string\" from the DI toolbar, yet its not what should be sent to the device?...

HARMAN_Jerome_King

SocketTest interprets messages as ASCII and it also adds a CR and LF to each message. As far as I can see, it is designed to test sockets and send simple ASCII messages. It cannot be used to send DI messages to a Soundweb.
Hercules allows you to enter a message in Hex format and it does not add CR and LF, so it can be used to send DI messages.