Posts made by Sir printsalot

Hello, I setup a new bl touch v3.0 physically mounted left of nozzle 35mm. 0mm in y. I placed this in my config.g g31 line and tried 3 possible entries. All three where ignored. First I wrote x35mm y0 z2.01 running the probe bed comp, probing wanted to start a x0 putting probe off the bed. I changed the offset value to x-35 and the x10. None of these value changes reflected any difference. All the time with my probe mesh grid defined as x52:300 y5:286. why would probing ever start at x0?

printer runs homing and than over to x0 and starts to z down off bed edge.0_1559756477300_cofig for probe.txt 0_1559756483694_override.txt 0_1559756490571_mesh.txt 0_1559756497003_bed.txt

thankyou!

New test results0_1559564317970_bl touch test for forum.txt

duet board doesn't supply the mosfet power directly to the heater. it's output is being used as signal input for a secondary heater ssr rated at 3 times the intended load.

should there be a m564 s1 command line in homing files involving probe during intended triggering of probe or does the g30 and g31 cover the stop at switch event part?

I removed the m401 and 402 from homeall.g and homez. I used the factor 1 meter cable that comes with the new v3.0 bl touch. It's a 2 pin yeelow orange and black mounted at the heater 7 connector on my duex 5 expansion board. Then the 2 pin white and black sensor connectotr is mounted to the duet ethernet board probe in connector. looking at the board the top 2 of the 4 probe pins with ground being the top most pin. I have had the bl touch v2.0 for a year, but bought the newset version to rule out a bad probe. I used the supplied cables. I also ran them and all end stop cable in copper shielded cable covers with kapton sleeve . emi shielding. extremely low noise over senor wiring. And in machine properties I see z endstop state change when I touch probe pin during sensor testing. It's just not stopping or reflecting the position change. I had this happen a years ago with 2.00 rcos but forget what the fix was in config.

Hello again, Ok I got the bl touch working by removing the I1 from m280. However homing machine probe deploys turns blue like it show but dont stop when triggered. the probe pin draws up on contact, but firmware isn't stopping movement. machine properties indicates z not stopped before homing, and after probe contact end stop hit. its just not stoping and setting zero0_1559522906537_homeall.txt 0_1559522913353_config.g new.txt

What should the line look like to run a heater rated for 12 volts of 24? In other words stretching the limits of pwm control. I route pwm signal from hotend jack from duet to the signal input from a stand alone solid state heating board intended to serve this function. Its 30 amp 12v - 72v ac or dc compatible with signal range from 1 pulse per sec to 48khz at 3.3vdc - 30vdc range.

so I just wanna supply the heater0_1559318431073_heater.txt a 50 percent pwm duty cycle rate to simulate 12vdc.

ok that cleared it up. I still can't explain how it worked that way under older firmware? I'd like to say who care it works now, but finding a more true understanding is the only recipe for success with this stuff anymore. Thanks Phaedrux and dc42 for you efforts, they paid off. If you ever need any uccnc or deskproto cam knowledge I'm your guy! I'm a mechanism at my local power plant, but code understanding is still not my strong suit. Thanks!

ok what was the i1 command? single inversion I guess? How does that relate to the expansion header?

This is what I got 0_1559300949515_config.g 0_1559300965861_deployprobe.g 0_1559300977009_retractact probe.txt

Ok so sd card copy of dwc worked to reconnect. Thanks much for that help! Now back to the probe issue. As a precaution I ordered a brand new bl touch v3.01 for the manufactures site. It's installed with factory wire and connectors pre made. With the files listed here it does not deploy,retract,reset,or self test. It does deploy and retract 2 cycles rapidly when board pwrs on. however through gcode nothing. m401 m280 p7 s10,90,120,160 i1 codes show up green fielded in gcode console lines but are unresponsive. And again it works with the older firmware and config.g. however longer prints fail because of so bug unknown to me. So my question is, have I made the correct alterations to these files? and if so why do these probes not work with this firmware version. again duet Ethernet, both bl touch v2.0 and v3.01 tested. and is the 2.02a combined firmware the correct version for second gen Ethernet board?

I removed config override and commented out m501 in config g for testing. no difference. and its an Ethernet with static ip and cat 6e tested with through put 897 mbps using Ethernet tester. Board wont connect any way I try. It's not a network issue, seeing as I upgraded firmware than close dwc it refused to connect again. I imported the combined firmware 2.02a plus the ip4e file listed and the dwc was instructed as combined. I received status update showing the firmware was correctly installed. However the dwc version did not reflect a change. I did hit the applied setting tab anyway. no luck. I'm stuck.

Can't connect after 2.02 firmware upgrade through dwc. no theres no usb communication despite the win driver being install. dwc opens but won't connect with no error. just says connecting forever. I pulled sd card and checked config.g for network info. It's correct. router shows it's online. lights all look good. what now?
it's ethernet.

