Last few days for reporting bugs in 1.19 beta firmware


  • administrators

    I aim to release firmware 1.19 within the next week. So you have only a few days left to report bugs in 1.19 beta firmware before the code freeze.

    • If there is a bug in firmware 1.19beta11 that you would like fixed, please report it here unless it is already listed below.
    • If there is a bug in an older 1.19beta or in 1.18.2 that you would like fixed, please check whether it is still present in 1.19beta11 before reporting it.

    The final feature enhancements to firmware 1.19 will be:

    • Support for the Duet3D filament sensor
    • Code for homing refactored and managed by the Kinematics classes. SCARA homing supported.
    • Support for an additional SX1509B-based expansion board to provide additional I/O pins
    • Support for binary file uploads via USB

    The bug investigations currently on the list for possible resolution in the 1.19 release are:

    • A report that G10 tool Z offsets still don't work
    • A report of an invalid JSON response being returned, causing the web interface to disconnect
    • A report that M999 sent from the web interface after M112 doesn't always reset the printer
    • [ADDED] If a pause is initiated while a macro invoked by the SD card file being printed is executed, the firmware has to be restarted
    • [ADDED] If a delta or SCARA printer reports an impossible XYZ position, the web server disconnects with an AJAX error

    I am also aware of two issues affecting WiFi, which I aim to fix in a subsequent version of DuetWiFiServer:

    • When the wifi module is configured as an access point using M552 S2, it fails to respond to clients
    • The automatic reconnect that is supposed to occur if connection to the access point is lost may not be working


  • Not sure if Web Interface bugs supposed to be reported here. I'm currently away from home, but there is a bug with the web interface if you turn on "show all successful g-codes" or something like that and "use html5 style notifications". It seem to append newer notifications to older ones instead of showing just latest notifications.
    Easiest way to reproduce is to issue M122 and then just refresh web interface (it will show M122 report again).
    I also have "auto-hide notifications" option on, not sure if relevant.


  • administrators

    @zlowred:

    Not sure if Web Interface bugs supposed to be reported here. I'm currently away from home, but there is a bug with the web interface if you turn on "show all successful g-codes" or something like that and "use html5 style notifications". It seem to append newer notifications to older ones instead of showing just latest notifications.
    Easiest way to reproduce is to issue M122 and then just refresh web interface (it will show M122 report again).
    I also have "auto-hide notifications" option on, not sure if relevant.

    So you mean you get multiple notifications instead of a single one? That has been the default behaviour for older notifications too, but nobody has complained about it yet. HTML5 notifications are only used when the web interface is not visible.

    If you get duplicate notifications with the same content I guess you are either using multiple devices or your IP address changes frequently. Is that the case?



  • I'm having some quirky and unnerving behavior in 1.19beta11 when I switch tools on my diamond hot end delta. Sometimes the printer will quietly switch without any retraction and sometimes it makes alarming noises while it retracts and extracts back and forth violently and very quickly. I'm not sure why it does one or the other. My tools definitions are as follows:

    ; Tool definitions

    M92 E60.28:60.28:60.28 ; Set extruder steps per mm
    M207 S3.75 F3000 ; set firmware retraction
    M563 P0 D0:1:2 H1 ; Define tool 0
    G10 P0 X0 Y0 ; Set tool 0 axis offsets
    G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
    M568 P0 S1 ; Enable mixing for tool 0
    M567 P0 E0.90:0.05:0.05 ; Set mixing ratios for tool 0 (90%,5%,5%)
    M563 P1 D0:1:2 H1 ; Define tool 1
    G10 P1 X0 Y0 ; Set tool 1 axis offsets
    G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
    M568 P1 S1 ; Enable mixing for tool 1
    M567 P1 E0.05:0.90:0.05 ; Set mixing ratios for tool 1 (5%,90%,5%)
    M563 P2 D0:1:2 H1 ; Define tool 2
    G10 P2 X0 Y0 ; Set tool 2 axis offsets
    G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C
    M568 P2 S1 ; Enable mixing for tool 2
    M567 P2 E0.05:0.05:0.90 ; Set mixing ratios for tool 2 (5%,5%,90%)
    M563 P3 D0:1:2 H1 ; Define tool 3
    G10 P3 X0 Y0 ; Set tool 3 axis offsets
    G10 P3 R0 S0 ; Set initial tool 3 active and standby temperatures to 0C
    M568 P3 S1 ; Enable mixing for tool 3
    M567 P3 E0.34:0.33:0.33 ; Set mixing ratios for tool 3 (34%,33%,33%)

    T3 ; select tool 3 (evenly mixed)

    I also seem to be having more problems with filaments jamming when I extrude single colors as opposed to evenly mixed which is working without issue.

    John


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.