
I'll let you know more when I've got more testing and it's ready to be hammered upon.
g.
Any idea of when it might be available? No matter what I do I'm still low between the X and Z tower and I know that the build is perfectly squaregeneb wrote:It's not released yet and when it is, it'll only work with the HE280 and Repetier Firmware.
There's a few outstanding issues that need to be resolved before it's generally available - and it'll require a specific version of the firmware in order to work.
Both in short and long term ? How much of an effort would it be to port it for repetier with FSR setup ?geneb wrote:it'll only work with the HE280 and Repetier Firmware.
Watching.... Patiently.geneb wrote:It's not released yet and when it is, it'll only work with the HE280 and Repetier Firmware.
There's a few outstanding issues that need to be resolved before it's generally available - and it'll require a specific version of the firmware in order to work.
g.
And other hotends retrofitted with the accelerometer board, right?geneb wrote:it'll only work with the HE280 and Repetier Firmware.
Yes, as long as it's the SeeMeCNC fork of Repetier that's running the printer.Jimustanguitar wrote:And other hotends retrofitted with the accelerometer board, right?geneb wrote:it'll only work with the HE280 and Repetier Firmware.
A knork, they would have a knork.mhackney wrote:Gene, would the SeeMeCNC knife or spoon (or maybe their spatula) work as well as the fork or does it have to be the fork?
Just in case, but double check the arm lengths and the widths on the carriages and platforms need to be the exact same. Small differences here cause the effector to tilt and wreak havok with software calibration, I learned this the hard way when I made my own mag arm parts for the umbee.1 mm difference between the carriage and platform width for the arms made the hotend very noticibly not perpendicular at the edge of the bed.wcogen wrote:DerStig wrote:
"Any idea of when it might be available? No matter what I do I'm still low between the X and Z tower and I know that the build is perfectly square"
This is exactly the problem I'm seeing. I'm really looking forward to a solution.
I might be sure!geneb wrote:The issue we're facing right now is that the more you run it, the lower the max Z gets and we're not quite sure why.
Code: Select all
// Normalize trim (this prevents downward creep)
auto mm = std::minmax({ cur_set->trim[X], cur_set->trim[Y], cur_set->trim[Z] });
cur_set->trim[X] -= mm.second;
cur_set->trim[Y] -= mm.second;
cur_set->trim[Z] -= mm.second;
set_trim(cur_set->trim[X], cur_set->trim[Y], cur_set->trim[Z]);
The original implementation of this algorithm is the C++ version in RepRapFirmware, so no need to touch JavaScript if you don't want to.626Pilot wrote:geneb wrote: BTW, my condolences re: having to touch JavaScript, the most annoying major programming language out there.
I want this for my Eris, which has a RAMBo.dc42 wrote:The original implementation of this algorithm is the C++ version in RepRapFirmware, so no need to touch JavaScript if you don't want to.