Skip to content

Release 3.2.2

Choose a tag to compare

View all tags
@wilriker wilriker released this 12 Nov 09:02
· 638 commits to master since this release
3.2.2
f9deb98

Version 3.2.2

Upgrade Notes:

  • This release is compatible with RepRapFirmware 3.2-beta1 or later. It will partially work with RepRapFirmware 3.1.1 but not with any older version.
  • Flashing this release will reset the configuration to defaults

Limitations

  • Due to the lack of RAM this build will not run on version 1 or early version 2 PanelDue boards that use the ATSAM3S2B chip.
    • Version 1.0, 1.1 and earlier v2 PanelDue: ATSAM3S2B processor (64MHz, 32kb RAM, 128kB flash) - these are the ones that the new firmware probably won't run on.
    • Version 2 PanelDue manufactured from August 2016: ATSAM3S4B processor (64MHz, 48kb RAM, 256kb flash). Will run the new firmware, but not as fast as version 3 will.
    • Version 3 PanelDue, including all 5i and 7i: ATSAM4S4B processor, 120MHz, 64kB RAM, 256kb flash. Will run the new firmware.
  • There will be no reliable status updates coming from RepRapFirmware while waiting for heaters to reach temperature (and some other cases) before RRF 3.2-beta4.

New and changed features:

  • Babystep amount is configurable from preset values
  • When babystep buttons are pressed the value on the screen will be updated immediately and will be overwritten
    with the actual value on the next status update (usually these values should be equal anyway)
  • Feedrate for move buttons is configuratble from preset values
  • PanelDueFirmware does no longer distinguish between responses to M409 with and without K parameter. This prevents
    issues if values are moved from live to detail response or vice versa
  • Provide interface for RepRapFirmware to reset as well as erase and reset the PanelDue
  • Preparations to show more than one bed/one chamber

Bug fixes:

  • Babystepping amount was not initialized

Bug fixes since 3.2.1:

  • Setting babystep amount to the lowest value would invalidate stored settings on next start of PanelDue
  • A chamber could steal the second slot and status/temperatures would alternate between the tool and the chamber
  • A null pointer dereference could occur when RRF was restarted leading to a reset of PanelDueFirmware
  • State "Initializing" was replaced too early by "Idle"
  • Fetching the first bed/heater would not filter out invalidated entries
  • Under rare cicumstances it could happen that selectin a bed/chamber or setting temperatures for these could
    cause a restart of PanelDueFirmware
Assets 16
Loading