Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Iskra AM550 - Data not published, CRC error #36

Open
osfog opened this issue Jan 30, 2022 · 4 comments
Open

Iskra AM550 - Data not published, CRC error #36

osfog opened this issue Jan 30, 2022 · 4 comments

Comments

@osfog
Copy link

osfog commented Jan 30, 2022

Hi is there anyway of troubleshooting issues with the crc checksum - looking at the log the received data indeed seems off however it doesn't seem quite like just poor wiring given how the positions where we see invalid data seems to be following a pattern... well at least a bit.

The meter is an Iskra AM550. I tried tweaking the delay and buffer size but no effect...

[09:41:26][D][data:305]: /ISk5\2M550T-2006
[09:41:26][D][data:305]:
[09:41:26][D][data:305]: 1-0:0.9.1(094127)
[09:41:26][D][data:305]: 1-0:0.9.2(220130)
[09:41:26][D][data:305]: 0-0:96.1.0(77516889)
[09:41:26][D][data:305]: 0-2:25.6.0(ER23)
[09:41:26][D][data:305]: 0-0:25.1.0(ER23)
[09:41:26][D][data:305]: 1-0:1.8.0(027257.748kWh)
[09:41:26][D][data:305]: 1-0:2.8.0(000000.000kWh)
[09:41:26][D][data:305]: 1-0:3.8.0(004565.274kvarh)
[09:41:26][D][data:305]: kW)
[09:41:26][D][data:305]: 1-0:41.7.0(01.422kW)
[09:41:26][D][data:305]: 1-0:42.7.0(00.000kW)
[09:41:26][D][data:305]: 1-0:61.7.0(00.842kW)
[09:41:26][D][data:305]: 1-0:62.7.0(00.000kW)
[09:41:26][D][data:305]: 1-0:31.7.0(011A)
[09:41:26][D][data:305]: 1-0:32.7.0(228.9V)
[09:41:26][D][data:305]: 1-0:51.7.0(006A)
[09:41:26][D][data:305]: 1-0:52.7.0(231.3V)
[09:41:26][D][data:305]: 1-0:71.7.0(003A)
[09:41:26][D][data:305]: 1-0:72.7.0(234.0V)
[09:41:26][D][data:305]: 1-0:0.2.0((ER11))
[09:41:26][D][data:305]: 1-0:0.2.8((ER11))
[09:41:26][D][data:305]: !F8D6
[09:41:26][I][crc:317]: Telegram read. CRC: BF63 = F8D6. PASS = NO
[09:41:36][D][data:305]: /ISk5\2M550T-2006
[09:41:36][D][data:305]:
[09:41:36][D][data:305]: 1-0:0.9.1(094137)
[09:41:36][D][data:305]: 1-0:0.9.2(220130)
[09:41:36][D][data:305]: 0-0:96.1.0(77516889)
[09:41:36][D][data:305]: 0-2:25.6.0(ER23)
[09:41:36][D][data:305]: 0-0:25.1.0(ER23)
[09:41:36][D][data:305]: 1-0:1.8.0(027257.762kWh)
[09:41:36][D][data:305]: 1-0:2.8.0(000000.000kWh)
[09:41:36][D][data:305]: 1-0:3.8.0(004565.277kvarh)
[09:41:36][D][data:305]: 1-0:4.8.0(001459.254kvarh)
[09:41:36][D][data:305]: 000kW)
[09:41:36][D][data:305]: 1-0:41.7.0(01.430kW)
[09:41:36][D][data:305]: 1-0:42.7.0(00.000kW)
[09:41:36][D][data:305]: 1-0:61.7.0(01.576kW)
[09:41:36][D][data:305]: 1-0:62.7.0(00.000kW)
[09:41:36][D][data:305]: 1-0:31.7.0(015A)
[09:41:36][D][data:305]: 1-0:32.7.0(228.1V)
[09:41:36][D][data:305]: 1-0:51.7.0(006A)
[09:41:36][D][data:305]: 1-0:52.7.0(231.3V)
[09:41:36][D][data:305]: 1-0:71.7.0(006A)
[09:41:36][D][data:305]: 1-0:72.7.0(233.4V)
[09:41:36][D][data:305]: 1-0:0.2.0((ER11))
[09:41:36][D][data:305]: 1-0:0.2.8((ER11))
[09:41:36][D][data:305]: !F1BC
[09:41:36][I][crc:317]: Telegram read. CRC: D65B = F1BC. PASS = NO
[09:41:46][D][data:305]: /ISk5\2M550T-2006
[09:41:46][D][data:305]:
[09:41:46][D][data:305]: 1-0:0.9.1(094147)
[09:41:46][D][data:305]: 1-0:0.9.2(220130)
[09:41:46][D][data:305]: 0-0:96.1.0(77516889)
[09:41:46][D][data:305]: 0-2:25.6.0(ER23)
[09:41:46][D][data:305]: 0-0:25.1.0(ER23)
[09:41:46][D][data:305]: 1-0:1.8.0(027257.780kWh)
[09:41:46][D][data:305]: 1-0:2.8.0(000000.000kWh)
[09:41:46][D][data:305]: 1-0:3.8.0(004565.280kvarh)
[09:41:46][D][data:305]: 1-0:4.8.0(001459.254kvarh)
[09:41:46][D][data:305]: 1-0:1.7.0(06.368kW)
[09:41:46][D][data:305]: )
[09:41:46][D][data:305]: 1-0:41.7.0(01.442kW)
[09:41:46][D][data:305]: 1-0:42.7.0(00.000kW)
[09:41:46][D][data:305]: 1-0:61.7.0(01.580kW)
[09:41:46][D][data:305]: 1-0:62.7.0(00.000kW)
[09:41:46][D][data:305]: 1-0:31.7.0(015A)
[09:41:46][D][data:305]: 1-0:32.7.0(228.2V)
[09:41:46][D][data:305]: 1-0:51.7.0(006A)
[09:41:46][D][data:305]: 1-0:52.7.0(231.3V)
[09:41:46][D][data:305]: 1-0:71.7.0(006A)
[09:41:46][D][data:305]: 1-0:72.7.0(233.5V)
[09:41:46][D][data:305]: 1-0:0.2.0((ER11))
[09:41:46][D][data:305]: 1-0:0.2.8((ER11))
[09:41:46][D][data:305]: !8190
[09:41:46][I][crc:317]: Telegram read. CRC: 630E = 8190. PASS = NO
[09:41:56][D][data:305]: /ISk5\2M550T-2006
[09:41:56][D][data:305]:
[09:41:56][D][data:305]: 1-0:0.9.1(094157)
[09:41:56][D][data:305]: 1-0:0.9.2(220130)
[09:41:56][D][data:305]: 0-0:96.1.0(77516889)
[09:41:56][D][data:305]: 0-2:25.6.0(ER23)
[09:41:56][D][data:305]: 0-0:25.1.0(ER23)
[09:41:56][D][data:305]: 1-0:1.8.0(027257.797kWh)
[09:41:56][D][data:305]: 0:41.7.0(01.446kW)
[09:41:56][D][data:305]: 1-0:42.7.0(00.000kW)
[09:41:56][D][data:305]: 1-0:61.7.0(01.581kW)
[09:41:56][D][data:305]: 1-0:62.7.0(00.000kW)
[09:41:56][D][data:305]: 1-0:31.7.0(015A)
[09:41:56][D][data:305]: 1-0:32.7.0(228.3V)
[09:41:56][D][data:305]: 1-0:51.7.0(006A)
[09:41:56][D][data:305]: 1-0:52.7.0(231.2V)
[09:41:56][D][data:305]: 1-0:71.7.0(006A)
[09:41:56][D][data:305]: 1-0:72.7.0(233.4*V)
[09:41:56][D][data:305]: 1-0:0.2.0((ER11))
[09:41:56][D][data:305]: 1-0:0.2.8((ER11))
[09:41:56][D][data:305]: !24AB
@osfog
Copy link
Author

