DMX Binding -Sending Direct Values instead of %

Hi All,

Is it possible for me to send direct DMX values to the dmx binding - ie I want to send 128 to channel X instead of 50%.

My reasoning is that for Xmas I have a need to control a few moving heads through the system for gobo projection and therefore need to control pan/tilt fairly accurately instead of reducing it down to % steps.

I know I can do this through the chaser module of the DMX binding, but wondered if it’s in some way possible directly.



The doc’s mention:
“Advanced options are the turnonvalue and the turnoffvalue . They default to 255 (equals 100%) and 0 (equals 0%) respectively. This value can be set individually for all DMX channels, the format is value1,value2, ... with values from 0 to 255.”

Would doing something like this work for your setup?


I noticed that issue too.

As it’s colour wheels, gobos, zoom, pan & tilt values you’re trying to set, have you considered using the DMX chaser ‘thing’. (Which does use 0 ~ 255 values in its setup string)

But instead thinking of it as a chaser, you could use it as a scene setter, or a chaser with multiple scenes.

I’d set the fade in times to 0 and use the hold times at the end. (Or don’t have a hold time, so that it sets the scene and stops.)

You could go wild and use;

  • 0:Step, 1, to, close, a, shutter:500|
  • 0:Step, 2, to, setup, the, wheels, and, new, position, with, a, ‘step, hold, time’ ,to, give, the, fixture/s, time, to, set:750|
  • 0:Step, 3, to, open, the, shutter, again?:0


Mac250 PDF in DMX1 mode - Page 21

Channel allocation


  • Channel 1 = shutter
  • Channel 2 = Dimmer
  • Channel 3 = Colour Wheel
  • Channel 4 = Gobo
  • Channel 5 = Gobo Rotation
  • Channel 6 = Focus
  • Channel 7 = Prism
  • Channel 8 = Pan
  • Channel 9 = Tilt

So a simple chase as a scene setter, with shutter control might look like…


Quick tip

If you’re going to split the elements of fixtures into different chases.


  • Gobo & shutter chase (channels 1,4,5,10,13,14,19,22,23)
  • Colour chase (channels 3,12,21)
  • Position chase (channel 8,9,17,18,26,27)

Don’t use the same channels in different chases.

IE, don’t put the shutter channel in more than one type of chase.

I hope that helps.

Good luck,


1 Like


Hi Scott

How did you get on?

As a result of thinking about your question, I have found a way to easily remotely control Jinx! from openHAB2.

I activated the Jinx! remote control and assigned the Art-Net or SaCN universe to listen to, and turned on the AUTO option in the scenes window (to automatically crossfade to the newly selected scene)

Then added a handful of Things and Items in to openHAB2 to send out a Master Dimmer control and a single DMX channel to select the chase.

In theory it is completely possible to replicate the Jinx! scene control UI in openHAB, if you switch off the AUTO mode in the scene window in Jinx! and use the appropriate DMX channels to select LEFT and RIGHT scene and cross-fade.

For reference, here are the Thing and Item files.

