You are not logged in.
Pages: 1
Topic closed
I'm sending data to a InfluxDb server (not localhost) by means of the Http function block (POST).
The data is mostly received good at the server side but still I get these -102 errors.
Is it possible that I have to many requests in one task and that this is causing these timeout errors?
Should I put all http function blocks into one single task and give this separate task more execution time?
If so....how should I do this in the best optimal way?
Offline
Hi scoobsalamander,
error -102 is related to the Timeout. Did you try to setup (extend) the "timeout" parameter of the HTTP function block?
How many requests do you send via HTTP blocks? How often do you send the requests? How often do you get the timeout error?
Or just upload your project files so I can have a look if you don't mind sharing it with community (or send it to support (at) rexcontrols.com).
There is also parameter "BLOCKING", which means that the task execution will wait for FB to finish. Please, note that this parameter can affect whole task (real-time behaviour is not assured any more).
Cheers, Tomas
Offline
Some requests are every 30 sec and some every 5 minutes. All together I think I have around 10 http function blocks in my project.
What happens when some of these are sharing the same trigger input? Are the requests done in the background one by one? I already tried to daisy chain the 'done' ouput to the next 'trigger' input but when the first one is not successfully completed all the others are skipped.
Unfortunately I will not be able to do some testing today....
Last edited by scoobsalamander (2017-01-02 15:40:15)
Offline
I just disabled all my http function blocks except one and I still get these errors....bizarre
I also tried to increase the timeout setting to 500 but this din't change anything.
The blocking parameter is not such a good idea because this makes my REXDraw and/or REXview loose their connection to the Rasp Pi. It gets very hard to download a new working config...if this happens what is the most appropriate way to get everything up and running again (without the blocking parameter box checked)?
I'm also sending by means of NODE-red on some other PC's data to the same database server without any issues.
Offline
Pages: 1
Topic closed