@guywinslow
Ok - that's good news but a mystery as to why it did not work the first time, as I assume you, effectively, just reinstalled from github.

If you had used the version I posted yesterday - there would have been a duetBackup ONLY log created (along with additional debug information) that you could access directly using the DWC UI.

The version that I sent to you yesterday will be the version posted in github soon. I do not use github for "in progress" builds - just for version bumps, once they are tested.

While I have tested on my 3.6 beta build - It would be very helpful if you could validate it against your 3.5 build.

Can you do that for me? I.e. Try the version I posted yesterday.

P.S. The permissions dsf:dsf from the ls -l look correct - so there may have been some other issue.

@droftarts I know where to copy my start and end Gcode into Orca. But I don't get the same heat up, bed leveling, then my purge line etc. Orca seems to go to the center deploy my BL touch then heats up. no bed mesh. I was asking in the big picture, is selecting any printer profile enough. The only thing which makes a printer profile RRF is switching Marlin to RRF? Which I know how to do. OR, are there other settings which need to be set to tell Orca it is RRF?

My bottom line, is neither the built in profiles are working for me. And if anyone who uses a similar printer have working profiles or knows were there are profiles I can DL online?

As I said, I really want to run through the Orca calibration functions.

@chrishamm @T3P3Tony
I have changed the requestBody in the OpenAPI.yaml file so that a parameter body is generated in Python. This works for uploading gcode files. I have not tested other files.

requestBody: required: true description: 'File content' content: application/octet-stream: schema: type: string format: binary

The function call in Python then looks like this:

# Upload a file file = "f:/temp/test.g" name = "0:/gcodes/test-1.g" try: body = open(file).read() duet_response = api_instance.rr_upload_post(body, name) except ApiException as e: print("Exception when calling DefaultApi->rr_upload_post: %s\n" % e)

@jltx

Your mental model is orthogonal to the intended use 🙂

Lets get something simple started and take it from there...

