Posts made by daavery

@dc42 double sided double density 1.2M

@dc42 https://www.dropbox.com/s/eh33zxsda53bvhv/2020-02-21 13.56.06.jpg?dl=0 look familiar?

https://www.dropbox.com/s/oamu8uhdz134qj6/2020-02-21 13.55.32.jpg?dl=0 from our antique computing pile at work

@Garfield the maxwell linkages allow for the spacing between the mounts to vary as the joints move. so using a ball socket joint will not work well

probably a good to post your config.g file

for reference adafruit DotStar LEDs are APA102(or SK98225) LEDs so any APA102 4 wire LEDS will work

g92 just sets the current position to the specified value

so G92 X100 sets the current location to X100 it will never move a motor

@chrishamm same here too from rc1 to rc2

@chrishamm Tested here - looks good - thanks

the BLV interface doesn't use i2c, it uses the existing paneldue serial/JSON interface. you might look at the M150 command which controls addressable LEDS from Gcode

@dc42 @chrishamm did you see the compare i did - doing a M111 P3 S1 and logging the duet3 usb port while running TEST.gcode ( see above) I see random lines of gcode being swapped in order. the 2 runs in the compare were done by just restarting the running job

i'm somewhat suprised others are not seeing the same issue.

@tekkydave yep that's all done in slic3r at slice time , nothing in the firmware

the usual technique is:

• probe one axis inside a circle - find the ends of the chord

• move the axis to mid-point of the chord - now you should be on the radius of the other axis

• probe the other axis - find the ends of the chord

• move to the mid-point of the chord ( which should be the diameter )

• re-probe the first axis now that you are centered in the circle

• midpoint of the chord should be a high accuracy center point

duet config

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 1.2.1.0
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta12 (2019-11-02b1)

pi config

Start-Date: 2019-12-26 09:07:20
Commandline: apt-get upgrade
Upgrade:
duettools:armhf (1.1.0.5, 1.2.1.0),
reprapfirmware:armhf (1.1.0.5-1, 1.2.1.0-1),
duetwebserver:armhf (1.1.2.1, 1.2.1.0),
duetcontrolserver:armhf (1.1.0.5, 1.2.1.0),
duetruntime:armhf (1.1.0.5, 1.2.1.0),
duetsoftwareframework:armhf (1.1.0.5, 1.2.1.0),
duetsd:armhf (1.0.4, 1.0.5)
End-Date: 2019-12-26 09:08:06

more detail - ran TEST.gcode 2 times from DWC - capturing M111 P3 S1 via duet3 micro usb port

there are obvious differences - random gcode lines are out of order

compare report

1 panel - 450 bored holes - 55 min - no glitches - looks like i'm running without the pi for now

@dc42 any debugging info I can get for you guys?

@dc42 waiting on 55min job to finish a test pass then i will do a full panel with router on

@dc42 yep that's where i started - then reverted to b12 - then disconnected the pi ribbon cable and connected a paneldue and made up an SD card to run on. that combo is working flawlessly

@dc42 the gcode looks fine - posted from fusion360 via reprapfw post

looks like its a DWC problem - running direct from SD on DUET3 and panel due the motion is flawless