Topics created by Phil333

@phil333 thanks for your sample. I will fix this in RRF 3.4.0beta7.

@phil333

var.temp0 evaluates to tools[0].active which points to an array containing elements (of I guess extruders) with the temperature for respective extruder (normally 0).

So if you write like this instead:

var temp0 = 0 if #tools[0].active != 0 set var.temp0 = {tools[0].active[0]} ;end if

I don't know if that answers your question some?

6916c6f2-1789-470e-a5e4-03d05ae07162-image.png

@t3p3tony said in multiple filament sensors:

the error messages are in the firmware code - they are not it a user editable text file. You could add a second notice to the user in your filamen-errorX.g

Thanks, then I will leave it as it is. 👍

@phil333 said in multiple filament sensors:

While testing this, I saw that sometimes the pausing of the print needs longer or kind of freezes the printer.
I mean the tool always stops and normally it goes back to its homing position.
But sometimes it stops, needs ~5-15 sec and then goes back.

Try and tie down what part of the gcode file has this issue, the shorter and more reproducible the better.

Does this happen with both tools or just one?

Its hard to say or to determinate which code is doing it, as there seems to be some background (firmware) code to be involved as well.

I think that it happens with both tools, but I will investigate more into it, to see if I can find more details or something reproducible.

I will report back 🙂

@dc42

Try again, I corrected it 😉

Here for a faster access:
https://youtu.be/IHGDNubi_jQ

Its a problem that you cant reproduce it.
I am using a Duet 2 Wifi v1.04c powered by 24V (Meanwell) and a quiet recent BLtouch (so v3.0 or 3.1)
All genuine and the issue is on my side 100% reproducible.

Wiring is definetly not the issue here. (tested with the clone directly connected to the Duet - shortest wire possible).
2 different BTtouch clones tested with the same issue.

I am pretty sure its a firmware issue.
Tested the BLtouch on exp.heater3 (connected currently) but also checked (exp.heater4 and exp.heater5.)

As the problems disappears on 3.2.0 and comes back again on 3.3+ I think we can say its not a hardware issue.

I already opened a thread only for this issue:
https://forum.duet3d.com/topic/25573/bltouch-problem-after-upgrade-to-rrf-3-3/5

But as more issues came up, I thought to open one not in the "third party add-on" section but rather to the "firmware" section".

All other problems then the BLtouch are solved.

@mfs12 said in Change preset feedrates and distances:

Added an github issue. Any changes on this topic will be add there.

Will be part of next release.

@phil333 this sounds similar to https://forum.duet3d.com/topic/25291/genuine-bltouch-v3-0-weirdness-with-rff-3-3?_=1635272591563 except that you are using a Duet WiFi instead of a Duet Maestro. I will take the fix that I implemented in RRF for the Maestro and port it to the Duet WiFi/Ethernet build.

@jay_s_uk
This solved the problem.
Thank you a lot 👍

@T3P3Tony I will recheck if G10 works on tuesday.
Its a error beeing generated by the Silyer (SuperSlicer) and it shows on a new opened error window on trying to slice.

I guess its a problem on using the "[next_extruder]" varialbe on a print that uses just one tool (and there is no "next extruder".
I didnt cross check it, but I think that also Slic3r and PrusaSlicer will have the same problem.

(as I am not allowed to edit my post 3600sec+ after writing)

EDIT:
After a while it worked.
Didnt tested it for a couple of hours but then it worked.

I will check if it just "needs its time" or if the network settings are now correct.
As I am away for a week it will take a while when I can tell more.

Thanks so far dc42 👍

@phil333 the other thing you can do is activate the tool first with active temperature set to 0, then set the temperature. That way no tool change command is sent, so tool change macros don’t run.

Ian

I just want to finalize this:

I bought a quite expensive (~30€ for 3m) twisted and shielded k type thermocouple wire from a german specialized manufacturer. The wire was tested by the manufacturer before shipping.

In the meantime I made my own twisted wire with 2 0.22mm² cables I had around.
Since then the temperature readings were good but every now and then when I touched the 3D printer, the failure happened again.

After the expensice wire came, I also tested this one.
Result is unchanged.

Nearly everytime I am touching the 3D printer, the thermocouple reads 2000°C and I have to shut the power off and on.
So I can not touch the 3d printer while printing or it will abort.

The reason for that is definetly the electrostatic charge I give the (metal case) 3d printer, that accumulates while walking on a carpet floor.

As the case is already earth grounded I think there is nothing else I can do to avoid this.

So I will order a thermistor and try to put it in between the silicon heating pat and the aluminium printbed.

Its a bit sad, that I spend 60€+ for the themocouple daughter board and the k type twisted wire for no benefit 😞

But at least I learned something.

If anyone has an idea that might solve my issue, you are welcome to help.
Otherwise I will just use the "dirty fix" with the thermistor.

RRF will accept GCode generated in Marlin mode by most slicers. Unfortunately, some of those slicers generate M201 and M203 commands that mess with the acceleration and speed limits. Worse, when Marlin implemented M203 the developer ignored the existing specification and changed the units in which the speed limits are configured. But it's usually possible to configure the slicer not to generate those commands.

AFAIK the current PrusaSlicer in RRF mode generates good code.

USB is essentially a serial port on the Duet. PanelDue port is a 3.3V UART as well.

So sounds like you'll have to be sharing either of those with your custome logic, or use HTTP and interface to Duet Web Control. (or even replace the wifi module with a SPI connection to the Duet when RRF 3.2 is released).

Forum has quite a few examples around the PanelDue port, and to share the USB serial port with the timelapse function you could use something like socat to multiplex the one serial port for multiple programs.

Check out this page if you haven't already seen it.

https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation?revisionid=HEAD#main