Jump to content

InteractiveTechnologies CueServer-Pro-CS-800: Difference between revisions

From LinuxMCE
Zaerc (talk | contribs)
m Cueserver dmx lighting moved to InteractiveTechnologies CueServer-Pro-CS-800: proper naming
mNo edit summary
Line 4: Line 4:
Its very basic at the moment however it is working using the serial port I have followed the guide in the wiki "Implementing Clipsal Interface using Generic Serial Device"also adding in device data #76 COM Port ParityBit/Stop(string) #78 COM Port BaudRate(string)
Its very basic at the moment however it is working using the serial port I have followed the guide in the wiki "Implementing Clipsal Interface using Generic Serial Device"also adding in device data #76 COM Port ParityBit/Stop(string) #78 COM Port BaudRate(string)


in the RUBY CODE under "Ruby Internal Commands"-"#384 Process Receive Command For Child "add  
in the RUBY CODE under "Ruby Internal Commands"-"#384 Process Receive Command For Child "add  


id=device_.childdevices_[cmd.devidto_].devdata_[12]#get child device number
id=device_.childdevices_[cmd.devidto_].devdata_[12]#get child device number
if cmd.id_==192 #192 is on
  conn_.Send("[c"+id+"atfl]\r") #set id to full
end
if cmd.id_==193 #193 is off
  conn_.Send("[c"+id+"rel]\r") #relase id to zero
end
if cmd.id_==184 #184 dimmer
  conn_.Send("[c"+id+"at50]\r") #set id to 50% it should step the light up or down this is not working at present
end


if cmd.id_==192 #192 is on
== Things To Do ==
 
* get #184 the dimmer command to work correctly
conn_.Send("[c"+id+"atfl]\r") #set id to full
* add log/messages to keep lmce up to date
 
* intergrate the 8 contact closures on the cueserver this could work as alarm interface
end
* get it to work over the ethernet write a driver in c++
 
if cmd.id_==193 #193 is off
 
conn_.Send("[c"+id+"rel]\r") #relase id to zero
 
end
 
if cmd.id_==184 #184 dimmer
 
conn_.Send("[c"+id+"at50]\r") #set id to 50% it should step the light up or down this is not working at present
 
end
 
 
THINGS TO DO
 
-get #184 the dimmer command to work correctly
 
-add log/messages to keep lmce up to date
 
-intergrate the 8 contact closures on the cueserver this could work as alarm interface
 
-get it to work over the ethernet write a driver in c++

Revision as of 13:18, 23 October 2011

This is a template for a DMX lighting controller by Interactive technologies - model Cueserver pro800 http://www.interactive-online.com/products/cueserver/overview Its very basic at the moment however it is working using the serial port I have followed the guide in the wiki "Implementing Clipsal Interface using Generic Serial Device"also adding in device data #76 COM Port ParityBit/Stop(string) #78 COM Port BaudRate(string)

in the RUBY CODE under "Ruby Internal Commands"-"#384 Process Receive Command For Child "add

id=device_.childdevices_[cmd.devidto_].devdata_[12]#get child device number
if cmd.id_==192 #192 is on
  conn_.Send("[c"+id+"atfl]\r") #set id to full
end
if cmd.id_==193 #193 is off
  conn_.Send("[c"+id+"rel]\r") #relase id to zero
end
if cmd.id_==184 #184 dimmer
  conn_.Send("[c"+id+"at50]\r") #set id to 50% it should step the light up or down this is not working at present
end

Things To Do

  • get #184 the dimmer command to work correctly
  • add log/messages to keep lmce up to date
  • intergrate the 8 contact closures on the cueserver this could work as alarm interface
  • get it to work over the ethernet write a driver in c++