osfog commented Jan 30, 2022

In the meantime i have changed to that i ignore the crc check and instead rely on the atio to returl non 0 and sending the
i.e.:


`    if (atof(value) != 0)
    {
      if (strncmp(obisCode, "1.8.0", 5) == 0)
      {
        parsed->cumulativeActiveImport = atof(value);
        cumulativeActiveImport->publish_state(parsed->cumulativeActiveImport);
      }`

@CarbonCollins
Copy link

CarbonCollins commented Sep 10, 2022 •
edited
Loading

I am also getting this issue with the same model of power meter. similar log output too:

[21:38:04][D][data:265]: /ISk5\2M550T-2006
[21:38:04][D][data:265]:
[21:38:04][D][data:265]: 1-0:0.9.1(203805)
[21:38:04][D][data:265]: 1-0:0.9.2(220910)
[21:38:04][D][data:265]: 0-0:96.1.0(77516706)
[21:38:04][D][data:265]: 0-2:25.6.0(ER23)
[21:38:04][D][data:265]: 0-0:25.1.0(ER23)
[21:38:04][D][data:265]: 1-0:1.8.0(008472.260kWh)
[21:38:04][D][data:265]: 1-0:2.8.0(000000.000kWh)
[21:38:04][D][data:265]: 1-0:3.8.0(000022.619kvarh)
[21:38:04][D][data:265]: 1-0:4.8.0(000701.265kvarh)
[21:38:04][D][data:265]: 1-0:1.7.0(00.500kW)
[21:38:04][D][data:265]: 1-0:2.7.0(00.000kW)
[21:38:04][D][data:265]: kW)
[21:38:04][D][data:265]: 1-0:22.7.0(00.000kW)
[21:38:04][D][data:265]: 1-0:41.7.0(00.494kW)
[21:38:04][D][data:265]: 1-0:42.7.0(00.000kW)
[21:38:04][D][data:265]: 1-0:61.7.0(00.013kW)
[21:38:04][D][data:265]: 1-0:62.7.0(00.000kW)
[21:38:04][D][data:265]: 1-0:31.7.0(000A)
[21:38:04][D][data:265]: 1-0:32.7.0(237.7V)
[21:38:04][D][data:265]: 1-0:51.7.0(002A)
[21:38:04][D][data:265]: 1-0:52.7.0(241.7V)
[21:38:04][D][data:265]: 1-0:71.7.0(000A)
[21:38:04][D][data:265]: 1-0:72.7.0(244.0V)
[21:38:04][D][data:265]: 1-0:0.2.0((ER11))
[21:38:04][D][data:265]: 1-0:0.2.8((ER11))
[21:38:04][D][data:265]: !1A56
[21:38:04][I][crc:276]: Telegram read. CRC: 7374 = 1A56. PASS = NO

