@Phaedrux

Update.
After a few more attempts, slicing other files etc.
I have discovered that the Z-Axis will not move even with Baby Stepping until somewhere around 1.3 - 1.5 mm.
It's difficult to tell exactly where as I'm attempting to hit the Baby Step button and watch the Z-Axis at the same time while it's printing.

I'm guessing there must be a setting somewhere that is causing this behavior.

@Heartleander81

So altering the smooth time value did improve your corners and PA alone did not?

"My guess is that it's a router issue, and changing the channel resets something in the router."

Do you have another none asus router to test with?

You could reverse the microstepping change and the M569 change and see if it makes a difference. You could also flash back to 3.3 firmware, but there's no similar bug that I'm aware of.

@sadrian said in Help setting up new Duet 2 Wifi:

Should the board respond in YAT even when no SD card is present?

Yes as long as there is firmware that's all that matters for USB serial terminal access.

@o_lampe , that's an interesting idea.

Another approach is not to brake the motor or belt but to park the carriage. E.g. it moved to a given height and one or more servo/solenoid activated pins lock it in place.

BTW, the Voron Switchwire uses this to balance gravity. https://www.amazon.com/KEY-BAK-SUPER48-Retractable-Polycarbonate-Oversized/dp/B0088MQA10

Edit: from dc42's post above: "RepRapFirmware 3.4 supports motors with brake solenoids, which can be purchased from stepperonline and elsewhere."

Have you redone a PID tune? What command did you use?

It could also be noise on the thermistor wiring.

Can you post your full config.g?

@ardisf It is heater3 on the expansion bus.

https://docs.duet3d.com/en/Duet3D_hardware/Duet_2_family/DueX2_and_DueX5#pin-names

@Thorpydo

something like (assuming a 6HC)
M584 X0 Y1 Z2 U3 V4 W5

then follow the convention through to set the correct maximum acceleration, speeds etc for those motors (not the effector).
e.g.
M201 X2000 Y2000 Z2000 U2000 V2000 W2000

etc

set the step/mm to something sensible (probably the amount the carriage moves up and down each axis) as you kinematics will then need to work out how much to move each arm on the axis in order to position the effector at the correct XYZ position in the build space, with the correct amount of rotation.

@damaged_goods said in config.g disappears:

RRF 3.4 is running now.

It was running 3.4 when it went missing?

@p8blr said in Prints Pausing: Connection Interrupted/Unknown msg type 6053:

@dc42 No it hasn't given that messages any of the last half dozen or so times it's paused. I have no information on the screen, and the console is basically empty, leading me to believe it's being reset.

In that case, please post a M122 report for each board in your system.

@benjorni in that case the simplest option would be to use a SAMMYC21 connected to the CAN bus to interface to the welding power source via a RS485 driver. There is sample code for the SAMMYC21 in our Duet3Expansion github repository. You would need to choose a SERCOM-capable port to connect the RS485 driver to.

The modifications to the sample code that you would need are in file src/GPIO/GpioPorts.cpp:

In function HandleM950Gpio, if the specified pin is the MODBUS port, initialise the pin in UART mode. You may also want to send a "welding power off" command at this point. In function HandleGpioWrite, if the port is the MODBUS port, write appropriate data to the UART instead of calling WriteAnalog.

As you want to control three parameters (voltage, current, wire feed speed) you might want to define 3 "pins" that write to the same UART.

In config.g you would use M950 commands to set up the connection to the SAMMYC21, then in the GCode you would use M42 commands to control the parameters.

I have it in mind to add a function similar to M260/M261 that writes to UART instead of I2C. If/when I implement this, it would simplify achieving your objective.

Okay, I understand.
Thanks for your help.

@Exerqtor

Nice!

I've been using the script for about 2 weeks now and has been working perfectly for me so far.
So I hope it does for you as well!

@badoobadoop the code is in file src/Heating/LocalHeater.cpp around line 480:

constexpr float avgFactor = HeatSampleIntervalMillis/(HeatPwmAverageTime * SecondsToMillis); averagePWM = (averagePWM * (1.0 - avgFactor)) + (lastPwm * avgFactor);

The two constants are defined in CANlib/src/RRF3Common.h like this:

constexpr uint32_t HeatSampleIntervalMillis = 250; // interval between taking temperature samples constexpr float HeatPwmAverageTime = 5.0; // Seconds

The intention is that the value reported for averagePWM is the instantaneous PWM value fed through a low pass filter with a time constant of 5 seconds.

@TechNi also post your deployprobe.g file.

@Phaedrux
Thank you very much for the response.
I think you may be onto something.

The router type is an ASUS RT-AC88U, and there is a way to disable the maybe not so "Smart Connect" feature. This allows for only the 2.4 or 5 Ghz band. I set it to 2.4, and all three printers connected in short order. Gonna call it quits for tonight, but I will have to do some reset testing very soon here.

Hopefully, I can call this solved!

In case anyone wants to know the config...

; Network M552 S1 P"mySSID" ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet

@TimV-0 said in Can't seem to set where the bed should be when print starts:

The heightmap tab was a big orange icon that said stop in the plugins. All the other plugins said start. Is this backwards or was it the only plug in running and I just shut it off? I clicked it again and it still shows the big green icon that says start?

If the plugin says stop, that means it's running. Clicking stop, stopped it. So no heightmap.

Start it again. This time go to the system tab in DWC and find the heightmap.csv file and delete it and then send G29 S0 to create a new mesh.