RepRapFirmware road map Q1 2021

Dougal1957

@chivel said in RepRapFirmware road map Q1 2021:

Dear Sirs
Please explain to me why in the Status section for the Delta printer at the HOME point, the head position X and Y coordinates are 0 and Z is 999.In Delta X,Y,Z are equivalent.
May be problem in Firmware version?

Because on a delta you should always home to X0 Y0 Z(max) as this is the only way the kinematic can know where the nozzle is located I think the main confusion comes from the Towers often labelled as X Y and Z instead of A B and C.

This this subject should not be in this thread it is off topic.

vistalert

I'm very much looking forward to the next wave of upgrades on RRF and also physical upgrades to my machine. I'll be selecting https://main.eva-3d.page/ for my carriage, and note that one of the community members has already created a design which includes support for the ADXL sensor, used in input shaping calibration.

If you're not aware of the EVA modular carriage system I'd encourage you to take a look. Like the team here, there is incredible work being done there.

compatibilizer

I was wondering if the experimental M954 command does (or could) work for the 6HC board too? I have a spare one which I would love to use as a 6 drive expansion board.

dc42

@compatibilizer said in RepRapFirmware road map Q1 2021:

I was wondering if the experimental M954 command does (or could) work for the 6HC board too? I have a spare one which I would love to use as a 6 drive expansion board.

In the latest beta firmware, yes it does.

jay_s_uk

@dc42 is there a planned improvements spreadsheet for 3.3 similar to the one made available for 3.2? https://forum.duet3d.com/topic/16291/reprapfirmware-3-2-planned-improvements

Diamondback

Really looking forward to the input shaping work that is already happening!
I have a question though.
I'm currently building the wiring loom for my custom toolchanger and was wondering if there is any thoughts yet on whether or not the Duets will have the abilitiy to connect something like an ADXL345 sensor to them for auto calibrating the input-shaping parameters.
If so, is there any preferred connection method yet (I2C vs SPI), if there is, I'd directly include the necessary cables in my loom to the carriage head, which has a built-in mount for such a sensor and save me some headache of having to rebuilt the loom further down the line.

Thanks

T3P3Tony

We are considering how we support stand alone accelerometers connected to Duet 3 mainboards. It is likely to be over SPI connected to the Temperature DB connector as I2C is not appropriate for long distance, off board wiring runs.

dc42

@jay_s_uk said in RepRapFirmware road map Q1 2021:

@dc42 is there a planned improvements spreadsheet for 3.3 similar to the one made available for 3.2? https://forum.duet3d.com/topic/16291/reprapfirmware-3-2-planned-improvements

Not yet, because whether some improvements go into 3.3 and 3.4 depends on when DCS 3.3 is ready. But now that 3.3beta2 is out, we have a much better idea. RRF 3.3 is likely to include the improvements already in 3.3beta2, plus the ability to switch tool heaters between off/active/standby without selecting/deselecting the tools, and a few more bug fixes and minor new features.

fcwilt

This post is deleted!

dc42

@fcwilt said in RepRapFirmware road map Q1 2021:

@dc42

Any chance of having G30 accept X and Y parameters (when no P parameter is present) thus doing the math and movement needed to place the probe at X and Y without needing a preceding G1 command?

Frederick

If the printer has not been homed then moving to an XY position at the start of a G30 probe move is problematic on some types of printer, e.g. delta printers. So it's possible after Z homing has been done (and the print head would move rapidly to the specified position and dive height before probing), but potentially problematic for a G30 homing move.

Diamondback

@T3P3Tony Perfect, thanks a lot, I will include wiring for 4-Wire SPI then.

fcwilt

This post is deleted!

droftarts

@fcwilt Could you move this suggestion to firmware wishlist? I think that would be a more appropriate place to discuss.

Ian

fcwilt

@droftarts said in RepRapFirmware road map Q1 2021:

@fcwilt Could you move this suggestion to firmware wishlist? I think that would be a more appropriate place to discuss.

Ian

Will do.

Frederick

oliof

@T3P3Tony Any chance for accelerometers to be connected to the 1LC?

dc42

@Diamondback said in RepRapFirmware road map Q1 2021:

@T3P3Tony Perfect, thanks a lot, I will include wiring for 4-Wire SPI then.

A quick update: I have determined that we also need an interrupt signal from the accelerometer in order to read the data fast enough. So in total it will need 5 signal wires, plus 3.3V power and ground.

yngndrw

Very excited about the input shaping, especially after this video was released yesterday:
https://www.youtube.com/watch?v=6JBIEJan6zs&ab_channel=Vez3D

DocTrucker

Is there a dynamic roadmap document that is periodically updated somewhere on the Github? I fully appreciate the complexities of working on projects like this and understand dates move, but perhaps a dynamic document with estimates for the next release date and a confidence level would save mods and Duet staffers fielding the same question repeatedly?

'When is RRFx.x.x' coming out mush be a very popular question on these forums!

dc42

@doctrucker said in RepRapFirmware road map Q1 2021:

Is there a dynamic roadmap document that is periodically updated somewhere on the Github? I fully appreciate the complexities of working on projects like this and understand dates move, but perhaps a dynamic document with estimates for the next release date and a confidence level would save mods and Duet staffers fielding the same question repeatedly?

Not yet, but we're working on making our development more transparent after the 3.3 release.