Quotechrishamm Thanks for your report, I have found the problem and fixed it in my new version 1.09z. You can use the web interface once again to update to it. This behaviour is intended, because I don't want to turn off all heaters when I restart a failed ABS print and the bed temperature is at 110C. That's why the web interface sends "M0 H1" to leave them active, but if you don't like that, Iby pantau - Duet
Update from 1.09x went ok as described above using iap.bin. FW and DWC But now I don't have file information, and print time information anymore . Everything shows n/a in the print status tab. Temperatur is updated as well as position. Also when I used pause print and after that cancel print, the heaters stayed on. After regular finish of a print they are switched off. All DWC control is workinby pantau - Duet
Quotechrishamm I've just pushed version 1.09x to my GitHub repository. This problem wasn't caused by the firmware update process, but because I forgot to initialise some time variables after I had restructured some initialisation routines in my previous release. I'm not sure why this problem didn't show up on my Ormerod 1 though, but I could easily reproduce it on my Ormerod 2. Ok, now everythinby pantau - Ormerod
Quotechrishamm pantau, thank you for that Wireshark dump. I have addressed the underlying problem in my new firmware release, please feel free to give it a try and let me know if that fixes your problem. I tried to flash dc42's firmware using the web interface as well, but this actually resulted in the first 512 bytes of flash memory being erased. Unfortunately I don't have a good explanation forby pantau - Ormerod
Quotechrishamm pantau, could you try out this binary instead? I think I've found the cause for this, sorry for the trouble. Also, can you confirm you were using DWC v1.10 while the AJAX errors showed up? If you're still on an older version (pre-1.08), you can use FileZilla as well to update all web interface files. Just make sure you limit the number of concurrent connections to 1 if you try thiby pantau - Duet
Quotechrishamm Quotepantau I get these errors a lot! But what is even more severe: Hot end temperature regulation is very unstable (+-5°C) and also PanelDue (no webend because of the errors) seems to report the wrong temperature in that case: My setpoint is 248°C for ABS, but even if it is reporting 248 unstable it is printing much hotter! A lot of smoke and very bad printing results... Going baby pantau - Duet
> To those who have been experiencing AJAX errors while using the web interface: I get these errors a lot! But what is even more severe: Hot end temperature regulation is very unstable (+-5°C) and also PanelDue (no webend because of the errors) seems to report the wrong temperature in that case: My setpoint is 248°C for ABS, but even if it is reporting 248 unstable it is printing much hotter!by pantau - Duet
Ok, I did go back to 1.09j and PanelDue worked right away. Problem is that it didn't pass the "double blind test": when I went back to 1.09k it also worked... ???... Before with 1.09k it didn't work for multiple days and multiple power cycles, so not sure what was going on.... I'm certain there have been no hardware or config changes in between... So looks like a false alert for know .. sorry forby pantau - Ormerod
> I still use the checksum option with my PanelDues and 1.09j, so I assume the "j" here is a typo and you mean "k" ? If so I will start testing once my big print stops and report back. Thanks!by pantau - Ormerod
For me PanelDue stopped working with 1.09k. With 1.09j everything was fine. I have to use checksum (M575 P1 B57600 S1) in my setup as otherwise PanelDue stopped my prints randomly. Could that be the reason? I am using PaneDue V 1.11. Will tryx without checksum enabled, but printer is busy right now...by pantau - Ormerod
Quotezombiepantslol Yes, that sounds like a good idea to me. I will add a confirmation dialog for this purpose to my next web interface version. I tried to do similar by uploading new config.g with ftp, switching to the webinterface and issue a M999. When trying to home the axes, printer went crazy. Reason was a corrupted config.g, just 392byte instead of 3,2k. Maybe reset occured to fast, on thby pantau - Ormerod
Quoteiamburny It did come complete and assembled with a heater, thermistor and pneumatic push fit type bowden type attachment, so i knocked up a quick mount for it, wired it up and ... Could you make the stl file available for the mounting adapter? Thanks Peterby pantau - Ormerod
The 4mm pneumatic fittings are also available with 1/4" (inch). For these the 5.2mm hole would be a perfect fit. Might be that the designer lives in a region which is not completely metric :-)by pantau - Ormerod
The "._" files are files from a MAC computer, they show up every time you hook up a non hfs filesystem to a MAC. I assume with the latest changes to support macro files with any name they are now visible.by pantau - Ormerod
Ok I already use this to control an additional fan, not the hotend fan. So am I correct only one fan is supported?by pantau - Ormerod
Quotezombiepantslol ... or with 4-pin PWM fans to adjust the speed on-the-fly It seems to be quite difficult to source them directly from the UK though. How do You use the pwm control? Is it included in the firmware of either you or dc42? I assume it Needs a dedicated pin. Same for the rpm feedback, supported?by pantau - Ormerod
I have the same issue as Dave (dc42) with exactly the same setup. Also my printer is in a pretty cold room (13-15C). Break happens not overnight, but after a couple of days of nonuse. Haven't had time to modify the setup, but maybe one could drill a hole from below meeting the filament channel below the hobbed insert. Put a bowden in that hole and guard the filament with a slightly bigger bend raby pantau - Ormerod
Quoterjmusto All the bearings, including the z axis were showing the same problem - so not a faulty bearing then. Took the top bracket off the z axis and worked on these two first. Used switch cleaner (is that ok here?) to give each one a good flush out. Then added some light oil (used on model trains, so very light) to lubricate. Much better after that. I can now drop them on the bar and they rby pantau - Ormerod
Hi Dave, thanks for the improvements, works excellent! I have seen just one "bug": - when selecting beep volume, the green settings overlay the beeb volume button, so you can't go back. Generally I would prefer to leave the overlayed menues by pressing anywhere else on the panel, not just the element which started the overlay. and one I'm not sure if it's a bug or feature: - when starting printby pantau - Ormerod
After each print I have some drooling out of the extruder nozzle, when the extruder is in park position and cooling down. It is just annoying to heat up the nozzle before you can start the next print and do an Z axes zero... But even when I clean the nozzle I have the issue on the next heat up, filament coming out and sometimes even ruining my print as it get's somewhere in between.... I was hopby pantau - Ormerod
Looks like with 1.00h the amount of g-code files you can have on the SD-card somehow changed? I first noticed that after uploading a new file (with the webinterface) it didn't show up in the list. Looking closer I noticed that I have less files shown, even if they are still on the card. E.g my setbed.g suddenly was not shown anymore in the control page. Reverting back to 1.00g and all files areby pantau - Ormerod
This link might be helpful: In fact I never oiled my linear bearings, because they are closed ones. My Ormerod 1 is from December 2013. The only thing I do oil is the Z rod from time to time.by pantau - Ormerod
Quotedc42 Thanks for the update! Would you care to add to the subject line now? I tried, but it seems that I can just edit my last post? Am I overlooking something?by pantau - Ormerod
Just a final update. I had no further errors with Duet firmware 1.00e and PanelDue 1.02 @ 57600Baud and checksum enabled. For my setup the checksums solved the issue, decrease in baud rate didn't help at all. This is after 4 more days with 8 prints. Thanks again for the great support. Peterby pantau - Ormerod
I did check my serial com with a scope. Scope was connected at Dout of the Panel at the Molex, GND at T1. Signal look good, see attached files. So signal quality is not the issue. I did upgrade to 1.00d and 1.02, activated checksum and set baud to 57600. I only had time for one print (2h) and that went through. But that happend before, will continue to test and keep you updated.by pantau - Ormerod
Dave, you change things faster than I can test them... :-) Unfortunatly the intermitted character of this failure makes it not easy to test. Yesterday I had a successful 2h print. Today the same print failed after 1:35h with the well known error. This was with the 57600 baud versions (1.00c/ 1.01). So seems like this is not (the only) solution. I also looked at my link with a scope. It looked reby pantau - Ormerod
Quotedmould Assuming that you are using a MAX232 or similar for level changing at each end, it will only be achieving +/- 8V or so and with 1m of wire I'd say that errors at that baud rate are very likely. Dave Dave (dc42), are the schematics from the PanelDue available? Haven't seen them on the github. I don't have access to the board right now, but I don't recall having seen a MAX 232, so Iby pantau - Ormerod
Quotedc42 The PanelDue send a M105 polling message every 2 seconds or so when you are not pressing anything, no matter what screen you are in. The only exception is when you are in the touch calibration screen. That's what I saw in the code. My question was the other way around: Assuming the root cause is a buffer overflow in the Duet: Shouldn't I get more problems if I use/play around with the pby pantau - Ormerod
Quotedc42 If the problem is an overrun error, turning in parity won't help. I've uploaded a version of 1.00c Duet firmware with the baud rate reduced to 57600 to the usual place, and I'm about to upload a 57600b PanelDue binary for the 4.3 inch screen. Please try them. Look for the files with 57600 in the filename. Ok will try in the evening, but shouldn't there be a dependency on which screenby pantau - Ormerod
Dave, the files I use are in the attached zip archive. I always used the setbed.g, so it is included as well. I have M0 in my custom end gcode. But I don't think the gcode interpreter could jump there? I was also wondering why nobody else has this issue. That's why I also looked into EMI. And I still can't rule it out completely. I was thinking that would contribute to bitflips on the serial linby pantau - Ormerod