Access Keys:
Skip to content (Access Key - 0)
 

DSCit100

Quintin Paulson

On May 19, 2012 22:59

Does anyone have a DSC alarm working with OpenRemote?

I installed openremote, created a simple custom sensor and panel.. but when OpenRemote tries to load the controlled it blows up.
The reason appears to be that id doesn't actually have a dscit100 module loaded or available to be loaded..

Is there a dscit100 module that has to be loaded manually?..

ERROR 2012-05-19 22:43:09,763 : Creating sensor failed. Error : No device protocol builders registered with protocol type 'dscit100'. 
 XML Element : <sensor xmlns="http://www.openremote.org" id="8" name="zone_status" type="custom">
      <include type="command" ref="7" />
      <state name="open" value="" />
      <state name="restored" value="" />
      <state name="fault" value="" />
    </sensor>

 
Labels: , , , ,
Participants: Eric Nelson , Marcus Redeker , Quintin Paulson
  1. May 20, 2012

    Quintin Paulson says:

    Well, there is little to no documentation on this.. but I have been making some ...

    Well, there is little to no documentation on this.. but I have been making some headway.. Thought I'd better post it so that others can figure this out as well..

    I managed to download the dscit100 protocol plugin from here:

    svn checkout "https://openremote.svn.sourceforge.net/svnroot/openremote/workspace/gdrapp/Controller_2_0_0_Alphas_DSCIT100/"
    

    Once I had src, I found a number of interesting things, one important tidbit is the default port its trying to connect on is port 5000..
    Ideally, it seems its best to get your serial->IP bridge listening on that port.

    You can build the jar files with:

    ant compile
    

    Once you have the jars you can copy them into your openremote 2.0 install

    from: dscit100/Controller_2_0_0_Alphas_DSCIT100/src/org/openremote/controller/protocol/dscit100
    to: OpenRemote-Controller-2.0.0/webapps/controller/WEB-INF/classes/org/openremote/controller/protocol/
    

    You then have to update the OpenRemote-Controller-2.0.0/webapps/controller/WEB-INF/classes/applicationContext.xml
    and in the section where you see

    <bean id = "commandFactory" class = "org.openremote.controller.command.CommandFactory">

    add the following:

            <entry key = "dscit100"         value-ref = "dscit100CommandBuilder"/>
    

    and then in the "COMMAND BUILDERS" section further down, add:

            <!-- DSC IT-100 Command Builder -->
            <bean id = "dscit100CommandBuilder" class = "org.openremote.controller.protocol.dscit100.DSCIT100CommandBuilder" />
    

    This will allow you to initialize the module..

    Once I have completed all this, I was able to load the controller.xml and follow the info here: http://www.openremote.org/display/docs/OpenRemote+2.0+How+To+-+DSC+Alarm+Systems

    Hope this helps others.

    1. May 20, 2012

      Quintin Paulson says:

      its all loading successful.. No errors anywhere, but when i try to get the ZONE_...

      its all loading successful.. No errors anywhere, but when i try to get the ZONE_STATUS i keep getting back either a "FAULT" or the app crashes on my phone ( android )..

    2. May 20, 2012

      Quintin Paulson says:

      Has anyone managed to get this working?? I am quite sure its connecting to the ...

      Has anyone managed to get this working?? I am quite sure its connecting to the device and communicating correctly.. Its still not working though.. I can see traffic on the serial device, the Alarm is pushing date/time probes every minute, but openremote is still reporting error/faults..

      There are no exceptions or errors in the logs at all.. Anyone have any ideas.. ?

      Thank you.

      1. May 21, 2012

        Quintin Paulson says:

        Updated the socat command below.. Its able to arm/disarm now.. but the STATE com...

        Updated the socat command below.. Its able to arm/disarm now.. but the STATE commands are still not working.

        1. May 21, 2012

          Quintin Paulson says:

          Its getting data from the socket.. Just seems like its not what its expecting as...

          Its getting data from the socket.. Just seems like its not what its expecting as it kees saying its getting an invalid checksum...

          Here are the logs, just encase someone has any ideas..

          DEBUG [Thread-3]: New packet created [command=002, data=,checksum=92]
          DEBUG [Thread-3]: Sending data to address 192.168.1.110 : 00292
          
          DEBUG [Thread-3]: Received data from 192.168.1.110 : �����������������������������������������50196
          ERROR [Thread-3]: Received packet with invalid checksum [packet=96,calculated=1B]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 0000227
          ERROR [Thread-3]: Received packet with invalid checksum [packet=27,calculated=F2]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : ����Zone    01                      6A
          ERROR [Thread-3]: Received packet with invalid checksum [packet=6A,calculated=44]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570002Zone    02                      6C
          DEBUG [Thread-3]: Broadcast label [number=2,label=Zone    02]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570003Zone    03                      6E
          DEBUG [Thread-3]: Broadcast label [number=3,label=Zone    03]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570004Zone    04                      70
          DEBUG [Thread-3]: Broadcast label [number=4,label=Zone    04]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570005Zone    05                      72
          DEBUG [Thread-3]: Broadcast label [number=5,label=Zone    05]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570006Zone    06                      74
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=Arming, state-3=System Busy, state-2=Armed, state-9=Alarming, state-8=Ready, state-5=Disarmed, state-4=Pending Action, state-7=Not Ready, state-6=Failed}]
          DEBUG [Thread-3]: Broadcast label [number=6,label=Zone    06]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=, state-2=null}]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Reading state for - [STATE:type=ZONE, target=2, address=192.168.1.110]
          WARN [Polling Sensor Thread ID = 60, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570007Zone    07                      76
          WARN [Polling Sensor Thread ID = 59, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: [state=NULL]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: [state=NULL]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Reading state for - [STATE:type=ZONE, target=1, address=192.168.1.110]
          DEBUG [Thread-3]: Broadcast label [number=7,label=Zone    07]
          WARN [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Cannot find state type information for [StateDefinition: type=ZONE, target=2]
          WARN [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Cannot find state type information for [StateDefinition: type=ZONE, target=1]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: [state=NULL]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : M���Zone    08                      78
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: [state=NULL]
          ERROR [Thread-3]: Received packet with invalid checksum [packet=78,calculated=9B]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570009Zone    09                      7A
          DEBUG [Thread-3]: Broadcast label [number=9,label=Zone    09]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570010Zone    10                      6A
          DEBUG [Thread-3]: Broadcast label [number=10,label=Zone    10]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570011Zone    11                      6C
          DEBUG [Thread-3]: Broadcast label [number=11,label=Zone    11]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 5���Zone    12                      6E
          ERROR [Thread-3]: Received packet with invalid checksum [packet=6E,calculated=7E]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : M���Zone    13                      70
          ERROR [Thread-3]: Received packet with invalid checksum [packet=70,calculated=97]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570014Zone    14                      72
          DEBUG [Thread-3]: Broadcast label [number=14,label=Zone    14]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570015Zone    15                      74
          DEBUG [Thread-3]: Broadcast label [number=15,label=Zone    15]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=, state-2=null}]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=Arming, state-3=System Busy, state-2=Armed, state-9=Alarming, state-8=Ready, state-5=Disarmed, state-4=Pending Action, state-7=Not Ready, state-6=Failed}]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 5���Zone    16                      76
          WARN [Polling Sensor Thread ID = 60, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          ERROR [Thread-3]: Received packet with invalid checksum [packet=76,calculated=82]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Reading state for - [STATE:type=ZONE, target=1, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Reading state for - [STATE:type=ZONE, target=2, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 5���Zone    17                      78
          WARN [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Cannot find state type information for [StateDefinition: type=ZONE, target=1]
          ERROR [Thread-3]: Received packet with invalid checksum [packet=78,calculated=83]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: [state=NULL]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: [state=NULL]
          WARN [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Cannot find state type information for [StateDefinition: type=ZONE, target=2]
          WARN [Polling Sensor Thread ID = 59, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: [state=NULL]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 5���Zone    18                      7A
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: [state=NULL]
          ERROR [Thread-3]: Received packet with invalid checksum [packet=7A,calculated=84]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570019Zone    19                      7C
          DEBUG [Thread-3]: Broadcast label [number=19,label=Zone    19]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570020Zone    20                      6C
          DEBUG [Thread-3]: Broadcast label [number=20,label=Zone    20]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570021Zone    21                      6E
          DEBUG [Thread-3]: Broadcast label [number=21,label=Zone    21]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570022Zone    22                      70
          DEBUG [Thread-3]: Broadcast label [number=22,label=Zone    22]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570023Zone    23                      72
          DEBUG [Thread-3]: Broadcast label [number=23,label=Zone    23]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570024Zone    24                      74
          DEBUG [Thread-3]: Broadcast label [number=24,label=Zone    24]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=, state-2=null}]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570025Zone    25                      76
          WARN [Polling Sensor Thread ID = 60, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Reading state for - [STATE:type=ZONE, target=1, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: [state=NULL]
          WARN [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Cannot find state type information for [StateDefinition: type=ZONE, target=1]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=Arming, state-3=System Busy, state-2=Armed, state-9=Alarming, state-8=Ready, state-5=Disarmed, state-4=Pending Action, state-7=Not Ready, state-6=Failed}]
          DEBUG [Thread-3]: Broadcast label [number=25,label=Zone    25]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : ����Zone    26                      78
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          ERROR [Thread-3]: Received packet with invalid checksum [packet=78,calculated=4B]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: [state=NULL]
          WARN [Polling Sensor Thread ID = 59, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Reading state for - [STATE:type=ZONE, target=2, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: [state=NULL]
          WARN [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Cannot find state type information for [StateDefinition: type=ZONE, target=2]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : M���Zone    27                      7A
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: [state=NULL]
          ERROR [Thread-3]: Received packet with invalid checksum [packet=7A,calculated=9C]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570028Zone    28                      7C
          DEBUG [Thread-3]: Broadcast label [number=28,label=Zone    28]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570029Zone    29                      7E
          DEBUG [Thread-3]: Broadcast label [number=29,label=Zone    29]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570030Zone    30                      6E
          DEBUG [Thread-3]: Broadcast label [number=30,label=Zone    30]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570031Zone    31                      70
          DEBUG [Thread-3]: Broadcast label [number=31,label=Zone    31]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570032Zone    32                      72
          DEBUG [Thread-3]: Broadcast label [number=32,label=Zone    32]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570033Zone    33                      74
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=, state-2=null}]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          DEBUG [Thread-3]: Broadcast label [number=33,label=Zone    33]
          WARN [Polling Sensor Thread ID = 60, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: [state=NULL]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 5���Zone    34                      76
          ERROR [Thread-3]: Received packet with invalid checksum [packet=76,calculated=82]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570035Zone    35                      78
          DEBUG [Thread-3]: Broadcast label [number=35,label=Zone    35]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Reading state for - [STATE:type=ZONE, target=1, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=Arming, state-3=System Busy, state-2=Armed, state-9=Alarming, state-8=Ready, state-5=Disarmed, state-4=Pending Action, state-7=Not Ready, state-6=Failed}]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Sensor read request [type=custom, stateMap={state-1=}]
          WARN [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Cannot find state type information for [StateDefinition: type=ZONE, target=1]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: [state=NULL]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570036Zone    36                      7A
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Reading state for - [STATE:type=ZONE, target=2, address=192.168.1.110]
          DEBUG [Thread-3]: Broadcast label [number=36,label=Zone    36]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          WARN [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Cannot find state type information for [StateDefinition: type=ZONE, target=2]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: [state=NULL]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570037Zone    37                      7C
          WARN [Polling Sensor Thread ID = 59, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: [state=NULL]
          DEBUG [Thread-3]: Broadcast label [number=37,label=Zone    37]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570038Zone    38                      7E
          DEBUG [Thread-3]: Broadcast label [number=38,label=Zone    38]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 5���Zone    39                      80
          ERROR [Thread-3]: Received packet with invalid checksum [packet=80,calculated=87]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570040Zone    40                      70
          DEBUG [Thread-3]: Broadcast label [number=40,label=Zone    40]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570041Zone    41                      72
          DEBUG [Thread-3]: Broadcast label [number=41,label=Zone    41]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=, state-2=null}]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          WARN [Polling Sensor Thread ID = 60, Name ='partition_status']: Cannot find state type information for [StateDefinition: type=PARTITION, target=1]
          DEBUG [Polling Sensor Thread ID = 60, Name ='partition_status']: [state=NULL]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570042Zone    42                      74
          DEBUG [Thread-3]: Broadcast label [number=42,label=Zone    42]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570043Zone    43                      76
          DEBUG [Thread-3]: Broadcast label [number=43,label=Zone    43]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 90100032  Date     Time MAY 20/12  9:50p1F
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Reading state for - [STATE:type=ZONE, target=1, address=192.168.1.110]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570044Zone    44                      78
          DEBUG [Thread-3]: Broadcast label [number=44,label=Zone    44]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Sensor read request [type=custom, stateMap={state-1=}]
          DEBUG [Polling Sensor Thread ID = 61, Name ='zone_status_2']: Reading state for - [STATE:type=ZONE, target=2, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Sensor read request [type=custom, stateMap={state-1=Arming, state-3=System Busy, state-2=Armed, state-9=Alarming, state-8=Ready, state-5=Disarmed, state-4=Pending Action, state-7=Not Ready, state-6=Failed}]
          DEBUG [Thread-3]: Received data from 192.168.1.110 : 570045Zone    45                      7A
          WARN [Polling Sensor Thread ID = 62, Name ='zone_status_1']: Cannot find state type information for [StateDefinition: type=ZONE, target=1]
          DEBUG [Polling Sensor Thread ID = 59, Name ='partition_status']: Reading state for - [STATE:type=PARTITION, target=1, address=192.168.1.110]
          DEBUG [Polling Sensor Thread ID = 62, Name ='zone_status_1']: [state=NULL]
          
          
          1. May 21, 2012

            Marcus Redeker says:

            I am not familiar with this protocol but you can find the code where the checksu...
            1. May 21, 2012

              Quintin Paulson says:

              Thanks for the info Marcus.. I looked at the src already.. I expect that its cor...

              Thanks for the info Marcus.. I looked at the src already.. I expect that its correct..
              I will play now with the different baud rates, though its supposed to be 9600 by default and I have been setting it to 9600, which should be the most stable..

    3. Nov 11, 2012

      Eric Nelson says:

      Actually, in the steps above, you need to copy the folder and .class files from ...

      Actually, in the steps above, you need to copy the folder and .class files from

      /Controller_2_0_0_Alphas_DSCIT100/build/classes/org/openremote/controller/protocol/dscit100

      into

      OpenRemote-Controller-2.0.0/webapps/controller/WEB-INF/classes/org/openremote/controller/protocol/

  2. May 21, 2012

    Quintin Paulson says:

    FYI also, if you have your serial device plugged into the same box running openr...

    FYI also, if you have your serial device plugged into the same box running openremote, like i do..
    you can run socat to allow openremote to connect to the serialdevice over TCP/IP.

    Like this:

    socat tcp-l:5000,reuseaddr,fork,crlf file:/dev/ttyUSB0,echo=0,b9600,raw,crnl,icanon=1
    

    You can test the serial connection by sending commands directly to it with

    socat READLINE /dev/ttyUSB0,raw,echo=0,crnl,b9600
    

    type in "00191" and hit enter.. You should get back a dump of information..

    Happy hacking.

    1. Nov 07, 2012

      Eric Nelson says:

      Hey Quintin, I have a raspberry pi and have my dsc-it100 connected to it via a U...

      Hey Quintin, I have a raspberry pi and have my dsc-it100 connected to it via a USB to serial interface cable. I'm able to communicate with the it-100 over that. Will the socat commands above allow me to still use OpenRemote with my current configuration?
      I've tried the commands above, but I get an E unknown device/address "READLINE". I was able to replace READLINE with STDIO and was able to input from the command line to test the dsc-it100 interface.

      Any tips?

Adaptavist Theme Builder Powered by Atlassian Confluence