I have changed the wiring and the machine is now working again! Thank you! Frankby Cash - Ormerod
Hi DC42, thank you very much, I think this is the problem! I found the desciption on the website about the changed wiring. Will check this in the evening... Frankby Cash - Ormerod
Possibly I used the wrong Firmware file for a newer duet board. Will check this this evening... Frankby Cash - Ormerod
Hi there, I updated my Firmware of the ReprapPro Ormerod today (0.60 to 1.19) and now the Z-Probe (poor old original IR-Sensor) is showing only values between about 300-420. In result the sensor will not work correctly as Endswitch for the X-Axis and also not for the Z-Axis! In my old configuration I had a threshold value of 500, like in the new firmware. It looks to me that the values are too lby Cash - Ormerod
Hi all, I am also using 1,75mm Filament diameter and that should be reflected at the Cura settings! Please be sure, if you are using Cura 14.01 use the preset file from the github repository. If you are using Cura 14.03 use the preset file posted a few thread ago... For Cura 14.03 the headers in the preset file are ending with "_0", e.g. . If you are using the preset file with at the beginningby Cash - Ormerod
Ok, I think this is possibly a general Cura problem. Have you tried another object? Cura sometimes removes walls completely, if they are too thin. Cheers, Frankby Cash - Ormerod
Hi Tim, would you attach the first about 50 lines of the generated gcode, than I will have a look at it!? What happens if you switch to the layer view in Cura? Cheers, Frankby Cash - Ormerod
Hi, It looks like Cura 14.03 has changed the headers ( to ) and ( to ) in the "current_profile.ini" file and therefore ignoring the settings. Changing this headers would help, I think. I have changed this in the attached file! By reviewing the generated gcode file it look ok for me now with Cura 14.03. Could someone please test it on the real hardware? Cheers, Frank Edit: Please use the otby Cash - Ormerod
Hi again, I'm so sorry, I found out that i did made another bug! I don't know how my tests are passed! I did only a quick view on the generated g-files and they looked correct, but today I looked again and I have seen a problem. I think the original plugin was still in the buffer at my last testing or so. Please try the actual file on Gitub: https://github.com/Cash70/EAtoR Sorry for any inconvby Cash - Ormerod
I have udated the Github repository! Hope it is all correct now! Sorry again! Cheers, Frankby Cash - Ormerod
Quoteormerod168 QuoteCash Possibly you changed something inside the start-gcode (added M-Commands)? Cheers, Frank If you were referring to me, no change to settings in Cura whatsoever, just substituted old EAtoR.py with the newly posted one and sliced the same file again (zombies.stI) Erik QuotePaulHam Why would it start to cause problems on Monday night? When I have been using it without proby Cash - Ormerod
Possibly you changed something inside the start-gcode (added M-Commands)? Cheers, Frankby Cash - Ormerod
Hi Paul, I am sorry, but I think there is something wrong if M-Codes are included in the lines that contains also X Y and Z values. I thought I changed this already! Please try the attached version of the Plugin, I will commit the changes this evening to Github! Cheery, Frank Edit: Ok, I used a wrong version for the github repository, sorry again!by Cash - Ormerod
Hi 88Zombies, I think the .ini files are not in the correct folder! They should not be in the "plugins" folder, only the plugin itself should be there! The two .ini files should replace the original .ini files inside the Cura program folder "C:\Program Files (x86)\Cura_14.01\Cura" or the equivalent program folder on your MAC. Be sure to replace the original files! Then be sure to check that theby Cash - Ormerod
Hi all, now the files are on a Github repository: https://github.com/Cash70/EAtoR ! The Plugin now contains a modification from the forums user "KP" with 2 additional parameters to set a new temperature (bed and extruder) after the first layer! Cheers, Frankby Cash - Ormerod
Quotedmould Not done any prints yet, but I noticed that if I reference the temperatures in the start g code, Cura will not set a temperature at the start. If the temperatures are not referenced (or the lines are commented out as they are in Cash's sample ini file), then Cura does indeed set the temperatures right at the start as you say. Good to know that! Also a good workaround I think. Frankby Cash - Ormerod
Doing this inside the start-gcode is not possible, because Cura is setting the temperatures ahead of the start-gcode. But I think at least the plugin can do the trick. I will see what I can do! Cheers, Frankby Cash - Ormerod
Hi Paul, i think Z180 should be the default value! Frank Edit: I remember that I had also problems with the Z-Axis at the beginning with vibrations. The bearing was not fixed inside the gearwheel and higher speeds of the Z-Axis caused a heavy vibration. Now I wound a little bit of isolation tape around the bearing inside the gearwheel (the hole for the bearring was too big) and it runs smoothby Cash - Ormerod
Hi Paul, are you using the actual 057n firmware from dc42? You could also try my V2.3 settings above at this thread, this was using slower settings! 30 minutes ago i finished a print with this settings without any problem. Ok, i think the bottom layer could be printed at a litte bit lower speed. I have also this heating issue, but it's no problem for me... Frank Edit: I think you could also tby Cash - Ormerod
Hi Arnaud, Yes, you can add or remove the plugin as you like. It is also possible to select a different machine, but i think you have to add or remove the plugin seperately. I'm not sure how the other settings are affected if you select a different machine, i use only one at the moment! Cheers, Frankby Cash - Ormerod
Quoterayhicks M203 sets the maximum speed (by default this is capped at 50mm/s or 3000 mm/minute in the firmware - I increased this limit in the version of firmware I uploaded: M203 X6000 Y6000 Z500 E3000 ; will allow 100mm/s sliced gcodes to work... if they have time/distance to get up to speed Ray I have added this line to my settings inside Cura (start g-code) and found out, that the pluginby Cash - Ormerod
I found out also, that if the walls are too thin, Cura does not print anything sometimes. You can verify this in the layers view. Possibly Cura removes structures that are smaller than the 0,5mm that the extruder is able to print. Frankby Cash - Ormerod
Hi Ray, thank you for the explanation! I will try the other firmware and the M-Codes this evening! It is not my goal to get the maximum speed out of my machine, but the best quality and an acceptable speed with no step loss! Frankby Cash - Ormerod
Hi Paul, Print speed is for perimeters (the surface), if you set another speed for infill. I set print speed to 15, infill to 100, bottom layer to 30 and travel speed to 100! But you can change this to match your requirements! Cheers, Frankby Cash - Ormerod
Happy to hear that! I'm using Cura all the time at the moment! You should also take a look at this thread: forums.reprap.org to archive best results. With that modified firmware I am using 15mm/s for perimeters and 100mm/s for infill and the results are very good. Better quality with less printing time! Frankby Cash - Ormerod
I have reduced now the perimeters to 15mm/s and infill/movement to 100mm/s as "quality settings". That looks really perfect (see attachment). And no bang/step loss so far! Frank Edit: Ignore the lower corners, they could not printed very good in the air! But the edges are very good... Edit2: See second attachment, robots, from left to right, Perimeter/Infill/Moving: 60/60/60mm/s - 20/20/20mm/sby Cash - Ormerod
Now i have printed 1 full size Cura Robot with 20mm/s and 2 Cura Robots with 60mm/s. No problem, no step loss, only the quality is not as good as with 20m/s. I am printing actually with 30mm/s perimeters and 100mm/s infill... Very smooth movements! Before i was not able to print the robot with 40mm/s without a step loss! Thank you again, Ray! I think i will save a lot of time in the future! Frby Cash - Ormerod
Printed the first object (Cura Robot scaled down by factor 0.5) with 60mm/s all speeds with no bang heard! Very happy! Frankby Cash - Ormerod
Quoterayhicks <- this seems to be working, I'm printing with 75mm/s on perimeters and 100mm/s travel without bangs, I had to slow the same print down to 40mm/s for the bangs not to affect the print quality on the same model previously. Thank you Ray, i will try it! I think all that code is experimental! First try looks very good, great work! Also web access is working. I will experiment nby Cash - Ormerod
Quoterayhicks I'd presumed something like that from reading the code, but it does work if there's time for it to slow down (ie direction is accounted for elsewhere) - it's just that if the next move is too short for deceleration but at the same speed, the previous move doesn't seem to bother decelerating and it's all down to the last, potentially too short, move to get rid of all that momentum Iby Cash - Ormerod