Integra "dot 8" series

jjames

Has anyone played with the Integra DTR-x.8 recievers yet? They apparently have network capability, and in fact can be integrated via the network. You can send commands via its web interface, so I'm trying to figure out how to send a command to it (via IP.)

In the browser, if you put http://192.168.1.59/1?3=!1PWR01 it powers the device on. I tried opening the a port and using this to communicate with it:

SEND_STRING dvDTR, "'GET /1?3=!1PWR01 HTTP/1.1',13,10,'Host: 192.168.1.59',13,10"

But it's not working like I expected.

Also, it was recognized in the DDD portion of the master, but a module compatible with it wasn't found. Anyway, just looking for some help with the IP control of this, but will resort back to serial if need be. The next question would be how would I recieve information from the device via IP? (If I could get it to work.)

Thanks in advance!

Marc Scheibein

You may have to send the cr/lf twice...
A working string I used on a dial-in router:

SEND_STRING dvIP_CLIENT,"'GET /cgi-bin/dial?rc=@&A=D1&rd=status http/1.1',13,10,13,10,'Host: 192.168.0.254',13,10,13,10"

vining

Have you tried to open a telnet session with it. CMD> telnet> o IP Address and then try to send commands directly. Although it seems to have a built in web server, for integration purposes I would think you could connect just as you would in telnet and once an IP client port is opened it would essentially be the same as a serial connection all your code would basically work the same.

If is only allows connection via HTTP then you have to find out if it drops the connection after each transfer. If it does you might want to consider using serial.

jjames

Okay, here's what I've figured. Marc - the commands work AFTER I hopped on port 80. (Go figure!) I was trying to send those commands through port 60128 (found under the setup for control.) Apparently, it doesn't support telnet, but from the protocol below, it appears like it should work like telnet.


Now - I also finally got the protocol for the ethernet control, and here it is.

1.2. ISCP over Ethernet (eISCP)

*Protocol is TCP(Transmission Control Protocol)
*Destination Port Number is 60000(default)
Please set the destination port number by the setup menu in the Receiver and turn off to stand-by once , If you need to change it from default.
*Receiver MAC Address
Please confirm the Receiver MAC address on the setup menu in the Receiver.
*eISCP Packet Format

Header Size is the size of eISCP Header. In order to extend header size in the future, it is necessary to take it into calculation. Now, it is 0x00000010. (**BIGENDIAN**)
Data Size is the size of the eISCP Data. (**BIGENDIAN**)
Version is ISCP version. Now, it is 0x01.
Reserved is used extending it in the future. Now, it is 0x000000.
Unit Type is the model category ID. The Receiver is "1".

Note: The communication between server and client should hold one connection continuously. Unless it has connected continuously, the notice of status cannot be performed from a client.
Note: The number of the connections who can connect with a client is one.
Note: The Interval Time Receiving the message needs to take more than 50msec.

See the attachment for more.

jjames

Update

Okay, after messing around and doing some IP sniffing and such, I finally got the header. Would anyone else agree the documentation is not as straight forward as one would think? Apparently, there will be a Duet module soon - so, we'll see how it goes. But, I'm able to keep my code that I've been using for years with the Ethernet control - woo-hoo!

Here's the header I'm using:

INTEGER nDTR_HEADER[] = {$00,$00,$00,$10,$00,$00,$00,$08,$01,$00,$00,$00}

SEND_STRING dvDTR_ETH, "'ISCP',nDTR_HEADER,'!1PWR00,CR"

Seems to work pretty well. Just wish I had a TP to see if the volume feedback speed is increased through ethernet.