Posts made by timonemycat

I removed the head and placed a bubble level on the top, and noticed a bunch of variation at the points specified in bed.g. Results are easier described with the video: https://youtu.be/VbzuqFZhGNA.

The tilt made me think it was an issue with the X-tower because of the deviation opposite it, so I checked the carriage and head effector more closely, and found that the threaded shafts that I'm using to attach my tricklaser carbon rods, (the version with ball links, not the injection molded ball links) are being bent by the way that the Rostock Max V2 carriages and effector attachment points are made.
I'd think that bend is a problem.

I've gone about replacing these components with the injection molded ball link versions to remove this incompatibility in the design.

That's exactly the page I followed, Michael has been invaluable to me and the community. I followed it to the T, and I'm still getting fairly bad results out of it. Could it be endstop inconsistency? How do you like the smart effector over FSRs?

Hey community,

I've got a Rostock Max V2 with a Duet V0.85 motherboard, and I'm using Tricklaser carbon arms and FSR sensors underneath a thick sheet of melamine for a rigid setup for autocalibration. I've checked to make sure my build is accurate; bed is perpendicular to the towers, the rod lengths are exactly the same between pairs, my carriages are solid.

In spite of all of this, I haven't been able to get the deviation under .134-.136. Every time I've calibrated gets me somewhere around there. What is a good deviation to be shooting for on a successful calibration?

I've gone through and updated the h parameters in the bed.g file to account for variances, which are very small, let me know if these are too small to have significance. They don't seem to help the deviation at all. The h values I've gotten are:
-0.03533333333
0.003333333333
-0.074
-0.03333333333
-0.07933333333
-0.044
-0.07
-0.027
0.02233333333
0.01233333333
0.002
0.01833333333

These are for the standard 18 points on my bed. These signify that the bed is pretty rigid correct? What other areas should I be checking for build accuracy? I've followed David's post at https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer, and haven't been able to spot an error, and haven't been able to improve the deviation. Any help would be greatly appreciated!

Thanks!

Mike! Noted, I'll look into that once I start seeing the tuning issues arise, thanks!

Appreciated, the motor current was too low, and in addition, I found a G92 command down lower in my config file that was overwriting the line I had above, those two things got me off and running.

Appreciate the help.

I've been working to get my zesty nimble set up on my Rostock Max V2, and I've got everything together.

The extruder motor is a KL17H248-15-4A, and I'm using a Duet v0.85.

Using the initial settings that Zesty put out for setup with a 1.8degree stepper motor, I'm seeing the extruder put out about 5% of what it should be. It's turning, and it's turning in the right direction, but I haven't been able to get it to the right speeds, as with the way it currently is, I'd need a steps/mm around 67000 (WRONG hahaha).

Here is my stepper section from my config file:

M350 E16:16:16:16:16:16 I1 ;1/16th Microstepping on Extruder motor
M92 X80 Y80 Z80 E2700 ; Set axis steps/mm
M906 X1000 Y1000 Z1000 E500:500:500:500:500:500 ; Set motor currents (mA); set each extruder explicitly
M906 I100 ; Set motor idle factor to 100% while testing so they don't idle at all
M201 X1000 Y1000 Z1000 E120 ; Accelerations (mm/s^2) Set all E-motors the same
M203 X20000 Y20000 Z20000 E1200 ; Maximum speeds (mm/min) Set all E-motors the same
M566 X1200 Y1200 Z1200 E60 ; Maximum instant speed changes mm/minute. Set all E-motors the same

I'm wondering if it's just something simple that I'm missing here?

Thanks for any help.

Thanks for the help. I got it running, entering the ip address assigned.

I'm going through the autocalibration process, and noticing some wierd behavior. I initially tried a G30 S-1 command above a bed point, and the probe moved to near the z tower, then between the z and x tower, and dipped like it was changing tooling. Is there something with the updated firmware that I wasn't able to find in the release notes? It's like I need to turn off probe deployment or something, as I'm using FSRs.

I am able to connect to the printer now via pronterface, but still not via the webcontrol. I deleted the /www folder and unzipped the duetwebcontrol v1.22.6 to a new www folder on the usb drive. As a basic check that it's connected, the orange light on the ethernet port should be on, right? Should I be able to ping the printer in the command prompt? Is there a default sys file that I can compare to my current file to make sure I have everything right as far as network goes?

Hey there Duet Community,

I've been trying to get my rostock max v2 up and running recently, and I'm on the Duet v0.85 motherboard.

I was on v1.13 up until today, when I decided to update. I tried to update to 1.21 through the web interface, and then went to update the sd card with the updated webinterface folder. I know I did something wrong, because I couldn't connect to it over the web.

I plugged the Duet in and got the driver installed so now it shows up properly in the device manager, but trying to connect via BOSSA does not work. Using YAT, I tried to get the Duet to respond to an M115 command; it shows that its connected, but just says OK in response.

Is there a good firmware to start with on the 0.85 motherboard? What can I do to get the Duet V.85 to a working firmware again if I've screwed things up?

I knew I shouldn't have gone to update the firmware, things were working fine! I appreciate any help given.