@minim said in Question about DWC v2xx:

You can also use the old interface when you run dwc2.0RC7. Just add "/reprap" behind the link. I do that since I find the old easier to use.

Thanks for that info.

So far I'm liking the new layout.

Frederick

As others have said, M28 ignores comments in commands. Like you can (probably, I haven't tried) send console commands with comments, but they are lost as soon as the command is sent.

I can see why you might want to do this (maybe for logging?), but it's probably easiest to write the gcode file in a text editor, then send each line by copying and pasting that into your terminal program (I assume that's how you're connecting). Then you'd have a local editable copy of the file from the SD card, with comments. Or remove the SD card from the Duet, copy the file onto it locally, then replace it in the Duet.

Ian

here is a more detailed guide.
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

use the Duet2CombinedFirmware.bin in that case.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M584_Set_drive_mapping

VERY IMPORTANT! Assigning a drive using M584 does not remove its old assignment. Therefore, if you assign a drive that defaults to being an extruder drive, you should also assign the extruder drives explicitly as in the above example. Failure to do so may result in unexpected behaviour.

you are not unassigning the Y from the extruder. this will cause strange behaviour.

Thats interesting, most network equipment only cache the mac to ip mapping for a few minutes (with the exception of the dhcp server). Would be interesting to see if a new reservation causes new problems or if it was a one off.

@dc42 ,

any thing else I need to do?
I can confirm that this issue exists with DuetWiFIServer 1.22 and Duet FW 2.02 as well.

THanks,
Madhu.

Check your config-override for M305 commands

I have it connected to Endstop for E0.
DWC does not report the sensor, but it does appear in M112:

=== Filament sensors === Extruder 0: pos -1.74, ok, measured min 61% avg 76% max 96% over 3368.6mm, errs: frame 6 parity 0 ovrun 0 pol 0 ovdue 0

Im assuming since its not a switch and a laser filament sensor its not reporting as expected in the json.

All good will try and work around it.

Supply voltage: min 23.3, current 24.1, max 24.6, under voltage events: 0, over voltage events: 0,
Supply voltage: min 20.7, current 23.9, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes

There was no undervolt event in both cases. Though a drop to 20V is significant. This could mean that either the psu is not enough for your setup, or its damaged.

@ram yes you can push files to the Duet but it can't go out and "pull" them (at least with Duet 2). Duet 3 OTOH will allow for a plugin to be written on the SBC that does that.

Yes, there is DEFINITELY something WRONG with filament estimating. This job did have wipe on retract checked, in a different slicer.

I really thought it was a "wait for it to converge" when other people posted. It is not. This job said "n/a" under filament for about 10 hours, then went to ridiculous numbers like shown. And, by the way, it did finish eight or nine minutes after this photo.

0_1565042374664_IMG_0657 (2).jpeg

Uh...never mind... my lack of knowledge. Just put in the proper address for my Duet and everything is running fine.

I would think its safe to say any consumer or nat capable router has built in dns server, what sets them aside is the dhcp and dns server talking to each other (or in the case of openwrt w/dnsmasq, being the same server daemon)

OK, I changed my setup to use TLS on the reverse proxy and it works. I had to completely reload the page, though but then it worked.

@SIam Did you compile the changes via npm run build and upload the resulting zip file?

EDIT: I uploaded a patched version of 2.0.0-RC7 to my Dropbox.

Seem to be related when settings go out of a specific bounds. It's working again after a manual level. Revert back to DWC 1 option not working at the moment though.

Dc 42
Thank you very much, that was it!
Had to download iap4e.bin as well.
All done!
Thanks guys
Rod

Do you have any of those commands in any other macros? Like bed.g or your homing files that may be over writing the ones from config.g?

It would be unusual for those to exist in config-override.g unless you put them there yourself.

It's working better than ever. Guess it just needed a firmware update.

Thanks a bunch for your fast and professional help. Even though the solution was simple, i likely wouldn't have ever fixed the issue since I was at the end of my rope. So, thanks again.