Hi,

You're right. Sorry.

@wilriker said in G30 - did something change a while back?:

I just added the default value to the documentation. I did not adjust the part where it says

[...] G30 commands with specified XY coordinates

since I do not know if that was originally intended to be a requirement (the specified XY coords) and it is a bug that it also works with a plain G30. @dc42 needs to clarify this.

Thanks Manuel,

Thanks for pinning this down, we'll get it sorted.

thank you very much 🙂 i think there went something wrong during the update... i erased everything and did an clean install and right now iam on 2.02 and everything works fine 🙂

@adrian52 Print completed fine. M122 from YAT gave this . M122 from DWC gave
alt text
The earlier two disconnects were responses to M122 before the print.

@albert said in Cant build RepRapFirmware:

Even though there was an error says that a .o file can not be found in the directory, it turns out that is because I did not match the configuration of CoreNG and RepRapFirmware ( I choose the SAM4E8E for CoreNG but Duet2_RTOS for ReprapFirmware). After I change the configuration of CoreNG to SAM4E8E_RTOS, everything is ok now.

That's correct. The SAM4E8E non-RTOS build of CoreNG is used by the DuetIAP project.

@garyd9 said in RepRapFirmware 2.02RC4 released:

@dc42 said in RepRapFirmware 2.02RC4 released:

Thanks. Does the problem only ever happen when it is the first time you have run the motor after VIN power has been restored?

I think so. I started paying much closer attention to the warning yesterday after my post (but I've only started 2 prints since then.) I'll certainly keep you informed if it happens other than the first time running the stepper after VIN is restored.

As luck would have it, this evening I had it happen when starting a new print with the printer NOT going into "ATX Off" first. Print ended, I hit the M80 macro (to counter a pending M81 S1), prepped a new plate, heated it up, and got the warning when leveling the build plate.

I just solved that error by downloading a v0.4.12 esptool.

@dc42

not the same way, but yesterday i paused the print to change filament and the DWC become unreachable again.
also the maestro freezed, I was unable to resume the print

@phaedrux Thanks!

Well thank you all for your help. With dc42 suggestion and Link to wiring diagram from T3P3Tony I have it fixed. I had the black and blue crossed. (So much for making black the standard ground or negative).
All is working as it should.

Cheers everyone.
Leif

@veti said in Maestro firmware and configuration guide:

you are right. acceleration is mm/s^2

and the default values 20 for y is very low. this might be a bug.

I agree, and we will change the default. I suggest you increase the Y value in the M201 command to 500, perhaps higher when you know what the printer is capable of.

I'll do that in future!

@buj the Duet cannot authenticate on university or similar networks that prompt for a user ID and password in the browser. In this case it is best to use the Duet in access point more and has been suggested.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M552_Set_IP_address_enable_disable_network_interface

@featheryjam2 said in Homing Issues with CoreXY and two z-axis drivers [SOLVED]:

I may have figured it out. Apparently it does not like when you do G28 X or G28 Y in the homez.g script.

That's correct. You can use M98 Phomex.g and M98 Phomey.g instead if you need to. However, as you are homing Z using a G30 command, you should have the Z endstop position set to "none" in the M574 command, and in that case the firmware will not let you home Z unless X and Y have already been homed.

@dc42 said in Time estimates not working:

;E
Just another tidbit I also have a laser filament monitor. I had to double the % count from 92% error to 184% error as everything else has doubled

OK I WILL LOOK INTO ADDING A BLTOUCH

@drammy I'm using the Pi camera module. V2 I believe.

The main config file is in fact "config.g" The movement section was created by adding a commented line ";movement section" followed by the required commands...