@ptegler DOOOHL! (brain fart ol' age) forgot stupid 6 pin stepper motor connectors (uses 4 of 6 pins) or NOT straight across coil to coil.
1-4 is one coil and 3-6 is the other coil (2 and 5 are not used) So the little adapter I made to go from the original Duet3d cable to the Ethernet2 board, I connected wrong. Swapped the two center pins of the mating 6 pin adapter connector (3 &4) and viola'.
all is well.
....head back under my rock
oh...P.S. love the idea of mounting the Orbiter directly on the Smart Effector, even printed up and had it mounted. But I've found higher speeds with less vibration artifacts leaving the extruder 'flying' as designed by the TEVO team (with my own adaptation to the flying bridge of course) works much better with lass mass to sling around

ptegler

@ptegler DOOOHL! (brain fart ol' age) forgot stupid 6 pin stepper motor connectors (uses 4 of 6 pins) or NOT straight across coil to coil.
1-4 is one coil and 3-6 is the other coil (2 and 5 are not used) So the little adapter I made to go from the original Duet3d cable to the Ethernet2 board, I connected wrong. Swapped the two center pins of the mating 6 pin adapter connector (3 &4) and viola'.
all is well.
....head back under my rock
oh...P.S. love the idea of mounting the Orbiter directly on the Smart Effector, even printed up and had it mounted. But I've found higher speeds with less vibration artifacts leaving the extruder 'flying' as designed by the TEVO team (with my own adaptation to the flying bridge of course) works much better with lass mass to sling around

ptegler

have been using a E3D Titan for years on my Tevo Little Monster.
DWC 3.4 Paneldue 3.3 Duet3d Ethernet 2. I was installing my Orbiter 2.0.

For initial testing I just have the orbiter hanging in the wind. Yes...brought the hot end up to temp I usually first calibrate my extrusion length without passing through the hot end, then verify all is well all hooked back up as ready to print.

I used the settings from [https://trianglelab.net/u_file/2112/11/file/Orbiterv20FirmwareConfiguration-031c.pdf](Triangle labs paperwork)
Those settings being:
Reprap Firmware Configuration:

M350 E16 I1 ;micro stepping set to 16 with interpolation
M92 E690 ;steps/mm - you may need to fine tune it
M203 E7200 ;max speed mm/min
M566 E300 ;instantaneous speed change mm/min
M201 E10000 ;acceleration mm/s2
M906 E1200 I10 ;motor current 1.2A idle current 10%
M572 D0 S0.02 ;pressure advance – to be calibrated
M207 S1.5 F7200 Z0.2 ;firmware retraction

But it appears to just make the motor dance, not a smooth rotation (with stepper removed from the orbiter) doing a simple 1-5mm extrusion at 1mm/s via DWC screen.
After a moment or two...the Orbiter will start running faster and start heating up. This is a brand new Orbiter just received this evening, after having smoked the first one a day-2 ago, having gotten a 'short' error from the Ethernet2 board in DWC error (and a super hot motor) the first time I tried to test it. (yes that first stepper now has a bad coil)

I reinstalled the old Titan, reset all the printer.cfg settings and that extruder runs just fine so apparently did not damage the Ethernet2 board.

So the question is...shouldn't I just be able to change the appropriate M commands in printer.cfg? nothing changes in firmware correct?

I've been away from RRF for a while working other projects. So I'm a tad foggy here. But this doesn't seem like it should be such a big issue. But I can't seem to get a simple stepper motor change to work!
HELP!

@jay_s_uk yep say beacon.... magnetics and carriage mounting limitations ...too many issues wit hte Beacon
I've got one in hand but have not gone beyong simple Arduino testing to play with it. (I like supporting the little guy developing stuff). A couple of the Klipper coders have played with it.... but no details as to integration are forthcoming.
The I2C interface is to the SBC. I've been trying to push the designer to talk to the various board mfrs to integrate, including pointing him here and at Duet3d specifically to support the RepRap community (as Marlin is already complete.) I told him indeed the RepRap community is still a much larger user base than Klipper. My initial Klipper support comments to the dev guy, he has since forked Klipper himself but i haven't played with it yet.
As to the choice of the I2C...he uses as different library...not constantly xmittng the address so much faster comms.

any plans to support the BD Sensor.... real time bed leveling without having the Z move. Marlins support exists, asn klipper is in the works.... hoping RepRap is coming. Enayone?
[https://github.com/markniu/Bed_Distance_sensor]
https://www.youtube.com/watch?v=yx8pluEu0sg
Can personally confirm that it DOES work reliably (BTDT testing)

Hi all.... new 500 size V-core-3 build, Duet 3 Mini 5+, running the latest 3.4.x.... just finished the wiring...was playing with config.g settings...decided to bust out the thermal camera just for a 'warm and fuzzy'

OK so the Q is...WHAT is the hotspot top center of the board (photo) network connector on the left (in the photo) screw power terminals on the right. The hot spot in question is just above the support post for the Pt100 daughter board. Two smaller spots to the right and lower appear to be inductors.

QUESTION is ...is this a power supply regulator? should it be a hotter spot than the rest of the board? temps go up 3-5 seconds after board is powered up See pic

Mini 5+ is running stand alone (no RPi) nothing on the 5V line except end stops and BLtouch)

ptegler

thanks @jay_s_uk ...figures...right after I posted I was able to resolve the issue. DNL'ed 3.3 and it uploaded as expected without issue. Then going back to 3.4 worked as expected without issue. Actually...the whole story...I expanded the zip first then uploaded the files en masse' so the DWC was not self unzipping the filed before upload. regardless I got past the CRC errors (finally)
v/r
ptegler

couldn't get 3.4 to upload without CRC errors so even tried back peddling to 3.3. same issue. Upload the ZIP file , it decompresses than half way through I get CRC errors and the uploads stop. Have tried pulling down the files multiple times and retried the upload through the DWC still no dice.
Any ideas? It fails on large AND smallish files. Currently on screen its a 495K file firmware/Duet2CombinedFirmware.bin that stopped it (rev 3.3 zip file) (setting up a brand new Mini 3 5+

ptegler