Topics created by ianlee74

@dc42:

See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Delta_printer#Homing_file, or read the comments in the sample homedelta.g file that I provide.

That F parameter is actually what I was thinking of when I said I didn't really want to increase the motor speed. However, its been many months since I last read that and had forgotten about the "300" values. I bet that's my issue. I'll double check that tonight. It's probably doing exactly what its been told to do. My Z height is somewhere around 335mm now…

Thank you!

I ended up loading the new beta firmware out of order, and promptly lost contact with the board. Reloading through the card wasn't working, and eventually wasn't responding to Repetier Host to even try that route.

I was waiting on Atmel for access to this file as well. The webmaster replied this morning after I reported the issue. She stated that they are having problems with myAtmel and asked what file I was trying to download, but then never replied after that point.

With this, I can at least boot a windows partition and get the Duet back online.

@T3P3Tony:

I have fixed the issue as far as I can test, took the opportunity to upgrade the forum software as well. please let me kow if its working for you.

Works for me now. Thanks!

@dc42:

Are you certain that it was reading config.g correctly? The only hardware fault I can think of that would change the behaviour in the ways you describe would be a failure to read and process config.g, perhaps because of a hardware fault in the SD card interface.

How can I know for sure? The controller board that I'm using now is running off the same SD card that I was using on the board that doesn't work. Because the new board hadn't been fired up in many months, all I did was upload all the latest .bin files and it works as expected. Is there some way I can test if the SD card interface is working as expected? FYI, my controller board is totally enclosed and the SD card wasn't touched at the time that it stopped working.

@ianlee74:

So, what does M500 currently do in RRF? Does the RR wiki need to be updated to say it isn't supported?

It already says that.

Good news. After some dissection today, I determined the extruder problem was due to a solder joint that was apparently not solid and came free. 🙂 Thank for the confirmation.

Ian

https://grabcad.com/library/duet-wifi-1

@dc42:

Currently the only way to change the name is to turn off wifi on your router so that the wifi module starts up in access point mode when you enable it.

I attempted that several times before posting this and could never see the AP again from my laptop the way I could during the initial setup. I'll try again tonight.

Thanks,
Ian

I finally tracked it down. I had a couple wires crossed. This also, unfortunately, explained why I melted my hotend this weekend. Thanks.

@LeonMF:

I gave up on the Tunell monitor as I didn't want to risk the electronics on my Duet.

I designed a simpler filament monitor using an optical sensor and a housing to hold the filament in the path of the sensor. You could do the same thing with optical or mechanical endstops. It will get you the filament out detection but not the tangled filament or clogged nozzle detection.

Thanks for the update, Leon.

Ian