Announcement

Collapse
No announcement yet.

Rain8Net Pro with Sena LS100 com/ip redirect

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Rain8Net Pro with Sena LS100 com/ip redirect

    Could someone help me connect the rain8net pro with the sena ls100, both of them bought from Homeseer.

    The rain8net works fine when connected directly to com port.

    I have not yet been able to get it functional connected to the Sena LS100 Com/IP redirect device

    Could you comment on the following parameters which I have to set in the Sena LS100 redirect device?

    Mode of communication

    Should device be set as a TCP Server a TCP Client or a TCP Server/Client?
    Currently it is set as a TCP Server/Client with the following parameters

    listening_port = listening TCP port = 6001
    dest_ip = destination IP address = 192.168.1.105
    dest_port = destination TCP port = 7001
    cyclic_connection_interval = cyclic connection interval in minutes = 10
    inactivity_timeout = inactivity timeout in seconds = 300

    Serial Port Configuration.

    baudrate: 1200, 2400, 4800, 9600, 19200, 38400, 57600, or 115200 = currently set to 4800

    data_bits: 7=7-bits / 8=8-bits = currently set to 8

    parity: n=none / e=even / o=odd = currently set to none

    stop_bits: 1=1-bit / 2=2-bits = currently set to 1

    flow_control: n=none / h=hardware = currently set to none

    dtr_option: h=always high / l=always low / s=show tcp connection = currently set to show tcp connection

    dsr_option: n=none / a=accept only by high / o=open,close TCP connection = currently set to none

    interchar_timeout: inter-character timeout value in milliseconds = currently set to 10

    Are there any other parameters that I should pay special attention to??

    Thanks

  • #2
    I suspect that not too many that could help have purchased the HS Sena product as there are aftermarket products at attractive prices such as Lantronix and Quatech that have been discussed quite a bit on the board. The support model for HST products is through their subscription service or perhaps Rupp if he happens to have experience with the product.

    In general your settings look reasonable. I suspect you will be running this as a server rather than a client. Since you are using the COM emulation driver your configuration will need to be whatever it is expecting. This driver may or may not support serial configuration via IP, but the configuration you have looks to be correct for the Rain8Net.

    Comment


    • #3
      configuration shots of ls100

      Thanks. Please see attached configuration screens. I bought the ls100 from homeseer thinking they could help me get it working with homeseer.
      Attached Files

      Comment


      • #4
        what com/ip device is known to work with rain8net?

        what com/ip device is known to work with rain8net?

        and what r the settings?

        Comment


        • #5
          Here is a recent thread that describes the Lantronix and Quatech products. http://board.homeseer.com/showthread.php?t=136420 I have setup with both of these. Comtrol Device Master is also a common interface. I have heard that setting it up in Raw mode is difficult, but use of the COM emulation is easier.

          The unit you have should work as well, but just no experience from user on this board. Your best avenue to to go directly to HST for support for their hardware.

          Comment


          • #6
            Trace of com/ip traffic during failed rain8net load

            Would u b so kind and look at this trace of com/ip traffic during failed rain8net load



            Thanks

            Here is the log file.

            18:57:37.948 COM10 : | Open
            18:57:37.948 COM10 : | Driver: SISerial 4.8.4
            18:57:37.948 COM10 : | Current UART Settings:
            18:57:37.948 COM10 : | Baud: 00004800
            18:57:37.948 COM10 : | Framing: 08,N,1
            18:57:37.948 COM10 : | DTR: 0 RTS: 1 CTS: 1 DSR: 1 CD: 0
            18:57:37.949 COM10 : | Port open
            18:57:37.949 COM10 : | CTS: 1 DSR: 1
            18:57:37.949 COM10 : | CTS: 1 DSR: 1 CD: 0
            18:57:37.949 COM10 : | Enable Nagle
            18:57:37.949 COM10 : | Disable Telnet
            18:57:37.949 COM10 : | Disable Telnet CR-padding
            18:57:37.949 COM10 : | Disable DTR emulation (Unimodem)
            18:57:37.949 COM10 : | Enable autoreconnect
            18:57:37.950 COM10 : | Disable User Authentication
            18:57:37.950 COM10 : | Connecting to server 192.168.1.105[6001]
            18:57:37.950 COM10 : | Proxy disabled; running in pass-through mode
            18:57:37.950 COM10 : | Trying 192.168.1.105...
            18:57:37.950 COM10 : | FlushTX
            18:57:37.950 COM10 : | FlushRX
            18:57:37.950 COM10 : | RTS: 1
            18:57:37.950 COM10 : | DTR: 1
            18:57:37.950 COM10 : | RTS: 1
            18:57:37.950 COM10 : | DTR: 1
            18:57:37.950 COM10 : | RTS: 1
            18:57:37.968 COM10 : | Connected to 192.168.1.105:6001



            18:57:38.960 COM10 : | FlushRX

            18:57:39.181 COM10 : | DTR: 0
            18:57:39.181 COM10 : | FlushTX
            18:57:39.181 COM10 : | FlushRX
            18:57:39.181 COM10 : | Close
            18:57:41.675 COM10 : | Open
            18:57:41.675 COM10 : | Driver: SISerial 4.8.4
            18:57:41.675 COM10 : | Current UART Settings:
            18:57:41.675 COM10 : | Baud: 00004800
            18:57:41.675 COM10 : | Framing: 08,N,1
            18:57:41.675 COM10 : | DTR: 0 RTS: 1 CTS: 1 DSR: 1 CD: 0
            18:57:41.676 COM10 : | FlushTX
            18:57:41.676 COM10 : | FlushRX
            18:57:41.676 COM10 : | RTS: 1
            18:57:41.676 COM10 : | DTR: 1



            18:57:42.687 COM10 : | FlushRX

            18:57:42.884 COM10 : | DTR: 0
            18:57:42.884 COM10 : | FlushTX
            18:57:42.884 COM10 : | FlushRX
            18:57:42.884 COM10 : | Close
            18:57:50.883 COM10 : | Port close
            18:58:07.482 COM10 : | Open
            18:58:07.482 COM10 : | Driver: SISerial 4.8.4
            18:58:07.482 COM10 : | Current UART Settings:
            18:58:07.482 COM10 : | Baud: 00004800
            18:58:07.482 COM10 : | Framing: 08,N,1
            18:58:07.482 COM10 : | DTR: 0 RTS: 1 CTS: 1 DSR: 1 CD: 0
            18:58:07.482 COM10 : | Port open
            18:58:07.482 COM10 : | CTS: 1 DSR: 1
            18:58:07.483 COM10 : | CTS: 1 DSR: 1 CD: 0
            18:58:07.483 COM10 : | Enable Nagle
            18:58:07.483 COM10 : | Disable Telnet
            18:58:07.483 COM10 : | Disable Telnet CR-padding
            18:58:07.483 COM10 : | Disable DTR emulation (Unimodem)
            18:58:07.483 COM10 : | Enable autoreconnect
            18:58:07.483 COM10 : | Disable User Authentication
            18:58:07.483 COM10 : | Connecting to server 192.168.1.105[6001]
            18:58:07.483 COM10 : | Proxy disabled; running in pass-through mode
            18:58:07.483 COM10 : | Trying 192.168.1.105...
            18:58:07.483 COM10 : | FlushTX
            18:58:07.483 COM10 : | FlushRX
            18:58:07.484 COM10 : | RTS: 1
            18:58:07.484 COM10 : | DTR: 1
            18:58:07.484 COM10 : | RTS: 1
            18:58:07.484 COM10 : | DTR: 1
            18:58:07.484 COM10 : | RTS: 1
            18:58:07.503 COM10 : | Connected to 192.168.1.105:6001



            18:58:08.488 COM10 : | FlushRX

            18:58:09.005 COM10 : | DTR: 0
            18:58:09.005 COM10 : | FlushTX
            18:58:09.005 COM10 : | FlushRX
            18:58:09.005 COM10 : | Close
            18:58:17.010 COM10 : | Port close
            18:58:17.905 COM10 : | Open
            18:58:17.905 COM10 : | Driver: SISerial 4.8.4
            18:58:17.905 COM10 : | Current UART Settings:
            18:58:17.905 COM10 : | Baud: 00004800
            18:58:17.905 COM10 : | Framing: 08,N,1
            18:58:17.905 COM10 : | DTR: 0 RTS: 1 CTS: 1 DSR: 1 CD: 0
            18:58:17.905 COM10 : | Port open
            18:58:17.905 COM10 : | CTS: 1 DSR: 1
            18:58:17.906 COM10 : | CTS: 1 DSR: 1 CD: 0
            18:58:17.906 COM10 : | Enable Nagle
            18:58:17.906 COM10 : | Disable Telnet
            18:58:17.906 COM10 : | Disable Telnet CR-padding
            18:58:17.906 COM10 : | Disable DTR emulation (Unimodem)
            18:58:17.906 COM10 : | Enable autoreconnect
            18:58:17.907 COM10 : | Disable User Authentication
            18:58:17.907 COM10 : | Connecting to server 192.168.1.105[6001]
            18:58:17.907 COM10 : | Proxy disabled; running in pass-through mode
            18:58:17.907 COM10 : | Trying 192.168.1.105...
            18:58:17.907 COM10 : | FlushTX
            18:58:17.907 COM10 : | FlushRX
            18:58:17.907 COM10 : | RTS: 1
            18:58:17.907 COM10 : | DTR: 1
            18:58:17.925 COM10 : | Connected to 192.168.1.105:6001



            18:58:18.909 COM10 : | FlushRX

            18:58:22.346 COM10 : | DTR: 0
            18:58:22.346 COM10 : | FlushTX
            18:58:22.346 COM10 : | FlushRX
            18:58:22.346 COM10 : | Close
            18:58:30.347 COM10 : | Port close
            19:08:57.891 COM10 : | Open
            19:08:57.891 COM10 : | Driver: SISerial 4.8.4
            19:08:57.891 COM10 : | Current UART Settings:
            19:08:57.891 COM10 : | Baud: 00004800
            19:08:57.891 COM10 : | Framing: 08,N,1
            19:08:57.891 COM10 : | DTR: 0 RTS: 1 CTS: 1 DSR: 1 CD: 0
            19:08:57.891 COM10 : | Port open
            19:08:57.891 COM10 : | CTS: 1 DSR: 1
            19:08:57.892 COM10 : | CTS: 1 DSR: 1 CD: 0
            19:08:57.892 COM10 : | Enable Nagle
            19:08:57.892 COM10 : | Disable Telnet
            19:08:57.892 COM10 : | Disable Telnet CR-padding
            19:08:57.892 COM10 : | Disable DTR emulation (Unimodem)
            19:08:57.892 COM10 : | Enable autoreconnect
            19:08:57.892 COM10 : | Disable User Authentication
            19:08:57.892 COM10 : | Connecting to server 192.168.1.105[6001]
            19:08:57.892 COM10 : | Proxy disabled; running in pass-through mode
            19:08:57.892 COM10 : | Trying 192.168.1.105...
            19:08:57.892 COM10 : | FlushTX
            19:08:57.892 COM10 : | FlushRX
            19:08:57.893 COM10 : | RTS: 0
            19:08:57.893 COM10 : | DTR: 1
            19:08:57.893 COM10 : | RTS: 1
            19:08:57.893 COM10 : | DTR: 1
            19:08:57.893 COM10 : | RTS: 1
            19:08:57.942 COM10 : | Connected to 192.168.1.105:6001



            19:08:58.897 COM10 : | FlushRX

            19:08:59.125 COM10 : | DTR: 0
            19:08:59.125 COM10 : | FlushTX
            19:08:59.125 COM10 : | FlushRX
            19:08:59.125 COM10 : | Close
            19:09:03.910 COM10 : | Open
            19:09:03.910 COM10 : | Driver: SISerial 4.8.4
            19:09:03.910 COM10 : | Current UART Settings:
            19:09:03.910 COM10 : | Baud: 00004800
            19:09:03.910 COM10 : | Framing: 08,N,1
            19:09:03.910 COM10 : | DTR: 0 RTS: 1 CTS: 1 DSR: 1 CD: 0
            19:09:03.910 COM10 : | FlushTX
            19:09:03.910 COM10 : | FlushRX
            19:09:03.910 COM10 : | RTS: 1
            19:09:03.910 COM10 : | DTR: 1



            19:09:04.919 COM10 : | FlushRX

            19:09:05.117 COM10 : | DTR: 0
            19:09:05.117 COM10 : | FlushTX
            19:09:05.117 COM10 : | FlushRX
            19:09:05.117 COM10 : | Close
            19:09:13.120 COM10 : | Port close
            19:09:36.963 COM10 : | Open
            19:09:36.963 COM10 : | Driver: SISerial 4.8.4
            19:09:36.963 COM10 : | Current UART Settings:
            19:09:36.963 COM10 : | Baud: 00004800
            19:09:36.963 COM10 : | Framing: 08,N,1
            19:09:36.963 COM10 : | DTR: 0 RTS: 1 CTS: 1 DSR: 1 CD: 0
            19:09:36.963 COM10 : | Port open
            19:09:36.963 COM10 : | CTS: 1 DSR: 1
            19:09:36.964 COM10 : | CTS: 1 DSR: 1 CD: 0
            19:09:36.964 COM10 : | Enable Nagle
            19:09:36.964 COM10 : | Disable Telnet
            19:09:36.964 COM10 : | Disable Telnet CR-padding
            19:09:36.964 COM10 : | Disable DTR emulation (Unimodem)
            19:09:36.964 COM10 : | Enable autoreconnect
            19:09:36.965 COM10 : | Disable User Authentication
            19:09:36.965 COM10 : | Connecting to server 192.168.1.105[6001]
            19:09:36.965 COM10 : | Proxy disabled; running in pass-through mode
            19:09:36.965 COM10 : | Trying 192.168.1.105...
            19:09:36.965 COM10 : | FlushTX
            19:09:36.965 COM10 : | FlushRX
            19:09:36.965 COM10 : | RTS: 1
            19:09:36.965 COM10 : | DTR: 1
            19:09:36.984 COM10 : | Connected to 192.168.1.105:6001



            19:09:37.973 COM10 : | FlushRX


            19:09:38.678 COM10 : | FlushRX

            Comment


            • #7
              In the thread I referenced it was disclosed that that the Rain8Net Pro does not work with the Lantronix EPS devices likely due to the TTL voltage levels used by the EPS. Same thing may be happening with your Sena unit. I looked at the HS store for the Sena and see in red type that they claim it only works for the Zwave interface and has not been tested with any other product. We know the Quatech works with the Rain8Net Pro. The Lantronix and Quatech and DeviceMaster are known to work with the Rain8Net.

              Comment


              • #8
                what lantronix or quatech device/model?

                could you tell me exactly what brand and model number to order from lantronix and/or quatech to work with rain8net pro? Thx

                Comment


                • #9
                  Look at the thread that I referenced earlier. It contains the links to the Quatech units that have been purchased by several. We know from that link that the Lantronix units will not work with the Rain8Net Pro. You should measure the voltage outputs of your unit to confirm that it is a voltage compatibility issue vs. something else.

                  Comment


                  • #10
                    voltage levels and quatech

                    I'm sorry but I don'tunderstand the words "TTL voltage levels used by the EPS". Where, what pins, do I measure the voltage and what relationship am I looking for on the com server and the rain8net?

                    I don't see a current quatech model in the thread. At the quatech web site below for serial servers, I find the following models. Which one do you recommend?

                    DSE-100D 2 port RS-232 Serial Device Server (DB9) $300.00

                    DSE-100D-5V 2 port RS-232 Port-Powered Serial Device Server with surge suppression and +5V at Pin 9 $350.00


                    http://www.quatech.com/catalog/rs232_sds.php

                    Comment


                    • #11
                      opps

                      I meant models

                      SSE-100D 1 port RS-232 Serial Device Server (DB9) $250.00

                      SSE-100D-5V 1 port RS-232 Port-Powered Serial Device Server with surge suppression and +5V at pin 9 $275.00

                      http://www.quatech.com/catalog/rs232_sds.php

                      Comment


                      • #12
                        You asked for models that were known to work. The only one that has been tested with the Rain8net Pro that was discussed on this board is the Quatech QSE-100D. It is likely that other models from this manufacturer that have similiar electrical specifications will work as well, but that has not been proven. There are more users of the Rain8net and there have been more IP/RS232 interfaces that have been shown to work with this unit. The Rain8net was actually redesigned to work with the Lantronix EPS that has a 0 to 3.5 volt drive voltage. TManufacturing.com was selling the DeviceMaster/Rain8net bundle. He included a nice step by step manual on how to set it up. I do not know if JR ever went to the Rain8net Pro. I suspect not because of the price point he was selling at. I also think he is getting out of the business because of the support issues as many customers did not have the expertise on working with a LAN.

                        There is also a product that has just been introduced on the message board called EtherRain which the manufacturer has provided a Homeseer interface. With it you have a LAN connection without an IP/RS232 adapter. If all you are looking for is a simple scheduling mechanism then this may be attractive. If you go this way then you will be a very early adopter and need to expect to be in a development/debug mode.

                        I again suggest that you work with HST to get the product you bought from them working to your satisfaction.

                        Comment


                        • #13
                          EtherRain clarification...

                          Hi Micheal,

                          Thanks for mentioning the EtherRain controller in your forum. As the manufacturer, I would like to clarify your statements, if allowed:

                          >>If all you are looking for is a simple scheduling mechanism then this may be attractive.

                          The new interface supplied July 31 provides more capabilities than the original. With it you can easily setup more than just a simple schedule. For example, you can set up a cycle with monthly setbacks, for water savings, plus you'll have access to two-click manual cycles, and one click disable with auto restart. In addition, because standard homeseer 2 events are used, unlimited control possibilities exist when used with weather sensors for example, and multiple cycles can be supported.

                          No doubt it would be possible to extend the current interface further, for example, to include integrated weather, reports, etc. Because the interface is openly available it would be easy for a HomeSeer developer to make these extensions, should a need arise.

                          >>If you go this way then you will be a very early adopter and need to expect to be in a development/debug mode.

                          The EtherRain controller has been on the market for 2 years (in use with different schedulers) and is currently in use throughout the US and Canada. The HomeSeer interface is new, however, it has been tested already and is being used by two experienced HomeSeer users. Most likely you will not find many posts about "issues" because the interface is very easy to setup and understand. In addition, because it uses the system drivers for access to the Ethernet connection, you most likely won't find any issues with connectivity or any hardware issues. My point is that the debug cycle for EtherRain and for the the interface has been completed.

                          Again, thank you for your mention.

                          Jim

                          Comment


                          • #14
                            Originally posted by Michael McSharry View Post
                            You asked for models that were known to work. The only one that has been tested with the Rain8net Pro that was discussed on this board is the Quatech QSE-100D. It is likely that other models from this manufacturer that have similiar electrical specifications will work as well, but that has not been proven. There are more users of the Rain8net and there have been more IP/RS232 interfaces that have been shown to work with this unit. The Rain8net was actually redesigned to work with the Lantronix EPS that has a 0 to 3.5 volt drive voltage. TManufacturing.com was selling the DeviceMaster/Rain8net bundle. He included a nice step by step manual on how to set it up. I do not know if JR ever went to the Rain8net Pro. I suspect not because of the price point he was selling at. I also think he is getting out of the business because of the support issues as many customers did not have the expertise on working with a LAN.

                            There is also a product that has just been introduced on the message board called EtherRain which the manufacturer has provided a Homeseer interface. With it you have a LAN connection without an IP/RS232 adapter. If all you are looking for is a simple scheduling mechanism then this may be attractive. If you go this way then you will be a very early adopter and need to expect to be in a development/debug mode.

                            I again suggest that you work with HST to get the product you bought from them working to your satisfaction.
                            Thanks, Jim. I gave up on the Sena after about 10 emails with their tech support, they simply could not get it to work. I bought the Quatech serial/ip and now everything is working great! Rick

                            Comment


                            • #15
                              Originally posted by Ricky View Post
                              Thanks, Jim. I gave up on the Sena after about 10 emails with their tech support, they simply could not get it to work. I bought the Quatech serial/ip and now everything is working great! Rick
                              Ricky - what model Quatech did you buy?

                              Comment

                              Working...
                              X