Topics created by rflulling

@rflulling said in DWC versus Direct, observation:

Looked at the Code just now and S3D does call out T0 in at least the head warm up commands. Does it also need to include T0 on all move commands?

It needs to be before the first command that does extruder heating, extrusion or retraction.

@rflulling said in Reset Extruder Ignored in DWC, and other observations.:

I do understand the whole, virtual versus literal value argument.

In the early days of 3D printing, extruders were treated just like axes for simplicity. So the E parameter in a G1 command was translated directly into a position of the extruder motor.

Now we have the M221 extrusion multiplier command, mixing extruders, pressure advance, and nonlinear extrusion. Each one of these features means that a direct translation is not possible. As all extruder movements have to be calculated in relative terms, using relative extruder motion makes the calculations simpler. But some slicers still default to absolute extrusion So the firmware maintains a "virtual extruder coordinate". When slicers use absolute extrusion, this is simply the last E value that was seen in a G1 or G92 command. Then when a new G1 command with an E parameter is received, the firmware subtracts the virtual extruder position to see how much filament should be extruded, and then updates the virtual extruder position.

It gets more complicated when a pause is commanded or a power fail pause occurs, because then the firmware needs to know what the virtual extruder coordinate should be when the print is resumed. This means that all the moves in the movement queue have to be tagged with their virtual extruder position. This wouldn't be necessary if we only needed to support relative extrusion values in G1 commands.

HTH David

I see. This is not an issue I have experienced. Addressing this reply from the standpoint of normal operation and standby to operational, I recognized from day one that as soon as the motors were disabled, End Stops were lost, this complicated setup very much. But once the config was stable, loss of end stop was no longer an issue, as G28 XYZ is built into my startup script.

@dc42 said in Heater Fault relative to Power Fluctuation?:

@rflulling said in Heater Fault relative to Power Fluctuation?:

During the event, the stepper motors are disabled. I never leave them enabled.

if stepper motors are disabled and then re-enabled, they are quite likely to jump to a new position 4 full steps from the original one.

@dc42

Thank you.

All notes committed to memory.

Also I am sorry. Discrepancy in my use of "RESET" vocabulary. In this instance I was using it to refer to a board that is lacking any programing. More correctly said to have been Fully ERASED. As the term RESET is used I think to refer to a power cycle and electronics reboot.

For whatever reason many of those who have ordered the cards without systems, seem to think they need to reset the board or use the erase pin before programing the first time.
Many get frustrated and assume the card is dead when it wont show in the Device Manager, or BOSSA. But having programed both a Maestro and an MKS 1.4V from new and they both looked dead, while just needing firmware. I am encouraging users to keep trying. 🙂

@T3P3Tony

Observed,

CAUSE IDENTIFIED: IF browser or tab is closed to DWC and no buttons to Extruder Control are pressed, then the first edit made to any button on either and both FeedAmount and FeedRate will be the value used for every time EXTRUDE/RETRACT is used until any button on FeedAmount or FeedRate is pressed.

IF edit FeedRate 100 to 400 and press EXTRUDE/RETRACT with 10 selected. 400 is extruded not 10.

AND, IF edit FeedRate 400 to 300, and press EXTRUDE/RETRACT with 10 selected, 400 is extruded, not 10 or 300.

AND, IF edit FeedRate 25 to 200, and press EXTRUDE/RETRACT with 10 selected, 400 is extruded, not 10 or 200.

IF edit AmountFeed 1 to 1000, then press EXTRUDE/RETRACT with 5 selected, rate is 1000, not 5.

IF, AmountFeed 100 to 400, with 10 selected and ALSO FeedRate 1 to 1000, with 5 selected, and EXTRUDE/RETRACT are pressed THEN result is AmountFeed 400, FeedRate 1000. .

IF any other button in DWC is pressed, after open new tab or reopen browser to DWC, then behavior is as reported above.

IF feedrate buttons or feedamount button is pressed. Then the behavior is broken, and extrude/retract behave as expected based on Button Selected.
.

@dc42 so you would prefer to make the behavior different for direct and WDC? Why?

Just fix the firmware code so that it says something like:
IF heater is in FAULT state, do nothing. ; Prevents start up of machine in FAULT.
IF heater is in FAULT state, and M564 S1 H0 sent, then unlock. ; Allows movement for servicing.

My point in giving the details was not to highlight function diffrences just observations. However the underlying mechanism in the code, in the firmware is the same regardless of the subset performing operational commands. Be it a function of WDC or USB. The part of the code in error is at the core of the firmware, the actual machine controller code that listens for an instruction.

My point is that regardless of where the instruction is coming from the controller should be saying:
Hey Operator! We have a problem! You need to fix the Heater before we can continue!

Thank you. I still want an actual interface for this. But, I will make note of this for future use.

@stephen6309 said in Connectivity:

@rflulling The M906 gcode can be sent at anytime to adjust the stepper current of the steppers.

see: https://duet3d.dozuki.com/Wiki/Setting_motor_currents

@fcwilt

By switching out the code as-is??

I was running my machine on the prior and it is currently running the later. No observable changes in behavior.

I ran and had been running test prints prior, and have made more prints after. No issues.