Ahhh--that makes sense now! Ok, I will revert to my original plan of using HTTP requests.
Thanks a ton for clearing this up.
Just curious, do folks know if there's any plan to port websocket support to the Duet Ethernet/Wifi? (Perhaps there are hardware limitations that make this nice-to-have feature difficult in practice?) I just want to make sure I do development on something lasting.
Thanks @gtj0. Does this code work for you?
I get the error:
websocket._exceptions.WebSocketBadStatusException: Handshake status 200 OK
when running it on "ws://192.168.1.2/machine"
This error happens on this line of execution:
ws = websocket.create_connection("ws://192.168.1.2/machine")
which prevents me from being able to reply back with the OK.
Is there any other sort of "handshaking" that the webui does before making this connection?
Thanks @Danal for the quick reply. I was definitely using RepRap 2 with the old interface. I'm now up-to-date with the RepRap 3 (beta) firmware and DWC 2.
Running this code
import socketio
sio = socketio.Client()
sio.connect("ws://192.168.1.2/machine", transports="websocket")
now errors out with:
websocket._exceptions.WebSocketBadStatusException: Handshake status 404 page not found<br>Check that the SD card is mounted and has the correct files in its /www folder
which looks closer. Ok, so now for some noob questions. Am I making the connection correctly? Attempting to connect to ws://192.168.1.2/machine is what my browser is connected to. Do I need to send the reprap password along in this transaction somehow?
Thanks again!
Hi folks,
I'd like to write a python-based that emulates the web behavior of being able to:
First off, are there leads on doing this already? I'm super new to web programming, but I want to adhere to best practices for interacting with the exposed network-based API. From what I've read, I should be connecting to the Duet via websockets, not via http polling.
I started by opening up dev-tools in my browser on DWC's main page, I was able to track down the connection on this URL:
http://192.168.1.2/rr_connect?password=reprap&time=2019-10-30T17%3A29%3A0
(My Duet has a static IP for now.) It looks like a password, date, and time are encoded too.
Pasting that URL into a connection from Python's socketIO library throws a 404 with this code, though:
import socketio
sio = socketio.Client()
sio.connect("http://192.168.1.2/rr_connect?password=reprap&time=2019-10-30T17%3A29%3A0")
However, using vanilla HTTP Requests with Python works flawlessly:
import requests
params = { "password": "reprap",
"time": "2019-10-30T17:29:0"
}
r = requests.get("http://192.168.1.2", params=params) # this works!
r = requests.get("http://192.168.1.2/rr_status?type=1") # this also works!
print(r.json())
What do folks recommend? I could simply setup a thread to poll the machine state and send GCode from the main thread using the Python requests library. Is there a better approach?
Thanks for taking a look and offering suggestions!
Finally, it looks like others have visited this topic before, but the conversation ended without any leads:
https://forum.duet3d.com/topic/441/web-ui-native-wrapper
I also referenced the Duet Web UI code, but I'm not a web programmer by trade.
Hi, fellow Duet users,
Just curious: is there a way to control individual drives via GCode?
Here's my main use case:
In a multitool setup, individual drive control would enable purging an idle extruder before invoking a tool change. Unfortunately, the toolchange macros don't easily afford this since the tool isn't specified until after tpreX.g, and tool offsets are already applied in tpostX.g. Trying to do any purge commands in tpreX.g throws an error: Attempting to extrude with no tool selected.
It would be convenient if the extruder drives were mapped to the extruder before tpreX.g. That way we could purge the extruder before actually doing the pickup move in tpreX.g.
My current hack is to basically leave tpreX.g blank and do both the tool purge and pickup entirely in tpostX.g, but I need to prefix all movement commands with G53 because tool offsets are applied in tpostX.g.
Thanks for taking a look!
Whoop--I have fixed my own problem. These files were missing because the projects were not inside of the workspace folder created by Eclipse but instead located elsewhere, so they were compiling individually without issue but couldn't link.
Gotcha; thanks for the update.
In that case, I'm having a compilation issue within Eclipse at the linking step.
arm-none-eabi-gcc: error: /home/poofjunior/Applications/eclipse/eclipse-workspaces/RepRapFirmware/CoreNG/SAM4E8E/cores/arduino/syscalls.o: No such file or directory
makefile:70: recipe for target 'Duet2CombinedFirmware.elf' failed
make: *** [Duet2CombinedFirmware.elf] Error 1
"make -j12 all" terminated with exit code 2. Build might be incomplete.
My setup is:
For reference, my target board is a Duet Ethernet.
I would much appreciate any pointers in the right direction; thanks!
Hi there,
It looks like the CoreNG dev branch is missing all the *_RTOS configurations on the dev branch. Going back through the commits, it looks like that may have happened here:
Any shot someone with Push access can add them back?
Finally, I encountered this issue when I was getting compilation errors while compiling CoreNG on the master branch. When I switched to the dev branch, I noticed that all the *_RTOS configurations weren't there.
Thanks for taking a look!