dort
About
- Username
- dort
- Joined
- Visits
- 10
- Last Active
- Roles
- Member
Comments
-
Hi, I don't see the issue any more. I have been using the api and often sending bad commands, so it was probably my fault.
-
Thank you for your prompt reply! You are awesome as usual. --D
-
Also, trying to change the behavior with extendPing at the beginning returns this: Sending extendPing:{"action":"extendPing","data":{"timeout":"100"},"printer":"MyPrinter","callback_id":199} Sending ping:{"action":"ping","data":{},"printer":"MyPrint…
-
Oh man...of course. That was it. Thank you.
-
This is great. I just updated server and the latest release handles the events correctly. With that I can set a "trap" and catch the event. Thank you!
-
Thank you. A question along these lines however: I apologize because I am new to websockets, but when I do a send of an M400, then do a recv(), I always get back a response immediately of the form: {"callback_id":10586,"data":{},"session":"4D9beRKS…
-
Thanks! I have no idea what was going on, but I modified those files and now I am good.
-
Yup! I think you got it. I was at 250000, and last night I reflashed the printer to 115200, and it works now. Interestingly, server did not work at exactly 250000...I actually had to set it to 256000 to work. Thanks for the help and info!