Error parsing register

[Villhahallon]

Hello! I hope this is not a dead project, I hope to get this working and get my spa running with this. I have an sv2 controller and I have build the board as described, and running the master branch. Looks like I get some data back on the serial communication but I'm stuck and not sure what do to. Could I get some guidance here?

This is how it looks when hooked up with telnet:

(D p:^1009ms) (getRegisters)(C1) Getting registers
(D p:^0000ms) (pollStatus)(C1) Polling Status with RF command
(D p:^0001ms) (sendCommand)(C1) Sending RF
(D p:^0361ms) (sendCommand)(C1) Received
(D p:^0005ms) (parseStatus)(C1) Parsing status string
(D p:^1003ms) (getRegisters)(C1) Getting registers
(D p:^0000ms) (pollStatus)(C1) Polling Status with RF command
(D p:^0001ms) (sendCommand)(C1) Sending RF
(D p:^0618ms) (sendCommand)(C1) Received RF:
(D p:^0005ms) ,R2,0,230,30,58,4,19,48,41,5,0,2010,206,9999,1,0,527,142,44,6000,782549,8359,0,0,0,0,0,67326,64511,41736:
(D p:^0011ms) ,R3,16,2,5,5,5,SW V2 24 09 13,SV2,14020001,20000546,1,0,0,0,1,0,NA,7,0,488,Fault,232,0,9,12,0,0:
(D p:^0003ms) ,R4,NORM,2,2,2,1,100000,0,4,16,0,1415823,0,0,0,0,0,0,2,0,100,0,100000,4,80,100,6,0,4:
(D p:^0011ms) ,R5,0,0,0,0,0,0,0,0,0,0,0,0,0,0,408,0,18,4,0,0,0,0,0,1,2,6:
(D p:^0004ms) ,R6,1,1,0,2,4,4,4,406,1,0,3584,5120,127,128,5632,5632,1792,1792,0,30,0,0:
(D p:^0011ms) ,R7,3072,0,1,0,1,0,1,10,10,0,242,203,0,1000,491,125,79,1,4,0,0,24,200,0,0,3,20,22,25,100:
(D p:^0013ms) ,R9,F1,441820,4875,4,14,219,9999,275,24,1,6,384:
(D p:^0003ms) ,RA,F2,441978,2604,6,17,221,9999,344,44,0,200,380:
(D p:^0001ms) ,RB,F3,781894,3341,6,0,216,9999,402,42,0,255,406:
(D p:^0011ms) ,RC,0,0,0,0,0,0,0,0,0,2:
(D p:^0002ms) ,RE,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,-4,13,30,8,5,1,0,0,0,0,0:*
(D p:^0011ms)
(D p:^0003ms) (parseStatus)(C1) Parsing status string
(W p:^0001ms) (updateRegister)(C1) Error parsing register, expected 33 fields, got 31
(D p:^0011ms) (updateRegister)(C1) Update register request -
(D p:^0003ms) ,R2,0,230,30,58,4,19,48,41,5,0,2010,206,9999,1,0,527,142,44,6000,782549,8359,0,0,0,0,0,67326,64511,41736
(W p:^0011ms) (updateRegister)(C1) Error parsing register, expected 30 fields, got 28
(D p:^0003ms) (updateRegister)(C1) Update register request -
(D p:^0010ms) ,R3,16,2,5,5,5,SW V2 24 09 13,SV2,14020001,20000546,1,0,0,0,1,0,NA,7,0,488,Fault,232,0,9,12,0,0
(W p:^0004ms) (updateRegister)(C1) Error parsing register, expected 31 fields, got 30
(D p:^0011ms) (updateRegister)(C1) Update register request -
(D p:^0003ms) ,R4,NORM,2,2,2,1,100000,0,4,16,0,1415823,0,0,0,0,0,0,2,0,100,0,100000,4,80,100,6,0,4
(W p:^0011ms) (updateRegister)(C1) Error parsing register, expected 29 fields, got 28
(D p:^0012ms) (updateRegister)(C1) Update register request -
(D p:^0003ms) ,R5,0,0,0,0,0,0,0,0,0,0,0,0,0,0,408,0,18,4,0,0,0,0,0,1,2,6
(W p:^0011ms) (updateRegister)(C1) Error parsing register, expected 31 fields, got 24
(D p:^0003ms) (updateRegister)(C1) Update register request -
(D p:^0011ms) ,R6,1,1,0,2,4,4,4,406,1,0,3584,5120,127,128,5632,5632,1792,1792,0,30,0,0
(W p:^0003ms) (updateRegister)(C1) Error parsing register, expected 34 fields, got 32
(D p:^0011ms) (updateRegister)(C1) Update register request -
(D p:^0003ms) ,R7,3072,0,1,0,1,0,1,10,10,0,242,203,0,1000,491,125,79,1,4,0,0,24,200,0,0,3,20,22,25,100
(W p:^0011ms) (updateRegister)(C1) Error parsing register, expected 15 fields, got 14
(D p:^0004ms) (updateRegister)(C1) Update register request -
(D p:^0011ms) ,R9,F1,441820,4875,4,14,219,9999,275,24,1,6,384
(W p:^0004ms) (updateRegister)(C1) Error parsing register, expected 15 fields, got 14
(D p:^0011ms) (updateRegister)(C1) Update register request -
(D p:^0003ms) ,RA,F2,441978,2604,6,17,221,9999,344,44,0,200,380
(W p:^0001ms) (updateRegister)(C1) Error parsing register, expected 15 fields, got 14
(D p:^0011ms) (updateRegister)(C1) Update register request -
(D p:^0003ms) ,RB,F3,781894,3341,6,0,216,9999,402,42,0,255,406
(W p:^0011ms) (updateRegister)(C1) Error parsing register, expected 17 fields, got 12
(D p:^0003ms) (updateRegister)(C1) Update register request -
(D p:^0011ms) ,RC,0,0,0,0,0,0,0,0,0,2
(W p:^0003ms) (updateRegister)(C1) Error parsing register, expected 33 fields, got 37
(D p:^0001ms) (updateRegister)(C1) Update register request -
(D p:^0011ms) ,RE,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,-4,13,30,8,5,1,0,0,0,0,0

[wayne-love]

This integration was built for a SpaNet 3 controller, you've got a SpaNet 2. It seems that they are return a very similar set of values that are slightly different. It should not be too hard to map the SV2 values if you have an existing OEM wifi adaptor. Do you have one?

[Villhahallon]

That would explain a few things... No I don't have an OEM Wifi adaptor sadly, and they are a bit costly to get one. I'm not to excited to spend much money on this spa as I got it almost for free with burned relays for heating. Fixed that and got a working spa, now the keypad took some frost damage and I can no longer operate the spa.

Would it be possible to work out the data using only the code that is already there? Much trail and error testing I guess...

[wayne-love]

Even if you could borrow one, it would be extremely helpful. Basically what we need is a copy of the support output from the spa net application.Once we have this mapping the fields becomes trivial.On 9 Aug 2024, at 2:19 PM, Villhahallon @.***> wrote: That would explain a few things... No I don't have an OEM Wifi adaptor sadly, and they are a bit costly to get one. I'm not to excited to spend much money on this spa as I got it almost for free with burned relays for heating. Fixed that and got a working spa, now the keypad took some frost damage and I can no longer operate the spa. Would it be possible to work out the data using only the code that is already there? Much trail and error testing I guess...

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>

[Villhahallon]

So I'm lost if I can not get a hold of one then? :( I will need to check around some then. Thank you for the help anyway.