now I can no longer connect. dwc opens but says it's not connected. usb doesn't respond. it's a dead sick. this all happened trying to run 2.02 combined. It worked somewhat until I closed my browser. chrome. doesn't work with fire fox either. I removed the sd card and put the old stuff back on the card. still no way to communicate.

override.g is clean nothing interupting bl touch related command.
And I believe I've read every piece of doc for the v2.0 bl touch.
I know it works fine under older firmware. I've read all the changes since my first firmware version. Everything to my understanding is correct. I left 1.21 because that version won't run stable more than 5 hours or so. It was a confirmed bug. All newer version have an issue with something not working. The last 4 releases, leave the probe dead. I haven't had a single print run in a year with all the advertised functions working. It's been confirm 3 times that my machine isn't the issue. It's a config file/ firmware related issue. I know alot, but Im not an engineer of firmware and should need to be. This stuff just doesn't play nice.

there will never be an actual fix. fix 1 and another 1 takes it's place. why can't we get a version where only bugs are fixed and nothing new added or changed. you know to calm the water and let people catch up stable.

0_1559150699004_duet config.g may two thousand nineteen.txt The probe deploys and retracts after board power on. However no response to and of the usually code like m280 p7 s10, s90, s160.
I tried I1 in m588 and m280 lines to invert. nothing. Running 2.02 combined. I checked all 5 wires with .02 ohms each. I don't know how to measure the servo control output, but is I had to guess it's functional, just not being performed. I will try to up load my config.g and deployprobe.g
Everything worked with 1.21 firmware. 2.01rc didn't work and this new stable 2.02a combined doesn't work either. If I revert back to 1.21 it works. It' a config firmware issue I can't overcome myself.[0_1559150508551_Duet2CombinedFirmware.bin](Uploading 100%)

probe is bl touch smart brand named probe pin. dive hieght is current position z neg 299 mm relative. so no static value to return to. Im away til sat vacation atm. get back to u soon. thank you for all your help. there is a solution.

that buttom is optioned out. When I hover mouse over it it show cycle with line through unable to toggle button icon. Non of any of the fixes are either working or available on my installation. I am experiencing behavior other aren't, or the same without the option to correct. I'm not sure if it's a windows thing.

As far as the triggered height from bed during probing, it's .96 mm. nozzle is offset higher .96mm I don't know where the additional 5mm is coming from. I have never written a lift of 5mm. after g30. The 5mm lift starting is avoidance of bed edge, because x moves 20 mm wider than bed on neg side. if nozzle was lower than bed nozzle will hit bed edge. But after nozzle is centered where it homes z z0 is .96mm above and my safe z travel height. I have never written to raise a second time. It does anyway. Look at my homez and my homeall. Homeall z is the same as homez a far as z homing goes. But homez raises the extra 5mm zeroing z there and homeall leaves z at .96 and writes the correct height. My question is why are the treated differently if the z portions are the same. My thing is after a homing run regardless of where machine goes, the readout needs to be the correct measured value from bed and it is 5mm higher than it actually is. Printing 5mm of air. I have to lower and g92 to correct it is using my Homez.g but not for my homeall.g and they are the same routine. makes no sense and is inconsistent comparatively.

sorry to keep adding but I wanted it documented. Ok so I left the machine at it's 5.96 height after homeall.g where display show 5.96 height. I than type in gcode field M401 and than G1 Z0 F2000 S1 and the results are.
M401 command probe deployed. G1 Z0 F2000 S1 displayed changed to Z0 no machine move physically happened. Same as sending a G92 Z0 command would. Some thing is definitely going on.

I'm not using printer anymore until someone has time to help. I already has bent parts. I will patiently wait for someone willing to help, I'm just lost. Thank you

; homez.g
; called to home the Z axis

this is homez.g where the 5mm lift isn't commanded but happens and reflects z0 when physically at 5.96
G91 ;relative moves
G1 Z5 F200 S2 ;raise head 2mm to ensure it above trigger height
G90 ;back to absolute moves this might be wrong G91
G1 X148.5 Y151 F2000 ;put probe at bed center
G91 ; relative moves
M401 ;run deploy probe macro
G30 ; lower head, stop when probe triggered and set Z to trigger height
M402 ;run Retract probe macro
G90 ;back to absolute
G92 Z0

this is homeall.g where z finishes out at 5.96 and physically there.

; homeX,Y.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Sat Nov 25 2017 12:15:39 GMT-0500 (Eastern Standard Time)

; Relative positioning
G91
G1 Z5 F3000 S2 ;lift Z 5mm
G1 X-295 y-302 F1500 S1 ;relative move to x,y -295mm neg dir stop at switch
G1 X5 Y5 F1000 S2 ;relative back off switch 5mm pos dir
G1 X-295 Y-302 F360 S1 ;relative move x,y -295mm alliance neg stop at switch slowly
G90 ;absolute moves
G1 X148.5 Y151 F2000 S2 ; put probe center of bed
G91
M401
G30 ;lower probe set height
M402
G90

i don't see anywhere in these macros a lift after completion and it didn't do it under 1.19.1 firmware and 1.15.1 dwc