New firmware 2.03RC2 available

minim

Anyone having issues with babystepping not working? On rc2 with dwc 1,23/2.0 and I can't step down but I've never tried on the stable. Will roll back after this print and check.

Edit: just read that M208 is stopping it from going below Z0. What a strange limit to have. Well then it's not a firmware issue atleast since I have M208 set to Z0.

ben_van

@dc42
Just did a few tests..
Everything works as expected for G0 moves if the feedrate set in M203 is higher than 60mm/min. If I set the max feedrate lower than 60mm/min in M203 for any axes, G0 moves will still request a speed of 60mm/min.
Setup:

Duet 2 Wifi
Web control 2.0.0-RC6
Wifi server 1.23
PanelDue 7.0i 1.23.2

Config.g is as follows:

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Network
M550 P ; Set machine name
M552 S1 ; Enable network
M587 S"" P"" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards

M350 X256 Y256 Z256 I0 ; Configure microstepping without interpolation
M350 E64 I1 ; Configure microstepping with interpolation
M92 X3769 Y2094 Z256000 E53 ; Set steps per mm //// XY:mm, Z:mm, E:ul

M566 X45 Y45 Z3 E200 ; Set maximum instantaneous speed changes (mm/min)
M203 X2500 Y2500 Z20 E10000 I1 ; Set maximum speeds (mm/min), and I (minimum speed)
M201 X2000 Y2000 Z10 E2000 ; Set accelerations (mm/s^2)
M906 X500 Y500 Z500 E500 I75 ; Set motor currents (mA) and motor idle factor in per cent
M84 S60 ; Set idle timeout

; Axis Limits
M208 X-75 Y-48 Z-30 S1 ; Set axis minima
M208 X0 Y0 Z0 S0 ;Set axis maxima

; Heaters
M140 H0 ; heater 0 is the bed
M305 P0 S"Vessel heater" T100000 B3950 R4700 C0;
M307 H0 A26.6 C73.9 D1.0 B0 S0.2 V12.6 ; set process parameters for heater 1, use PID, and limit heater 1 PWM to 20%
M143 H0 S45 ; Set temperature limit for heater 0 to 50C

; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0.5 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 S0.5 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Automatic saving after power loss is not enabled

; Custom settings

