Re: Understanding S-Link Communication

>>

1) Should any S-Link enabled device send a message when it does something (ie, when it recieves a

command via IR, or when I press a button on the device)? <<

Usually, but not always. Some IR / front panel actions elicit no S-Link messages.

>>

2) Is there any way to configure CDJ (or write a custom app), to report ALL the messages received over a

given S-Link bus? <<

CDJ already does this.

>>

3) Can someone offer any example code that uses the ActiveX control to send arbitrary messages with the

"test" command available in some of the device files (in particular, the sls.cde file). <<

assuming you've already figured out how to use normal commands, the test[] command is pretty straight forward:

sls:test[9000]

would send the bytes 0x90 and 0x00 hex out the S-Link port (this command will cause CD Player 1 to play)

if you're trying to find new S-Link codes for your DVD, let me give you some advice:

1) The S-Link code structure can be generalized as follows: [device ID byte][command byte][optional additional data bytes...]

most devices I've seen have remarkably similar command bytes, and only really differ in their device IDs. For example, most devices support the mode (0x0F) command.

2) With this in mind, you first task is to hunt down the device ID. CDJ is a great tool for this. Install the sls.cde on a port and then go to the S-Link viewer. Type sls:test[**0F] as a command and hit the iterate wildcards button. CDJ will loop through the 256 possible device IDs sending out mode commands. All you have to is look for the ones that get responses.

3) Now fix the device ID and start looping through command bytes to start discovering commands. Like I said before, many of these will be the same as what you see in cdpcx200sls.cde and cdpcx220slr.cde, so read up on those first.