I got it working now 👍

There was a endstop set for the z axis

; Endstops
M574 X1 S1 C0
M574 Y1 S1 C1
M574 Z2 S1 C2
M574 U1 S1 C4
M574 V1 S1 C3

So I changed it to

M574 X1 S1 C0
M574 Y1 S1 C1
M574 Z0
M574 U1 S1 C4
M574 V1 S1 C3

and now it's working. Thank you all for your help.

No need to feel dumb, it's not at all obvious. The issue is that SDHC can use the FAT16 or FAT32 format (depending on capacity), whereas SDXC needs to use exFAT format, which requires paying a license fee to Microsoft. That's why open source software does not generally support exFAT or SDXC.

Tested old DWC too /reprap.htm an the behaviour is the same.

But I think I understand the behavior now, the heater state is cycled Active->Standby->Off->Active-> ... and so on.
So to go from standby ro active, manually, must go via off.

So it seems to by design. But a better solution would be preferable, one where any of the states can be selected directly.

could it be related to https://github.com/dc42/RepRapFirmware/issues/274 ?

try again with a really big file, see if that makes a difference

frank26080115 created this issue in dc42/RepRapFirmware closed [RRF 2.02 WIFI 1.22] FTP transfer of large files truncated to 2048 bytes on SD card #274

I've had Web Control 2.0.0RC2 installed for a while and not had this problem until 2 days ago when firefox had an update. The problem isn't there if I open the interface in Microsoft Edge but obviously Edge is crap because it doesnt allow streaming from the camera.

@surgikill said in DWC always showing layer X/775:

So my DWC always shows a max of 775 layers. I'm not sure if this is a known issue with DWC, or maybe it's a browser issue or something with my gcode. Any ideas?

Do you mean that it shows the print as having 775 layers? If so, that's because you have a G1 Z command to move the print head to a high print height, in your slicer ending script. To fix it, either add a comment starting with ";E" to that line, or use an end.g file and put the command in that file.

@kraegar Yep, I think that has been fixed in RC6.

OK Gents

I have overcome the issue, in a very strange way. And I dont fully understand what the root cause of the issue was. Hopefully some other can advise.

I tried resetting the wifi network and I used Pronterface did all required and after I rebooted I started receiving the message "WiFi reported error: no known networks found"

Which left me thinking hmmmm, I wonder.

So I switched over to YAT, cleared the network that was saved then I input the following command: M587 S"Your SSID" P"your-network-password"

This reported as successful with the M552 S1 reporting connected to my network.

And I am now able to connect using the web interface with no issue.

Now I wanted to check why I could connect when I couldnt before. So I carried out all as before but with pronterface. I noticed that using the M587 command in pronterface saves the SSID & Password all in Upper case instead of what it wa supposed to be, so that solved that part of the mystery.

What I dont fully understand is why the web browser found the printer and would open its IP address but would stumble when trying to connect, and why clearing the saved networks (which are all the same as before and havent changed for years) and using YAT to reconnect fixed the problem.

And the config.g is still the same as when I couldnt connect.

So its solved, but why is it solved and what was the root cause ?

This may be a temporary work around: https://duet3d.dozuki.com/Wiki/Gcode#Section_M589_Configure_access_point_parameters

Setting up the duet to work as an access point allows it to create it's own wireless network which you can connect to from your control device.

The P parameter of M552 can tell it what network to use from the list previously stored onto the wifi using M587.

Use M588 to delete networks.

I've not got a wifi to test this on, just searched the gcode guide: https://duet3d.dozuki.com/Wiki/Gcode

Your post always enlightens me on something new! I didn't know about M208!! Thank you! will go and change my code ^^ cheers

@dc42
THANKS! ...and sorry for hijacking the OP here...
(Would be really cool if you could add this in a future build also to the PanelDue...)

I figured out why this is happening and I will provide a fix very soon.

I am using a backup as we speak to get up and running again with one issue.I will be starting a thread to figure that out in a few seconds.

@supraguy said in Duet Web Control 2.0.0-RC3 is ready:

It mostly works as expected, but for whatever reason, on the dialog box to jog the Z axis, I can only press each button once. After that there is a spinning circle in place of the adjust amount, and it will not respond to another click.

Same here when trying to run manual Delta calibration using G32.

config.g contains

M558 P0 G31 X0 Y0

Using the old DWC (/reprap.htm) the process does work, though.

@nicolab28 thanks, that worked....but I guess it is not how is supposed to work, But for now it will do. At least I don't have to switch to the old DWC

@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.
.

Ahh, yes, it works - Thanks!

I didn't think of that! I'm glad you solved it.