it was a spammer. they are getting more sophisticated,

@xXJRUSHMANXx said in POLAR PRINTER:

So, It's correct M669 K7 R100:400 H100?

That's correct if your radial homing switch triggers at radius 100mm.

@xXJRUSHMANXx said in POLAR PRINTER:

If I have TB6600 drivers configurated by micro-stepping, I understand that I no need Snnn and Tnnn (segmentation), true?

Segmentation is always used when polar kinematics is selected. You can omit the S and T parameters to use the default, or choose them yourself.

In a sample, you don't have M208 for Z axis. I think that its necesary here.

Yes, you should use M208 to configure the Z axis limits.

About the interface, I don't khnow softwares that can manipulate "donut_print_zone", should I send Gcodes manually (in cartesian coordinates)?

For normal prints that don't have a large hole in the centre on all layers, you will need to offset the print so that e.g. all X coordinates are at least +100mm. You may be able to configure this in your slicer. Alternatively, use G10 with parameter L2 to configure a workplace offset, and put this in your slicer start GCode.

@KenW I do have that macro, and earlier today I accidentally hit the button for that on the PanelDue when I meant to hit Filament Load. That explains it. I'll get rid of that file. Thanks again for the quick help, Ken!

@Herve_Smith This Forum post was made prior to us planning on supporting DWC-only, since then we have developed a plugin that works with DWC-only configurations, see forum comment:

@Peter-Lebiedzinski said in AI Print Monitoring / Printer Health monitoring:

@DNvM84 @jay_s_uk
I've created a Plugin for DWC-only configurations to be able to run the AI monitoring. It will work for DWC 3.4, 3.4.6, and 3.5.0-rc as of now. It can be found here: https://github.com/printpal-io/DWC_PrintWatchAI_Plugin

In order to use the plugin, you still need a device (Raspberry Pi, or any SBC) running the AI backend component, and it needs to be on the same network (Ethernet or WiFi) as the Duet mainboard. The backend component as well as how to set it up can be found here: https://github.com/printpal-io/PrintWatchAI_Backend

I would recommend using a Raspberry Pi for running the backend since they are simple and easy to use.
I have also tested the Plugin's Backend component with great success on an Orange Pi Zero3 board and it works just as well. The Orange Pi Zero3 is a little more economical ($22.99 on amazon: https://www.amazon.com/Orange-Pi-Allwinner-Quad-Core-Development/dp/B0CB1BYTT8/ref=sr_1_5?crid=BYJ6JUDXT64O&keywords=orange+pi+zero+3&qid=1694217352&sprefix=orange+pi+zero+3%2Caps%2C118&sr=8-5)

When testing, please run with Test Mode enabled, since the code that checks if the printer is 'Printing' has not been fully tested.

@dc42 Ah, thanks for the name. I'm able to find some. I also considered a vacuum to hold the bed in place and electro magnet but they seem impractical.

Also, is there any build surface, beside glass, that can be used for high temp plastics? As glass is heavy and also cannot be used with magnet base.

I think that you can send gcode commands from the ESP32 to the Duet to execute. Via HTTP or serial connection. I guess that this allows you to send gcode such as setting global variables that your conditional code can access. Others may know more details.

@Surgikill Good catch, I had overlooked the I1 parameter, though that shouldn't give any problems; the parameter is ignored. The rest of the deployprobe.g and retractprobe.g are correct though, and that should not give an error.

@R006 thanks, I've logged https://github.com/Duet3D/RepRapFirmware/issues/912/

dc42 created this issue in Duet3D/RepRapFirmware open Resume after power fail when print is from external SD card (standalone mode) #912

@Herve_Smith in my experience some things, like the processing speed of complex macros, are slower in SBC mode than standalone. Mostly due to the fact that the SBC has to go back to the mainboard for info etc

@dc42 You actually recommended I use a type 8 in another forum post because M401 and M402 weren't working properly.

https://forum.duet3d.com/topic/31077/pneumatic-probe?_=1695134579442

Thanks

Are these errors happening on motors with fixed wiring or wiring that moves with the print head?

The error message is saying that there may be disconnected wiring, perhaps even intermittent. So that would be the first thing to check.

It's unlikely that a firmware update would improve the situation if it's been working fine as it is.

Has the configuration changed recently?

@sandmaker said in Not able to connect to wifi after printer working for 3 months.:

sending M122 I got the response, Emergency Stop! Reset the controller to continue.

It sounds like you send M112 instead of M122. M112 is to restart the firmware.

@sandmaker said in Not able to connect to wifi after printer working for 3 months.:

I managed to fix the printer, It had deleted it's config file and I was able to find the original file for it to replace it. Thanks for the help guys.

Glad you got it sorted out!

@zapta yes you should disable mesh bed compensation when collecting accelerometer data.

Automatic checking of the accelerometer axes is a good idea.

@zapta you could get round the Z homing issue by homing X and Y and then sending G92 Z0. But I take your point, the connector is too deep for the accelerometer to fit the right way up on some hot end assemblies.

@jens55 said in Using te Duet Ecosystem:

@Ktorty429, support for RRF and Duet is absolutely the best and that alone makes the Duet ecosystem the clear choice!

Very much so. To the point that the hardware and software designers are accessible here.