via google translator

Awesome !! I have tried the new DWC 2.0.0 RC1 and looks very well done and will allow a lot of evolution. Only one thing. I had to comment on the line that defines the machine's password (M551) in order to access the machine. With the password I was not allowed to enter on Safari (Mac and IOS), Explorer (Windows) Google Chrome (Mac, IOS and Windows).
Thanks for the good work and have a good Christmas

@c310
i use this commands to declare the "virtual" sensors

M308 S20 Y"mcu-temp" A"CPU" ; Defineix sensor S20 com a temperatura de la CPU
M308 S21 Y"drivers" A"Duet_drv" ; Defineix sensor S21 com a temperatura dels drivers de la duet
M308 S22 Y"drivers-duex" A"Duex_drv" ; Defineix sensor S22 com a temperatura dels drivers de la duex5

In this case, sensors 20 to 22 to declare mcu & drivers.
After that, use it as a standard sensor.

Hope it helps you. I'm runing 3.0RC1 on a DuetWifi + Duex5 and there is no issue at all. A little tricky to configure but not impossible, using Reprap config tool as a start point.

The printing time appears in “enventlog.txt” if you have it activated whit M929 P"eventlog.txt" S1

@paboman

This may help you

https://duet3d.dozuki.com/Wiki/Duet_Wiring_Diagrams

See the xpansion pinout. 35 to 39 are what you are looking for, I think

@wkellyo

Given the ease of programming the WS2812b type RGB LEDs in the arduino environment, here's what I've done:

• set an output PIN for use with M42
• Connect this output pin to an analog input pin of the arduino. In my case I use an ESP32 which can bé easily purchased.
• Monitor the input of the arduino to see what values ​​it gives according to the values ​​set on the M42. Depending on whether it is 8 or 32 bits the sampling may be different
• Decide what values ​​I use and why (Warm up, start, print, ....)
• Program the Arduino with the FastLED library that will assign a color / effect according to the value of the input PIN
• Write a macro in the DUET for each output value of the PIN that connects to the Arduino
• Call the Macro in order to provoke the output by the DUET PIN which will be sampled by the Arduino and execute the code to put the LEDS in the color chosen in previous steps.
  I have it that way and set different scenarios for Standby, warming, cooling, calibrating, printing and off. I call macros from confit.g at printer startup or from G-code generated by Slic3r. Alternatively I can enable them from the PanelDue.

Hope it helps as Google Translator helps me

@tratoon

Try this too, this thread inspired me when i need it

https://forum.duet3d.com/topic/14428/full-shutdown-after-prints

@zapta

hi, i sent my address and t’he amazon code via chat, i think.
I don't know if you received it or not, I don't get along with chats

Via GoogleTranslator

@zapta

Is there any possibility to sign up on the wait list?I like to have one of those analyzer

Thanks

@Szwalkiewicz

greetings
I see that in the M669 command of config.g you only define the kinematics type as corexy (K1) but you do not define the motion matrix.
i use the following command on my corexy printer and it works fine for me
M669 K1 X1: 1 Y1: -1

the console output it gives me is as follows:

M669
Kinematics is CoreXY, matrix:
1.00 1.00 0 0
1.00 -1.00 0 0
0 0 1.00 0
0 0 0 1.00

I hope it serves

The printing time appears in “enventlog.txt” if you have it activated whit M929 P"eventlog.txt" S1

@observatoer
Considering that you have the z-probe fine Tuned and configured. You commented that you have the problem when you do the homing. Is it possible that you do not use the z-probe to set z=0 and that there is this difference of one millimeter between the z-axis sensor and the z-probe?

In my printer, with dual z axis, after home with micros witches every motor, I run a G30 command to set Z=0 with de Z-probe then I run a G32 command.

It works well for me in reprap 3.1 on a duetWifi+Duex

@deckingman

well seen !! I didn’t notice how fast it was going to the axis of the abscissas, the seconds that pass while print

Hi!!

Hope this helps you using RGB leds

@Pertti

See if variations occur when there is a layer change. There are many slicers that in the layer change send the temperature values for the extruders. It seems that the temperature variation seen in the graph is between 140ºC (which are the ones you have defined in the G10 command) and 195ºC which are the ones that Cura must send to each layer change.

it is a very strange graph showing the temperature followed by the second extruder.
The hot bed (blue) is correct and stable as well as the first extruder (red), it is the second extruder (green) which has a very erratic graph. I imagine you made the right tuning using the M303: Run heater tuning command on the second extruder as well