Announcement

Collapse
No announcement yet.

Feature Requests

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Feature Requests

    Please post your feature requests here.

    Thanks
    NicolaiL
    Nicolai L

  • #2
    Would it be possible to use this plugin via a global cache serial port?

    Comment


    • #3
      Yes, you can use the plug-in with virtual com ports such as the Global Cache serial port.

      In fact, although I haven't got round to documenting this, nor creating the relevant setup on the config page, you can even communicate directly with the Global Cache directly via IP.

      Edit the izDuskySky.ini file by hand and include the below and then restart the plug-in:

      Code:
      [SETTINGS]
      Debug=0
      Console Debug=0
      IPAddress=192.168.x.x
      TCP Port=4999
      Use COM Port=FALSE
      The IPAddress should be set to the IP address of your Global Cache device.
      Nicolai L

      Comment


      • #4
        Following your suggestion to connect directly to the GC via IP - i edited the izDuskySky.ini file using Port 5000 to try to connect to the 2nd serial port, however it doesn't want to make a connection.
        Baud rate is set at 57600
        I can get the full connection working to the duskySky box if i use drhsIpPlugIn so i know its working ,however i would like to get it working via your plugin for ease of use.
        Any ideas?

        Comment


        • #5
          Originally posted by waszaa View Post
          Following your suggestion to connect directly to the GC via IP - i edited the izDuskySky.ini file using Port 5000 to try to connect to the 2nd serial port, however it doesn't want to make a connection.
          Baud rate is set at 57600
          I can get the full connection working to the duskySky box if i use drhsIpPlugIn so i know its working ,however i would like to get it working via your plugin for ease of use.
          Any ideas?
          Sorry, was away on holiday. Can you try and set the debug level to 5 and capture a log file to see if you can see any errors in the log that would point ot the issue?
          Nicolai L

          Comment


          • #6
            Here is the log its not able to connect to the port!

            Jun-01 1:39:11 PM izDuskySky ERROR Can't connect to TCP Port
            Jun-01 1:39:11 PM izDuskySky ERROR Can't connect to TCP Port
            Jun-01 1:38:50 PM izDuskySky DEBUG Connecting to TCP port
            Jun-01 1:38:50 PM izDuskySky TCP port successfully closed.
            Jun-01 1:38:50 PM izDuskySky TCP port successfully closed.
            Jun-01 1:38:50 PM izDuskySky DEBUG Shutting Down TCP Port ...
            Jun-01 1:38:50 PM izDuskySky ERROR TCP port dicconnected. Attempting to reconnect ...
            Jun-01 1:38:50 PM izDuskySky ERROR TCP port dicconnected. Attempting to reconnect ...
            Jun-01 1:38:50 PM izDuskySky DEBUG Running timer event ...
            Jun-01 1:37:50 PM Plug-In Finished initializing plug-in izDuskySky
            Jun-01 1:37:50 PM izDuskySky Initialised, up and running ...
            Jun-01 1:37:50 PM izDuskySky Initialised, up and running ...
            Jun-01 1:37:50 PM izDuskySky ERROR Can't connect to TCP Port
            Jun-01 1:37:50 PM izDuskySky ERROR Can't connect to TCP Port
            Jun-01 1:37:29 PM izDuskySky DEBUG Connecting to TCP port
            Jun-01 1:37:29 PM izDuskySky DEBUG Device: izDuskySky-ROOT already exists. No need to create devices
            Jun-01 1:37:29 PM izDuskySky DEBUG Plug-In Version: 3.0.1.1
            Jun-01 1:37:29 PM izDuskySky DEBUG In izStd.IniPlugIn
            Jun-01 1:37:29 PM izDuskySky DEBUG In izInit...
            Jun-01 1:37:29 PM Info Plugin izDuskySky has connected. IP:127.0.0.1:61204
            Jun-01 1:37:28 PM Plug-In Interface izDuskySky is running as a trial, 20 days remaining.

            Config -[SETTINGS]
            Debug=5
            Console Debug=5
            IPAddress=10.0.1.199
            TCP Port=5000
            Use COM Port=FALSE
            [COM]
            Speed=9600

            Comment


            • #7
              Attached screenshot of HS3 devices created!
              Attached Files

              Comment


              • #8
                Well the error message is suggesting that PI can not connect to that port. I am assuming you are using a valid port number as you have it working with drhsIpPlugIn.

                When you try this have you shut down drhsIpPlugIn? I am wondering if they are both trying to communicate on the same port and drhsIpPlugIn opens the port before my PI tries?
                Nicolai L

                Comment


                • #9
                  I have put 3.0.1.2 in the updater. This version has a bit more debugging information. If you don't find anything else already using port 5000 (as suggested above) then please try this version and post the debug info here.
                  Nicolai L

                  Comment


                  • #10
                    Seems from the Log and not sure why its trying to connect to port 4999 at address 192.0.2.60 even though my config.ini is still as posted above??

                    Jun-01 7:46:01 PM izDuskySky ERROR Can't connect to TCP Port: 4999 at address: 192.168.1.60
                    Jun-01 7:46:01 PM izDuskySky ERROR Can't connect to TCP Port: 4999 at address: 192.168.1.60
                    Jun-01 7:45:40 PM izDuskySky DEBUG Connecting to TCP port
                    Jun-01 7:45:40 PM izDuskySky TCP port successfully closed.
                    Jun-01 7:45:40 PM izDuskySky TCP port successfully closed.
                    Jun-01 7:45:40 PM izDuskySky DEBUG Shutting Down TCP Port ...
                    Jun-01 7:45:40 PM izDuskySky ERROR TCP port dicconnected. Attempting to reconnect ...
                    Jun-01 7:45:40 PM izDuskySky ERROR TCP port dicconnected. Attempting to reconnect ...
                    Jun-01 7:45:40 PM izDuskySky DEBUG Running timer event ...
                    Jun-01 7:44:40 PM Plug-In Finished initializing plug-in izDuskySky
                    Jun-01 7:44:40 PM izDuskySky Initialised, up and running ...
                    Jun-01 7:44:40 PM izDuskySky Initialised, up and running ...
                    Jun-01 7:44:40 PM izDuskySky ERROR Can't connect to TCP Port: 4999 at address: 192.168.1.60
                    Jun-01 7:44:40 PM izDuskySky ERROR Can't connect to TCP Port: 4999 at address: 192.168.1.60
                    Jun-01 7:44:19 PM izDuskySky DEBUG Connecting to TCP port
                    Jun-01 7:44:19 PM izDuskySky DEBUG Device: izDuskySky-ROOT already exists. No need to create devices
                    Jun-01 7:44:19 PM izDuskySky DEBUG Plug-In Version: 3.0.1.2
                    Jun-01 7:44:19 PM izDuskySky DEBUG In izStd.IniPlugIn
                    Jun-01 7:44:19 PM izDuskySky DEBUG In izInit...
                    Jun-01 7:44:19 PM Info Plugin izDuskySky has connected. IP:127.0.0.1:57284
                    Jun-01 7:44:19 PM Plug-In Interface izDuskySky is running as a trial, 19 days remaining.

                    Comment


                    • #11
                      Thanks, just what I needed to see! Please try 3.0.1.4 which is now in the updater. I believe this should fix the issue.
                      Nicolai L

                      Comment


                      • #12
                        Yep its fixed now! Thats great thanks.

                        Comment

                        Working...
                        X