Ok, never mind, figured it out .... I have to use the slider on the bottom. If it is all the way to the right then no listing, anything else and it shows the listing of the gcodes that are being run.
Thanks for replying - it actually got me to realize that it makes no sense to display all the gcodes from an entire layer and I decided to try the slider to get to a more focused look and there it was .... so indirectly you gave me the answer. Thanks !
@dc42 Thanks! I try this:
...add command G1 R2 X0 Y0 Z2 Fxxx followed by G1 R2 Z0 Fxxx to the end of your tpost#.g files...
Looks like it works. Maybe better if the last leg before the new-tool-print-start could travel i mm higher, now it is scratching the print a little. I'm using the rapid change hotends an they can bend easily when touching the print.
Here I want to ask how to set standby temperatures to tools. I did not find such a feature in Prusa.
And how to tell the machine to put back the last tool after finishing the job.
I spoke with the owner and he said that they are not currently working on a Duet / RRF integration. But, if they get enough requests for it, they will do it. So, if this sounds cool drop them a line and request it!
He also pointed out that it is open source, so anyone can tinker on their own.
@jens55 Hmm I think I'm seeing whats going on with the layer height. On my above example I have the infill and support printing at .4mm heights, but the Cura and Craftware preview show it as .1mm layer heights. If I incrementally move the layers upwards/downwards, it properly reflects that one infill/support layer is printed for every four outer line layers (since the infill and support is printed at 4x the layer height).
Getting the layer thickness preview to properly represent different thicknesses per line type sounds like a good enhancement request.
@Torin Hello! I tried using this to send a text message to my phone via email. I have "email: email@example.com" and I keep getting messages from firstname.lastname@example.org that delivery failed permanently and the recipients is "(empty line)". Is it possible that the email address starting with a number is not working as intended?
@stuartofmt sudo -H -u pi python3 /home/pi/DuetLapse/DuetLapse3.py -duet 192.168.1.217 -seconds 20 -detect none -camera1 web -weburl1 http://192.168.1.217:8090/stream I have this line In rctest.local along with a line that starts videostream.
In my DuetLapse/duet3/192-168-1-217 I have 2 folders: 603 & 1639 Both with JPEGS that give errors when I try opening something about it starts with some character. I also have a bunch of logs in there.
Also - if you are having problems, its best to run the program from the command line and include -verbose. That way you will get a log file and be able to see if there are issues being reported on the console.
@deckingman My first computer: Timex-Sinclair ZX81, then got a Color Computer 2 16k, upgraded to 64k and extended basic , floppy drive , multipak interface, use Microware's OS9 Level One.
Then got a Color Computer 3, upgrade 512k, DISTO floppy controller, and Microware's OS9 Level Two, then got a SuperIDE interface, now using NitrOS9. Still have them.
After @engikeneer confirmed that it should work with no need to have the extra lines in the start g-code and @Arnold_R_Clark advising me to do a re-install and that didnt work it got me thinking, so i just did a system rollback in win10 to before i even downloaded PrusaSlicer.
I then went and checked in my appdata folders and i found a very old installation of PrusaSlicer from over 2 years ago, i must have tried it uninstalled and forgot, i used to run simplify3d before installing ideamaker.
deleted the old appdata files, ran a regedit scan using CC cleaner and that cleared out a pile of old broken registry files relating to PrusaSlicer and a reboot and re-install and it now works as @engikeneer said it should. it must have been windows being windows..
thanks to you both for helping me to fix this with the confirmation and the re-install ideas. i will mark it as a question and solved.