Hi, I am investigating some PID with very long data. I am using the PID scanner for this.When I turn on the log level debug , I can see this as the first repy D (1456677) obd2ecu: Rcv 7ec: 8 (15 df 62 48 83 0 0 0)
From the Canbus doc, I understand that the first "1x (15)" tells me that this is the first frame of a multi frame, and the length is "5df" . The Pid scanner seems to return only "df", not "5df" data, and I can see in the log that I have around 1500 byte returned, not 220. Any explanation ? anyone see this problem as well ?
The scan command is (I had to hack the code to allow timeout > 10sec) re obdii scan start 1 7e4 4883 4883 -r500-7ff -t22 -x30 Didier
Didier, the PID scanner normally works perfectly with multi frame responses, but I haven't had a response that long yet. For 1503 bytes, 215 consecutive frames need to be transmitted. The PID scanner requests these to be sent with 25 ms separation time, so they should need 5.375 seconds. Maybe some frame gets lost, or maybe the device doesn't allow a separation time that high for a transmission that huge. Your log quote wasn't from the re-pid component but from obd2ecu, which has nothing to do with the RE tools. You should raise the log level for re-pid to see more info. Another tracing option is to use the CAN log monitor. Btw, you should never need 30 seconds timeout for a PID poll, as the scanner checks against the last frame reception. Regards, Michael Am 28.03.21 um 17:52 schrieb didier@ernotte.com:
I am investigating some PID with very long data. I am using the PID scanner for this. When I turn on the log level debug , I can see this as the first repy
D (1456677) obd2ecu: Rcv 7ec: 8 (15 df 62 48 83 0 0 0)
From the Canbus doc, I understand that the first "1x (15)" tells me that this is the first frame of a multi frame, and the length is "5df" . The Pid scanner seems to return only "df", not "5df" data, and I can see in the log that I have around 1500 byte returned, not 220. Any explanation ? anyone see this problem as well ? The scan command is (I had to hack the code to allow timeout > 10sec) re obdii scan start 1 7e4 4883 4883 -r500-7ff -t22 -x30
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Ok, I think I found the issue.In void OvmsReToolsPidScanner::IncomingPollFrame(const CAN_frame_t* frame) frameLength should not be a 8 bits, it should rather be a 16 bits uint8_t frameLength = frame->data.u8[0] & 0x0f; Didier Le dimanche 28 mars 2021 13 h 40 min 02 s UTC−4, Michael Balzer <dexter@expeedo.de> a écrit : Didier, the PID scanner normally works perfectly with multi frame responses, but I haven't had a response that long yet. For 1503 bytes, 215 consecutive frames need to be transmitted. The PID scanner requests these to be sent with 25 ms separation time, so they should need 5.375 seconds. Maybe some frame gets lost, or maybe the device doesn't allow a separation time that high for a transmission that huge. Your log quote wasn't from the re-pid component but from obd2ecu, which has nothing to do with the RE tools. You should raise the log level for re-pid to see more info. Another tracing option is to use the CAN log monitor. Btw, you should never need 30 seconds timeout for a PID poll, as the scanner checks against the last frame reception. Regards, Michael Am 28.03.21 um 17:52 schrieb didier@ernotte.com: I am investigating some PID with very long data. I am using the PID scanner for this. When I turn on the log level debug , I can see this as the first repy D (1456677) obd2ecu: Rcv 7ec: 8 (15 df 62 48 83 0 0 0)
From the Canbus doc, I understand that the first "1x (15)" tells me that this is the first frame of a multi frame, and the length is "5df" . The Pid scanner seems to return only "df", not "5df" data, and I can see in the log that I have around 1500 byte returned, not 220. Any explanation ? anyone see this problem as well ?
The scan command is (I had to hack the code to allow timeout > 10sec) re obdii scan start 1 7e4 4883 4883 -r500-7ff -t22 -x30 -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Didier, nice find, are you going to submit a PR for this fix? Regards, Michael Am 28.03.21 um 23:46 schrieb didier@ernotte.com:
Ok, I think I found the issue. In
voidOvmsReToolsPidScanner::IncomingPollFrame(constCAN_frame_t*frame)
frameLength should not be a 8 bits, it should rather be a 16 bits
uint8_tframeLength= frame->data.u8[0] & 0x0f;
Didier Le dimanche 28 mars 2021 13 h 40 min 02 s UTC−4, Michael Balzer <dexter@expeedo.de> a écrit :
Didier,
the PID scanner normally works perfectly with multi frame responses, but I haven't had a response that long yet.
For 1503 bytes, 215 consecutive frames need to be transmitted. The PID scanner requests these to be sent with 25 ms separation time, so they should need 5.375 seconds.
Maybe some frame gets lost, or maybe the device doesn't allow a separation time that high for a transmission that huge.
Your log quote wasn't from the re-pid component but from obd2ecu, which has nothing to do with the RE tools. You should raise the log level for re-pid to see more info. Another tracing option is to use the CAN log monitor.
Btw, you should never need 30 seconds timeout for a PID poll, as the scanner checks against the last frame reception.
Regards, Michael
Am 28.03.21 um 17:52 schrieb didier@ernotte.com <mailto:didier@ernotte.com>:
I am investigating some PID with very long data. I am using the PID scanner for this. When I turn on the log level debug , I can see this as the first repy
D (1456677) obd2ecu: Rcv 7ec: 8 (15 df 62 48 83 0 0 0)
From the Canbus doc, I understand that the first "1x (15)" tells me that this is the first frame of a multi frame, and the length is "5df" . The Pid scanner seems to return only "df", not "5df" data, and I can see in the log that I have around 1500 byte returned, not 220. Any explanation ? anyone see this problem as well ? The scan command is (I had to hack the code to allow timeout > 10sec) re obdii scan start 1 7e4 4883 4883 -r500-7ff -t22 -x30
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Hi Michael, Even if I used to be a developer, I am not familiar with branching and PR in Git. Can someone else take it from here ? Didier Le lundi 29 mars 2021 02 h 58 min 33 s UTC−4, Michael Balzer <dexter@expeedo.de> a écrit : Didier, nice find, are you going to submit a PR for this fix? Regards, Michael Am 28.03.21 um 23:46 schrieb didier@ernotte.com: Ok, I think I found the issue. In void OvmsReToolsPidScanner::IncomingPollFrame(const CAN_frame_t* frame) frameLength should not be a 8 bits, it should rather be a 16 bits uint8_t frameLength = frame->data.u8[0] & 0x0f; Didier Le dimanche 28 mars 2021 13 h 40 min 02 s UTC−4, Michael Balzer <dexter@expeedo.de> a écrit : Didier, the PID scanner normally works perfectly with multi frame responses, but I haven't had a response that long yet. For 1503 bytes, 215 consecutive frames need to be transmitted. The PID scanner requests these to be sent with 25 ms separation time, so they should need 5.375 seconds. Maybe some frame gets lost, or maybe the device doesn't allow a separation time that high for a transmission that huge. Your log quote wasn't from the re-pid component but from obd2ecu, which has nothing to do with the RE tools. You should raise the log level for re-pid to see more info. Another tracing option is to use the CAN log monitor. Btw, you should never need 30 seconds timeout for a PID poll, as the scanner checks against the last frame reception. Regards, Michael Am 28.03.21 um 17:52 schrieb didier@ernotte.com: I am investigating some PID with very long data. I am using the PID scanner for this. When I turn on the log level debug , I can see this as the first repy D (1456677) obd2ecu: Rcv 7ec: 8 (15 df 62 48 83 0 0 0)
From the Canbus doc, I understand that the first "1x (15)" tells me that this is the first frame of a multi frame, and the length is "5df" . The Pid scanner seems to return only "df", not "5df" data, and I can see in the log that I have around 1500 byte returned, not 220. Any explanation ? anyone see this problem as well ?
The scan command is (I had to hack the code to allow timeout > 10sec) re obdii scan start 1 7e4 4883 4883 -r500-7ff -t22 -x30 -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Have you broke something? E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2710323) ovms-server-v2: Status: Error: Connection failed I (2770323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2770323) ovms-server-v2: Status: Connecting... E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2770333) ovms-server-v2: Status: Error: Connection failed I (2830323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2830323) ovms-server-v2: Status: Connecting... E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2830353) ovms-server-v2: Status: Error: Connection failed I (2890323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2890323) ovms-server-v2: Status: Connecting... E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2890323) ovms-server-v2: Status: Error: Connection failed I (2950323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2950323) ovms-server-v2: Status: Connecting... E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2950323) ovms-server-v2: Status: Error: Connection failed I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: 8b=72312-80768 32b=10360) I (3010323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3010323) ovms-server-v2: Status: Connecting... E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3010323) ovms-server-v2: Status: Error: Connection failed I (3070323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3070323) ovms-server-v2: Status: Connecting... E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3070323) ovms-server-v2: Status: Error: Connection failed I (3130323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3130323) ovms-server-v2: Status: Connecting... E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3130353) ovms-server-v2: Status: Error: Connection failed I (3190323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3190323) ovms-server-v2: Status: Connecting... E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3190323) ovms-server-v2: Status: Error: Connection failed I (3250323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3250323) ovms-server-v2: Status: Connecting... E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3250333) ovms-server-v2: Status: Error: Connection failed I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: 8b=72312-80768 32b=10360) I (3310323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3310323) ovms-server-v2: Status: Connecting... E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3310333) ovms-server-v2: Status: Error: Connection failed W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue overflow resolved, 1948 drops I (3730323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3730323) ovms-server-v2: Status: Connecting... E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 29 Mar 2021, at 16:55, didier@ernotte.com wrote:
Hi Michael,
Even if I used to be a developer, I am not familiar with branching and PR in Git. Can someone else take it from here ?
Didier
Le lundi 29 mars 2021 02 h 58 min 33 s UTC−4, Michael Balzer <dexter@expeedo.de> a écrit :
Didier,
nice find, are you going to submit a PR for this fix?
Regards, Michael
Am 28.03.21 um 23:46 schrieb didier@ernotte.com <mailto:didier@ernotte.com>:
Ok, I think I found the issue. In
void OvmsReToolsPidScanner::IncomingPollFrame(const CAN_frame_t* frame)
frameLength should not be a 8 bits, it should rather be a 16 bits
uint8_t frameLength = frame->data.u8[0] & 0x0f;
Didier Le dimanche 28 mars 2021 13 h 40 min 02 s UTC−4, Michael Balzer <dexter@expeedo.de> <mailto:dexter@expeedo.de> a écrit :
Didier,
the PID scanner normally works perfectly with multi frame responses, but I haven't had a response that long yet.
For 1503 bytes, 215 consecutive frames need to be transmitted. The PID scanner requests these to be sent with 25 ms separation time, so they should need 5.375 seconds.
Maybe some frame gets lost, or maybe the device doesn't allow a separation time that high for a transmission that huge.
Your log quote wasn't from the re-pid component but from obd2ecu, which has nothing to do with the RE tools. You should raise the log level for re-pid to see more info. Another tracing option is to use the CAN log monitor.
Btw, you should never need 30 seconds timeout for a PID poll, as the scanner checks against the last frame reception.
Regards, Michael
Am 28.03.21 um 17:52 schrieb didier@ernotte.com <mailto:didier@ernotte.com>:
I am investigating some PID with very long data. I am using the PID scanner for this. When I turn on the log level debug , I can see this as the first repy
D (1456677) obd2ecu: Rcv 7ec: 8 (15 df 62 48 83 0 0 0)
From the Canbus doc, I understand that the first "1x (15)" tells me that this is the first frame of a multi frame, and the length is "5df" . The Pid scanner seems to return only "df", not "5df" data, and I can see in the log that I have around 1500 byte returned, not 220. Any explanation ? anyone see this problem as well ?
The scan command is (I had to hack the code to allow timeout > 10sec)
re obdii scan start 1 7e4 4883 4883 -r500-7ff -t22 -x30
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev> _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Strange. No issues here, no reports from other users… the cert hasn't changed in a while and is valid for another month. The CA cert is valid until september. Does your module have the right system date? Regards, Michael Am 31.03.21 um 12:54 schrieb Shane @ Kilve Engineering:
Have you broke something?
E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2710323) ovms-server-v2: Status: Error: Connection failed I (2770323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (2770323) ovms-server-v2: Status: Connecting... E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2770333) ovms-server-v2: Status: Error: Connection failed I (2830323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (2830323) ovms-server-v2: Status: Connecting... E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2830353) ovms-server-v2: Status: Error: Connection failed I (2890323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (2890323) ovms-server-v2: Status: Connecting... E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2890323) ovms-server-v2: Status: Error: Connection failed I (2950323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (2950323) ovms-server-v2: Status: Connecting... E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2950323) ovms-server-v2: Status: Error: Connection failed I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: 8b=72312-80768 32b=10360) I (3010323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3010323) ovms-server-v2: Status: Connecting... E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3010323) ovms-server-v2: Status: Error: Connection failed I (3070323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3070323) ovms-server-v2: Status: Connecting... E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3070323) ovms-server-v2: Status: Error: Connection failed I (3130323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3130323) ovms-server-v2: Status: Connecting... E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3130353) ovms-server-v2: Status: Error: Connection failed I (3190323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3190323) ovms-server-v2: Status: Connecting... E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3190323) ovms-server-v2: Status: Error: Connection failed I (3250323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3250323) ovms-server-v2: Status: Connecting... E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3250333) ovms-server-v2: Status: Error: Connection failed I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: 8b=72312-80768 32b=10360) I (3310323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3310323) ovms-server-v2: Status: Connecting... E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3310333) ovms-server-v2: Status: Error: Connection failed W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue overflow resolved, 1948 drops I (3730323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3730323) ovms-server-v2: Status: Connecting... E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
It’s using time from gps as that’s ticked Only started last few days but is ok on an older bin file Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 31 Mar 2021, at 12:13, Michael Balzer <dexter@expeedo.de> wrote:
Strange. No issues here, no reports from other users… the cert hasn't changed in a while and is valid for another month. The CA cert is valid until september.
Does your module have the right system date?
Regards, Michael
Am 31.03.21 um 12:54 schrieb Shane @ Kilve Engineering:
Have you broke something?
E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2710323) ovms-server-v2: Status: Error: Connection failed I (2770323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2770323) ovms-server-v2: Status: Connecting... E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2770333) ovms-server-v2: Status: Error: Connection failed I (2830323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2830323) ovms-server-v2: Status: Connecting... E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2830353) ovms-server-v2: Status: Error: Connection failed I (2890323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2890323) ovms-server-v2: Status: Connecting... E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2890323) ovms-server-v2: Status: Error: Connection failed I (2950323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2950323) ovms-server-v2: Status: Connecting... E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2950323) ovms-server-v2: Status: Error: Connection failed I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: 8b=72312-80768 32b=10360) I (3010323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3010323) ovms-server-v2: Status: Connecting... E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3010323) ovms-server-v2: Status: Error: Connection failed I (3070323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3070323) ovms-server-v2: Status: Connecting... E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3070323) ovms-server-v2: Status: Error: Connection failed I (3130323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3130323) ovms-server-v2: Status: Connecting... E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3130353) ovms-server-v2: Status: Error: Connection failed I (3190323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3190323) ovms-server-v2: Status: Connecting... E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3190323) ovms-server-v2: Status: Error: Connection failed I (3250323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3250323) ovms-server-v2: Status: Connecting... E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3250333) ovms-server-v2: Status: Error: Connection failed I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: 8b=72312-80768 32b=10360) I (3310323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3310323) ovms-server-v2: Status: Connecting... E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3310333) ovms-server-v2: Status: Error: Connection failed W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue overflow resolved, 1948 drops I (3730323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3730323) ovms-server-v2: Status: Connecting... E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Shane, found it: you've broken it by your pull request #596, and I've broken it by not recognizing this when reviewing your PR. You added a revert of the mongoose submodule checkout point to your PR: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/596/fi... I've pushed the fix & published a new build to edge. Regards, Michael Am 31.03.21 um 13:21 schrieb Shane@Kilve-Engineering.co.uk:
It’s using time from gps as that’s ticked
Only started last few days but is ok on an older bin file
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 31 Mar 2021, at 12:13, Michael Balzer <dexter@expeedo.de> wrote:
Strange. No issues here, no reports from other users… the cert hasn't changed in a while and is valid for another month. The CA cert is valid until september.
Does your module have the right system date?
Regards, Michael
Am 31.03.21 um 12:54 schrieb Shane @ Kilve Engineering:
Have you broke something?
E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2710323) ovms-server-v2: Status: Error: Connection failed I (2770323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (2770323) ovms-server-v2: Status: Connecting... E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2770333) ovms-server-v2: Status: Error: Connection failed I (2830323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (2830323) ovms-server-v2: Status: Connecting... E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2830353) ovms-server-v2: Status: Error: Connection failed I (2890323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (2890323) ovms-server-v2: Status: Connecting... E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2890323) ovms-server-v2: Status: Error: Connection failed I (2950323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (2950323) ovms-server-v2: Status: Connecting... E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (2950323) ovms-server-v2: Status: Error: Connection failed I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: 8b=72312-80768 32b=10360) I (3010323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3010323) ovms-server-v2: Status: Connecting... E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3010323) ovms-server-v2: Status: Error: Connection failed I (3070323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3070323) ovms-server-v2: Status: Connecting... E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3070323) ovms-server-v2: Status: Error: Connection failed I (3130323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3130323) ovms-server-v2: Status: Connecting... E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3130353) ovms-server-v2: Status: Error: Connection failed I (3190323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3190323) ovms-server-v2: Status: Connecting... E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3190323) ovms-server-v2: Status: Error: Connection failed I (3250323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3250323) ovms-server-v2: Status: Connecting... E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3250333) ovms-server-v2: Status: Error: Connection failed I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: 8b=72312-80768 32b=10360) I (3310323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3310323) ovms-server-v2: Status: Connecting... E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert E (3310333) ovms-server-v2: Status: Error: Connection failed W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue overflow resolved, 1948 drops I (3730323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870> maxushunnsnet I (3730323) ovms-server-v2: Status: Connecting... E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870>) failed: Invalid SSL CA cert
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
My bad But well spotted and thank you for sorting Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 31 Mar 2021, at 13:05, Michael Balzer <dexter@expeedo.de> wrote:
Shane,
found it: you've broken it by your pull request #596, and I've broken it by not recognizing this when reviewing your PR.
You added a revert of the mongoose submodule checkout point to your PR: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/596/fi...
I've pushed the fix & published a new build to edge.
Regards, Michael
Am 31.03.21 um 13:21 schrieb Shane@Kilve-Engineering.co.uk:
It’s using time from gps as that’s ticked
Only started last few days but is ok on an older bin file
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 31 Mar 2021, at 12:13, Michael Balzer <dexter@expeedo.de> wrote:
Strange. No issues here, no reports from other users… the cert hasn't changed in a while and is valid for another month. The CA cert is valid until september.
Does your module have the right system date?
Regards, Michael
Am 31.03.21 um 12:54 schrieb Shane @ Kilve Engineering:
Have you broke something?
E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2710323) ovms-server-v2: Status: Error: Connection failed I (2770323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2770323) ovms-server-v2: Status: Connecting... E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2770333) ovms-server-v2: Status: Error: Connection failed I (2830323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2830323) ovms-server-v2: Status: Connecting... E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2830353) ovms-server-v2: Status: Error: Connection failed I (2890323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2890323) ovms-server-v2: Status: Connecting... E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2890323) ovms-server-v2: Status: Error: Connection failed I (2950323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2950323) ovms-server-v2: Status: Connecting... E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2950323) ovms-server-v2: Status: Error: Connection failed I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: 8b=72312-80768 32b=10360) I (3010323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3010323) ovms-server-v2: Status: Connecting... E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3010323) ovms-server-v2: Status: Error: Connection failed I (3070323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3070323) ovms-server-v2: Status: Connecting... E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3070323) ovms-server-v2: Status: Error: Connection failed I (3130323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3130323) ovms-server-v2: Status: Connecting... E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3130353) ovms-server-v2: Status: Error: Connection failed I (3190323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3190323) ovms-server-v2: Status: Connecting... E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3190323) ovms-server-v2: Status: Error: Connection failed I (3250323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3250323) ovms-server-v2: Status: Connecting... E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3250333) ovms-server-v2: Status: Error: Connection failed I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: 8b=72312-80768 32b=10360) I (3310323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3310323) ovms-server-v2: Status: Connecting... E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3310333) ovms-server-v2: Status: Error: Connection failed W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue overflow resolved, 1948 drops I (3730323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3730323) ovms-server-v2: Status: Connecting... E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Hi Michael, this had already made its way into the https://github.com/MG-EV-Hackers/Open-Vehicle-Monitoring-System-3-MGEV <https://github.com/MG-EV-Hackers/Open-Vehicle-Monitoring-System-3-MGEV> repository how’s best to fix this? Regards Shane
On 31 Mar 2021, at 13:04, Michael Balzer <dexter@expeedo.de> wrote:
Shane,
found it: you've broken it by your pull request #596, and I've broken it by not recognizing this when reviewing your PR.
You added a revert of the mongoose submodule checkout point to your PR: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/596/fi... <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/596/files#diff-5ab2a552f205c6fe33b157a2dc27590aa7258070eb926a8fc3719657dbcc2fd4>
I've pushed the fix & published a new build to edge.
Regards, Michael
Am 31.03.21 um 13:21 schrieb Shane@Kilve-Engineering.co.uk <mailto:Shane@Kilve-Engineering.co.uk>:
It’s using time from gps as that’s ticked
Only started last few days but is ok on an older bin file
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 31 Mar 2021, at 12:13, Michael Balzer <dexter@expeedo.de> <mailto:dexter@expeedo.de> wrote:
Strange. No issues here, no reports from other users… the cert hasn't changed in a while and is valid for another month. The CA cert is valid until september.
Does your module have the right system date?
Regards, Michael
Am 31.03.21 um 12:54 schrieb Shane @ Kilve Engineering:
Have you broke something?
E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2710323) ovms-server-v2: Status: Error: Connection failed I (2770323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (2770323) ovms-server-v2: Status: Connecting... E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2770333) ovms-server-v2: Status: Error: Connection failed I (2830323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (2830323) ovms-server-v2: Status: Connecting... E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2830353) ovms-server-v2: Status: Error: Connection failed I (2890323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (2890323) ovms-server-v2: Status: Connecting... E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2890323) ovms-server-v2: Status: Error: Connection failed I (2950323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (2950323) ovms-server-v2: Status: Connecting... E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2950323) ovms-server-v2: Status: Error: Connection failed I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: 8b=72312-80768 32b=10360) I (3010323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3010323) ovms-server-v2: Status: Connecting... E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3010323) ovms-server-v2: Status: Error: Connection failed I (3070323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3070323) ovms-server-v2: Status: Connecting... E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3070323) ovms-server-v2: Status: Error: Connection failed I (3130323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3130323) ovms-server-v2: Status: Connecting... E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3130353) ovms-server-v2: Status: Error: Connection failed I (3190323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3190323) ovms-server-v2: Status: Connecting... E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3190323) ovms-server-v2: Status: Error: Connection failed I (3250323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3250323) ovms-server-v2: Status: Connecting... E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3250333) ovms-server-v2: Status: Error: Connection failed I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: 8b=72312-80768 32b=10360) I (3310323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3310323) ovms-server-v2: Status: Connecting... E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3310333) ovms-server-v2: Status: Error: Connection failed W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue overflow resolved, 1948 drops I (3730323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3730323) ovms-server-v2: Status: Connecting... E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
By merging my fix… which already has been done. Regards, Michael Am 31.03.21 um 19:58 schrieb Shane @ Kilve Engineering:
Hi Michael, this had already made its way into the
https://github.com/MG-EV-Hackers/Open-Vehicle-Monitoring-System-3-MGEV <https://github.com/MG-EV-Hackers/Open-Vehicle-Monitoring-System-3-MGEV> repository how’s best to fix this?
Regards Shane
On 31 Mar 2021, at 13:04, Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote:
Shane,
found it: you've broken it by your pull request #596, and I've broken it by not recognizing this when reviewing your PR.
You added a revert of the mongoose submodule checkout point to your PR: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/596/fi...
I've pushed the fix & published a new build to edge.
Regards, Michael
Am 31.03.21 um 13:21 schrieb Shane@Kilve-Engineering.co.uk:
It’s using time from gps as that’s ticked
Only started last few days but is ok on an older bin file
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 31 Mar 2021, at 12:13, Michael Balzer <dexter@expeedo.de> wrote:
Strange. No issues here, no reports from other users… the cert hasn't changed in a while and is valid for another month. The CA cert is valid until september.
Does your module have the right system date?
Regards, Michael
Am 31.03.21 um 12:54 schrieb Shane @ Kilve Engineering:
Have you broke something?
E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2710323) ovms-server-v2: Status: Error: Connection failed I (2770323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (2770323) ovms-server-v2: Status: Connecting... E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2770333) ovms-server-v2: Status: Error: Connection failed I (2830323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (2830323) ovms-server-v2: Status: Connecting... E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2830353) ovms-server-v2: Status: Error: Connection failed I (2890323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (2890323) ovms-server-v2: Status: Connecting... E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2890323) ovms-server-v2: Status: Error: Connection failed I (2950323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (2950323) ovms-server-v2: Status: Connecting... E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (2950323) ovms-server-v2: Status: Error: Connection failed I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: 8b=72312-80768 32b=10360) I (3010323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3010323) ovms-server-v2: Status: Connecting... E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3010323) ovms-server-v2: Status: Error: Connection failed I (3070323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3070323) ovms-server-v2: Status: Connecting... E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3070323) ovms-server-v2: Status: Error: Connection failed I (3130323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3130323) ovms-server-v2: Status: Connecting... E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3130353) ovms-server-v2: Status: Error: Connection failed I (3190323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3190323) ovms-server-v2: Status: Connecting... E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3190323) ovms-server-v2: Status: Error: Connection failed I (3250323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3250323) ovms-server-v2: Status: Connecting... E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3250333) ovms-server-v2: Status: Error: Connection failed I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: 8b=72312-80768 32b=10360) I (3310323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3310323) ovms-server-v2: Status: Connecting... E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert E (3310333) ovms-server-v2: Status: Error: Connection failed W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue overflow resolved, 1948 drops I (3730323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> maxushunnsnet I (3730323) ovms-server-v2: Status: Connecting... E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Then how come if I delete the repository and then re download the problem is still there? Regards Shane
On 1 Apr 2021, at 07:10, Michael Balzer <dexter@expeedo.de> wrote:
By merging my fix… which already has been done.
Regards, Michael
Am 31.03.21 um 19:58 schrieb Shane @ Kilve Engineering:
Hi Michael, this had already made its way into the
https://github.com/MG-EV-Hackers/Open-Vehicle-Monitoring-System-3-MGEV repository how’s best to fix this?
Regards Shane
On 31 Mar 2021, at 13:04, Michael Balzer <dexter@expeedo.de> wrote:
Shane,
found it: you've broken it by your pull request #596, and I've broken it by not recognizing this when reviewing your PR.
You added a revert of the mongoose submodule checkout point to your PR: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/596/fi...
I've pushed the fix & published a new build to edge.
Regards, Michael
Am 31.03.21 um 13:21 schrieb Shane@Kilve-Engineering.co.uk:
It’s using time from gps as that’s ticked
Only started last few days but is ok on an older bin file
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 31 Mar 2021, at 12:13, Michael Balzer <dexter@expeedo.de> wrote:
Strange. No issues here, no reports from other users… the cert hasn't changed in a while and is valid for another month. The CA cert is valid until september.
Does your module have the right system date?
Regards, Michael
Am 31.03.21 um 12:54 schrieb Shane @ Kilve Engineering:
Have you broke something?
E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2710323) ovms-server-v2: Status: Error: Connection failed I (2770323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2770323) ovms-server-v2: Status: Connecting... E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2770333) ovms-server-v2: Status: Error: Connection failed I (2830323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2830323) ovms-server-v2: Status: Connecting... E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2830353) ovms-server-v2: Status: Error: Connection failed I (2890323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2890323) ovms-server-v2: Status: Connecting... E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2890323) ovms-server-v2: Status: Error: Connection failed I (2950323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (2950323) ovms-server-v2: Status: Connecting... E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (2950323) ovms-server-v2: Status: Error: Connection failed I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: 8b=72312-80768 32b=10360) I (3010323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3010323) ovms-server-v2: Status: Connecting... E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3010323) ovms-server-v2: Status: Error: Connection failed I (3070323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3070323) ovms-server-v2: Status: Connecting... E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3070323) ovms-server-v2: Status: Error: Connection failed I (3130323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3130323) ovms-server-v2: Status: Connecting... E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3130353) ovms-server-v2: Status: Error: Connection failed I (3190323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3190323) ovms-server-v2: Status: Connecting... E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3190323) ovms-server-v2: Status: Error: Connection failed I (3250323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3250323) ovms-server-v2: Status: Connecting... E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3250333) ovms-server-v2: Status: Error: Connection failed I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: 8b=72312-80768 32b=10360) I (3310323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3310323) ovms-server-v2: Status: Connecting... E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert E (3310333) ovms-server-v2: Status: Error: Connection failed W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue overflow resolved, 1948 drops I (3730323) ovms-server-v2: Connection is ovms.dexters-web.de:6870 maxushunnsnet I (3730323) ovms-server-v2: Status: Connecting... E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870) failed: Invalid SSL CA cert
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
You probably forgot to do git submodule update --recursive after checking out the branch. Regards, Michael Am 01.04.21 um 09:31 schrieb Shane@Kilve-Engineering.co.uk:
Then how come if I delete the repository and then re download the problem is still there?
Regards Shane
On 1 Apr 2021, at 07:10, Michael Balzer <dexter@expeedo.de> wrote:
By merging my fix… which already has been done.
Regards, Michael
Am 31.03.21 um 19:58 schrieb Shane @ Kilve Engineering:
Hi Michael, this had already made its way into the
https://github.com/MG-EV-Hackers/Open-Vehicle-Monitoring-System-3-MGEV <https://github.com/MG-EV-Hackers/Open-Vehicle-Monitoring-System-3-MGEV> repository how’s best to fix this?
Regards Shane
On 31 Mar 2021, at 13:04, Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote:
Shane,
found it: you've broken it by your pull request #596, and I've broken it by not recognizing this when reviewing your PR.
You added a revert of the mongoose submodule checkout point to your PR: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/596/fi...
I've pushed the fix & published a new build to edge.
Regards, Michael
Am 31.03.21 um 13:21 schrieb Shane@Kilve-Engineering.co.uk:
It’s using time from gps as that’s ticked
Only started last few days but is ok on an older bin file
Regards Shane Hunns Kilve Engineering Ltd. 0792 0729 316
On 31 Mar 2021, at 12:13, Michael Balzer <dexter@expeedo.de> wrote:
Strange. No issues here, no reports from other users… the cert hasn't changed in a while and is valid for another month. The CA cert is valid until september.
Does your module have the right system date?
Regards, Michael
Am 31.03.21 um 12:54 schrieb Shane @ Kilve Engineering: > Have you broke something? > > > > > E (2710323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (2710323) ovms-server-v2: Status: Error: Connection failed > I (2770323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (2770323) ovms-server-v2: Status: Connecting... > E (2770333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (2770333) ovms-server-v2: Status: Error: Connection failed > I (2830323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (2830323) ovms-server-v2: Status: Connecting... > E (2830353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (2830353) ovms-server-v2: Status: Error: Connection failed > I (2890323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (2890323) ovms-server-v2: Status: Connecting... > E (2890323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (2890323) ovms-server-v2: Status: Error: Connection failed > I (2950323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (2950323) ovms-server-v2: Status: Connecting... > E (2950323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (2950323) ovms-server-v2: Status: Error: Connection failed > I (3001323) housekeeping: 2021-03-31 10:07:14 BST (RAM: > 8b=72312-80768 32b=10360) > I (3010323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (3010323) ovms-server-v2: Status: Connecting... > E (3010323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (3010323) ovms-server-v2: Status: Error: Connection failed > I (3070323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (3070323) ovms-server-v2: Status: Connecting... > E (3070323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (3070323) ovms-server-v2: Status: Error: Connection failed > I (3130323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (3130323) ovms-server-v2: Status: Connecting... > E (3130353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (3130353) ovms-server-v2: Status: Error: Connection failed > I (3190323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (3190323) ovms-server-v2: Status: Connecting... > E (3190323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (3190323) ovms-server-v2: Status: Error: Connection failed > I (3250323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (3250323) ovms-server-v2: Status: Connecting... > E (3250323) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (3250333) ovms-server-v2: Status: Error: Connection failed > I (3301323) housekeeping: 2021-03-31 10:12:14 BST (RAM: > 8b=72312-80768 32b=10360) > I (3310323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (3310323) ovms-server-v2: Status: Connecting... > E (3310333) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > E (3310333) ovms-server-v2: Status: Error: Connection failed > W (3717913) websocket: WebSocketHandler[0x3f84d2d0]: job queue > overflow resolved, 1948 drops > I (3730323) ovms-server-v2: Connection is > ovms.dexters-web.de:6870 <http://ovms.dexters-web.de:6870/> > maxushunnsnet > I (3730323) ovms-server-v2: Status: Connecting... > E (3730353) ovms-server-v2: mg_connect(ovms.dexters-web.de:6870 > <http://ovms.dexters-web.de:6870/>) failed: Invalid SSL CA cert > > Regards > Shane Hunns > Kilve Engineering Ltd. > 0792 0729 316
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Hi, Don't you think this fix has a bigger impact on vehicle.cpp, and all implementations ?I have started creating the Jaguar Ipace vehicle, and I see a very similar code (and fix) in IncomingPollReply, for the size (16 bits) of the "length" protected: virtual void PollerStateTicker(); virtual void IncomingPollReply(canbus* bus, uint16_t type, uint16_t pid, uint8_t* data, uint8_t length, uint16_t mlremain); virtual void IncomingPollError(canbus* bus, uint16_t type, uint16_t pid, uint16_t code); and void OvmsVehicleJaguarIpace::IncomingPollFrame(CAN_frame_t* frame){ uint8_t frameType = frame->data.u8[0] >> 4; uint16_t frameLength = frame->data.u8[0] & 0x0f; uint8_t* data = &frame->data.u8[1]; uint16_t dataLength = frameLength; Didier Le mardi 30 mars 2021 13 h 58 min 20 s UTC−4, Greg D. <gregd2350@gmail.com> a écrit : Just to close out this loose end... OBD2ECU doesn't do any multi-frame PIDs other than responding to requests for the VIN (fixed format) and ECU Name (20 characters, user configurable). The flow control frame for both of these are kludged with a simple (fixed) 10ms delay, i.e. it doesn't actually wait for the flow control frame to be received before proceeding, and ignores them when received. Proper processing was seen as unnecessary complexity when I wrote the first prototype, and was never "corrected". Greg Michael Balzer wrote: Didier, the PID scanner normally works perfectly with multi frame responses, but I haven't had a response that long yet. For 1503 bytes, 215 consecutive frames need to be transmitted. The PID scanner requests these to be sent with 25 ms separation time, so they should need 5.375 seconds. Maybe some frame gets lost, or maybe the device doesn't allow a separation time that high for a transmission that huge. Your log quote wasn't from the re-pid component but from obd2ecu, which has nothing to do with the RE tools. You should raise the log level for re-pid to see more info. Another tracing option is to use the CAN log monitor. Btw, you should never need 30 seconds timeout for a PID poll, as the scanner checks against the last frame reception. Regards, Michael Am 28.03.21 um 17:52 schrieb didier@ernotte.com: I am investigating some PID with very long data. I am using the PID scanner for this. When I turn on the log level debug , I can see this as the first repy D (1456677) obd2ecu: Rcv 7ec: 8 (15 df 62 48 83 0 0 0)
From the Canbus doc, I understand that the first "1x (15)" tells me that this is the first frame of a multi frame, and the length is "5df" . The Pid scanner seems to return only "df", not "5df" data, and I can see in the log that I have around 1500 byte returned, not 220. Any explanation ? anyone see this problem as well ?
The scan command is (I had to hack the code to allow timeout > 10sec) re obdii scan start 1 7e4 4883 4883 -r500-7ff -t22 -x30 -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
I don't see any issues in the standard poller. The "incoming" methods get called per frame. You can verify it's working correctly by doing an obdii request. Regards, Michael Am 02.04.21 um 12:55 schrieb didier@ernotte.com:
Hi,
Don't you think this fix has a bigger impact on vehicle.cpp, and all implementations ? I have started creating the Jaguar Ipace vehicle, and I see a very similar code (and fix) in IncomingPollReply, for the size (16 bits) of the "length"
protected: virtualvoidPollerStateTicker(); virtualvoidIncomingPollReply(canbus*bus, uint16_ttype, uint16_tpid, uint8_t*data, uint8_tlength, uint16_tmlremain); virtualvoidIncomingPollError(canbus*bus, uint16_ttype, uint16_tpid, uint16_tcode);
and
voidOvmsVehicleJaguarIpace::IncomingPollFrame(CAN_frame_t*frame) { uint8_tframeType= frame->data.u8[0] >> 4; uint16_tframeLength= frame->data.u8[0] & 0x0f; uint8_t* data= &frame->data.u8[1]; uint16_tdataLength= frameLength;
Didier
Le mardi 30 mars 2021 13 h 58 min 20 s UTC−4, Greg D. <gregd2350@gmail.com> a écrit :
Just to close out this loose end...
OBD2ECU doesn't do any multi-frame PIDs other than responding to requests for the VIN (fixed format) and ECU Name (20 characters, user configurable). The flow control frame for both of these are kludged with a simple (fixed) 10ms delay, i.e. it doesn't actually wait for the flow control frame to be received before proceeding, and ignores them when received. Proper processing was seen as unnecessary complexity when I wrote the first prototype, and was never "corrected".
Greg
Michael Balzer wrote: Didier,
the PID scanner normally works perfectly with multi frame responses, but I haven't had a response that long yet.
For 1503 bytes, 215 consecutive frames need to be transmitted. The PID scanner requests these to be sent with 25 ms separation time, so they should need 5.375 seconds.
Maybe some frame gets lost, or maybe the device doesn't allow a separation time that high for a transmission that huge.
Your log quote wasn't from the re-pid component but from obd2ecu, which has nothing to do with the RE tools. You should raise the log level for re-pid to see more info. Another tracing option is to use the CAN log monitor.
Btw, you should never need 30 seconds timeout for a PID poll, as the scanner checks against the last frame reception.
Regards, Michael
Am 28.03.21 um 17:52 schrieb didier@ernotte.com <mailto:didier@ernotte.com>:
I am investigating some PID with very long data. I am using the PID scanner for this. When I turn on the log level debug , I can see this as the first repy
D (1456677) obd2ecu: Rcv 7ec: 8 (15 df 62 48 83 0 0 0)
From the Canbus doc, I understand that the first "1x (15)" tells me that this is the first frame of a multi frame, and the length is "5df" . The Pid scanner seems to return only "df", not "5df" data, and I can see in the log that I have around 1500 byte returned, not 220. Any explanation ? anyone see this problem as well ? The scan command is (I had to hack the code to allow timeout > 10sec) re obdii scan start 1 7e4 4883 4883 -r500-7ff -t22 -x30
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
participants (5)
-
didier＠ernotte.com -
Greg D. -
Michael Balzer -
Shane ＠ Kilve Engineering -
Shane＠Kilve-Engineering.co.uk