Quotedc42 Hi Mark, I'm guessing that "inf" means infinity. I'll take a look at the firmware and see if I can work out what could be generating that, and how to fix it. There was a problem in my PrintMonitor class, however a fix for this issue (in fact a possible division by zero) is included in my 1.09a firmware release.by chrishamm - Ormerod
Quoteshauna Quotezombiepantslol You must select the first tool by sending "T0" first before you can heat up and extrude any filament. Also see I did have the tool selected with all my original problems. In this case it sounds like you never reach the target temperature and the cold extrusion prevention kicks in. You can verify this by checking the G-Code log for warning messages. Quoteshaunaby chrishamm - Ormerod
Quoteshauna The hot end doesn't always heat up and when it does the printer moves as if was printing but it does not extrude anything. You must select the first tool by sending "T0" first before you can heat up and extrude any filament. Also see If your nozzle takes a long time to heat up, the easiest way to speed it up would be to increase the 'S' term via M301. You could try this out by sendby chrishamm - Ormerod
I must admit I was facing the same issue, but I finally found the solution: I replaced the printed Y parts (y idler bracket and y motor bracket) when I got my Ormerod 2, but the front left corner was always off by 0.4mm - 1.0mm. So I reprinted these parts again (if using ABS you definitely need a brim), mounted them once more and checked my bed level. Again, the bed was off by a fraction. So I tby chrishamm - Ormerod
Hi nebras, The current RepRapFirmware will run on an Arduino Due, however be aware the the Duet uses several pins that are NOT available on the Due. I guess it would be possible to simply change the missing pins in an individual firmware branch, but be aware you'll have to maintain your own fork in this case. I don't know Grbl, so I cannot say what you need to consider if you decide to go with iby chrishamm - Ormerod
QuoteDarathy if it no trouble i would be interested to test it No problem, here you go Zonzo, your Slic3r config looks good to me except for two things: You have this "M203 X6000 Y6000 Z500 E3000 ; Allow 100mm/s speeds" in your start G-code but you don't need it, it actually slows down some moves, and you have slowdown_below_layer_time set to zero. In Slic3r you can find this setting if yoby chrishamm - Ormerod
Trust me, ABS is the wrong material for that testpiece. I tried to print one on my Ormerod 1 a few days ago but then switched back to PLA, because the X+Y columns will actually deform a tiny bit as they cool down. The reason why your Z column looks so horrible is the lack of cooling. I replaced my fan duct with a modified version of the O2 variant with enlarged cooling holes about a week ago, hoby chrishamm - Ormerod
Hello everyone, I've released version 1.09a of my firmware fork on GitHub. It provides several improvements and a few bug fixes, but the major change in this release is the introduction of a new Makefile to build the firmware easily with Arduino 1.6.4. For Windows there is also a build script available, however that script does NOT evaluate the build dependencies yet. This means, if you're usingby chrishamm - Ormerod
I have an improved version of the Z height detection ready, however I want to do a few more tests before I release a new firmware version. That firmware binary (or rather the changes from it) will be needed to hopefully fix your issue.by chrishamm - Ormerod
Which firmware are you using? My Duet Web Control should automatically show your extruders and heads, but you need firmware 1.09 for it to work. And please post your config file, it might help, too.by chrishamm - Ormerod
Your output looks good to me, and it tells me you already have a tool defined. FYI you do this via M563 in your config.g file. Send "T0" (or T) to select the tool, then you will see that M105 reports the current temperature as seen in the instructions. Also check out this article. The H0 and H1 values report the current and target temperatures for all configured heaters. You'd only have to worrby chrishamm - Ormerod
I've just looked at the code (of my fork) and it looks like the fan value is toggled only when a new move starts. This means you must either send a (valid) non-extrusion move or M107 to turn it off again.by chrishamm - Ormerod
Hello Sven, Can you post the end of your G-code file? I need to know what your last two G1/G0 ... Z# codes looks like.by chrishamm - Ormerod
My fork uses the same fix from dc42's fork, so I'd expect it to work just as well. The web interface usually doesn't interfere with M571 unless you enforce the current fan value, which is occasionally handy to override the generated M106 codes from a G-code file. So unless you've checked that option on the Print Status page, the web interface won't change the fan value automatically.by chrishamm - Ormerod
QuoteDarathy should i increase Z Motor current after installing the ALu X plate? have it set to 800 atm That's not necessary IMO, I've been using 800mA on my O1 with that alu x plate and that setting appears to be sufficient.by chrishamm - Ormerod
Hmm, works on my printer (I know the firmware version says 1.09a but the webserver code is the same as in the official 1.09 version): dc42's suggestion is good though, please post the output of M122 and your entire config.g file here. Edit: I've just spotted you were trying to upload your config file via Upload & Print, which isn't correct. Go to the Settings page and upload it there.by chrishamm - Ormerod
In my opinion it is a bit unfortunate that the front linear bearing of the Ormerod Y axis isn't held in place very tightly by the supplied plywood rib, which in my case resulted in the fact that I could easily push down the front of my heated bed by 1mm or so. That's why I decided to design my own clamp and mounted it on my machine: Now with that clamp mounted the bed is properly secured and Iby chrishamm - Ormerod
Sorry to hear you were experiencing this kind of problem, but it sounds very unlikely to me that this was caused specifically by my firmware fork, especially because the official RRP firmware 1.09 uses exactly the same move and hardware code as my 1.08f release. Can you confirm the precompiled firmware binary is identical to the one I provide on my GitHub site (preferably by comparing the checksuby chrishamm - Ormerod
If anyone notices that my modified version cracks, please let me know and I'll reinforce it a bit more. So far I'm quite happy with my modded version, though.by chrishamm - Ormerod
QuoteDarathy i think you dont have java installed ,web interface requires it i think Urgh no, the web interface is entirely based upon HTML5 and JavaScript, and you don't need Java to run JavaScript.by chrishamm - Ormerod
Quotecua193 I do have another problem. The computer I wish to use for the printer won't show the Web Interface properly - see attached file - with or without the LAN cable connected. This is obviously a Windows problem as the file works on my other computer which has the same version of XP. You may want to try this: I've heard of a few users who could fix their connectivity problems by resettinby chrishamm - Ormerod
I believe those parts are identical. I exchanged the z-lower-mount of my Ormerod 1 a while ago and modified it to use M4x12 cap head screws instead of the countersunk ones, see here:by chrishamm - Ormerod
I haven't experienced this white page problem once, so I can't fix what I can't reproduce. If anyone provides a Wireshark capture though, I'll look through it again. As said earlier Android's stock browser is no longer supported, so either try out Firefox or Chrome if it's supported on your device. I did receive an Android WebView update a few days ago on my Lollipop phone, but I don't have theby chrishamm - Ormerod
Yep indeed, I doubt we would have ever gotten to this stage of firmware quality without David's contributions. When I started my firmware development about a year ago, I chose David's fork as a base for a reason, especially because it turned out to be somewhat usable compared to the old RRP firmware at that time! I remember the old firmware used to hang up quite frequently and didn't even have thby chrishamm - Ormerod
That sounds reasonable, I may adopt your changes in my next firmware release. I'll investigate this problem once I've managed to get the firmware to compile again with Arduino 1.6.4 - the board files are ready and work, but Lwip's directory structure is too complex for Arduino's build system, which is why I'm considering to move away entirely from Eclipse/Arduino IDE for compilation and to use qmby chrishamm - Ormerod
I tried to print ABS on sugar coating many months ago, but I found it wasn't sticky enough for larger objects. Then I bought two alu plates, but unfortuantely ruined both of of them (first one by printing Nylon on it and the second one when I did some experiments with SoftPLA). I guess they have some kind of PEI coating which is excellent, but it only works with pure PLA and ABS AFAICT. If affordby chrishamm - Ormerod
Treito, I was only talking about the Pronterface / Arduino IDE serial log. If you don't get any error messages, you could enable debugging for the network and webserver modules by running M111 S1 P1 M111 S1 P2 from either Pronterface or Arduino's serial console. This problem sounds very weird to me, I still have no explanation why it's working for you with dc42's fork, but not with mine. A Wirby chrishamm - Ormerod
QuoteTreito Running a linux 64-bit-System I was not able to start Slic3r 1.2.6 as it crashed immediately. The reason was quite simple: One delivered .lib was incompatible with recent graphics driver from Nvidia starting with 340.xx, I think. I had to rename one lib to get Slic3r run. Same story on my Linux installation, but compiling Slic3r 1.2.6 from scratch fixed it for me.by chrishamm - Ormerod
Btw my next web interface version will also change the page title to the machine's name, that should make it a bit easier if you're working with multiple machines.by chrishamm - Ormerod
dmould is correct, providing your LAN address won't do any harm. I haven't spotted any problem in your config.g except for the last line: "T 0" should actually read "T0", else your first tool might not be selected on start-up. But that's another topic. When using my firmware fork (or the official RRP firmware), do you get any unusal messages in the USB log while attempting to connect to the boarby chrishamm - Ormerod