Now that RC2 is released I am closing this topic. I moved the post by @carlosspr to the RC2 thread.

Thank you, I think I have it figured out now, trying out a test print

@dc42 said in New experimental firmware 2.0beta3 available:

Have you checked that the power connections are still tight?

Have you tried the 2.0RC1 release and the new DWC?

Yes, the power connection were checked fairly recently.

I will try the new releases.

@wilriker said in Fan tachometer input:

Maybe a stupid question or something I missed in the wiki but how do you even connect the signal wire when there are only two pins for fans in the first place?

The fan tacho output can be connected to PB6 on the expansion connector via a diode (cathode to tacho output). It will only work reliably if used with a 4-wire PWM-controllable fan.

See https://duet3d.com/warranty.

You can check my configs here:
https://github.com/zen/zHevo

This branch contains experimental configuration with BLtouch
https://github.com/zen/zHevo/tree/bltouch

I'm till testing it, a lot of problems with the clone. If you have questions just let me know.

See the upgrade notes for version 1.20 at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.

My mistake.
I had re-wired the z-probe from the smart effector to the Duet wifi and had swapped the gnd with the mod by accident.
It seems fine now.
Sorry for the incovince.

/Quadcells

I am closing this thread because 2.0beta3 is now available. See https://forum.duet3d.com/topic/5120/new-experimental-firmware-2-0beta3-available.

@dc42

Just an update, you are legitimately and objectively awesome. We got it to work!

Just to try to help people in the future who have this same problem, in your config file, make sure to set the axis mins and max, otherwise it won't be able to move in the direction where the mins and max aren't defined.

We also set our X axis offset at 50 as a test, but the first print sometimes the X axis won't do the offset, but after redoing the same print file, the X axis offset will work so I think it has to do with the same problem. Will report back with an update

@spodeopieter said in No communication after erase button pressed:

3.3 v rail seems good , the SAM chip is getting a little hot , around 40 degrees , the esp is ice cold.

Just another thing I noticed , if I press the erase or reset button , nothing happens , no flashing of any LED's

The SAM shouldn't get hot if it's just waiting to be flashed. Perhaps it is faulty.

Once the chip is erased and waiting to be bootloaded, I wouldn't expect the Erase or Reset buttons to flash any LEDs.

It's possible in theory to program the processor via the PanelDue port (and for the same reason, having a PanelDue connected might interfere with programming over USB, although in practice it doesn't seem to). You would need Bossa or SAM-BA and a serial-to-UART converter with 3.3V signal levels.

@flippnswitchez On a CoreXY swapping the motors reverses an axis. There are 8 combinations:

Motor 1 Motor 2 X Motor forward Y Motor forward X Motor forward Y Motor backward X Motor backward Y Motor forward X Motor backward Y Motor backward Y Motor forward X Motor forward Y Motor forward X Motor backward Y Motor backward X Motor forward Y Motor backward X Motor backward

One of these combinations will always result in a left handed cartesian system. The other combinations will result in either a right handed cartesian system, reversed axises, or swapped axises. The exact setup you need depends on your motor location, wiring, and possibly belt routing.

For reference you ultimately want a left handed cartesian system. This is important because a right handed system will print things backwards, this isn't a problem 90% of time but is maddening 10% of the time. The correct cartesian co-ordinate system looks like this:

0_1523851005936_Cartesian System.png

Purple is the location of my end stops so they are configured for X min, Y max and in my homing files I tell the printer to "home" to back-left corner.

@kosh271 You need to select the heaters to monitor on the last page if you want to use thermostatic control. But I agree it would be better if the config tool generated an error if thermostatic control is turned on but no heater is selected. I'll have a look at this.

@snowcrash thanks for your kind words.

I believe it already is. On the General page select Firmware version 1.20 or newer.

@ivang glad you got it sorted!

RRF 2.0beta 1 has now been released. Please post further comments and feedback in the thread I have created about that release, https://forum.duet3d.com/topic/4871/reprapfirmware-2-0beta1-available.

Many thanks. The issue was I was using Pronterface which was as you said sending capital letters. Changed to YAT and worked fine.

I could not have done this without your help.

Many Thanks once again.

@BPisLife:

Ok, thanks for confirming I am not the only one coolice. Phaedrux, that link doesn't work.

Sorry about that. Bad timing. It should work now.

Yes, that should have been picked up by visual inspection. I believe the batch that has just started shipping was tested with firmware 1.21, so in future that would be picked up during testing.