Ok back to the Original Topic.
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?
Like I said, never have a trouble with control when direct over USB no mater how many times I reset. But if from SD card, and I reset I loose the Extruder.
What would I be looking for in the code to know if it was causing an issue?
@phaedrux
Would like to try a MicroSwiss, but they are costly and to take full advantage I would need a whole new hot end assembly. 
Did not know about the Beta. Thanks.
I had been talking about their prototype after seeing it on a youtube interview from 2017?
But then 2018 and it was not shown in videos. Taz was talking up their own product. I wondered if I was confused as to who was developing this.
Arrived just as Joel was give away his printer. Sadly did not have much control over the arrival with work and travel. Had about 20 min after the giveaway then names were being called out. Then it became almost impossible to move as every one formed up a line that blocked movement, as the catering started. I asked about that but every one played dumb. So kept trying to shuffle around. By the time I got over to your side almost every one had beers and chips, most were settling down with a mouth full, that is other than those frozen in place with conversation. Though it looked like E3D had been drinking for a while. Ended up talking to Olsen Ruby.
About an Hour later got over to the other hall. Many were leaving. I forget the name of the group up in the front corner, but they didn't look like they had much to show. But the whole area smelled like an open tap. I kept moving. Talked to the TH3D guys.
If I had gotten in at E3D, I am sure I would have realized Duet was next door.
-Sorry I missed you too. I was looking forward to the meet and greet.
@Phaedrux Well, thats just annoying.
I have a very distinct feeling that I popped up at that table but every one was engaged in other conversations. I know I was at the E3D table. Could not get any one to notice. Not the end of the world. I am not exactly a big investor.
I know, I could not even get any place near the Bondtech table. To many very firmly rooted feet, in place, not moving an inch for very long conversations. Closest I got was the table with the Mosquito hot ends. Was a wall of men from that point on, all the way to the E3D table.
Did see the SeeMeCNC stuff. Paired up with TAZ. The props on the table, and the giant machine in the corner.
Saw Joel too, and similar, always a wall. Not that I had any business with him.
-Was a bit like seeing the back of Bruise Willis's head (I sub contracted at a hotel he stayed at in NYC).
Chatted up the Guys at Olsen Ruby a bit. Found out that the Ruby is not for me until I start working with abrasives. Tried to take interest in the PLA booth directly across from them. But other than having a massive stock they had nothing I wanted.
Coolest things I saw were the Lady with the fully articulated Jackalope from hell. And the guy with the mechanically functional Engine w/ functional Transmission. Those two were impressive.
Got to meet the guys from TH3D. That was cool.
The Railcore ii builds were for sure worth note too. I want their aluminum parts, and linear rail computer leveled 3 axis Z. I want to add that to the E3D multi head machine. Then incorporate the TH3D sensor. -Well, I can dream right??
So E3D's multi head, how come that thing isn't official but so many seemed to have it? are the plans public now? or have I over looked it's launch? What happened to the TAZ variant? Heck, why didnt TAZ have much to anything to even show this year, despite launching their PRO only days before the show, whats up with that?
One thing to look forward too, the guys selling goop, said they have a PETG compatible line coming. So that applies to me. Yay. I asked then to look at M3D Tough Ink too. So I look forward to their spray on stuff or PETG and maybe Tough Ink.
There was a guy building a Railcore II. He had a pile of thin washer/shims that he was using and gave me the empty bag to help me find them online. Very valuable, since the FT-6 shipped with washers that grab both sides of the bearings and these shims will let the bearings spin properly!
I hoped to see more next gen tech previews. Maybe some new hot end tech. But didn't.
Still need All metal hot end parts that actually fit together properly.
Still looking for hacks to help with making better and worse skins.
etc.
@Stephen6309 Ahh, yes E3D was there by TAZ. Is @Phaedrux with E3D? I wanted to talk to them but they were always in other conversations, or eating. I wanted to ask about the head switching machines I thought they develped and I saw several of then in the building. But then a video from last year showed TAZ with an advanced Head switching machine that sounded like what I thought E3D was tinkering with, but further along.
@dc42
Noted. I will look for this and see if some how it is the reason. S3D does denote a tool as far as I know.
sorry @dc42 your reply some how did not show up until after I had addressed @Phaedrux
@Phaedrux
By default a tool is always specified in the gcode. Why should a user need to take an additional step to tell the DWC that they are going to use a tool?
@phaedrux said in DWC versus Direct, observation:
@rflulling do you have a tool selected when trying to start a new print?
By the way @Phaedrux , not that I would have known who to look for, but I did not see you or any one from Duet at MRRF.
Though I did notice a booth selling stacks of boxes marked as DuetWifi and Maestro.
Never made any customization's to those files. They are what they were on the day they were downloaded from GitHub. Save only for defaults added by RRF.
I honestly cannot believe that either of these files are doing anything at all.
Cancle.g
; stop.g
; called when a print is cancelled after a pause.
Stop.g
; stop.g
; called when M0 (Stop) is run (e.g. when a print from SD card is cancelled)
;
; generated by RepRapFirmware Configuration Tool v2 on Sun Jan 27 2019 20:58:34 GMT-0600 (Central Standard Time)
I will be there Tomorrow. Look forward to finding every one. -The ones that cannot run away that is.
When in DWC and a print from SD card is failed, then print is paused and canceled. After board is cleared and print is started fresh, Extruder motor will only twitch causing not so much a fail but a total lack of anything. This behavior does not resolve on it's own, and printer must be reset to get the extruder running again.
This behavior does not happen even under exact same circumstances, when operated by direct control. Infact, I have never seen this issue until after using DWC for prints.
I will add to this thread as I gather info.
Symptoms:
Normal print behaviors,
DWC shows no errors,
DWC shows normal extrude count up,
No prime before print start,
No layer at print start (not in itself a symptom),
Directly Follows all canceled prints in DWC
Thank you.
I stand by everything I have reported, as yes if you do as I have done you should repeatably get the same results. However, other than when putting in the codes manually. I have not demonstrated that they will have any effect on a normal user.
I do understand the whole, virtual versus literal value argument. Been through that one with M3D enough times when regarding the Z height and their calibration system in the Early days. That literal Z was below the build plate. But virtual Z was calibrated just above it.
-By default the Virtual Z values were the ONLY value a user would see, unless they were in manual calibration.
So for me I always want to know where the Printer thinks it is, not where it should be. -Though both pieces of info are highly useful at the right times.
I will try reverting the firmware to test. But have had a print running so cannot test more just at this time.
Thank you for looking into this. I hope I was thorough in testing and reporting the observations.
I would suggest to test, G28, then G90, then M104 S210 T0 (assuming you have PLA loaded), then G1 Z10 F200, then G0 X20 Y20 Z20. Now in DWC enter G92 X100. See it change? Now enter G92 E100, see a change? Nope should not. Try G92 E0, still nothing right? Now run G92 X0, notice both X and E go to Zero. Now, see if you can change it back. Try, G92 E100, then G92 X100, nothing right? Try G92 X9, betcha it just changed. Try any value 0-9 and it will work, for both X and Y.
@phaedrux said in Reset Extruder Ignored in DWC, and other observations.:
I'm unable to duplicate the G92 X Y Z behavior you describe on a Duet Wifi and firmware 2.02 and DWC 1.22.6 . However, the G92 E does not change the extruder position display at all, as you describe.
Can you confirm if the behavior still exists if you return to firmware 2.02?
I believe I understand your reasoning. I have gotten used to Clearing the Extrude data before starting a print. Otherwise risk the count stored at the beginning of a print interfering, and I suspect it has been but have not proven it yet. This is as because most of my work has been done on S3D for Marlin 1.04 not RepRap. I have worked hard to maintain an operation that is flexible between so that I do not need to literally toss everything learned out the window and start over.
@dc42 said in Reset Extruder Ignored in DWC, and other observations.:
G92 E0 resets the virtual extruder position. This command is generated by slicers frequently when they use absolute extrusion, to avoid the build up of rounding error. However, the virtual extruder position is not useful to an end user, so DWC shows the total net extrusion instead, separately for each extruder. If you really want to check the virtual extruder position, use M114.
In testing startup code by hand, I found that when I enter G92 E0.00 nothing happens. On screen the Extruder count will remain at 20, -100, 80, etc. Only a G28 command resets this number. No errors are given.
This was noticed in troubleshooting after realizing that the one time I used the baby step command (to help find a best start offset for a material in use), baby steps were shown in their own box but did not show in the global absolute values above.
I decided to run through my startup script by hand, only to discover that the when entered by hand the extruder does not reset. I should wonder if this happens when in normal operation too.
I do not know if this behavior is normal, or if it is a big to the beta RepRap, or a bug to DWC.
E0.00 is a value I have used since Marlin 1.04 as some how using E0 allowed floating values to escape being zeroed out. So this value is deliberate.
When testing against other instances of this behavior in RepRap and DWC, I can confirm that G92 E0, G92 E100, G92 E0.0 all have no effect at all, DWC does not reflect the command.
Further testing uncovered something interesting:
For me it is important that the values shown in the DWC are current, an exact always, for troubleshooting. If they read false, I will make incorrect conclusions about the work. If they read false normally, I will be unable to trust the readout in the DWC.
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.
Michael Armani, aka Marmani on the Discord channels responded to the conversation with a point that I did not know, and is not mentioned on the Troubleshooting guide.
If using the Duet instructions for SAM-BA.
(https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_3)
Please DO NOT select at91sam4e8.
-That describes the Duet Wifi, not the Maestro.
Instead choose ATSAM4s8.
However, we do not use this tool and strongly recommend using Bossa instead. Please see our repair instructions https://coda.io/d/M3D-Public_dzE73kMbIAL/Duet-Maestro_sui8n#Cards_tubJG/r1, I would say at least 50% of the time we recover a board with funky behavior (No usb response, SD card reading, even sometimes a stuck pin). Updating the firmware helps with these, and sometimes the board just needs a refresh.
All makes sense and is expected.
So I should expect a UPS would cure this, but what do you think? Can a code be used to tell the firmware to ignore the glitch? Maybe this is something that can be added as an auto recovery function using a statement that says if the power drops and the temp drops, glitch happens only one time in X amount of time ignore and restore the temp. But if it happens several times, engage Thermal Protection?
I guess it is fruitless to speculate a fix when I am not even quite sure what the cause is?
Yes. Fully Tuned. M303 stored using M501. No issues there. Temp seem stable and extruding more or less as expected with no reason suspect any issues withe tuning or hardware.
If you tune heater tuning using a recent firmware version, and you copied all the discovered M307 parameters including the V parameter across to config.g (or used M500 and config-override.g), then heater power is already compensated for changes in the VIN voltage. However, heater power goes as the square of the voltage; so if you have only 9.3V available to power a 24V heater, then the maximum power output that the firmware can command is only 15% of the rated power of the heater.
During the event, the stepper motors are disabled. I never leave them enabled.
Only the heater is on, to alleviate warm up time and possible clogs.
The other issue you face is that the stepper drivers shut down below about 9.5V.
I know I am late to this party. I have a feeling that familiar issue of the M574 command will bite me when I update too. -"M574 X2 Y1 Z1 S0" currently being the magic configuration for a Wanhao i3 Mini running 2.02(RTOS) (2018-12-24b1). I will also have to test the "M574 X2 Y0 Y0 S0" which has previously produced identical results for this hardware configuration. Perhaps that has changed under 2.03
Will chime in further if there are any issues to provide feed back on. Only doing update to participate in a community action.
Been working with a few and it seems that they are unable to get a response when the Erase pin was used. One did get a partial response but once the pin was cleared and the board reset it never came back and even though all seemed normal, it never presented to windows.
I cannot validate this further as no one has sent their cards to me for help.
-Though to be fair this is not a service I am offering, yet. I also have no contract with M3D or Duet to offer services so if I find a card really is dead, I have no idea where to go from there in terms of a proper hand off for warranty if any at all.
I think if I or we can Identify the reason why some ERASE pin cards, will not present at all. Then more can be helped to recover from these kinds of mistakes. -For now I have been trying to warn other users to NOT use the ERASE pin unless told to by support staff.
Referencing post: https://forum.duet3d.com/topic/4417/heater-pid-tuning/4
I believe this event is caused by a fluctuation in power provided by the local substation. The printer was in standby with a temp of 210C for PETG.
Perhaps a transformer switch over or to many air conditioners switched up just then... Regardless a small brown out. Not enough to fully reset the hardware but enough to cause some faults, it seems. Input voltage should be 24V normal, and 5V constant is received over USB. My more robust systems were not effected, maybe a larger capacitive buffer?? I do not have any UPS in service. I would say that voltage dropping to anything less than 2V under expected should be reason for a fault, just not thermal. -Maybe some one more familiar with the Firmware code can explain what is happening during a brown out?
I noted on comment 4, that M570 can be used to create an offset value to help with false positive error detection in the heater Thermal Runaway circuit. So if I understand it correctly, I input a time value to IGNORE a difference so that the temp can catch up?
This particular event I have no means of simulating to see if it has been resolved. Perhaps this is not something that can be resolved if the source is infect a Brown Out caused by a local Transformer? Perhaps the result will always be a thermal fault, if the heater is active when the brown out happens?
This fault never happens when I am working with the machine or on the computer watching, always when I have stepped away. Since this fault is not happening while a print is in progress or during warm up, I do not suspect a power supply issue at this time.
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. 
There is much data posted regarding this topic so am not looking to rehash. I am also not having any trouble with my card. These questions are to make sense of the many possible results and actions that might be required of a user who thinks they have a dead card. In particular post RESET pin. I see this pop up a lot thats some one thought they needed to do this while trying to figure out how to program the card for first run. Since my card is working I am not willing to hit the reset just to test any of this.
-If possible all answers ONLY from those who have done full resets.
-If possible all answers in YES/NO replies.
Can it be assumed that if the card does not show in either SAMBA or BOSSA that it is either partially configured or totally bricked?
If a card is fully wiped, 100% reset, should it always show in SAMBA or BOSSA?
I have never seen the card show in either SAMBA or BOSSA, and both always reject the port as valid, but then mine has valid firmware and bootloader, so I assume this to interfere with detection by lower level utilities that would be used in initial setup phase.
If a card is partially configured it should always show one of the expected results listed on the Troubleshooting and Setup pages, right?