@CarbonCollins
Copy link

I spent a bit more time looking into the log output and noticed that in both mine and @johansvenson log outputs, there seems to be an inconsistency with some of the output. for instance:

This telegram has two blank lines:

[11:44:44][D][data:265]: /ISk5\2M550T-2006
[11:44:44][D][data:265]:
[11:44:44][D][data:265]: 1-0:0.9.1(104445)
[11:44:44][D][data:265]: 1-0:0.9.2(220911)
[11:44:44][D][data:265]: 0-0:96.1.0(77516706)
[11:44:44][D][data:265]: 0-2:25.6.0(ER23)
[11:44:44][D][data:265]: 0-0:25.1.0(ER23)
[11:44:44][D][data:265]:
[11:44:44][D][data:265]: 1-0:4.8.0(000704.980kvarh)
[11:44:44][D][data:265]: 1-0:1.7.0(00.199kW)
[11:44:44][D][data:265]: 1-0:2.7.0(00.000kW)
[11:44:44][D][data:265]: 1-0:3.7.0(00.000kvar)
[11:44:44][D][data:265]: 1-0:4.7.0(00.276kvar)
[11:44:44][D][data:265]: 1-0:21.7.0(00.004kW)
[11:44:44][D][data:265]: 1-0:22.7.0(00.000kW)
[11:44:44][D][data:265]: 1-0:41.7.0(00.189kW)
[11:44:44][D][data:265]: 1-0:42.7.0(00.000kW)
[11:44:44][D][data:265]: 1-0:61.7.0(00.005kW)
[11:44:44][D][data:265]: 1-0:62.7.0(00.000kW)
[11:44:44][D][data:265]: 1-0:31.7.0(000A)
[11:44:44][D][data:265]: 1-0:32.7.0(230.4V)
[11:44:44][D][data:265]: 1-0:51.7.0(001A)
[11:44:44][D][data:265]: 1-0:52.7.0(245.1V)
[11:44:44][D][data:265]: 1-0:71.7.0(000A)
[11:44:44][D][data:265]: 1-0:72.7.0(244.6*V)
[11:44:44][D][data:265]: 1-0:0.2.0((ER11))
[11:44:44][D][data:265]: 1-0:0.2.8((ER11))
[11:44:44][D][data:265]: !B587
[11:44:44][I][crc:276]: Telegram read. CRC: C779 = B587. PASS = NO

