[Ovmsdev] Simple TCP client
ovms at soko.cc
Mon Aug 24 00:00:26 HKT 2020
I have my own home automation running at home. I want to push the current values (SoC, odometer, ...) once my car is in the driveway and OVMS is booked into my WiFi. My home automation has a TCP server running were I process the data further.
I don't want to the OVMS Server functionality as I'm not a Linux guy, don't want the data in the internet and no SIM use on the OVMS.
So does the canlog_tcpclient.cpp take care of the concurrency etc. correctly? I will do the same in my code. Or should I start a separate task from the vehicle task for every push?
On 23 August 2020 16:37:46 CEST, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
>What are you trying to do?
>From a design point of view, it seems strange to have an outgoing tcp
>connection from a vehicle module. Those modules need to be very
>responsive and realtime.
>Mongoose is the correct approach. But take care, because most of the
>work is done in the network (not vehicle) task, so you need to deal
>with mutex and other concurrency issues.
>> On 23 Aug 2020, at 7:54 PM, Soko <ovms at soko.cc> wrote:
>> Hey everyone,
>> I'm trying to send a simple tcp msg to a remote tcp-server. I've
>looked into the FreeRTOS example
>(esp-idf\examples\protocols\sockets\tcp_client\) which works (kinda)
>but OVMS behaves weirdly when I do it like that.
>> Thomas pointed me to mongoose...
>> So is this the way to go? I would take canlog_tcpclient.cpp as a
>> Ohh... and is it OK if I send my tcp msg in the vehcile task?
>Mongoose should take care of unforeseen errors so the task shouldn't
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
>OvmsDev mailing list
>OvmsDev at lists.openvehicles.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev