Posts made by JoeBone

You get a biscuit today!!

That did the trick! thank you so much… I would have never figured that out.

HooRay!

The lights come on when triggered during any probing call but the machine will ignore it.
The only time I can get it to work correctly is when I send a G30 with nothing else (P… X... Y...)

with G30, the head moves down and begins to slow as it reaches the bed and then stops and reports the distance to the DWC.
Like it's supposed to.

When i send G29 or G32, lights come on, but will not stop...

When idle i can move a paper under the sensor and I can see the numbers change on the PanelDue and DWC.

Really scratching my head, Everything looks to be correct, and why it works OK with G30 but not anything else is beyond me.
This is the last thing I need to do to get the printer running. My boss is starting to give me side eyes.
lol

Do you think a fresh firmware install is needed??

I should mention that I do not have my thermistors or heaters hooked up yet, so they are reading 2000.
Everything else is operational, machine homes and jogs and can dry run gcode.

thanks!!

Hi David,

My config.g does have those items in it.

; Endstops
M574 X2 Y2 Z2 S0 ; Define active low and unused microswitches
M558 P1 X0 Y0 Z0 H5 F1000 T2000 I0 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31  P500 X0 Y0 Z1.5 ; Set Z probe trigger value, offset and trigger height
M557 R130 S20 ; Define mesh grid

Firmware is:

Duet WiFi 1.0
1.19.2 (2017-09-01) -Firmware
1.19.2 - WiFi server
1.19.3 - Web Interface

I just tested the following with the same result.

Probing starts, machine moves towards the bed. As I trigger the sensor by hand the lights come on, but machine continues downward and ignores the sensor trip.

G30 P0 X10 Y10 X-9999 (doesn't stop)
G29 S0 (doesn't stop)
G32 (or from PanelDue) (doesn't stop)

This is the weird part. If i do a G30 with no parameters… it's stops as expected.

Please help, my brain hurts now.

thanks!

Hi,

I'm trying to commission my delta to use DC42's IR probe and I'm having some issues for a few days now.

I have the probe installed and it's flashing 4x on boot up.
It reports correct values on the PanelDue. Wiring is correct and it works… a little.

When I command G30, the printer moves down and triggers correctly.
When I use G32 (bed.g) the probe wont trigger (it turns red) but doesn't stop.

I want the probe to do my delta calibration and bed leveling, but I need it to function first.
Any help is greatly appreciated. Can someone post their bed.g or let me know what i'm doing wrong?

thanks!

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool on Mon Dec 18 2017 11:48:15 GMT-0600 (Central Standard Time)

; Clear any bed transform
M561

; Probe the bed at 6 peripheral and 3 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y124.42 H0 Z-99999
G30 P1 X100.43 Y57.98 H0 Z-99999
G30 P2 X100.43 Y-57.98 H0 Z-99999
G30 P3 X0 Y-124.42 H0 Z-99999
G30 P4 X-108.25 Y-62.5 H0 Z-99999
G30 P5 X-108.25 Y62.5 H0 Z-99999
G30 P6 X0 Y61.46 H0 Z-99999
G30 P7 X46.77 Y-27 H0 Z-99999
G30 P8 X-54.13 Y-31.25 H0 Z-99999
G30 P9 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

Hi,

I'm seeing some fairly long waits between tool changes. It's really killing my print times.
It's usually around 10-15 seconds, but I cant for the life of me figure out why.
Wish it was instant.

Is this a firmware / configuration issue or software issue?

Is anyone else seeing this?

using Simplify3D

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19RC6 (2017-08-10)
WiFi Server Version: 1.19beta10
Web Interface Version: 1.19-RC1

thanks,

firmware is 1.16

Yes, it is repeatable. I didn't even think about the firmware.. I bet that's it.

https://www.applied-motion.com/products/stepservo-integrated-motors/tsm23p-2ag

They have a nice selection in their StepServo lineup.

The tuning features are pretty amazing. You can really dial in the accuracy based on the inertia and mechanics of your system.
Pretty pricey, but a really nice total package solution.

This is a great idea! There are a lot of motors on the market that have encoders built into them. We are using ones with 20,000 counts per revolution. It would be amazing to have a fully closed loop system.

I just noticed a problem with the Pause / Cancel / Resume buttons on the PanelDue.

I can pause a print, but I cannot cancel or resume it from the screen.

Homing issue is fixed.

Thanks DC!

Odd homing behavior with Height Map active.

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19RC5 (2017-08-07)
WiFi Server Version: 1.19beta10
Web Interface Version: 1.17+2

Machine homes correctly multiple times, as soon as I load the Height Map the machine lifts up on Z and either stops or it's moving VERY slowly. I placed my hand on the screw and it seems to be just slightly rotating.. almost impossible to tell.

; homeall.g
; called to home all axes
;
; Author: S. Halbrader
; Date: 5/16/2017

; Relative positioning
G91

; Lift Z
G1 Z10 F6000

; Course home X and Y
G1 X-1005 Y-1005 F4500 S1

; Move away from the endstops
G1 X5 Y5 F6000

; Fine home X and Y
G1 X-1005 Y-1005 F360 S1

; Course home Z
G1 Z-505 F2500 S1

; Lift Z
G1 Z2 F2800

; Fine home Z
G1 Z-505 F360 S1

; Absolute positioning
G90

Would be nice to have the offset stored and recalled instead of setting it for every print.

All,

I have a Cartesian printer where my probe is 121mm behind T0 and 11mm to the right of T0.

I placed this into my config: G31 P100 X11 Y122 Z1.255
This all makes sense to me, but in my bed.g I have to start my probe on Y at 125mm for it to work because of the large offset.

; define probe area
M557 X50:900 Y125:850 S75

When I run mesh bed leveling this puts the nozzle at X39 and Y3 on the first point.

My questions / confusion is, will the heightmap compensate for where my nozzle is during probing or where the probe is?
I hope that makes sense.

thank you!

As we calibrate our machines we need to store the tool offsets from G10 P1 X__ Y__
Tried M500 and it didn't store the offsets.

We can of course just update the config file, but that requires a bit more work.
Any idea if this could be saved to the EEPROM in the future?

thanks,

Hi

I have my Cartesian machine all setup with a BLtouch. It probes properly and stores a height map.
My problem is my Z axis screws definitely do not turn to compensate for the bed errors. The screen and the web interface show a steady number on Z

here's my height map:

So it's out of level, but it seems like the map is being completely ignored.

my config.g

; Endstops

M574 X1 Y1 Z0 S0 ; Define active low and unused microswitches
G31 P1 X0 Y0 Z0.0 ; Set Z probe trigger value, offset and trigger height

; BLTouch Bed Probe

M307 H7 A-1 C-1 D-1 ; Set Heater 7 as servo pin for BLTouch
M558 P6 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type and the axes for which it is used and the probe + travel speeds

I am doing something a bit atypical with the H7 and the Z0 endstop… could that be the problem?
Using the probe for homing works great, everything is operating perfectly but not the actual compensation.

here's my bed.g

;HOME ALL
G28

; PREPARE PROBE
M280 P7 S60 I1; CLEAR ERRORS

; PREPARE Z AXIS
G1 Z10 F2800

; DEPLOY PROBE
M280 P7 S10 I1; DEPLOY PROBE

; define probe area
M557 X100:800 Y100:800 S100

; mesh probe
G29 S0

G1 X100 F4800
G1 Y100 F4800

totally out of ideas… any suggestions??? Am I probing too many points on this large bed?