You will have news, I hope that no, but... If you see in the press at the end of January, in the events section, that there has been a fire in Valencia (Spain), by a 3d printer ... it may have been me
@merlin246 I suspect that your university WiFi uses WPA2-Enterprise. This is not supported in RepRapFirmware yet, however we have work in progress which will make it easier for us to add support in future.
@dc42 Exact same issue happened to me when building the last printer. Was a bad connection in the CAN cable. I had uses a solder sleeve to attach the tool board wires and when the cables got moved just right it lost connectivity. Re-did it with direct solder and its been fine ever since.
@o_lampe assuming that you don't have a DueX connected to the Duet, RRF will know that they are not TMC2660 drivers. Just configure the microsteps/mm value in M92.
@timtom you will need to fill in the form anyway so that we can contact Filafarm and authorise them to replace your board. Yes Brexit is a horrible mess and makes things difficult, so we will arrange for Filafarm to provide the replacement.
We thought that since the wifi was connecting when the Modix was turned on, everything was fine. Wrong. After some minutes of printing, the disconnect/connect behavior begins again. See screen shot. I have a new board sent b y Modix, so we will put that in next week. The adventure continues.
This allows you to have (say) 1 tool at 0,0 on XY and then another tool with a different offset when its picked up by a toolchanger. these offsets are applied as described in the documentation you quoted.
@j3d the reason is that we want file uploads to be as fast as possible, and SD cards prefer large block writes; so RRF uses a 8K write buffer. In contrast, it's rare to download files from the Duet, and other file reads from the SD card don't need large blocks of data in one go; so RRF uses much smaller read buffers.
none of the files on the SD card are ever changed by the fw
there are some files which are changed:
config-override.g <- every time you send M500
heighmap.csv <- every time you probe the bed and save the height map
*.json within the /sys directory <- various DWC and plugin settings that can change
The firmware binaries and other /sys macros are not changed by the printer. and in the case of the /www directory and firmware binaries, those are on github to download again.