Posts made by mperdue

Thanks for the replies. I’ll take a look at the available expansion boards and give it a shot.

I'm currently running a printer with a tool changer using a Duet 2 WiFi and Duex5. This allows me to have 4 tools but I sometimes it would be nice to have one or two more. Yes, I know that will be true regardless of how many tools I have, but please humor me.

It's my understanding that I can add two more drivers to the Duet using a header connector. I assume that this is best done with a small PCB plugged into that header. So, my question is, is there a PCB available for doing this or will I need to roll my own?

My first tool change test worked! Now I need to get the tool connected to the Duet so I can test printing.

@Phaedrux Yeah, that's what I did. I was in pretty good shape with most of the files. Now it's time to add the tools and the macros to support tool changing. It's all going smoother than I expected.

@Phaedrux Thanks for posting that. I was pulling what little hair I have left out while trying to figure out why my freshly upgraded devices wouldn't talk to each other. The M575 fixed me up. Now I need to go through the Gcode files and make sure I have RRF3 compatible files installed for everything.

It looks like I can just go directly to the current release. I’m now running the current version and the basic machine functionality seems to be there. My PanelDue no longer works so I suspect I need to do some updates on it as well. Fortunately, it communicates with my iPad well so I’m able to keep going with this printer build.

Now i need to figure out how to ge Bossa working on my iMac Studio.

@HebigT Thanks. Once I get to 3.0 do I need to step thru all the upgrades or can I go directly to the latest version?

I'm reusing a Duet Wifi that was previously used in an older 3D printer. It will be placed in a new Jubilee printer that I have built. I figure now is as good of a time as any to move to RRF3 since I have the standard config files and stuff needed for the Jubilee build. What is the best way to move to RRF3 in this situation. Is it best to clear the firmware and reload it from scratch or should I step through the updates.

Any suggestions appreciated.

@pjl It certainly looks like they have invested a lot of time and money into this machine. The number of demo units that have been placed in reviewers' hands bodes well for them already having the ability to make and sell the device.

I’ve decided to take a chance with this one.

I've been looking at the information on this printer, too. It will be interesting to see if it actually lives up to the hype, assuming it is ever released.

The vibration compensation and LIDAR aspects of the printer could certainly be good things to have.

I finally had an opportunity to correct this problem. It took a couple of attempts but the first printer is back on the network and working fine. The other one will be reconnected later today. Thanks for pointing me in the right direction.

Thanks.

@OwenD said in Redefining WiFi:

First see

https://duet3d.dozuki.com/Wiki/Gcode#Section_M588_Forget_WiFi_host_network

then

https://duet3d.dozuki.com/Wiki/Gcode#Section_M589_Configure_access_point_parameters

@bearer said in Redefining WiFi:

@mperdue said in Redefining WiFi:

newer firmware required more than the 2 characters I was using

sure about that?

In any case, look up M587
Newer firmware in my WiFi router, not the duet.

I had to reinstall my WiFi in my home today and was not able to use my existing SSID because the newer firmware required more than the 2 characters I was using. Now I need to reset my Duet WiFi network connect but I’ve been unable to find the proper instructions. Can someone point me in the right direction?

Thanks guys. I knew someone here would know what to do.

I've always noticed a difference between the various time estimates with the layer based estimate being very far off the other two - sometimes by two orders of magnitude. I finally looked at it and the reason is that it calculates the time based on some period related to the time to print a layer (current time, average, whatever) times the number of remaining layers. The problem is that the number of remaining layers is based on the stopping position of the Z axis divided by the layer height. In my ending script I always send the Z axis to 300 to make accessing the part easier. This causes the system to assume there are 2999 layers when my layer height is set to 0.1mm even when the actual part is only 10mm tall. Is there a code that can be put in the script to tell it that the part stops here?

No, it's not needed. In my case the printers are not near my computer so the PanelDue is very handy. I would not want to work in my setup without the PanelDue.

Yeah, I had moved that when I updated the firmware but I guess I forgot to remove it from the original line. Thanks for the heads up.

Before today mine was significantly slower than yours.