M106 P0 I-1 ; Disable the Fan
M106 P2 I-1 ; Disable the Fan
M452 P22 R255 F8000 ; Set the printer into Laser mode P(Fan) R(Max power value for S command with M3) F(PWM frequency used)
M564 S1 H1 ; H0 allow movement before homing, S1 limit motion between axis boundaries
M574 X2 Y1 Z2 S0 ; Set active low endstops (for some reason never set z properly in configuration

; Tools
M558 P0; disable the z probe
M563 P0 S"Laser"
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
G10 P0 X0 Y0;

M563 P1 S"Camera"
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
G10 P1 X-1 Y-0.6;

M563 P2 D0 S"Extruder" ; Define tool 2
G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C
G10 P2 X0 Y0 ; Set tool 2 axis offsets

T0 ; Select tool 0 (laser) on startup

wilriker

@ben_van said in New firmware 2.03RC2 available:

I spotted to minor issues that have nothing to do with your minimum-speed-issue though:

M350 E64 I1         		      ; Configure microstepping with interpolation

Duet Wifi's TMC2660 only support interpolation with x16 microstepping. The above command won't do any harm but it will be "only" at x64 microstepping and won't be interpolated to x256.

M563 P1 S"Camera"
G10 P0 R0 S0                 ; Set initial tool 0 active and standby temperatures to 0C
G10 P1 X-1 Y-0.6;

There is a typo or copy-and-paste error in the middle line of this block. You define tool 1 but the middle line is still for tool 0.

ben_van

@wilriker Ah thankyou for pointing this out. The G10 for tool 1 was a typo from copy/paste. I guess I never noticed since i don't have any heaters bound to the tool anyway. As for the M350 extruder microstepping, I will change to the following:
M350 X256 Y256 Z256 E256 I0
Not sure why I didn't have it written like that before..

gavatron3000

@dc42 the m291 isn't unlocking a tool change still when called. Or is this impractical to do within a tool change?

dc42

@ben_van said in New firmware 2.03RC2 available:

As for the M350 extruder microstepping, I will change to the following:
M350 X256 Y256 Z256 E256 I0

We don't recommend using native x256 microstepping. You will be limited to low speeds if you do, because generating the step pulses will use up too much processor time. It may be OK for a CNC machine, but not for a 3D printer.

ben_van

@dc42 said in New firmware 2.03RC2 available:

@ben_van said in New firmware 2.03RC2 available:

As for the M350 extruder microstepping, I will change to the following:
M350 X256 Y256 Z256 E256 I0

We don't recommend using native x256 microstepping. You will be limited to low speeds if you do, because generating the step pulses will use up too much processor time. It may be OK for a CNC machine, but not for a 3D printer.

I understand the computational expense of doing this.. going fast is the last thing i want Most of the stuff made with this machine is seldom larger than 1mm, at speeds less than 50mm/min, and we have never experienced speed issues being limited by the CPU. This doesn't solve the G0 problem though..
To give you an idea of why this matters, here is a sample pic of one of the things we can do with this machine + duet . It's too small to see properly with the naked eye.

jv43

@ben_van looks interesting, but what the heck is that?

ben_van

@jv43 said in New firmware 2.03RC2 available:

@ben_van looks interesting, but what the heck is that?

It is a generic 2D scaffold used for cell culture. Tissue engineering is not my field of expertise but for the people I am working with it is. This is just a test print to show we are working on a scale smaller than that of a stem cell, and about the size of a T-cell.
Cells are present while this structure is printed and are encapsulated inside the bio-compatible gel, where they then grow/multiply inside it, as it is like food for them. I like to think of it like bread crumbs, where we can coax the cells to grow and develop in a very controlled manner.
Whilst i can't dive into many specifics of how everything works until something is published, I can say that we have been getting some very good results
The benefit of using all open source software is once the groundwork is in place for this method, we can easily use readily available 3D printer slicers to make any micro 3D structure straight from a CAD model, and hopefully be able to provide this to people wanting to experiment without the $100k+ pricetag that comes with anything with the word 'bio' in it.

deckingman

@ben_van Fascinating stuff. Out of curiosity, are you using "standard" 1.75mm diameter filament? I've always thought that to extrude tiny amounts of filament, the way forward is to use something that has a much smaller cross sectional area to start with.

ben_van

@deckingman said in New firmware 2.03RC2 available:

@ben_van Fascinating stuff. Out of curiosity, are you using "standard" 1.75mm diameter filament? I've always thought that to extrude tiny amounts of filament, the way forward is to use something that has a much smaller cross sectional area to start with.

I didn't mention that this machine doesn't use filaments. It uses a tightly focused laser (we can easily change the dot size) to solidify tissue-like gels that are synthesised with certain proteins etc. It is somewhat similar to a traditional SLA machine but with differences in the layering methods.
Extruding filaments to that size would be cool though, and i definitely agree with you there. Other than there not being much of a demand for printing such small things, maybe filaments with such small diameters would just be too fragile..

dc42

@ben_van said in New firmware 2.03RC2 available:

Just did a few tests..
Everything works as expected for G0 moves if the feedrate set in M203 is higher than 60mm/min. If I set the max feedrate lower than 60mm/min in M203 for any axes, G0 moves will still request a speed of 60mm/min.

I found the problem. M203 enforced a minimum movement speed of 1mm/sec. Fixed in 2.03RC3.

I also found that DWC 2.0.0-RC5 rounds up the displayed top speed to the nearest 1mm/sec. So it displays 1mm/sec even when the actual speed is 0.5mm/sec.

dc42

@lb said in New firmware 2.03RC2 available:

Now somebody wants to print somewhere else on the table (on the same or new fabric). Instaed of just updating G55 in x&y for positioning the print (or doig an shift/offset in the the slicer), because of getting in a lazy fashion the printhead out of the way, the person just homes x e.g., THEN: Not only is the printhead moving in x only - as one would suspect and as it does usually with standard-homing after powering up - BUT (I think because of the delta between G54 and G55 in X&Y) it makes a diagonal move of the amount in X & Y AND if that offset was very big, this is of course a big diagonal move I do not understand AND it ignores only on that move totally any endstop? What am I doing wrong? Should I open a diffrent thread and post all homing and config files?

I have fixed a similar-sounding issue in 2.03RC3. Please try it when I release it.

gavatron3000

@dc42 did you see my post above regarding m291?

dc42

@gavatron3000 said in New firmware 2.03RC2 available:

@dc42 did you see my post above regarding m291?

There is a problem in supporting M291 commands that require acknowledgement or allow axis movement within tool change files. If the tool change command is sent from DWC or PanelDue, then RRF is executing that command for that channel until the tool change is complete. That means that it cannot execute an axis jog command or M292 acknowledge command that comes from the same channel as the tool change command. This is what causes the firmware to lock up in the tool change. If you send M292 from another device, it continues.

gavatron3000

ok no worries are we able to support it at the end of tpre and tfree instead?

dc42

@gavatron3000 said in New firmware 2.03RC2 available:

ok no worries are we able to support it at the end of tpre and tfree instead?

Not easily, because the tool change sequence isn't complete until tpost has completed.

dc42

I've just released firmware 2.03RC3 so I am locking this thread.