Bridge dmx:artnet-bridge:JinxBridge "JinxArtNet" [ mode="unicast", address="", universe=0 ] {
dimmer JinxMaster  "Jinx Master Dimmer" [dmxid="7", fadetime=1000, dimtime=1000 ]
  dimmer JinxChaseChannel  "Jinx Chase Channel" [dmxid="1" ]
  chaser chase01 "Jinx Chase 01" [dmxid="1", steps="0:1:0" ] 
  chaser chase02 "Jinx Chase 02" [dmxid="1", steps="0:2:0" ] 
  chaser chase03 "Jinx Chase 03" [dmxid="1", steps="0:3:0" ] 
  chaser chase04 "Jinx Chase 04" [dmxid="1", steps="0:4:0" ] 
  chaser chase05 "Jinx Chase 05" [dmxid="1", steps="0:5:0" ] 
  chaser chase06 "Jinx Chase 06" [dmxid="1", steps="0:6:0" ]
  chaser chase07 "Jinx Chase 07" [dmxid="1", steps="0:7:0" ] 
  chaser chase08 "Jinx Chase 08" [dmxid="1", steps="0:8:0" ] 
  chaser chase09 "Jinx Chase 09" [dmxid="1", steps="0:9:0" ] 
  chaser chase10 "Jinx Chase 10" [dmxid="1", steps="0:10:0" ] 
  chaser chase11 "Jinx Chase 11" [dmxid="1", steps="0:11:0" ] 
  chaser chase12 "Jinx Chase 12" [dmxid="1", steps="0:12:0" ] 
  chaser chase13 "Jinx Chase 13" [dmxid="1", steps="0:13:0" ]
  chaser chase14 "Jinx Chase 14" [dmxid="1", steps="0:14:0" ] 
  chaser chase15 "Jinx Chase 15" [dmxid="1", steps="0:15:0" ] 
  chaser chase16 "Jinx Chase 16" [dmxid="1", steps="0:16:0" ] 
  chaser chase17 "Jinx Chase 17" [dmxid="1", steps="0:17:0" ] 
  chaser chase18 "Jinx Chase 18" [dmxid="1", steps="0:18:0" ] 
  chaser chase19 "Jinx Chase 19" [dmxid="1", steps="0:19:0" ] 
  chaser chase20 "Jinx Chase 20" [dmxid="1", steps="0:20:0" ]


Switch JinxMasterMute "Jinx Master Mute" { channel="dmx:artnet-bridge:JinxBridge:mute" }
Number JinxChaseChannel "Jinx Chase Channel" { channel="dmx:dimmer:JinxBridge:JinxChaseChannel:brightness" }
Number JinxChaseChannel256 "Jinx Chase Channel as 256"
Dimmer JinxMaster "Jinx Master" { channel="dmx:dimmer:JinxBridge:JinxMaster:brightness" }
Switch JinxChase01 "Jinx Chase 01" { channel="dmx:chaser:JinxBridge:chase01:switch" }
Switch JinxChase02 "Jinx Chase 02" { channel="dmx:chaser:JinxBridge:chase02:switch" }
Switch JinxChase03 "Jinx Chase 03" { channel="dmx:chaser:JinxBridge:chase03:switch" }
Switch JinxChase04 "Jinx Chase 04" { channel="dmx:chaser:JinxBridge:chase04:switch" }
Switch JinxChase05 "Jinx Chase 05" { channel="dmx:chaser:JinxBridge:chase05:switch" }
Switch JinxChase06 "Jinx Chase 06" { channel="dmx:chaser:JinxBridge:chase06:switch" }
Switch JinxChase07 "Jinx Chase 07" { channel="dmx:chaser:JinxBridge:chase07:switch" }
Switch JinxChase08 "Jinx Chase 08" { channel="dmx:chaser:JinxBridge:chase08:switch" }
Switch JinxChase09 "Jinx Chase 09" { channel="dmx:chaser:JinxBridge:chase09:switch" }
Switch JinxChase10 "Jinx Chase 10" { channel="dmx:chaser:JinxBridge:chase10:switch" }
Switch JinxChase11 "Jinx Chase 11" { channel="dmx:chaser:JinxBridge:chase11:switch" }
Switch JinxChase12 "Jinx Chase 12" { channel="dmx:chaser:JinxBridge:chase12:switch" }
Switch JinxChase13 "Jinx Chase 13" { channel="dmx:chaser:JinxBridge:chase13:switch" }
Switch JinxChase14 "Jinx Chase 14" { channel="dmx:chaser:JinxBridge:chase14:switch" }
Switch JinxChase15 "Jinx Chase 15" { channel="dmx:chaser:JinxBridge:chase15:switch" }
Switch JinxChase16 "Jinx Chase 16" { channel="dmx:chaser:JinxBridge:chase16:switch" }
Switch JinxChase17 "Jinx Chase 17" { channel="dmx:chaser:JinxBridge:chase17:switch" }
Switch JinxChase18 "Jinx Chase 18" { channel="dmx:chaser:JinxBridge:chase18:switch" }
Switch JinxChase19 "Jinx Chase 19" { channel="dmx:chaser:JinxBridge:chase19:switch" }
Switch JinxChase20 "Jinx Chase 20" { channel="dmx:chaser:JinxBridge:chase20:switch" }

I have added a rule that reads back the chase channel % value and converts it back to a 256 value to confirm that the right channel is in use.

To take it a step further, I created a rule that steps through the chases when a power socket is ON in my house. (The socket powers other lights)

var int XmasInterval = 10
var int XmasSteps = 0
var Timer XmasTimer = null
var double Val256 = 0
var double chaseval = 0

	rule "Convert percent to 256"
		Item JinxChaseChannel changed

		JinxChaseChannel256.postUpdate(256 * JinxChaseChannel.state as Number)

rule "Step sequence"

     Item LoungeGreenSocket changed from OFF to ON
	XmasInterval = 400


     XmasTimer = createTimer(now.plusSeconds(XmasInterval))
 			if(XmasSteps == 0){

 				XmasSteps = 1
 			}else if(XmasSteps == 1){

 				XmasSteps = 2
 			}else if(XmasSteps == 2){

 				XmasSteps = 3
 			}else if(XmasSteps == 3){

 				XmasSteps = 4
 			}else if(XmasSteps == 4){

 				XmasSteps = 5
 			}else if(XmasSteps == 5){

 				XmasSteps = 6
 			}else if(XmasSteps == 6){

 				XmasSteps = 7
 			}else if(XmasSteps == 7){
 				XmasSteps = 8
 			}else if(XmasSteps == 8){

 				XmasSteps = 9
 			}else if(XmasSteps == 9){

 				XmasSteps = 10
 			}else {

 				XmasSteps = 0


rule "Timer Stop" when
     Item LoungeGreenSocket changed from ON to OFF
 	if(XmasTimer !== null){
 		XmasTimer = null



Ooh the jinx option looks quite interesting… I ended up going for the chaser method to get me through for the moment… but thats certainly what I’m about to go and explore now!!

1 Like


I don’t know if the Jinx! route will work so well for moving head fixtures, because of the exact DMX channel values you need.

If you’ve dabbled with MagicQ you’ll have found the option to remotely control that, so I’ll assume that other lighting control systems have remote control options.

If you can get them to respond to an Art-NET or sACN universe, then you should be able to use the same Things & Items in openHAB2 :slight_smile:

Please do let us know how you get on, I’d be very interested.

Good luck,


I will do! Shouldn’t be a massive problem as I’ve been plotting the look on an ETC Gio@5 and grabbing the raw DMX values to feed back in again

I can see why you wouldn’t want to leave a ETC Gio@5 on site just to move some heads around :wink: