Topics created by blandified

@dc42

Just an update, you are legitimately and objectively awesome. We got it to work!

Just to try to help people in the future who have this same problem, in your config file, make sure to set the axis mins and max, otherwise it won't be able to move in the direction where the mins and max aren't defined.

We also set our X axis offset at 50 as a test, but the first print sometimes the X axis won't do the offset, but after redoing the same print file, the X axis offset will work so I think it has to do with the same problem. Will report back with an update

@dc42

Thanks for your help!

Just to updated, we haven't done the cooling portion yet but we wanted to let you know about the DC regulator you recommended.

So when we heat up to say 40degC, the peltier only receives anywhere from 7V to 10V, so it's not like it is receiving the full 24V. Because of this we haven't used the peltier yet. Just to let you know

This is addressed in https://github.com/dc42/RepRapFirmware/pull/179 but in firmware as @tjb1 suggested. Then it will be only a matter of adding the respective M106 ... commands to your config.g - though I am not sure how DWC will react to setting a fan slider to 100% but the output being limited to e.g. 50%. But since there already is a lower limit I guess it will just handle this out-of-the-box as well.

wilriker opened this pull request in dc42/RepRapFirmware closed Add a maximum fan speed parameter and enforce it #179

I'm glad you solved it. Your M584 command creates a new axis U, so it needs to be before all other commands that refer to U.

@Jackal:

Maybe you have set your printer to use delta kinematics.
Please show us your config file

Hey everyone.

So I used this tool here: https://configurator.reprapfirmware.org/

I made sure to customize it as closely as possible to what we need (mainly making sure to set the coordinates to Cartesian), and then uploaded the generated zip to the Duet. We ended up having some communication problems, so we redid the steps and had to disable DHCP and enable static IP. After this, it worked!

We are now able to send individual X Y Z commands and it moves the appropriate motor by itself, so it seems your suggestions was spot on! Thank you

@Danal:

Also, to your original question, there is no "recompile". Using the above, just change an html or js file in the editor, save it, refresh the browser.

When all your mods are finished, you may wish to compress and zip up YOUR version and put it on your Duet. You don't have to… it runs fine from a local PC file system. If you wish to put it on a duet, you can:

Follow the build scripts, which only run on Linux (not even a Mac!!). Then upload the resulting zip via DWC's standard upload.

Do the rough equivalent of the build scripts by hand. That is, compress and zip and gzip things. Personally, I'd skip all the minifiy stuff if I was the only person using it. Again, upload via DWC.

Don't even compress or anything, just load your files "as is" to the Duet SD. If you do this, there is one quirk to know about: If Duet sees a given file, say "reprap.htm" and the gzipped version of that same file, say "reprap.htm.gz", it will use the .gz. The easiest way round this is to put the SD card in a PC/Mac and completely clean out the /www directory, then put your files in /www.

Any of these three will work fine. I've done them all and verified that they work.

Dude, I can't believe how helpful this is!! You're amazing!! Thank you so much, this is exactly what I am looking for.

The way our project is set up, we don't have physical access to all our gear (duet, rpi, etc) during the week since it stays in the boss-man's office, so that's why I spend all week asking questions, so when we meet in our weekly meeting we are ready and raring to go lol.

This is such a great few posts, thanks again!

It doesn't forget about the previous tool, it sets the previous tool to its standby temperature. In FDM printing, the standby temperature is normally set a little lower than the normal extrusion temperature to control oozing.

@dc42:

DWC runs in the web browser, so in your setup using a RPi you would need to replicate whatever DWC functions you want to use on the RPi, for example in Octoprint.

Hey dc42, hope you're doing well.

Would this example of python and http POST requests be what we are looking for?

url = '[Duet_IP_Address]/rr_upload?name=gcodes/[filename].gcode'
files = {'file': open('[filename].gcode', 'rb')}
values = {'author': 'John Smith'}
r = requests.post(url, files=files, data=values)

As mentioned in the build instructions, you need to have a copy of the 'make' program on your PATH. However, you can probably make do without one if in the project properties you go to "C/C++ Build" and select "Builder type: Internal builder".