RepRapFirmware 3.0
-
That last build does not move the extruder for me on a CR-20. I checked by moving the extruder motor to X and was able to move it. Downgrading to 2.03RC2 (what I ran previously) fixed the extruder.
I am pretty sure that nothing in my config.g needs changing, but maybe I overlooked something in the wiki. See attached file.
-
@oliof you did have the nozzle heated didn't you?
-
Yes, this was with a heated nozzle -- DWC showed extruder moves in the UI, but the motor was not moving and there was no error regarding attempting to extrude with a cold nozzle. And even enabling cool extrusion (with filament removed) with
M302 P1
did not allow the extruder motor to move. -
@oliof just checking as it is a common mistake but not valid in this case
-
@dougal1957 it's absolutely fair to ask (-:
-
Was the extruder motor connected directly to an output on the Duet?
-
Yes, to output "E0" on the duet wifi board.
-
Sane for me. Just loaded latest 3.0 and modified my m558 as I use fsr’s on endstop e0. Motion control all fine as is bed and nozzle heat bur the extruder E0 will not extrude or retract. Its at temperature.
-
Same here using RepRapFirmware 3.0beta3 (2019-05-16b1) . In my case I have two tools (two extruders and one heater). The following is the configuration of my TOOLS section:
;_____ TOOLS M563 P0 D0 H1 ; Define tool 0 to use extruder drive 0 and heater 1 G10 P0 S0 R0 X0 Y0 ; set tool 0 temperatures and offsets M572 D0 S0.1 ; Pressure advance enable for extruder 0 M563 P1 D1 H1 ; Define tool 1 to use extruder drive 1 and heater 1 G10 P1 S0 R0 X0 Y0 ; set tool 1 temperatures and offsets M572 D1 S0.1 ; Pressure advance enable for extruder 1
None of the tools would move, neither with temp nor forcing cold extrusion with
M302
-
Run M584 and check whether the extruders are mapped to drivers 3 and 4.
-
@dc42 Yes they are mapped to drivers 3 and 4. The result of M584 is : Driver Assignments X0 Y1 Z2 E3:4, 3 axes visible.
-
Thanks, I will look into it.
-
Hello, I have a single extruder configuration. I just tried to install the RepRap firmware 3 and I had had the same problem, no way to move the extruder motor.
-
I will do a new RRF3 beta release next week. I need to do another 2.03RC release first.
-
I am planning a new build of RRF 3 later this week, incorporating the recent improvements in RRF 2.03RC3. Meanwhile, I think you can probably get extrusion working if you use M584 to assign extruder drives explicitly. Although M584 appears to shows the correct extruder drive mapping by default, in reality the extruder data has not been set up fully.
-
@veti said in RepRapFirmware 3.0:
@dc42 said in RepRapFirmware 3.0:
The current plan is 30V or perhaps 36V. It's difficult to find 5V buck regulator chips that accept higher than 40V input.
why not says that for input above 30V the 5V line has to be supplied via the ext 5V?
I think that the board could have separate V_MOT and V_IN terminals.
The V_MOT could accept higher voltage which would go solely to the motor drivers.
The V_IN could accept 25-30V max as you will probably need 12/24V for the hotends or fans anyway, or for other automation purposes in CNC. This is how I usually do in custom machines I design.Those who don't need higher voltage or anything special just have to connect the V_MOT and V_IN parallel, those who need it could use two power supplies.
-
@dc42 Sorry for my confusion but if you (or anyone) could help me I would appreciate it. I just got the delta endstops and homing working but I do have 2 things remapped. My bed heat SSR's are connected to E1 and my part fan is connected to H0.
I managed to get the part fan working with:
M950 F0 C"bedheat" Q25500Autotuned the hotend but the bed is the problem.
For the bed I am trying:M140 H2 (without this the thermistor shows 2000 in web)
M950 H0 C"e1heat" Q10And when I try autotune I get:
M303 H0 S110
Error: heater 0 reported error 'unknown temperature sensor channel' at start of auto tuningThe web interface shows the bed temp
What am I doing wrong?
-
A little further testing.
M950 H2 C"nil"
M950 H0 C"e1heat" Q10Sending "M950 H0"
I receive "Heater 0 pin e1heat, frequency 10Hz"However the bed temp in the web interface shows 2000 with the thermistor plugged into either the board bed heat or E1 spots.
-
Nevermind, I went back through this thread and found that I needed to explicitly release all 3 pins before remapping.
M950 H0 C"nil"
M950 H2 C"nil"
M950 F0 C"nil"
M950 H0 C"e1heat" Q10
M950 F0 C"bedheat" Q25500Now when I plug the bed thermistor into the standard bed heat jack it reports in the web interface and bed heat appears to work.
-
@dc42 as you know, I've pointed a number of issues around implicit logic vs explicit logic and my desire for there to be no implementation of implicit logic because it is not possible for an opinionated system to fit everyone's needs without requiring extra work by anyone who doesn't use the majority case.
I've been thinking about this after reading some of posts on this thread that demonstrate the coming complexity and others that propose implicit logic. That seemed like a bad idea, at first...
I have the beginnings of a concept, but not a concrete example yet. Maybe I can do a sufficient job in conveying my concept.
Some observation: I know the board is a CNC board. It is controlled by g-code. The current complex behavior co-opts g-code for the purpose of configuration.
Some opinion: I believe not all configuration should be in g-code. Assigning pins, for example. These are lower level than other configs because they change how the board presents itself to the things connected to it as well as what connection contract it's expecting.
I was thinking that since there is added complexity, a tiered configuration may make more sense.
My idea is to have personalities.
- 5-axis CNC
- 3-axis CNC
- CoreXY printer
- H-bot printer
Etc.
I think this separation cleans up the organization and presentation of configuration. It also allows for MORE implicit logic.
It'd be awesome to go to https://configurator.reprapfirmware.org/ and have a choice to pick from these personalities to begin the process and you input the high level configuration that seems appropriate for g-code like dimensions, tools, etc. All of those configs actually depend on the lower level config.
This would allow for a more concise g-code that isn't polluted with things that machine itself doesn't care about once it's personality is set.