Can't run pressure advance g-code

jay_s_uk

@gbartsch drives for extruders start at 0 so even though you have driver 3 mapped to the extruder, it's the first extruder driver and is therefore D0

gbartsch

@jay_s_uk Thank you. I'll run through this again using D0.

gbartsch

Well, I've run the g-code numerous times with small to extreme levels of pressure advance to no effect. I've put a line in my filament g-code with no effect. I give up for now.

oliof

@gbartsch you could use https://ellis3dp.com/Pressure_Linear_Advance_Tool/ before giving up, that tool generates the ramp up of PA values itself and it works really well IMO.

gbartsch

@oliof Thank you. My firmware is 2.04 (2019-11-01b1) so am not sure if it can work. I ran the print but could see no variance in the pattern. I used a natural PLA because that was in the machine so couldn't get a decent picture. I'll change to an opaque filament and run it again and post a picture.

Phaedrux

Why such old firmware?

gbartsch

This is the result of the pressure advance test. I see no variation. Maybe my firmware is too old for this script to work?

gbartsch

@Phaedrux I'm clueless and not sure I could upgrade it without goofing something up. My friend set up my Duet and has moved away so I'm still using this. It's been working so I haven't needed to upgrade so far but it seems I should learn how.

Phaedrux

@gbartsch No reason to update firmware if you're still happy with how it's running. But if you do decide to give it a try, start a new thread and we'll be happy to help you along.

If the script isn't doing it for you I would try the living tuning method. Plop a cube down in the slicer and stretch it out in one axis so you have a long flat rectangle with rectilinear infill. Then start the print and manually send the gcode command to enable PA and send a new value to increase it and see how it changes.

Unless you have a very long bowden setup even a small amount of PA is better than no PA. Somewhere in the 0.02 to 0.04 range is probably going to be usable on a direct drive or short bowden.

gbartsch

@Phaedrux Thanks a lot! I'd really appreciate help with upgrading the firmware. I'll look into the procedure and then likely make a post with some questions.

I printed this shape at 60mm/sec and manually sent codes from M572 D0 S0.025 to M572 D0 S0.085. I don't see any difference in the seam.

Phaedrux

@gbartsch said in Can't run pressure advance g-code:

I'll look into the procedure

this is what I usually tell people.

If you still have access to DWC. Upload these zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zip

That will get your firmware and DWC up to date.

You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3
https://docs.duet3d.com/en/User_manual/Reference/Gcodes

gbartsch

@Phaedrux Thanks! I'll read the sources you suggest.

So this is incremental upgrade method is used because the firmware is so old? But you don't recommend I do that?

I should use the configurator and skip the above steps?

I'm wondering if I could use a file compare tool (I use Beyond Compare) to look inside new versus old files? That might help with finding settings that need to move over?

I have a disability so will have to wait for someone to help me remove/re-insert the MicroSD card so I can backup my current config.

Phaedrux

Uploading the zip files is usually a pretty quick and easy way to get up to date if you already have a working board. The fallback would be to use bossa to flash the firmware directly, but then you also have to manually place the correct files and update the DWC files manually. The zip file upload just takes care of everything for you.

You would still need to use the config tool to generate a new config file set that would work with RRF3. You would need to know the details of your printer setup before hand to make it easier. If you uploaded your current files it would be possible to provide you with a basic config set.

You don't need to remove the SD card to create a backup of the config files on the card since you can download them from DWC, but having a full copy of the card contents is always a good idea anyway.

gbartsch

@Phaedrux Ah! OK, this is starting to make a little sense. Now I am getting intrigued and would like to upgrade the firmware so my machine would the have the newest version of firmware and DWC and learn to how to do it.

Because this is off-topic from the pressure advance question should I do as you suggested and start a new thread? I really appreciate you being willing to help me. I'm sure if I can learn, anyone could and such a thread might be useful to others.

Phaedrux

Sure you can start a new thread. Include your config.g and homing files. Go through the config tool and try and create a new config set and include that as well and we can compare to see how far off it is.

https://configtool.reprapfirmware.org/Start

gbartsch

@Phaedrux Thank you! I will get started soon.

tas

@gbartsch My turn to apologize for being tardy.

Your sample prints definitely have no pressure advance happening at all.

If your extruder jerk setting is too low it can limit Pressure Advance ability to function. Maybe that is what is happening.

Duet3D Documentation

Check the 'Side effects of Pressure Advance' section at the bottom of the page.

Pressure Advance was working for 2.04 as far as I can remember but I still think it is worth upgrading as @Phaedrux suggested. You do have to do it in the order he suggested.

Do post your config to get it checked before trying to print with the new firmware. There are a few significant changes. If only I had written them down.

gbartsch

@tas said in Can't run pressure advance g-code:

If your extruder jerk setting is too low it can limit Pressure Advance ability to function. Maybe that is what is happening.

Thank you!

Well that might be the problem as my jerk is lower than default even. My machine is the Cartesian style with heavy X and Y movements so I lowered the jerk to reduce shaking. I'll increase it and run the test.

M566 X800.00 Y800.00 Z24.00 E300.00     ; set maximum instantaneous speed changes (mm/min)

gbartsch

@tas said in Can't run pressure advance g-code:

Do post your config to get it checked before trying to print with the new firmware. There are a few significant changes. If only I had written them down.

I posted my config.g files in my firmware post (https://forum.duet3d.com/topic/31263/idiot-s-guide-to-upgrading-duet-firmware/10) and am looking at the differences. There are a number of them and I'm gathering that sorting them out will be the trickiest part of upgrading firmware; the other steps seem easy.

tas

@gbartsch I have set my max E jerk to 3000. I also had it at 300 to begin. I have an E3D V6 on a Creality Ender 5 Pro x-carriage with an LGX Lite bowden setup.

Setting the max to a high value does not force it to use that setting it simply allows it to go that high if the gcode commands require it.

This should not affect the X and Y. The M566 parameters are per axis so E only affects extruder jerk. It shouldn't make your printer shake.

It would be great if that change can solve your problem.