g2core - Edge Branch

G2 Edge is the branch for beta testing new features under development. New features are developed in feature branches and merged into the edge branch. Periodically edge is promoted to master.

That said, Edge is for the adventurous. It is not guaranteed to be stable, but we do our best to achieve this. For production uses we recommend using the Master branch.

Firmware Build 101 {fb:101.xx}

Feature Enhancements

The fb:101 release is a mostly internal change from the fb:100 branches. Here are the highlights, more detailed changelog below:

• Updated JT (Junction integration Time, a.k.a. "cornering") handling to be more optimized, and to treat the last move as a corner to a move with no active axes. This allows a non-zero stopping velocity based on the allowed jerk and active JT value.
• Updated motion execution at the segment (smallest) level to be linear velocity instead of constant velocity, resulting in notably smoother motion and more faithful execution of the jerk limitations. (Incidentally, the sound of the motors is also slightly quieter and more "natural.")
• Probing enhancements.
• Added support for gQuintic (rev B) and fixed issues with gQuadratic board support. (This mostly happened in Motate.)
• Temperature control enhancements. (Ongoing.)
• More complete support for TMC2130 by adding more JSON controls for live feedback and configuration.
• Initial support for Core XY kinematics.
• Boards are in more control of the planner settings.
• Experimental setting to have traverse (G0) use the 'high jerk' axis settings.

Project Changes

Changelog for Edge Branch

Edge branch, Build 101.xx

This build is primarily focused on support for the new boards based on the Atmel SamS70 family, as well as refining the motion control and long awaited feature enhancements. This list will be added to as development proceed.s

Functional Changes:

Note: Click the header next to the arrow to expand and display the details.

Linear-Velocity Segment Execution

• The overall motion is still jerk-controlled and the computation of motion remains largely the same (although slightly simplified). At the smallest level above raw steps (what we call "segments," which are nominally 0.25ms to 1ms in duration) we previously executed the steps at a constant velocity. We now execute them with a linear change from a start velocity to an end velocity. This results in smoother motion that is more faithful to the planned jerk constraints.
• This changed the way the forward differences are used to compute the segment speeds as well. Previously, we were computing the curve at the midpoint (time-wise) of each segment in order to get the median velocity. Now that we want the start and end velocity of each segment we only compute the end (time-wise) of each segment, and use that again later as the start-point of the next segment.

Probing enhancements

• Added {"prbs":true} to store the current position as if it were to position of a succesful probe.
• Added {"prbr":true} to enable and {"prbr":false} to enable and disable (respectively) the JSON {prb:{...}} report after a probe.

gQuintic support

• Support for the gQuintic rev B was added. Support for rev D will come shortly.

Temperature control enhancements

• Added the following settings defines:
• HAS_TEMPERATURE_SENSOR_1, HAS_TEMPERATURE_SENSOR_2, and HAS_TEMPERATURE_SENSOR_3
• EXTRUDER_1_OUTPUT_PIN, EXTRUDER_2_OUTPUT_PIN, and BED_OUTPUT_PIN
• Added BED_OUTPUT_INIT in order to control configuration of the Bed output pin settings.
  • Defaults to {kNormal, fet_pin3_freq}.
• EXTRUDER_1_FAN_PIN for control of the temperature-enabled fan on extruder 1. (Only available on extruder 1 at the moment.)
• (Experimental) Analog input is now interpreted through one of various ADCCircuit objects.
  • Three are provided currently: ADCCircuitSimplePullup, ADCCircuitDifferentialPullup, ADCCircuitRawResistance
  • Thermistor and PT100 objects no longer take the pullup value in their constructor, but instead take a pointer to an ADCCircuit object.
• Thermistor and PT100 objects no longer assume an ADCPin is used, but now take the type that conforms to the ADCPin interface as a template argument.
• TODO: Make more of these configurable at runtime. Separate the ADC input from the consumer, and allow other things than temperature to read it.

TMC2130 JSON controls

• Added the following setting keys to the motors (1 - 6):
  • ts - (R) get the value of the TSTEP register
  • pth - (R/W) get/set the value of the TPWMTHRS register
  • cth - (R/W) get/set the value of the TCOOLTHRS register
  • hth - (R/W) get/set the value of the THIGH register
  • sgt - (R/W) get/set the value of the sgt value of the COOLCONF register
  • sgr - (R) get the SG_RESULT value of the DRV_STATUS register
  • csa - (R) get the CS_ACTUAL value of the DRV_STATUS register
  • sgs - (R) get the stallGuard value of the DRV_STATUS register
  • tbl - (R/W) get/set the TBL value of the CHOPCONF register
  • pgrd - (R/W) get/set the PWM_GRAD value of the PWMCONF register
  • pamp - (R/W) get/set the PWM_AMPL value of the PWMCONF register
  • hend - (R/W) get/set the HEND_OFFSET value of the CHOPCONF register
  • hsrt - (R/W) get/set the HSTRT/TFD012 value of the CHOPCONF register
  • smin - (R/W) get/set the semin value of the COOLCONF register
  • smax - (R/W) get/set the semax value of the COOLCONF register
  • sup - (R/W) get/set the seup value of the COOLCONF register
  • sdn - (R/W) get/set the sedn value of the COOLCONF register
• Note that all gets retrieve the last cached value.

Core XY Kinematics Support

• Enabled at compile-time by setting the KINEMATICS define to KINE_CORE_XY
  • The default (and only other valid value) for KINEMATICS is KINE_CARTESIAN
• Note that the X and Y axes must have the same settings, or the behavior is undefined.
• For the sake of motor mapping, the values AXIS_COREXY_A and AXIS_COREXY_B have been created.
• Example usage:

#define M1_MOTOR_MAP                AXIS_COREXY_A           // 1ma
#define M2_MOTOR_MAP                AXIS_COREXY_B           // 2ma

Planner settings control from board files

• The defines PLANNER_BUFFER_POOL_SIZE and MIN_SEGMENT_MS are now set in the board/*/hardware.h files.
• PLANNER_BUFFER_POOL_SIZE sets the size of the planner buffer array.
  • Default value if not defined: 48
• MIN_SEGMENT_MS sets the minimum segment time (in milliseconds) and several other settings that are comuted based on it.
  • Default values if not defined: 0.75
  • A few of the computed values are shown:

  #define NOM_SEGMENT_MS              ((float)MIN_SEGMENT_MS*2.0)        // nominal segment ms (at LEAST MIN_SEGMENT_MS * 2)
  #define MIN_BLOCK_MS                ((float)MIN_SEGMENT_MS*2.0)        // minimum block (whole move) milliseconds
  

Experimental traverse at high jerk

• The new define TRAVERSE_AT_HIGH_JERK can be set to true, making traverse (G0) moves (including E-only moves in Marlin-flavored gcode mode) will use the jerk-high (jh) settings.
  • If set to false or undefined G0 moves will continue to use the jerk-max (jm) settings that feed (G1) moves use.