Firmware 1.19RC5 released - last chance to report issues

deckingman

@Dougal1957:

David would it help if I sent you a diamond hotend ( I have one I bought but unlikely to use dont have the heatsinks for it tho)

I've got a spare I could lend you as well - in fact I have all the components to make a complete 3 colour Diamond (nozzle, heat sinks, and insulator) apart from heater and thermistor. Send me an email if you want me to post it to you.

dc42

Thanks, both of you. There is a SCARA printer kit on its way to me, and perhaps that may be able to be modified to accept a Diamond. I don't think either of my existing printers (Ormerod and large delta) could handle the size of a Diamond.

TYPPA Albert Einstein

@dc42:

@TYPPA:

M292 BUG
if set Z0 appear the jog control ,also is set Z1 ?
Thanks David for all time devoloper this FW
Giorgio

All Z motors are always moved together, except in the special case of using multiple independently-driven Z motors to perform bed leveling.

sorry David is my error on typing !!!
M291: Display message and optionally wait for response
The parameter Z0 also the Z1 visualize the jog on message box

deckingman

@dc42:

Thanks, both of you. There is a SCARA printer kit on its way to me, and perhaps that may be able to be modified to accept a Diamond. I don't think either of my existing printers (Ormerod and large delta) could handle the size of a Diamond.

Could you simulate it? By that I mean just hook up 3 extruder motors and do an air print. I could probably supply a gcode file and config file that'll demonstrate the problem.

Kulitorum

RC5 seems to be ok for me.
Where do I find the debug information? - I see no difference in the console when enabling debugging for all modules.

Regarding the requested tool change gcode, here you go:

G1 X116.118 Y109.931 E5.6070
G1 X119.931 Y106.118 E5.8007
G1 X116.537 Y106.118 E5.9226
G1 X116.118 Y106.537 E5.9439
G92 E0
G1 E0.0000 F600
G1 Z1.280 F9000
; process Tool 0
; layer 8, Z = 0.780
G1 z0.780
T0
; tool H0.200 W0.480
; inner perimeter
G1 X115.720 Y125.720 F4500
G1 Z0.780 F9000
G1 E0.0000 F600
G92 E0
G1 X134.280 Y125.720 E0.6667 F2250
G1 X134.280 Y144.280 E1.3334
G1 X115.720 Y144.280 E2.0001

dc42

Debug info is sent to the USB port only.

dc42

Kulitorum, thanks for your feedback. I'll assume that the slow homing issue you reported with a previous RC is fixed now.

Nobody else has reported any issues with RC5, so I'll assume that no news is good news. Expect a 1.19 release in the next day or two.

sigxcpu

OK, I am ready to try again 1.19, but I fail to find "the important upgrade notes". There are references in "what's new" page, but there is no actual link.

Kulitorum

Is there any way to set the speed of a G1 P1 command?

T3P3Tony

@sigxcpu:

OK, I am ready to try again 1.19, but I fail to find "the important upgrade notes". There are references in "what's new" page, but there is no actual link.

its here:

https://duet3d.com/wiki/DuetWiFiFirmware_1.19beta

Kulitorum

Also, any positive movement with my U axis, with S1 defined ignores any F data and just runs at full speed. RC5

dc42

@sigxcpu:

OK, I am ready to try again 1.19, but I fail to find "the important upgrade notes". There are references in "what's new" page, but there is no actual link.

Upgrade notes are always in the WHATS_NEW file in the root of my RepRapFirmware github repository, as linked to in the first post in this thread. If you look past the list of new features (which is rather long for this release) and the list of bug fixes, you will find the upgrade notes.

dc42

@Kulitorum:

Is there any way to set the speed of a G1 P1 command?

The P parameter is just a modified for the G1 command, so the speed of movement is set by the F parameter as usual.

dc42

@Kulitorum:

Also, any positive movement with my U axis, with S1 defined ignores any F data and just runs at full speed. RC5

Can you confirm that you have a space character in the command string immediately before the letter F ?

DjDemonD

I don't know if it helps but the issue I reported under RC1 (in that thread) on my corexy with the duet board crashing and trying to send information to the USB was still happening earlier today. I upgraded to RC5 and it is working normally. Many thanks for all the hard work.

dc42

Thanks for the feedback! Good to know that it is fixed.

Kulitorum

Yes, there is a space.

U at 211:
G1 U300 F100 S1

https://www.youtube.com/watch?v=Zy6cDdJbkhY

sigxcpu

@dc42:

@sigxcpu:

OK, I am ready to try again 1.19, but I fail to find "the important upgrade notes". There are references in "what's new" page, but there is no actual link.

Upgrade notes are always in the WHATS_NEW file in the root of my RepRapFirmware github repository, as linked to in the first post in this thread. If you look past the list of new features (which is rather long for this release) and the list of bug fixes, you will find the upgrade notes.

That is what happens when you read the first two paragraphs of that huge page

Did the upgrade, everything looks fine. No real print yet (CoreXY 300x300x300)

dc42

@Kulitorum:

Yes, there is a space.

U at 211:
G1 U300 F100 S1

https://www.youtube.com/watch?v=Zy6cDdJbkhY

I still can't reproduce this. Please can you give me the exact sequence you are using from power on to make this happen.

There are a few things not quite right with your config and homing files, although I don't think they are relevant to this issue, but please try them anyway:

In your M574 command in config.g you should have U2 not U1 because the U endstop is at the high end
In your M208 S0 command the U parameter should be the point at which the endstop switch triggers
The G1 S1 commands in your homing files should be executed in relative mode. For example, homex.g:

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Wed May 17 2017 18:05:05 GMT+0200 (Romance Daylight Time)

; Lift Z relative to current position
G91
G1 Z1 F6000

; Move quickly to X axis endstop and stop there (first pass)
G1 X-255 F3000 S1

; Go back a few mm
G1 X5 F3000

; Move slowly to X axis endstop once more (second pass)
G1 X-10 F360 S1

; Lower Z again
G1 Z-1 F6000
G90

Homeu.g:

; homeu.g
; called to home the U axis
;
; generated by RepRapFirmware Configuration Tool on Wed May 17 2017 18:05:05 GMT+0200 (Romance Daylight Time)

; Lift Z relative to current position
G91
G1 Z1 F6000

; Move quickly to X axis endstop and stop there (first pass)
G1 U370 F6000 S1

; Go back a few mm
G1 U-5 F6000

; Move slowly to X axis endstop once more (second pass)
G1 U10 F360 S1

; Lower Z again
G1 Z-1 F6000
G90

[Edited the above to make somie corrections to homeu.g]

You don't need the G92 commands as long as you have set the U axis maximum in your M208 command to the point at which the switch triggers.

Also the zip file you provided had an old version of iap4e.bin in it.

Kulitorum

I applied your changes, and it made no difference.

So I made a test.gcode file with one line:

G1 U400 F2000 S1 ; test

And when I "Emergency stop" and print that file, it runs at full speed.

But when I "Emergency stop" and paste the same line "G1 U400 F2000 S1 ; test" into "Send Gcode" field in the top left of the web interface, it runs at the requested speed.

Until I press "-100" for the U axis (executes correctly) and then press "Send" again - then it runs at too high speed.

I hope this makes sense.