[Ovmsdev] Framework V3.1

[Tom Parker]

On 08/01/17 01:38, Michael Balzer wrote:

> You can now see these error in the "*-OVM-ServerLogs" CSV as well, 
> I've just extended the logging a bit to also capture logins and 
> terminations.

Thank you, that was helpful.

> For sending data, it's mostly a question of the available modem send 
> buffer and actual network MTU. You can query the available max send 
> size by...
>
> AT+CIPSEND=?
>
> ...which will normally be around 1460. You need to add base64 encoding 
> and line termination overhead, but that still allows for multiple data 
> rows to be added to one send.

I'm not checking the size, can it ever be very low?

By sending all the messages in one packet I'm now reliably sending 5 
reasonably short messages.

I did uncover a bug in the server, I'm sending 4 NL-COM-CAN messages and 
a NL-COM-HIS message in one packet, I can see all of them arrive in the 
server logs:

2017-01-13 02:35:09,28654,'#22 C rx msg H 
NL-COM-CAN,3,86400,054A120070072600003F'
2017-01-13 02:35:09,28655,'#22 C rx msg H 
NL-COM-CAN,3,86400,054B0078880924000001'
2017-01-13 02:35:09,28656,'#22 C rx msg H 
NL-COM-CAN,3,86400,054C6566C00000807E00'
2017-01-13 02:35:09,28657,'#22 C rx msg H 
NL-COM-CAN,3,86400,054F4801090007808836'
2017-01-13 02:35:09,28658,'#22 C rx msg H 
NL-COM-HIS,0,86400,003F0305001F00B000E000D9'

But only the first NL-COM-CAN and the NL-COM-HIS show up in the separate 
.csv files for the message types. It looks like it's only taking the 
first message per packet or per second and recording that?

I'll be putting this firmware back into my car soon but right now it's 
not sending those messages.