• State Not Answered
  • Replies 38 replies
  • Subscribers 78 subscribers
  • Views 4436 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 296987
Options

PPK2 reports implausible values & modifiers - how to recalibrate?

PurpleSequoia

Hello,

My PPK2 is reporting 2 zetta amperes power usage, and I found out that the "modifiers" appear really broken:

Calibrated: 0
R0: 3095044895830869060112875520.0000
R1: 0.0000
R2: 0.0000
R3: 0.0000
R4: 0.0000
GS0: 0.0000
GS1: 138.3582
GS2: 21.5994
GS3: 3.0130
GS4: 0.0876
GI0: 1.0000
GI1: 0.9614
GI2: 0.9534
GI3: 0.9415
GI4: 0.9521
O0: 0.0000
O1: -2814926129201152.0000
O2: 0.0000
O3: -2251799813685248.0000
O4: 0.0000
VDD: 3300
HW: 54350
mode: 2
S0: -0.000000009
S1: -0.000000064
S2: -0.000000512
S3: -0.000004891
S4: 0.002447326
I0: 0.000000044
I1: 0.000000364
I2: 0.000061116
I3: -0.000254856
I4: -0.007713722
UG0: 1.00
UG1: 1.00
UG2: 1.00
UG3: 1.00
UG4: 1.00
IA: 58
END

I have attempted to re-flash the ppk2 firmware, but that had no effect.

This affects both measurement modes, but in source mode the correct voltage is still output.

Intercepting the modifiers before they are parsed and replacing them with some from a different PPK2 again results in plausible measurements.

This may be related to accidentally writing a binary image intended for a different device onto the PPK2 serial port, assuming there are serial commands to configure those values which do not verify plausibility and do not have a checksum.

Is it possible to re-calibrate the device, or will it have to be replaced?

Parents
  • 0

    Hi

    It has been put on our development teams agenda, so it's just a matter of getting to it now. I don't have details on a timeline unfortunately, and you'll need to contact the RSM (regional sales manager) for something like that. I can help you get in touch if necessary!

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi! I think I hit a somewhat similar problem with my unit:

    Calibrated: 0
R0: 0.0000
R1: 0.0000
R2: -0.0000
R3: 0.0000
R4: -0.0000
GS0: 0.0000
GS1: 154.0610
GS2: 23.3921
GS3: 3.3710
GS4: 0.1094
GI0: 1.0000
GI1: 0.9572
GI2: 0.9503
GI3: 0.9362
GI4: 0.9440
O0: 151.8414
O1: 103.3884
O2: 87.8562
O3: 66.8046
O4: 118.2776
VDD: 3018
HW: 32241
mode: 2
S0: -0.000000028
S1: -0.000000274
S2: -0.000001803
S3: -0.000021984
S4: 0.001923220
I0: 0.000000118
I1: 0.000001097
I2: 0.000071752
I3: -0.000214770
I4: -0.007002169
UG0: 1.00
UG1: 1.00
UG2: 1.00
UG3: 1.00
UG4: 1.00
IA: 57
END

    Nothing looks outrageously wrong but the reading are off by 30% (at least on the high range), the R values are cleared so it's picking the default from the code.  could you find the values for my unit? Rev 1.0.1, 2020.46, C23136C8. Thanks!

  • 0 in reply to FabioFW

    Hi Fabio

    It took a while to find, but here are the logged calibration data for your device, hope they help: 

    'Calibrated: 0'
'R0: 1004.5699'
'R1: 102.1842'
'R2: 10.3829'
'R3: 0.9723'
'R4: 0.0567'
'GS0: 0.0000'
'GS1: 154.0610'
'GS2: 23.3921'
'GS3: 3.3710'
'GS4: -0.4158'
'GI0: 1.0000'
'GI1: 0.9572'
'GI2: 0.9503'
'GI3: 0.9362'
'GI4: 1.0004'
'O0: 151.8414'
'O1: 103.3884'
'O2: 87.8562'
'O3: 66.8046'
'O4: 118.8287'
'VDD: 4000'
'HW: 32241'
'mode: 2'
'S0: -0.000000028'
'S1: -0.000000274'
'S2: -0.000001803'
'S3: -0.000021984'
'S4: -0.082889386'
'I0: 0.000000118'
'I1: 0.000001097'
'I2: 0.000071752'
'I3: -0.000214770'
'I4: 0.120635465'
'UG0: 1.00'
'UG1: 1.00'
'UG2: 1.00'
'UG3: 1.00'
'UG4: 1.00'
'IA: 56'
'END']

    Best regards,

    Simon

  • 0 in reply to Simonr

    Many thanks Simon! I was actually able to write those back to the calibration eeprom and have the device back functioning correctly with ho hacks on the app code. :-)

    Thanks again for digging these out.

  • 0 in reply to FabioFW

    Could you share how you restored the values? I believe it might help me solve my case

Reply Children
Related
Terms of service