Announcement

Collapse
No announcement yet.

Endurance test

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • John245
    replied
    Originally posted by John245 View Post
    Hi Beerygaz,

    I added some registers (43 in total currently, see also http://forums.homeseer.com/newreply....reply&t=176088) and did start an endurance test today. I will report the results later on.

    ---
    John
    Hi Beerygaz,

    As promised the results of the endurance test. The PI is stable for at least the period between the roll-out of the windows patches. Currently 4 gateways and 85 devices enabled.

    ---
    John

    Leave a comment:

  • John245
    replied
    Hi Beerygaz,

    I added some registers (43 in total currently, see also http://forums.homeseer.com/newreply....reply&t=176088) and did start an endurance test today. I will report the results later on.

    ---
    John

    Leave a comment:

  • John245
    replied
    Originally posted by John245 View Post
    Beerygaz,

    Applying these settings:

    Read/Write Retries: 3
    Read/Write Timeout (ms): 2100
    Delay between each poll (ms): 1000

    Will result in a failure after approx. 12 hours (as was also the case in the past). The Modbus interface stops and needs a reset (also same behavior as in the past). I will contact the supplier to see if read/write retries are allowed.
    According to the supplier the max. value for 'Read/Write Retries' is 1.

    So I will perform a test with the following settings:
    Read/Write Retries: 1
    Read/Write Timeout (ms): 2100
    Delay between each poll (ms): 1000

    ---
    John

    Leave a comment:

  • John245
    replied
    Beerygaz,

    Applying these settings:

    Read/Write Retries: 3
    Read/Write Timeout (ms): 2100
    Delay between each poll (ms): 1000

    Will result in a failure after approx. 12 hours (as was also the case in the past). The Modbus interface stops and needs a reset (also same behavior as in the past). I will contact the supplier to see if read/write retries are allowed.

    Jan-22 10:48:49 Modbus Debug Updating device 47398 : Address 47398 as HoldingRegister:Int16 to 201
    Jan-22 10:48:49 Modbus Debug Updating device 43420 : Address 43420 as HoldingRegister:Int16 to 2970
    Jan-22 10:48:49 Modbus Debug Updating device 43009 : Address 43009 as HoldingRegister:Int16 to 391
    Jan-22 10:48:49 Modbus Debug Updating device 43005 : Address 43005 as HoldingRegister:Int16 to -15
    Jan-22 10:48:49 Modbus Debug Updating device 40083 : Address 40083 as HoldingRegister:Int16 to 12
    Jan-22 10:48:49 Modbus Debug Updating device 40081 : Address 40081 as HoldingRegister:Int16 to 9
    Jan-22 10:48:49 Modbus Debug Updating device 40079 : Address 40079 as HoldingRegister:Int16 to 17
    Jan-22 10:48:49 Modbus Debug Updating device 40033 : Address 40033 as HoldingRegister:Int16 to 200
    Jan-22 10:48:49 Modbus Debug Updating device 40016 : Address 40016 as HoldingRegister:Int16 to 103
    Jan-22 10:48:49 Modbus Debug Updating device 40015 : Address 40015 as HoldingRegister:Int16 to 133
    Jan-22 10:48:49 Modbus Debug Updating device 40014 : Address 40014 as HoldingRegister:Int16 to 457
    Jan-22 10:48:49 Modbus Debug Updating device 40013 : Address 40013 as HoldingRegister:Int16 to 485
    Jan-22 10:48:49 Modbus Debug Updating device 40012 : Address 40012 as HoldingRegister:Int16 to 372
    Jan-22 10:48:49 Modbus Debug Updating device 40008 : Address 40008 as HoldingRegister:Int16 to 371
    Jan-22 10:48:49 Modbus Debug Updating device 40004 : Address 40004 as HoldingRegister:Int16 to -23
    Jan-22 10:48:36 Modbus Debug Trying Slave: 1 Address: 40004 HoldingRegister:Int16
    Jan-22 10:48:36 Modbus Debug Polling Modbus RTU Gateway. Reading 15 registers from slaves
    Jan-22 10:48:34 Modbus Debug Trying Slave: 1 Address: 47398 HoldingRegister:Int16
    Jan-22 10:48:26 Modbus Debug Trying Slave: 1 Address: 43420 HoldingRegister:Int16
    Jan-22 10:48:17 Modbus Debug Trying Slave: 1 Address: 43009 HoldingRegister:Int16
    Jan-22 10:48:09 Modbus Debug Trying Slave: 1 Address: 43005 HoldingRegister:Int16
    Jan-22 10:48:00 Modbus Debug Trying Slave: 1 Address: 40083 HoldingRegister:Int16
    Jan-22 10:47:52 Modbus Debug Trying Slave: 1 Address: 40081 HoldingRegister:Int16
    Jan-22 10:47:43 Modbus Debug Trying Slave: 1 Address: 40079 HoldingRegister:Int16
    Jan-22 10:47:35 Modbus Debug Trying Slave: 1 Address: 40033 HoldingRegister:Int16
    Jan-22 10:47:27 Modbus Debug Trying Slave: 1 Address: 40016 HoldingRegister:Int16
    Jan-22 10:47:18 Modbus Debug Trying Slave: 1 Address: 40015 HoldingRegister:Int16
    Jan-22 10:47:10 Modbus Debug Trying Slave: 1 Address: 40014 HoldingRegister:Int16
    Jan-22 10:47:01 Modbus Debug Trying Slave: 1 Address: 40013 HoldingRegister:Int16
    Jan-22 10:46:53 Modbus Debug Trying Slave: 1 Address: 40012 HoldingRegister:Int16
    Jan-22 10:46:44 Modbus Debug Trying Slave: 1 Address: 40008 HoldingRegister:Int16
    Jan-22 10:46:36 Modbus Debug Trying Slave: 1 Address: 40004 HoldingRegister:Int16
    Jan-22 10:46:36 Modbus Debug Polling Modbus RTU Gateway. Reading 15 registers from slaves
    Jan-22 10:45:31 Modbus Debug Updating device 47398 : Address 47398 as HoldingRegister:Int16 to 201
    Jan-22 10:45:31 Modbus Debug Updating device 43420 : Address 43420 as HoldingRegister:Int16 to 2970
    Jan-22 10:45:31 Modbus Debug Updating device 43009 : Address 43009 as HoldingRegister:Int16 to 391
    Jan-22 10:45:31 Modbus Debug Updating device 43005 : Address 43005 as HoldingRegister:Int16 to -15
    Jan-22 10:45:31 Modbus Debug Updating device 40083 : Address 40083 as HoldingRegister:Int16 to 12
    Jan-22 10:45:31 Modbus Debug Updating device 40081 : Address 40081 as HoldingRegister:Int16 to 9
    Jan-22 10:45:31 Modbus Debug Updating device 40079 : Address 40079 as HoldingRegister:Int16 to 17
    Jan-22 10:45:31 Modbus Debug Updating device 40033 : Address 40033 as HoldingRegister:Int16 to 200
    Jan-22 10:45:31 Modbus Debug Updating device 40016 : Address 40016 as HoldingRegister:Int16 to 103
    Jan-22 10:45:31 Modbus Debug Updating device 40015 : Address 40015 as HoldingRegister:Int16 to 133
    Jan-22 10:45:31 Modbus Debug Updating device 40014 : Address 40014 as HoldingRegister:Int16 to 457
    Jan-22 10:45:31 Modbus Debug Updating device 40013 : Address 40013 as HoldingRegister:Int16 to 485
    Jan-22 10:45:31 Modbus Debug Updating device 40012 : Address 40012 as HoldingRegister:Int16 to 372
    Jan-22 10:45:31 Modbus Debug Updating device 40008 : Address 40008 as HoldingRegister:Int16 to 371
    Jan-22 10:45:31 Modbus Debug Updating device 40004 : Address 40004 as HoldingRegister:Int16 to -23
    Jan-22 10:45:22 Modbus Debug Trying Slave: 1 Address: 47398 HoldingRegister:Int16
    Jan-22 10:45:14 Modbus Debug Trying Slave: 1 Address: 43420 HoldingRegister:Int16
    Jan-22 10:45:05 Modbus Debug Trying Slave: 1 Address: 43009 HoldingRegister:Int16
    Jan-22 10:44:57 Modbus Debug Trying Slave: 1 Address: 43005 HoldingRegister:Int16
    Jan-22 10:44:50 Modbus Debug Trying Slave: 1 Address: 40083 HoldingRegister:Int16
    *************** Above the reading stops *****************
    Jan-22 10:44:49 Modbus Debug Read Slave: 1 Address: 40081 HoldingRegister:Int16 as 9
    Jan-22 10:44:47 Modbus Debug Trying Slave: 1 Address: 40081 HoldingRegister:Int16
    Jan-22 10:44:46 Modbus Debug Read Slave: 1 Address: 40079 HoldingRegister:Int16 as 17
    Jan-22 10:44:44 Modbus Debug Trying Slave: 1 Address: 40079 HoldingRegister:Int16
    Jan-22 10:44:43 Modbus Debug Read Slave: 1 Address: 40033 HoldingRegister:Int16 as 200
    Jan-22 10:44:43 Modbus Debug Trying Slave: 1 Address: 40033 HoldingRegister:Int16
    Jan-22 10:44:42 Modbus Debug Read Slave: 1 Address: 40016 HoldingRegister:Int16 as 103
    Jan-22 10:44:42 Modbus Debug Trying Slave: 1 Address: 40016 HoldingRegister:Int16
    Jan-22 10:44:41 Modbus Debug Read Slave: 1 Address: 40015 HoldingRegister:Int16 as 133
    Jan-22 10:44:41 Modbus Debug Trying Slave: 1 Address: 40015 HoldingRegister:Int16
    Jan-22 10:44:40 Modbus Debug Read Slave: 1 Address: 40014 HoldingRegister:Int16 as 457
    Jan-22 10:44:40 Modbus Debug Trying Slave: 1 Address: 40014 HoldingRegister:Int16
    Jan-22 10:44:39 Modbus Debug Read Slave: 1 Address: 40013 HoldingRegister:Int16 as 485
    Jan-22 10:44:39 Modbus Debug Trying Slave: 1 Address: 40013 HoldingRegister:Int16
    Jan-22 10:44:38 Modbus Debug Read Slave: 1 Address: 40012 HoldingRegister:Int16 as 372
    Jan-22 10:44:38 Modbus Debug Trying Slave: 1 Address: 40012 HoldingRegister:Int16
    Jan-22 10:44:37 Modbus Debug Read Slave: 1 Address: 40008 HoldingRegister:Int16 as 371
    Jan-22 10:44:37 Modbus Debug Trying Slave: 1 Address: 40008 HoldingRegister:Int16
    Jan-22 10:44:36 Modbus Debug Read Slave: 1 Address: 40004 HoldingRegister:Int16 as -23
    Jan-22 10:44:36 Modbus Debug Trying Slave: 1 Address: 40004 HoldingRegister:Int16
    Jan-22 10:44:36 Modbus Debug Polling Modbus RTU Gateway. Reading 15 registers from slaves
    Jan-22 10:43:05 Modbus Debug Updating device 47398 : Address 47398 as HoldingRegister:Int16 to 201
    Jan-22 10:43:05 Modbus Debug Updating device 43420 : Address 43420 as HoldingRegister:Int16 to 2970
    Jan-22 10:43:05 Modbus Debug Updating device 43009 : Address 43009 as HoldingRegister:Int16 to 391
    Jan-22 10:43:05 Modbus Debug Updating device 43005 : Address 43005 as HoldingRegister:Int16 to -15
    Jan-22 10:43:05 Modbus Debug Updating device 40083 : Address 40083 as HoldingRegister:Int16 to 12
    Jan-22 10:43:05 Modbus Debug Updating device 40081 : Address 40081 as HoldingRegister:Int16 to 59
    Jan-22 10:43:05 Modbus Debug Updating device 40079 : Address 40079 as HoldingRegister:Int16 to 64
    Jan-22 10:43:05 Modbus Debug Updating device 40033 : Address 40033 as HoldingRegister:Int16 to 199
    Jan-22 10:43:05 Modbus Debug Updating device 40016 : Address 40016 as HoldingRegister:Int16 to 87
    Jan-22 10:43:05 Modbus Debug Updating device 40015 : Address 40015 as HoldingRegister:Int16 to 127
    Jan-22 10:43:05 Modbus Debug Updating device 40014 : Address 40014 as HoldingRegister:Int16 to 457
    Jan-22 10:43:05 Modbus Debug Updating device 40013 : Address 40013 as HoldingRegister:Int16 to 485
    Jan-22 10:43:05 Modbus Debug Updating device 40012 : Address 40012 as HoldingRegister:Int16 to 377
    Jan-22 10:43:05 Modbus Debug Updating device 40008 : Address 40008 as HoldingRegister:Int16 to 376
    Jan-22 10:43:05 Modbus Debug Updating device 40004 : Address 40004 as HoldingRegister:Int16 to -23
    Jan-22 10:43:04 Modbus Debug Read Slave: 1 Address: 47398 HoldingRegister:Int16 as 201
    Jan-22 10:43:02 Modbus Debug Trying Slave: 1 Address: 47398 HoldingRegister:Int16
    Jan-22 10:43:01 Modbus Debug Read Slave: 1 Address: 43420 HoldingRegister:Int16 as 2970
    Jan-22 10:42:59 Modbus Debug Trying Slave: 1 Address: 43420 HoldingRegister:Int16
    Jan-22 10:42:58 Modbus Debug Read Slave: 1 Address: 43009 HoldingRegister:Int16 as 391
    Jan-22 10:42:58 Modbus Debug Trying Slave: 1 Address: 43009 HoldingRegister:Int16
    Jan-22 10:42:57 Modbus Debug Read Slave: 1 Address: 43005 HoldingRegister:Int16 as -15
    Jan-22 10:42:57 Modbus Debug Trying Slave: 1 Address: 43005 HoldingRegister:Int16
    Jan-22 10:42:56 Modbus Debug Read Slave: 1 Address: 40083 HoldingRegister:Int16 as 12
    Jan-22 10:42:50 Modbus Debug Trying Slave: 1 Address: 40083 HoldingRegister:Int16
    Jan-22 10:42:49 Modbus Debug Read Slave: 1 Address: 40081 HoldingRegister:Int16 as 59
    Jan-22 10:42:47 Modbus Debug Trying Slave: 1 Address: 40081 HoldingRegister:Int16
    Jan-22 10:42:46 Modbus Debug Read Slave: 1 Address: 40079 HoldingRegister:Int16 as 64
    Jan-22 10:42:44 Modbus Debug Trying Slave: 1 Address: 40079 HoldingRegister:Int16
    Jan-22 10:42:43 Modbus Debug Read Slave: 1 Address: 40033 HoldingRegister:Int16 as 199
    Jan-22 10:42:43 Modbus Debug Trying Slave: 1 Address: 40033 HoldingRegister:Int16
    Jan-22 10:42:42 Modbus Debug Read Slave: 1 Address: 40016 HoldingRegister:Int16 as 87
    Jan-22 10:42:42 Modbus Debug Trying Slave: 1 Address: 40016 HoldingRegister:Int16
    Jan-22 10:42:41 Modbus Debug Read Slave: 1 Address: 40015 HoldingRegister:Int16 as 127
    Jan-22 10:42:41 Modbus Debug Trying Slave: 1 Address: 40015 HoldingRegister:Int16
    Jan-22 10:42:40 Modbus Debug Read Slave: 1 Address: 40014 HoldingRegister:Int16 as 457
    Jan-22 10:42:40 Modbus Debug Trying Slave: 1 Address: 40014 HoldingRegister:Int16
    Jan-22 10:42:39 Modbus Debug Read Slave: 1 Address: 40013 HoldingRegister:Int16 as 485
    Jan-22 10:42:39 Modbus Debug Trying Slave: 1 Address: 40013 HoldingRegister:Int16
    Jan-22 10:42:38 Modbus Debug Read Slave: 1 Address: 40012 HoldingRegister:Int16 as 377
    Jan-22 10:42:38 Modbus Debug Trying Slave: 1 Address: 40012 HoldingRegister:Int16
    Jan-22 10:42:37 Modbus Debug Read Slave: 1 Address: 40008 HoldingRegister:Int16 as 376
    Jan-22 10:42:37 Modbus Debug Trying Slave: 1 Address: 40008 HoldingRegister:Int16
    Jan-22 10:42:36 Modbus Debug Read Slave: 1 Address: 40004 HoldingRegister:Int16 as -23
    Jan-22 10:42:36 Modbus Debug Trying Slave: 1 Address: 40004 HoldingRegister:Int16
    Jan-22 10:42:36 Modbus Debug Polling Modbus RTU Gateway. Reading 15 registers from slaves

    ---
    John

    Leave a comment:

  • John245
    replied
    Originally posted by John245 View Post
    Hi Beerygaz,

    Running Modbus PI v3.4.5858.29617 for more than 30 hours at the moment with the settings below.

    Read/Write Retries: 0
    Read/Write Timeout (ms): 2100
    Delay between each poll (ms): 1000

    System seems very stable. I will let it run till the next version of the PI is available.

    But I trust it is stable now, as in the pas my up times were at max. 12 hours.

    Good job done

    ---
    John
    Hi Beerygaz,

    It seems that the stability issues is solved (running for over 54 hours at the moment).

    I will let it run till the next version of the PI is available or till a time period of 100 hours is reached.

    After that I will try the following settings:


    Read/Write Retries: 3
    Read/Write Timeout (ms): 2100
    Delay between each poll (ms): 1000

    I will only change the read/write retries as the other settings are prescribed in the documentation of the interface.

    ---
    John
    ---
    John

    Leave a comment:

  • John245
    replied
    Hi Beerygaz,

    Running Modbus PI v3.4.5858.29617 for more than 30 hours at the moment with the settings below.

    Read/Write Retries: 0
    Read/Write Timeout (ms): 2100
    Delay between each poll (ms): 1000

    System seems very stable. I will let it run till the next version of the PI is available.

    But I trust it is stable now, as in the pas my up times were at max. 12 hours.

    Good job done

    ---
    John

    Leave a comment:

  • John245
    replied
    I will disable the logging. I'm almost sure that logging will not cause the freeze as this was disabled in my case


    Verzonden vanaf mijn iPhone met behulp van Tapatalk

    Leave a comment:

  • beerygaz
    replied
    Also, for the endurance test disable log to file. I want to make sure it's not a log rollover issue. Pretty sure it isn't, but want to be sure.


    Sent from my iPhone using Tapatalk

    Leave a comment:

  • John245
    replied
    Ok I will test the following:
    1. Endurance test with only read-only devices, if this is not stable I will run test 2
    2. Endurance test with your suggested settings, if this is not stable I will run test 3
    3. Endurance test with Modbus Poll software


    ---
    John

    Leave a comment:

  • beerygaz
    replied
    1. 3
    2. 2100
    3. 0

    I'll run some similar tests to try to reproduce the issue.


    Sent from my iPhone using Tapatalk

    Leave a comment:

  • John245
    started a topic Endurance test

    Endurance test

    Running version 3.3 of the PI my interface (including or heating pump) will freeze between 8 - 12 hours. A disable and enable of the PI do not start logging.

    Running version 3.1 this freeze was not there. Disabling and enabling the PI did start logging of the values.

    Which parameters should I set for the settings below to have the same behaviour as version 3.1
    1. Read/Write Retries
    2. Read/Write Timeout (ms)
    3. Delay between each poll (ms)


    ----
    John
    Tags: None
Previous template Next
Working...
X