whereas this one seems to have some malformed data part way through the telegram...:

[11:45:24][D][data:265]: /ISk5\2M550T-2006
[11:45:24][D][data:265]:
[11:45:24][D][data:265]: 1-0:0.9.1(104525)
[11:45:24][D][data:265]: 1-0:0.9.2(220911)
[11:45:24][D][data:265]: 0-0:96.1.0(77516706)
[11:45:24][D][data:265]: 0-2:25.6.0(ER23)
[11:45:24][D][data:265]: 0-0:25.1.0(ER23)
[11:45:24][D][data:265]: 1-0:1.8.0(008478.205kWh)
[11:45:24][D][data:265]: 1-0:2.8.0(000000.000kWh)
[11:45:24][D][data:265]: 1-0:3.8.0(000022.619kvarh)
[11:45:24][D][data:265]: 00kW)
[11:45:24][D][data:265]: 0(00.000kvar)
[11:45:24][D][data:265]: 1-0:4.7.0(00.275kvar)
[11:45:24][D][data:265]: 1-0:21.7.0(00.004kW)
[11:45:24][D][data:265]: 1-0:22.7.0(00.000kW)
[11:45:24][D][data:265]: 1-0:41.7.0(00.188kW)
[11:45:24][D][data:265]: 1-0:42.7.0(00.000kW)
[11:45:24][D][data:265]: 1-0:61.7.0(00.005kW)
[11:45:24][D][data:265]: 1-0:62.7.0(00.000kW)
[11:45:24][D][data:265]: 1-0:31.7.0(000A)
[11:45:24][D][data:265]: 1-0:32.7.0(233.6V)
[11:45:24][D][data:265]: 1-0:51.7.0(001A)
[11:45:24][D][data:265]: 1-0:52.7.0(244.1V)
[11:45:24][D][data:265]: 1-0:71.7.0(000A)
[11:45:24][D][data:265]: 1-0:72.7.0(243.8V)
[11:45:24][D][data:265]: 1-0:0.2.0((ER11))
[11:45:24][D][data:265]: 1-0:0.2.8((ER11))
[11:45:24][D][data:265]: !0904
[11:45:24][I][crc:276]: Telegram read. CRC: 3AB6 = 0904. PASS = NO

you can also see this in the telegram I posted above too...

@CarbonCollins
Copy link

CarbonCollins commented Nov 17, 2022 •
edited
Loading

Hi again,

I've been looking into the issue a bit more as of late and think I may have come to a idea as to what was occuring.

It seems that the AM550 was pushing data faster than what the reader was processing causing the internal serial buffer to fill up and drop data. This is mainly from the way the data was malformed in the previous telegrams I posted. I had success doing one of two things:

  1. decrease the delay at the end of the while loop from 40 to 10 which makes the reader empty the serial buffer more frequently.

  2. Increase the internal serial buffer from the 256 default to 1024 by adding Serial.setRxBufferSize(1024); in the setup function.

In either of these two cases I did not get CRC check errors nor any malformed telegrams. Ive been running it live for the last month or so without any issues here!

I'm not sure which option would be the better choice to raise as a PR though, any thoughts on this?

@makkanftw makkanftw mentioned this issue Aug 18, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CarbonCollins @osfog