Duet Wifi+Duex5 + 5way Diamond + Cura = Need help to finetune config.

dintid

Hmm, after updating firmware, my X axis moves when I Press Y and the other way around?
Edit: Running CoreXY

I've changed nothing in my config and it worked before.

Firmware Electronics: Duet WiFi 1.0 + DueX5
Firmware Version: 1.19RC3 (2017-08-05)
WiFi Server Version: 1.19beta10
Web Interface Version: 1.17+2

Edit 2: I also get this error: Can't open 0:/sys/oem.json to read, error code 4

dc42

If you were using 1.17 or earlier series firmware or 1.18 firmware (not 1.18.1 or 1.18.2) and a Windows operating system, then to get USB working you need to install a newer version of the Windows device driver from https://github.com/dc42/RepRapFirmware/tree/dev/Driver.

Re the X and Y issue, read the upgrade notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.

dintid

@dc42:

If you were using 1.17 or earlier series firmware or 1.18 firmware (not 1.18.1 or 1.18.2) and a Windows operating system, then to get USB working you need to install a newer version of the Windows device driver from https://github.com/dc42/RepRapFirmware/tree/dev/Driver.

Re the X and Y issue, read the upgrade notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.

The drivers thing should really be noted in the upgrade info I just used the latest stable firmware before this, but I havn't used USB since I first got the board up and running, so hard to know.

I have looked in and tried to find anything relevant the notes.. but I havn't been able to find anything in there… got a search string so I can find the relevant info?

Anything on the error I also recieve? Can't open 0:/sys/oem.json to read, error code 4

edit: I can connect now, after driver update, but printer acts odd still - led blinking.

dintid

@dc42:

If you were using 1.17 or earlier series firmware or 1.18 firmware (not 1.18.1 or 1.18.2) and a Windows operating system, then to get USB working you need to install a newer version of the Windows device driver from https://github.com/dc42/RepRapFirmware/tree/dev/Driver.

Re the X and Y issue, read the upgrade notes at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.

Ok, I found the note, ~~but I don't know what to do about it.~~

Important! On a CoreXY machine, if upgrading from a version prior to 1.19beta9, you need to reverse the Y motor direction. Similarly for CoreXZ and CoreXYU machines.

~~If I change M560 P1 and P2 from S1 to S0 they just go the other way, but they X is still moving when Y should move, and the other way.~~
Ok, figured out I needed to jus reverse Y motor.

Please consider when you help people, which you do very fast, don't just link and say "look in this document".. I'll bet most users in here allready did that, but were unable to find anything they thought relevant..
Either tell them the info they need exactly, or at least tell them where to look in the respective document…

In my case you could just have told me to reverse motor Y.. that would have saved a lot

dc42

1. I don't have time to give personalised advice every time, posting links is quicker
2. I want to encourage everyone to read the upgrade notes every time they upgrade firmware
3. There may be something else in the upgrade notes that matters in your configuration, so by making you read them I may have saved you some time.

dintid

@dc42:

1. I don't have time to give personalised advice every time, posting links is quicker
2. I want to encourage everyone to read the upgrade notes every time they upgrade firmware
3. There may be something else in the upgrade notes that matters in your configuration, so by making you read them I may have saved you some time.

I honestly couldn't find the notes at first, but now I know where they are.

About nr. 1)
Problem is not finding the source for info.. most people have read it several times and tried solving a problem for days before asking for help.
The problem is understanding what's in the source. Explaining how something works on component level and then expect people to figure out Gcode commands to match it, goes way above most people's capabilities.

When people specifically say they have read the relevant sources then linking to them again is rather rude.. as it's a non-answer. Same when people say "use Google"
Edit: at least tell them what to look for. In several posts I've written that I have read the page several times and couldn't figure it out… giving me link to same page without any form of help is demeaning - might as well tell me you think I'm rather dumb.

About nr. 2
Sure, in the ideal world everyone read all release notes. In the ideal world people also understood what was written in them.
In the real world however I would recommend doing like Synology does and split release notes into Important notes and Fixed issues. If changes to Firmware updating method or other important system changes (motors now go in reverse) takes place, they should be under Important notes.

About nr. 3
Yes, I understand that, but reading the Release notes is a real chore as most of it is gibberish to me. I skim the notes, which is more than most I guess.
I've always just updated firmware and then go through and look at the GUI to see changes. I always only use Stable, but this time I had to use RC in order to get Volumetric support.

dintid

[h]Solution to use Duet + Diamond Hotend w. firmware retract + Cura[/h]

There are some inherent problems using Cura and Duet

Need to comment out M83 in config.g + Use M82 in cura startgcode.

Adding Diamond hotend and we need more changes:
[h]Firmware Retract and Volumetric[/h]
Now, in order to use Firmware Retract in Cura we need to use either the Ulticode or RepRap (Volumetric) Gcode Flavor in Machine settings.
We can’t use the Ulticode one, as it removes the startup.gcode option and the second one requires Duet to use Volumetric.

Duet only just supported Volumetric extrusion in 1.19RC/Beta, so you need to upgrade firmware if you havn't allready.

Extra special important note: Be sure to read upgrade instructions if using 1.18 or earlier

So, in order to use Volumetric we need to use 1.19 or newer + use the M200 D1.75 gcode in config.g
Firmware retract enabled by using M207 S1.5 F3000

Now it actually all works Extruding manually using web interface after enabling Volumetric extrusion via M200 now extrudes only 4/10 though.. guess it’s to consider a firmware bug.

[h]Summary[/h]

Need to comment out M83 in config.g + Use M82 in cura startgcode. (This is always the case when using Duet with Cura)
Use Duet Firmware 1.19 or newer
Cura - Use RepRap (Volumetric) Gcode Flavor in machine settings - to support Firmware Retract.
Duet Config.g - Enable Firmware Retract using M207 S1.5 F3000 - Diamond hotend retract at 1.5mm is good.
Duet Config.g - Enable Volumetric printign using M00 D1.75

Edited lots of times for readability and stuff

dc42

1. Using M82 in the Cura start gcode is sufficient to make absolute extrusion work.

2. In RC5 I've changed volumetric extrusion to work on a per-input basis. This means that you will need to put the M200 command in your Cura start gcode, because Cura doesn't generate it even when it is set to volumetric extrusion.

dintid

@dc42:

1. Using M82 in the Cura start gcode is sufficient to make absolute extrusion work.

2. In RC5 I've changed volumetric extrusion to work on a per-input basis. This means that you will need to put the M200 command in your Cura start gcode, because Cura doesn't generate it even when it is set to volumetric extrusion.

Also need to remove M83 from config.g unless you changed something in 1.19
But Volumetric works now using RC3. I print just fine now after the changes made as described. Am a bit confused as to what you are saying.
When having configured duet to Volumetric it extrudes 4/10 amount only, when using webinterface? If I comment out the M200 line it works fine, untill I put it back… Seems the Webinterface does not support Volumetric printing?

Current startupcode - disregard the drop-down selection as I am using RepRap(Volumetric).

dc42

Have you tried RC5, and put the M200 command in the slicer start gcode and nowhere else? I find it surprising that Cura doesn't add the M200 command itself.

Nobody else has reported having to remove M83 from config.g to use absolute extrusion, as long as they included M82 in the start gcode