Quoteormerod168 Yes, that would be the correct way to do it, there's a howto in this link if you are using dc42's firmware: Thanks to dc42's improvements this works with my firmware fork too Older versions of RepRapFirmware relied on G92 in the homing files, but that concept is really out-of-date...by chrishamm - Ormerod
Thorn666: Yes, you can upgrade your Fisher to my latest firmware and web interface. It has been tested and is known to work quite well. gazoox: The problem you're experiencing is because my fork of the firmware processes G-codes in parallel. This means you must pause the print before changing the position, else wrong XY coordinates may be used for your Z move. I may improve the corresponding parby chrishamm - Ormerod
Hi Florent, The base point must be in the bottom left bottom corner (i.e. 0, 0, 0) as seen here: You can configure all those settings in the G-code tab of your printing profile. This is what my current Ormerod profile looks like: I have attached my firmware configuration file (which you can import under Tools -> Firmware configuration) too. I can share my start and end G-codes as well iby chrishamm - Ormerod
Yes, my fork allows tool heaters to be switched off by sending G10 P0 S-273.15 R-273.15by chrishamm - Ormerod
Quotedc42 Quotechrishamm Hmm, that is really strange! The only difference between dc42's and my fork is that my fork runs the tool change macros if you have a T-code in your config file. My fork doesn't run tool change macros unless all axes have been homed, precisely to avoid this sort of behaviour. Heh, and this time it's me who thinks it's a bad idea to make this code context-specific Can wby chrishamm - Ormerod
Hmm, that is really strange! The only difference between dc42's and my fork is that my fork runs the tool change macros if you have a T-code in your config file. But it definitely doesn't start any moves on its own when it's booting up! Could you add M111 P3 S1 to the beginning of your config file and check which codes are executed on start-up? Edit: I sometimes have problems loading the webby chrishamm - Ormerod
If I reduce the browser width, I can't spot anything unusual in Firefox. Would you be so kind and upload a screenshot so I get an idea? Are you absolutely sure this homing problem isn't a hardware error? What do your homing files look like, did you make any adjustments to them? I have no trouble homing all axes on my Ormerod 1 (with high Y endstop) and on my Ormerod 2 (with low Y endstop). I sugby chrishamm - Ormerod
I've just released version 1.09o of my firmware on GitHub, which should provide a fix for the issue you described. If you get a chance, please test it and let me know if it fixes your problems.by chrishamm - Controllers
Thanks for your reports! I could reproduce this problem and I'm now working on a fix.by chrishamm - Controllers
Quoteormerod168 Quotechrishamm One more suggestion: Could you remove the asterisk from the directory buttons in one of your next releases? Why would you want that? Erik It's no big deal, but I'd change it for optical reasons. I don't find an asterisk in a directory name very pretty, but maybe it would be better to replace it with an icon for users who don't know their own file structure.by chrishamm - Ormerod
Hi Dirk, I don't use Safari on my setup, so I actually can't tell how well it performs! But could you try to use it with Firefox or another free browser (except for IE)? I haven't had any problems with connects or file uploads with Firefox or Chrome yet. I'm planning to changing the layout in my next version - ideally only the content div would have to be scrolled, but this requires several othby chrishamm - Controllers
Quoteappjaws1 The miscellaneous section, containing fan control is at the bottom of the screen and has a large gap above. Hmm, could you post a screenshot? I use Firefox too and it looks quite normal on my setup (see screenshot). Quoteappjaws1 On switch on of my ormerod 1 the bed moves to the left and tries to keep going, it's almost as if the end stop is not working, but it is connected. I prby chrishamm - Ormerod
If it worked before and if your E0 heater still does, then I think one of your bed MOSFETs (TR1 or TR2) is broken. If the bed heater is reported to be off on the web interface and yet the bed keeps heating, this would confirm my assumption. In this case I'd contact RRP's support and ask for an exchange.by chrishamm - Ormerod
Sven, thanks for the video, but I am aware of this behaviour It's FileZilla that doesn't work the way you expect, because it always tries to open a second connection when you start a file upload unless you tick the checkbox on the server manager.by chrishamm - Ormerod
Treito, I don't quite see how this is related. You must clear the queue before you edit the server settings and reconnect, else the old server profile might be used and uploads would fail. I tried to reproduce your report three times and every time it worked correctly, so I cannot identify a problem in the firmware.by chrishamm - Ormerod
Hmm, you have a couple of TCP retransmissions at the end of that dump, but they are sent from the Duet to your PC while your PC doesn't reply. My guess is that this is somehow related to your PC, maybe your firewall/anti-virus or faulty network drivers. It's fairly possible that this is related to your Windows upgrade too. You can also try out my latest firmware (and web interface) from here andby chrishamm - Ormerod
Hmm, that's strange. I just tried to reproduce this with FileZilla by unchecking "Limit concurrent connections" in the server manager, connected to my Duet and tried to upload the whole /www directory at once. Of course this failed with a 421 error message, so I cancelled all pending transfer, went to the server manager once more and limited the number of connections again. After I had reconnecteby chrishamm - Ormerod
Thanks David, I've just tried your latest beta and it's working well on my printer. I really like the new icons too, and I can confirm that all of your changes are working well on my 4.3'' display. One more suggestion: Could you remove the asterisk from the directory buttons in one of your next releases?by chrishamm - Ormerod
First of all, thanks for the kind feedback! QuoteTreito There is a problem regarding FTP and FileZilla for example: I accidentally set to allow multiple transfer connection to the Duet which is not supported by the FW. No problem, but FZ fails to transfer all files and most annoying is that afterwards I am not able to transfer any data using FZ until I restart the Duet. I had a similar problemby chrishamm - Ormerod
Yes, probably, but I haven't tested that yet and as I said, there will be a few feature that won't work well if you try to use it. My firmware is entirely compatible to his one, though - there is no need to adjust anything if you want to try it out.by chrishamm - Ormerod
Hi Olaf, My firmware was originally forked from dc42's repository, but a couple of things have been implemented differently. Basically the entire movement code is identical to dc42's fork though, and I can confirm that my firmware works as well on Delta and CoreXY printers. Besides, all G-Codes should be compatible, because I usually merge in most of dc42's changes when he releases a new firmwarby chrishamm - Controllers
I'm pleased to release version 1.09n of my firmware fork and version 1.07 of my Duet Web Control. This time I've further increased network reliability and added many usability tweaks along with fotomas's dark CSS theme, which can be now activated on the settings page. Here the complete changelogs of these two versions: Quote DWC version 1.07: - Thanks to fotomas a new dark theme can now be set oby chrishamm - Controllers
The ATX switch on the web interface sends either M80 or M81, which controls the PS_ON pin on the Duet. On the Fisher this pin is not used, so these buttons won't have any effect. You can disable it on the settings page once again unless you are planning to modifying your machine.by chrishamm - Fisher
I'm pleased to release version 1.09n of my firmware fork and version 1.07 of my Duet Web Control. This time I've further increased network reliability and added many usability tweaks along with fotomas's dark CSS theme, which can be now activated on the settings page. Here the complete changelogs of these two versions: Quote DWC version 1.07: - Thanks to fotomas a new dark theme can now be set oby chrishamm - Ormerod
Be aware that your tool change macro (in particular tpost0.g) blocks all other codes while heating up the hot end if it contains an M116 code (which is a default setting AFAIR). If you have a single-nozzle printer, then you can remove this code from your tool change macro file, but in turn you will probably have to add an extra M116 code to your start G-code in your slicer to make the printer waiby chrishamm - Ormerod
Try to send T0 instead of T1. If that doesn't help, please post your config file here.by chrishamm - Ormerod
Did you restart the PanelDue/your printer after that? Your screenshot looks good to me.by chrishamm - Ormerod
Quotedc42 1. Please increment the version number every time you publish a change. Otherwise it's hard for users to know whether they are running the latest version. Are you referring to the documentation or to the status response itself? DWC v1.07 should work with the old protocol standard as well (it tries to maintain backward-compatibility), but certain features won't work well if some fieldsby chrishamm - Ormerod
Quotedc42 How about having the web interface check whether the returned fan value is an array or not, and if it is, just pick the first element? That sounds fair. I've already made the necessary adjustments in the JS code of my next web interface version, which I'm hoping to release either tonight or tomorrow. This change won't affect the fanRPM field though, but I think expanding this one wouldby chrishamm - Ormerod
PanelDue can be flashed like the Duet. Seeby chrishamm - Ormerod