@dc42 said in ZProbe Mode 4 enhancement:

I/O mapping strategy of RRF is being reviewed because the next generation Duet needs something more flexib

Sounds great! I got some more pins I'd like to remap, I'll wait and see what you guys churn out.

@resam said in LaserWeb4 Support:

Did you see M452? It provides a laser mode. There are a few forum posts here describing how to use it, and also some problems with it.
I'm using LaserWeb together with M452 and M3/M5 command to do laser cutting (no engraving or rastering).

Yes, I'm aware of this, and using it currently.

Just saw the last comment from @dc42 on that thread though:

Support for using the S parameter to control laser power on G1 moves will be added in firmware 2.02.

So this thread just became redundant 🙂

Hi everyone, I solved this buying a silicon cover for the heat block (as Phaedrux mentioned) you can get some pretty cheap on Ebay, I also realised that you don't need to have a E3D hotend, they are not available for every hotend, but you can found for the most common. With this the temperature only goes down 5 degrees and in a few seconds it's in the desired temperature again.
Thanks everyone!

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 will only change the places you told me. Your information is valuable for me to further understand the code.

No spaces in my path. It is on a different drive, due to available disk space, and the path is a bit longer.

@dc42 said in Guidance regarding Source Code:

The "main program" file is in project CoreNG because it does initialisation first. It calls UrgentInit and later AppMain in the RepRapFirmware project.

Make sure you use the v2-dev branches of RepRapFirmware and CoreNG because that's where development takes place at present.

I can only see 'UrgentInit' being called from '/src/Platform.cpp', but that's under the main tree, not v2-dev branch.

Can't see 'AppMain' being called anywhere.

I know it's a pain to create, but I think a wiki with some overview and guidance to help understand the software structure and flow process would come a long way in helping developers contribute to the duet project.

Not have an attached SD card would be a severe disadvantage, so I suggest you use SPI. Alternatively, use a SAM chip with HSMCI support and more pins. For the Duet Maestro, we chose the 100-pin SAM4S.

Ok, I'll do that. Thanks.

Probably would be a good idea to have some error rejection built in to the upload function. Maybe this can get moved to the DWC/firmware wishlist section?

You are welcome!

Hi Danny,
I am mechanical Engineer and i have my own job that we make plastic injection mold. So we have 3 EDM machines and CNCs..
I used several CAM programs and now i use PowerMill. I just build my 3D printer with duetwifi , duex2 and paneldue 7". I am suffering from slicers because i can't control everything but I get used to it all day.
I developed all electric plastic injection machine controller by using PIC32MZxx now it is testing phase.
Cafer

OK, thanks a lot.

Somehow, my GitHub desktop repository for the DuetWiFiSocketServer was not showing me that there even was a 'dev' branch, so I kept checking and synching to just the master.

I downloaded the ZIP file instead and it works (builds Duet2CombinedFirmware.bin) now.

Window, Preferences, C/C++, Indexer

I had to change the Indexing Strategy to "Use Active Build Configuration" to make them go away.

@kelchm, heated enclosure is more complicated and requires all printer components to handle such temperature.

@vsch, when I was mainly printing ABS, I was thinking to heatup the cooling air too!

I think it is possible to simplify your setup: in order to get a constant temperature, independently of fan speed, I would build a heater element with a high thermal inertia, and make a long exchanger, so air will output at a constant temperature, whatever speed is. For example, a few turns of copper tube cast in a cement bloc, with a good heater cartridge.

Another idea I had, at the time, was to make the air circulate under the bed, as it is also heated up at 110°C. I'm about to receive my silicone bed, so I will see if I can make such setup.

BTW, point 2) is not that easy: if you pause printing, you will have to manage the filament, and may need to purge before restart printing.

Yes it should be fixed. Please test it.

When we change the format, we change the magic value to indicate that.

I didn't update the buildinstructions.md file after I added the Tools folder to the github project. I have done so now.

I have modified the source code to declare the time field in the software reset data as 32 bits unsigned, with casts to and from time_t where necessary. This will be in the 1.21RC3 source code.