Topics created by brunofporto

@droftarts and @dc42 thank you very much!

@dc42 said in CoreXY homing:

Assuming that you are using one of our standard stable builds of RRF, I can't see any way that RRF could fail to execute a G90 command. Please check using M115 or M122 exactly which firmware version you are using and tell us.

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet Ethernet 1.02 or later FIRMWARE_DATE: 2022-11-30 19:36:12

Thanks, I will remove the "fine hope" part

That's what I use here, bondtech hobbed gear.

So after using the calibration factor + few change on the indirect casing, I now have this reported values :

measured min 93% avg 101% max 107% over 12365.3mm

Looks far better than what I ever achieved with direct reading.
I still have some false trigger because of the PTFE tube moving too fast with high acceleration, I will restrain it before the filament reader.

@fcwilt That should do it! Thanks! 😄

That would be because I switched the file system to use UTF8-encoded file names instead of code page 850. Two questions:

If you upload a new file with accented characters in the name through DWC, is the filename displayed correctly in DWC?

If the answer to #1 is yes: if you then put the SD card in a PC, which of the 2 filenames does the PC display correctly? I doubt that it will be both.

One way to implement a hardware lock is simply to put a toggle switch in the power line (plus, not ground). Literally power it off when it is not being used. When powered up, it will "re-sync" itself.

Neither "disappearing" or "reappearing" will affect the actual Duet and/or print job progress.

DC42 and the folks at Duet/Escher can't really "recommend" or "support" this, because, in theory, power cycling COULD cause some kind of problem someday... and power cycling just flatly makes design engineers uncomfortable. 🙂

However, as an end user, I can say I've unplugged and re-plugged PanelDue devices from Duets that were printing, many times. I've even upgraded PanelDue firmware (unplug, carry to computer, upgrade, carry back to printer, plug in) during the middle of a multi day print.

Your decision...

@deckingman said in Control dual heaters of the same heatbed.:

It seems the form search funtion works really well.

It is really dumb and obvious when I use the right set of words to search something I was struggling to find information about 😄

Keep up the great work. I have so far switched my hypercube over to your idlers and motor mounts. It has been printing without a break for a little over a week now!

I think from your data you can derive good limits for each different filament and put them into the filament's config.g. At least that is what I will do. I don't think it will be possible to find one value pair that suits all filaments.
What I do is to check the lowest and highest value for each filament where prints did not under- or over-extrude. Subtract or add to minimum and maximum respectively 5-10% and use these values to setup for this filament.

AFAIK there currently is no way implemented in the firmware that will allow different behaviors based on type of issue because the sensor does not have a concept of different types of issues. It will see movement or not and can compare to what has been commanded. If that is differing too much it will lead to pausing the print. You could work around that by using a very large safety-margin in the percentage configuration. But it will be a workaround.

@dc42 Yes I have a PanelDue. No... it does not appear there even when the macro is executed from PanelDue.

Same behavior as DWC: Right after resetting the macro works (it halts at the end of the macro but works until that). But If I execute anything before it (like a G32) it does halt after the first M291 S3 as Busy and does nothing.

@yd14 You should probably start a new thread for your problem rather than posting in a thread that is already marked as solved.

@gnydick Well.... That is true.... Thank you!!!

But I'll take your comment seriously and first look for a more silent alternative with the same size and flow rate.

If I do not find a good alternative I'll add a thermal fuse inside the power supply that will cut the AC power for good if it overheats. The power supply is rated to work within environments with up to 60C. If I configure the fan to turn on at 50C of inside temperature and considering that the surrounding is at nice 23C due to air conditioning it should be fine.

Better noisy than a fire starter for sure.

@dc42 Thank you. I am not with the latest PanelDue firmware yet. I'll test it asap.

It's a very new feature.

@dc42 That should do the trick! Thank you very much!! 😄

@dc42 I do not want to compare on the fly 😄 Would be great but not what I would like for now - just register the data then I will manually fill the data to a spreadsheet and compare the gcode extrusion length data with measured data.

Then I'll force a failure (holding the filament, opening the extruder, cutting it, closing the nozzle exit with a tool etc.) and compare with normal printing data to look where those failures happened during a print - as the sensor is not configured to pause or do anything right now.

@bfpa40 said in Issues using stall detection when loading filament:

@dc42 I is : (M574 X1 S3 ) Correct if I want to use an endstop switch. I dont wish to use sensorless I want to use my endstop switch with that being the case how should the below line in the homex.g file look?

M574 X1 S3 ; set endstops to use motor stall

See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Movement_section and https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_Set_endstop_configuration.