The usual approach is to start recording images at the start of the print. At the end of the print DuetLapse will create a video (you don't need to so so). You tell DuetLapse HOW you want images recorded with the options. These options are in the configuration file. At a broad level, images can be captured by layer, by time or even a combination.

What you were doing with your approach was asking DuetLapse the create a snapshot VIDEO on every layer change. It could not do that (not enough images) so it was spinning its wheels ...

I also suspect there may be other issues with your configuration (your reported delay between layers) but lets start off simply.

Why don't you try this config file - YOU DO NOT NEED TO PRINT . When you start the DuetLapse plugin you should see something like the screenshot below (after a few seconds). It will capture a new image every 10 seconds.

I'm assuming you are using a camera that streams via http. If that's not the case then tell my what you are doing.

-duet <your duet ip address> -port <something other than 8080 e.g. 8084> -basedir /opt/dsf/sd/DuetLapse3 -camera1 stream -weburl1 <your camera stream source e.g. http://192.168.10.140:8090/stream> -seconds 10 -dontwait -keepfiles -restart -verbose

Make sure you have a working installation. Something like this after about 15 seconds.

60a6a451-212c-4c4d-a17c-cafbb2c9c226-image.png

Wait until you have over 51 images (Status tab keeps count) - this will take about 8 minutes. You can wave your hand in front of the camera or something to while away the time 🙂
Then:
[1] From the DWC interface send M3291 B"DuetLapse3.completed"
[2] Wait 15 seconds or so - video creation can take 10s of minutes with a large number of images.
[3] In DuetLapse UI -- Go to the Files tab - you should see a video has been created. You can click on it.

If there are issues with the above then before I can help - I will need a copy of the log file and configuration file.
You can click on the logfile from the Files Tab and it will download via your browser.

When you have this verified - come back here and I can give you a couple of changes to config and let you loose on a print job.

ALSO _ PLEASE USE THIS VERSION OF THE PLUGIN. I have been making some minor changes and introduced a bug. I am not sure what I had done / not done with the version I posted a few days ago.

DuetLapse3-5.3.7.zip.txt

Well that was quick. I found if I right click there is a reload menu which caused it to come alive. All works great now! Hope this helps someone else.

Thank you, this looks promising

You may have a look at https://forum.duet3d.com/topic/36297/simplyprint-io-unoffical-duet-connector
You can use it to control your duet powered printer via an app or browser while not at home (via an raspberry pi with this software running) and still be able to use DWC while at home.

Thats at least what I do 🙂

@cosmowave Duet 3 boards now support notifications via MQTT over WiFi interfaces. In RRF 3.6 that will be extended to Ethernet interfaces. Unfortunately Duet 2 boards have insufficient flash memory and RAM to support MQTT.

@chrishamm Thank you so much!

It didn't work indeed in standalone nodejs. However, that was easy to fix (in case anyone is interested).

Install @duet3d/connectors, @duet3d/objectmoddel and xhr2 package: npm install @duet3d/connectors npm install @duet3d/objectmodel npm install xhr2 Import XMLHttpRequest from xhr2 package in BaseConnector.js file const XMLHttpRequest = require("xhr2"); Import WebSocket from ws package in RestConnector.js: const WebSocket = require('ws');

Then everything work as normal.

@bartekp

PrusaSlicer is telling your printer to move farther than the bed limits in your config file. That is why the back end of your print is cut off.

It looks like the bed dimensions shown in PrusaSlicer do not match your actual bed so that has to be fixed.

Your part is centered on the bed in the slicer but not on the actual bed.

I have found these issues are related to the origin in the 'bed shape' for PrusaSlicer but the way to fix it is rather complex.

First set the origin in PrusaSlicer Printer Settings - Size and coordinates - Bed Shape - Set to X:0 Y:0. I know that is not how you are supposed to do it but it is the only way I could get it to work. My X = 0 is actually X = +7mm on the bed but I ignore that.

Measure the total movement of your nozzle from your 0, 0 point to the maximum in X and Y. Set those values as the X and Y Size in Bed Shape - Settings.

On my printer my total X travel is 364mm and Y travel is 387mm.

In config.g M208 (Axis Limits) set these same X and Y values. So for my printer:
M208 X0:364 Y0:387

The final part of the solution is to create a custom bed image to show the actual bed limits.

To do this create an image where one pixel = 1mm. This makes it much easier to draw an image to scale. Draw the image to reflect the actual origin. It should also show any keep out zones. In my case I have a glass sheet with bed clips all around. The clips extend 5mm into the bed.

Here is my bed image as an example (Creality Ender 5+ with LGX Lite Pro and REVOsix):
5Plus w REVO Bed printable.png

Load the image in PrusaSlicer Printer Settings - Size and coordinates - Bed Shape - Set - Texture - Load and select your custom bed image.

I used a solid red border to indicate where the clips are. Orange is where I do not like to print as it is too close to the edge of the bed. Notice on the left side there is no red area because the nozzle can not reach far enough to touch the clips so there is no danger of hitting them.

The black/striped area at the front of the bed is where the nozzle can reach but there is no bed under it.

This allows me to place objects on the bed in Prusa Slicer and have them print in those exact locations on the actual bed.

I hope that helps.

@JRCL If you need something for ethernet then there is also this option, which would allow you define your own notification rules/endpoints etc. It uses node-red and works off the basis of polling the board, and provides built in nodes to define events based off the object model data.

A quick note that I just published a small update as release: v1.2.0

This removes the need to have a the separate compatLib.py library present; all the cross-python handling is now done in serialOM.py itself. Nothing else is changed.

@moth4017 I haven't seen a plugin for it, but i've seen talk trials of using macros @ daemon.g, can't remember how it panned out though.

I found another application that works quite easily and has the benefit of being able to adjust all the settings from the web interface.

It's called picamera2-WebUI-Lite

webui-lite-screen.png

There's a slight error on the instructions to install and it doesn't tell you how to set it up as a service, so I've listed thesteps.

To install.

SSH into your PI (or open a terminal if using a desktop)

Change directory

cd /usr/local/bin/

Clone the repositry

sudo git clone https://github.com/monkeymademe/picamera2-WebUI-Lite.git

Change directory

cd /usr/local/bin/picamera2-WebUI-Lite

Test that it's running

python3 app.py

Open your browser and go to
http://raspberrypi.local:8080/

To see just the video feed go to
http://raspberrypi.local:8080/video_feed

Go back to the terminal and hot CTRL + C to shut the app down

To set it up as a service
Change directory

cd /etc/systemd/system

Open a text editor to create a system service file

sudo nano webui-lite.service

Paste in the following

[Unit] Description=Start script for WebUi-Lite as a service After=syslog.target network.target [Service] WorkingDirectory=/usr/local/bin/picamera2-WebUI-Lite/ ExecStart=/usr/bin/python3 /usr/local/bin//picamera2-WebUI-Lite/app.py Restart=always RestartSec=120 [Install] WantedBy=multi-user.target

Press CTRL + X to exit and Y to save

Reload the daemon

sudo systemctl daemon-reload

Enable the service

sudo systemctl enable webui-lite.service

NOTE that if you already have the other streamVideo service I listed above using Picamera you will have to disable it as you can't run both.

sudo systemctl disable streamVideo.service

Reboot the system to make sure the service starts

sudo shutdown -r now

Adjust your DWC settings as follows
webui.png

This will allow you to easily get to the settings page by clicking on the webcam image in DWC
From there adjust your resolution and you can also zoom in a particular area using the scaler crop settings.

Full view
fullscreen.png

Cropped view
zoomed.png

@sebkritikel Thanks for the explanation. S3D seems to be doing it right.

@chrishamm There is and I successfully do it by passing an iterator as "data" to POST request, it feeds the request with chunks of data. Everything is fine but it is a blocking IO. I'm trying to make it async, ond one of the ways is to pass chunks sequentially in subsequent POST requests, only RRF treats each chunk as a separate file.
I have to dig into it more and perhaps make an async iterator and use it with async uploader, which I failed to do as of yet.

This is a working non async upload code:

import requests class upload_in_chunks(object): def __init__(self, filename, chunksize=1 << 13): self.filename = filename self.chunksize = chunksize self.totalsize = os.path.getsize(filename) self.readsofar = 0 def __iter__(self): with open(self.filename, 'rb') as file: while True: data = file.read(self.chunksize) if not data: sys.stderr.write("\n") break self.readsofar += len(data) percent = self.readsofar * 1e2 / self.totalsize sys.stderr.write("\r{percent:3.0f}%".format(percent=percent)) yield data def __len__(self): return self.totalsize def sendme(): requests.get(baseurl+'/rr_connect?password=reprap') requests.post(url, data=upload_in_chunks(afile, chunksize=10))

@DocTrucker said in OrcaSlicer 1.9.0 adds codes that breaks printer.:

Not sure why they'd want to change max speed on the fly rather than just use feed rates?

I think the only gcode limit Cura changes now is M566 for jerk. Feedrate is handled by G1 and for acceleration I believe they use M204.

I can't say what other slicers do. Last I checked Prusa didn't allow for on the fly jerk changes at all without post processing.