I'm afraid no. That VM111 is a built-in function in Chrome/Chromium and not part of the web interface, so I can't help here! Without an error message or a Wireshark dump that reveals possible TCP problems I don't even remotely know what could be the cause of your problems.by chrishamm - Firmware - mainstream and related support
Thanks, but if this one doesn't cause any problems, it won't help me! Can you post an excerpt from a file that does not work instead, like your DM_Tree3_full_sculped_fixed.gcode?by chrishamm - Firmware - mainstream and related support
Thanks for those files, but unfortunately I cannot spot anything suspicious in there. Can you please make another dump while loading the web interface? And this time leave the JS console open to check for possible JS errors and bad HTTP requests.by chrishamm - Firmware - mainstream and related support
Can you post the first 200 lines of your G-code file excluding comments?by chrishamm - Firmware - mainstream and related support
The default nozzle diameter is set to 0.5mm and usually this is sufficient for most first layer detections. This means that your first layer can be up to 1.5mm thick. Does your detected first layer height match the actual first layer height? I'm planning on modifying the detection algorithm a bit, so it will scan the read block for lower Z heights even after a valid Z height has been found. Unforby chrishamm - Firmware - mainstream and related support
1) What OS are you using? 2) When opening the JS console (via F12), can you spot JS errors or do you see any other error messages? 3) If some resources fail to load, could you record a Wireshark dump and either upload it here or send it to me via PM?by chrishamm - Firmware - mainstream and related support
Quotemhackney @chrishamm - a gent on the google delta group asked for screenshots of the DuetWebControl interface. I posted a set there and also on my blog: SublimeLayers. I'd like to make the screenshots available to you to post on the GitHub. In fact, I'd love to pay it forward and write up a description of DuetWebControl and some basic instructions with the screenshots (including installationby chrishamm - Firmware - mainstream and related support
I'm not aware of that problem, but if you upgrade make sure to adjust your config.g from an example config from either my or dc42's SD-image directory. In detail you should change the M201, M203 and M566 codes, and add the new M574 code.by chrishamm - Ormerod
If there had not been so many people with large config files, I would not have had to introduce a new HTTP response. But you should really clean up your G-code directory - if there are too many files in one directory, the file responses may be truncated. Unfortunately we only have 96KB of RAM available on the SAM3X which is used for everything, so there is no easy fix for this. I could already inby chrishamm - Firmware - mainstream and related support
If your X-arm is twisted, this may be an option for you: Or even better: Get one of DaveK's alu X-arm replacements, I've never had this problem since I mounted it.by chrishamm - Ormerod
I'm glad you got this sorted. If you are looking for more improvements, I suggest you try out my DWC v1.08 sometime soon as wellby chrishamm - Firmware - mainstream and related support
AFAIR there was an issue in older Arduino versions concerning the USB port detection, so I suggest you either add another Arduino core patch to merge in the changes from a recent release or implement your own timer-based solution. I can confirm that this problem is not present in my fork. Edit: I can confirm this problem only if the USB port is not closed before the USB cable is disconnected. Iby chrishamm - Firmware - mainstream and related support
Hmm I see, that's a shame. I thought the autosize JS library would take care of this regardless of the used theme, but in this case I will exchange it in my next web interface version. Until then you can work-around this problem by disabling the dark theme temporarily.by chrishamm - Firmware - mainstream and related support
Hmm, not sure what you mean. Everything is looking nice on my setup and works as I would expect, see the attached file (don't mind the white stripe below the menu, that's just showing because I took a screenshot). I have just pushed firmware v1.09r-ch to my GitHub account. If you are already using v1.09q and not using thermocouples, inkjets or a Roland mill, there is no need to upgrade to this fby chrishamm - Firmware - mainstream and related support
That's intentional, the textarea is supposed to resize dynamically depending on its content. That's why I added js/jquery.autosize.min.js to this version. But you should be able to use the scroll wheel or touchpad to scroll up and down as wellby chrishamm - Firmware - mainstream and related support
To drive a thermocouple, you need a MAX31855 device and connect it to the SPI MISO/MOSI/SCLK pins on the expansion header. Please refer to the Duet Expansion Header description in the Documentation directory on my GitHub repo, but be aware that currently only one thermocouple is supported by my latest firmware version. I will increase the number to two in my next release and move some of the Rolaby chrishamm - Firmware - mainstream and related support
It would be interesting to hear if these problems persist once you upgrade to DWC v1.08 and my latest firmware version. If it does and you're using Windows, please perform a TCP/IP stack reset. If that doesn't cure your symptoms, please send me a Wireshark dump so I can look into this again.by chrishamm - Ormerod
If you're interested, have a look at I have just pushed v1.09r-ch to my GitHub repo. If you are already using v1.09q-ch and don't use thermocouples, inkjet functionality or a Roland mill, there is no need to upgrade to this version.by chrishamm - Ormerod
Despite the loss of RepRapPro, I'm pleased to release Duet Web Control v1.08 and RepRapFirmware v1.09r-ch for the Duet platform. I think this new web interface version leaves nothing to be desired, but if you're wondering what has changed this time, here the full changelog: Quote Cookies are no longer used and settings are now stored in localStorage Added French and Swedish translations (thanksby chrishamm - Firmware - mainstream and related support
Just be aware that I won't officially support IE/Edge as long as these browsers require so many work-arounds. You don't need to ignore cookies in the webserver either, my next web interface release moves all settings to HTML5's localStorage anyway and I believe this feature isn't supported by IE either. I hope that will at least partially fix the connection problems a few users have been experienby chrishamm - Ormerod
I find it really sad to see RepRapPro Ltd closing up, especially after the vast improvements we have seen over the past years. But Adrian's statement makes clear why this had to happen and I agree that such a decision - even if it's tough - must be made before it's too late. Just as many others here I found Ian's support to be excellent throughout and I wish him and all other ex-employees the verby chrishamm - Ormerod
The main reason the progress bar and the end-time estimations don't work properly is because your G-code does not contain any comments. Which slicer did you use to generate that one? I'd check if there is an option to enable them so that the filament usage can be used. As for the object height detection, the easiest way to prevent the firmware from parsing an additonal lift is to encapsulate theby chrishamm - Firmware - mainstream and related support
Why do you probe at X=0 Y=0? I guess the probe will stay above the endstop piece when you home Z, so it's not surprising that you don't get a reasonable Z value. Also, be aware that the Z trigger value of the stock O1 probe changes depending on the external lighting, so I really suggest you consider to upgrade to dc42's IR probe. Try to change G1 X0 Y0 F2000 to G1 X45 Y0 F2000, that's what RRP'sby chrishamm - Ormerod
I'm no fan of defining tool T127, so if you can, remove the line starting with M563 P127... from your /sys/config.g file. After that, restart your printer and check if that has any effect. As an alternative (assuming you just cannot select T0 on the web interface), send "T0" via the G-code input boxes. If that doesn't work, please check if you get any error messages in the G-code console and iby chrishamm - Ormerod
I suspect this problem may be related to too long cookies being sent to the Duet as part of HTTP requests. Fortunately 1pennyshort informed me that there is now a better way to store configuration parameters in the web browser (in detail that's HTML5's localStorage), so I'll drop cookies in my next DWC release and use that instead. I hope this will eventually eliminate this kind of connection proby chrishamm - Controllers
Quotedmould I decided to get my X-arm anodized - mainly for the appearance (it's a really nice electric blue colour). But anodizing also creates a harder surface on the aluminium, and perhaps that it why there is no sign of wear under the bearing despite having had a lot of use. Anodizing a single part is however likely to cost as much as the arm! Dave Sounds interesting, now I'm curious whatby chrishamm - Ormerod
Hi Dave, Quotedmould 1) How many people need all 3 time estimates? (Filament, layer, file). Personally I only ever bother with the estimate based on filament use. If that's not available for any reason the next best IMO is layer time, and finally file usage is usually the least accurate IME. The three estimates take up quite a bit of space on the page and yet two will likely never be looked aby chrishamm - Ormerod
QuoteTreito BUT the new solution is far away from beeing better. There is no guidance for the cable. Now I need about 1 meter space in the y-direction because of the cable for the heated bed which is going somewhere like it wants to go. Bad idea. Really bad idea. There is actually a solution, but it may need some further customisation to fit the latest O2 models:by chrishamm - Ormerod
Well... :-)by chrishamm - Ormerod