Wiser Pulse Power Meters

Discussion in 'C-Bus Wiser 1 Controller' started by automatedhome.dp, Oct 25, 2017.

  1. automatedhome.dp

    automatedhome.dp

    Joined:
    Oct 25, 2017
    Messages:
    3
    Likes Received:
    0
    Location:
    Ukraine
    Hello ladies and gentlemen,
    I have Wiser Home Control a network C-Bus. It worked well. After 5104BCL i connected an electric meter. The measurements last 3-6 hours and are interrupted. Diagnostic Utility shows an error at about this time:
    13:40:38 Rx : 0565DF000E0207E10A18010D010D282501989B<CR>
    13:40:38 Rx : = Clocks: Date: Tuesday 24/10/2017; Clocks: Time: 13:40:37 Daylight Savings Offset: 1 hour(s); LENGTH ERROR
    Can you suggest something or where to look for a solution to the problem?
    Yours faithfully, Anatoly
     

    Attached Files:

    automatedhome.dp, Oct 25, 2017
    #1
  2. automatedhome.dp

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,427
    Likes Received:
    64
    Location:
    Adelaide
    The length error means there was an additional byte in the message that could not be properly parsed by the log parser.

    That message was sent by a unit with the unit address $65 (101 decimal).

    What unit is at that address?

    Nick
     
    NickD, Oct 26, 2017
    #2
  3. automatedhome.dp

    automatedhome.dp

    Joined:
    Oct 25, 2017
    Messages:
    3
    Likes Received:
    0
    Location:
    Ukraine
    Thank you for responding to my problem.
    Unit address $65 ? PC-CNIEI Wiser. Day all works correctly.
    But I want to understand why there was a mistake. In normal mode every 30 minutes, the following lines are sent:
    09:18:13 Rx : 0565DF000E0207E10A1A030D0109120F015F<CR>
    09:18:13 Rx : = Clocks: Date: Thursday 26/10/2017; Clocks: Time: 09:18:15 Daylight Savings Offset: 1
    hour(s)

    Yours faithfully, Anatoly
     
    automatedhome.dp, Oct 26, 2017
    #3
  4. automatedhome.dp

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,427
    Likes Received:
    64
    Location:
    Adelaide
    Ok... that is the Wiser's CNI.

    If the Wiser has NTP sync, it's normal as part of the C-Bus time mastering process for it to send the current time on C-Bus every 30 minutes.

    I'm not sure why they occasionally have the extra byte that causes the length error, or whether this would cause any further issues.

    If the time does get changed though, the historical measurement data gets shifted to match the time change, so if the time *is* ever wrong then the measurement data would be affected.

    Nick
     
    NickD, Oct 27, 2017
    #4
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.