@chrishamm yes, I send the session key in the header, I also checked how the duet gui does it and I have the same
Posts made by Seba7890
-
RE: Problem with /rr_reply
-
Problem with /rr_reply
I'm creating my own duet management gui and I came across a problem with /rr_reply when I send rr_gcode with the appropriate parameters and it is sent in a longer time interval, e.g. 5 seconds, it worked properly, but when we send it quickly, the current ones are added to the previous response and that's how I get them. Is there a solution for this? What could it be related to? I'll add that I created a mechanism in accordance with https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests#http-client, i.e. I check in the interval whether the seqs are not changing and then I send /rr_reply
Thanks in advance for your answer
-
RE: Connection dropping using Duet Web API with fetch
So if I need to receive data asynchronously, I need to connect a raspberry pi to Duet 3d and set up DuetWebServer and use the REST API https://github.com/Duet3D/DuetSoftwareFramework/wiki/REST-API
-
Connection dropping using Duet Web API with fetch
Re: Connection dropping using Duet Web API from python script
Hi
I'm currently working on custome gui for duet and using HTTP requests https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests
I am able to connect and receive data, but the problem occurs when fetches are performed asynchronously and starts 4 times in an interval of 250 milliseconds, then after some time the fetch status appears net::ERR_SOCKET_NOT_CONNECTED, it is random and some fetches are executed correctly. does it have to do with limited duet 3d memory? and I need to limit the number of queries sent to API? Additionally, while my application is running, I run Duet Web Control and it disconnects the connection from time to time