Why I went back to RRF2
-
Hello,
I think you have a scaling issue on the Y axis (the length of the rrf3 part is wrong). the chiron has two different belt pulleys.
Overextrusion is the result.
Greetings,
Vincent -
@rabbit said in Why I went back to RRF2:
Hello,
I think you have a scaling issue on the Y axis (the length of the rrf3 part is wrong). the chiron has two different belt pulleys.
Overextrusion is the result.
Greetings,
VincentAnd you think i dont know that.............. that was taken in account when swapping over the firmware, steps/mm were the SAME between firmwares
-
@CaLviNx
I think your steps/mm (X and Y) are not defined correctly in your RRF3 config. (because of wrong dimensions of your print) -
@CaLviNx
Please post your RRF2 and RRF3 config. Further discussion without true information dos not make sense.... -
@CaLviNx Out of interest, which one is the correct size? I'm assuming it's the top RRF2 one? But apart from the shite quality, there has to be a reason why RR3 comes out so different - even the scale is all wrong.
Yet, there are a few of us on RRF3 who haven't seen anything like that, so it would be useful if you could share your settings. I'm not doubting that you configuration is the same between prints, but it would be useful if we could compare your config.g with our config.g files.
-
@CaLviNx said in Why I went back to RRF2:
I updated multiple Duet-2 Wifi boards and couldnt get prints to complete
In what way did the prints not complete? Did the Duet reset (in which case, did you run M122 to get the reason); or did the extruder jam; or something else?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
You sound much more interested in convincing everyone that "you did the right thing" in reverting to RRF2, than in fixing the issue you ran into.
Maybe it's a bug. But, more likely, it is a mistake that you made.
Instead of telling us how everything you did was perfect, like Trump; post both config files and stop snapping at everyone who is spending their time trying to help you.
-
@CCS86 said in Why I went back to RRF2:
... stop snapping at everyone who is spending their time trying to help
I don't think the OP asked for help. Read his post.
-
@zapta said in Why I went back to RRF2:
@CCS86 said in Why I went back to RRF2:
... stop snapping at everyone who is spending their time trying to help
I don't think the OP asked for help. Read his post.
Yup, I read his post. Check out sentence #1 of my post; I covered that.
This is a forum for people to help each other and share ideas. I really doubt if anyone cares about his justifications for giving up almost immediately. But, a bunch of people cared enough to help him fix the actual problem.
This category specifically is for example prints. This isn't an "example" of how prints come out with RRF3. It is a configuration error, or bug. Both can be fixed with some participation.
-
@CaLviNx, FYI, according to this thread, in a month or so it will be easier to switch to V3.
https://forum.duet3d.com/topic/16326/its-safe-to-move-a-duet-v2-to-firmware-3-x/5?_=1589924880315
-
I moved two printers from 2 to 3.1.1. A delta and a cartesian and had no substantial problems without using the configuration software. I don't think I can see any difference between a part printed in RRF2 versus one printed in 3. I certainly don't see any reason to move back to 2.
-
This post is deleted! -
@DaveA said in Why I went back to RRF2:
I moved two printers from 2 to 3.1.1. A delta and a cartesian and had no substantial problems without using the configuration software. I don't think I can see any difference between a part printed in RRF2 versus one printed in 3. I certainly don't see any reason to move back to 2.
I think you need to look at this exact forum others have reported issues, and even to the point where they are posting they are reverting back to older firmware. And i think if you look even harder there are actual instances for the duet team advising people to revert back.......
-
You sound much more interested in convincing everyone that "you did the right thing" in reverting to RRF2, than in fixing the issue you ran into.
Maybe it's a bug. But, more likely, it is a mistake that you made.
Instead of telling us how everything you did was perfect, like Trump; post both config files and stop snapping at everyone who is spending their time trying to help you.
Why must we get political?? This is the Duet forum not facebook.
-
@luckyflyer said in Why I went back to RRF2:
Why must we get political?? This is the Duet forum not facebook.
What is political about that? I made reference to a human being who constantly tells the world about how perfect he is, and blaming everything besides himself for any shortcomings. I'm talking about character, not political policy.
"what did I mess up", " what could I have done better" are the types of questions we should ask ourselves, if we want to be better makers.
-
@dc42 said in Why I went back to RRF2:
@CaLviNx said in Why I went back to RRF2:
I updated multiple Duet-2 Wifi boards and couldnt get prints to complete
In what way did the prints not complete? Did the Duet reset (in which case, did you run M122 to get the reason); or did the extruder jam; or something else?
What happened in every other case apart from the print I showed, is that at various random times the print head would try to dive itself back into the print which would lead to the the z axis complaining and me hitting the emergency stop button, So I didn't even consider doing a M122. The one time I did do a M122 the only info I got is that the board reset with no reason given.
And as someone noticed the Y axis steps/mm didnt seem to be correct this I played with and didnt get any resolution with some odd number of steps being required to get it anywhere near correct but then on another print the steps/mm value would require to be changed again
In the beginning I was not thinking it was a firmware issue (I was convinced it was dodgy SD cards) coming to the conclusion that the firmware could be an issue issue was the LAST step.
The work you and the core guys here do is sterling, and as I tried to allude to in my initial post this is not a bash RRF3 firmware or Duet3d in any way (no matter how much some of the little girls in here seem to have gotten their panties in a bunch) I have a total of 18 duet equipped machines, I will only ever fit Duet and NOTHING else.
And For clarity, the test printer in question (an Anycubic Chiron) has had a duet 2 wifi installed for nearly 2 years and after its initial setup it has been a "press print & forget it" machine for all of that time on RRF2.
-
@CCS86 said in Why I went back to RRF2:
What is political about that? I made reference to a human being who constantly tells the world about how perfect he is, and blaming everything besides himself for any shortcomings. I'm talking about character, not political policy.
You may intended to discuss Trump's character but instead you revealed yours.
-
@zapta said in Why I went back to RRF2:
@CCS86 said in Why I went back to RRF2:
What is political about that? I made reference to a human being who constantly tells the world about how perfect he is, and blaming everything besides himself for any shortcomings. I'm talking about character, not political policy.
You may intended to discuss Trump's character but instead you revealed yours.
If you get offended that easily, I wish you the best of luck, sir.
-
Moderators .... could we please lock this thread and stop with the negativity please ?
-
@jens55 said in Why I went back to RRF2:
Moderators .... could we please lock this thread and stop with the negativity please ?
Yikes. Consider it locked! I take a day to do some yard work and y'all turn to hooliganism!
