thank you a lot!

Yes, that's what I observed with this code:

M84 Y ; de-energize Y motor (CoreXY X-Y) G1 X10 S2 ; move X motor (CoreXY X+Y), leaving Y motor non energized.

The G1 reenergizes the Y motor. I wanted to try the CoreXY homing of leaving one motor non energized and letting the otherwise turn until it stall s at the corner.

I didn't complain about this because the printer works fine and I've done a good suite of tests, but I took this picture of my slightly bent PCB a few months ago

alt text

@digid Thank you for that very thorough answer :). It's probably the next stage in my "get the Trium up to snuff" masterplan.
@dc42 Thank you for that explanation... was fearing something like that...

I replaced a bunch of stuff:

E3D v6 Hotend (instead of the stock crappy one) Nozzle Piezo probe (instead of the inductive crappy one)

Now, my bed leveling looks like this:
0_1553883052279_trium-mesh-v3.png

I think I'm pretty happy with that... 🙂

Ok, thank you!

You can find the relevant formula here to set the steps for the leadscrew axis

https://duet3d.dozuki.com/Wiki/Going_from_Marlin_on_Arduino_to_RepRapFirmware_on_Duet

Thanks folks!

Thanks for reporting this. I have found the reason and I will fix it in the next beta. I think you may find that in this release, P3 works in M106 in place of P1.

We are using RJ11 connectors for the CAN bus, because RJ11 cables are easy to source.

They may be on the large size for a two data wires connector but I don't know what the board size.

Since you have local sensing and control, you can also implement local safety, independent of the main board. E.g. shutting down the heater in case of over temperature, bad sensor, unreasonable commands from main board, or communication loss, but I am sure you already thought about it. ;-).

I love this idea. Moving the complexity from copper to silicon.

Also, make sure you have a tool selected when you try to extrude.

@zapta said in Hotend over powered warning:

@dc42 said in Hotend over powered warning:

To estimate the maximum temperature of the bed, add the gain value to ambient temperature.

Thanks, that's very useful. 64+25 gives about 90C which I like. (I print PLA and PETG at 60C and the magnetic bed will get damaged going much above it).

As for the extruder, if I want to find the max temp if I will reduce heater from 40W to 25W cartridge, is it reasonable to run the command [M303 H1 P0.79 S230] and use (gain+25) as an estimation for max temp?

(0.79 = sqrt(25/40), which I guess is the right duty cycle (?))

I don't think that will work, because the gain is calculated at full power even if you use a lower limit. But as a very rough guide, gain is proportional to heater power. So a 25W heater should still allow you to reach well over 300C, unless you are using a very large nozzle (in which case higher power is needed when extruding fast).

@dc42 said in Extruder behaves strangle when disabling pressure advance:

waits for all moves in the pipeline to complete,

this results in a different disadvantage?

@phaedrux said in How to pause a program/macro?:

I've found that if you start a macro on the DWC, the jog buttons that show up on the panel due will not work.

That sounds like a bug.

Also, it doesn't seem like the PanelDue movement increments are obtained from the DWC. If I start the macro from the DWC, the job buttons will take their resolution from the DWC settings, but the Panel due will still be 0.2, 2, etc.

But that sounds normal/expected since DWC and PanelDue are completely separate communication channels to the Duet. I think they don't even know about each other's existence.

@slkittie said in Micro USB OTG to USB Camera:

USB connection to use Webcam

you can take +5v and GND from board and solder it to separate USB plug

0_1553716114226_1ddcfba7-4059-441e-97c2-babb673a2356-изображение.png

You have no tool selected.

Type in 'T0'
and try again.

This happens on some browsers only. There is a setting in the User Interface page that can be changed to avoid it.

Sensorless bed probing has been used on a Cartesian machine and it is configured by using P10 in the M558 command. However, a delta printer does not have sufficient Z resolution for it to work. The Z resolution of a delta using belt drive is at best 12.5 full steps per mm. Stall detection is accurate to +/- 1 full step at best. So you would get height errors of up to about 0.1mm.

It's possible to use stall detection to replace homing switches on a delta, but only if you then use a Z probe to run a quick calibration cycle.

btw I am surprised to hear that someone used stall detection on a Smoothieboard, because the stepper driver chips on Smoothieboard don't support it. I guess they must have used an external driver.

The Slice thermistor has extremely high resistance at low temperatures and will report as min temp on most firmwares using standard thermistor tables. The table linked here needs to be defined:

https://docs.google.com/spreadsheets/d/e/2PACX-1vTHfmSmnGNEuHzjCHEjkA9_DUgnCD9z5E_7Gk1BjUgBYEBtJ6Dlj3hhnFuhFeOfnIc_7zE69VS1tAbx/pubhtml

0_1553613727447_heightmap.csv
Delta height map