Maslow #29 BuildLog

Projects
81

Here’s what I see when running that same process.

[MSG:INFO: Channel auto report interval set to 50 ms]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
[MSG:INFO: Retracting all belts]
[MSG:INFO: 0 pulled tight with offset -0.043]
[MSG:INFO: 1 pulled tight with offset 0.064]
[MSG:INFO: 3 pulled tight with offset -0.011]
[MSG:INFO: 2 pulled tight with offset 0.021]
[MSG:INFO: Extending all belts]
[MSG:INFO: All belts extended to center position]
[MSG:INFO: Measured waypoint 0 -> (0.000, 0.000)]

[MSG:INFO: 0 pulled tight with offset -0.043]
[MSG:INFO: 1 pulled tight with offset 0.064]
[MSG:INFO: 3 pulled tight with offset -0.011]
[MSG:INFO: 2 pulled tight with offset 0.021]

These numbers being close to zero just means that the machine already knew where it’s belts were when retract was pressed so I don’t think that’s our culprit

I think that this is what is missing:

[MSG:INFO: All belts extended to center position]

It seems like the machine doesn’t think that the belts were fully extended?

82

When I extend slack only 1 motor is at it’s full end. Should I try fully extending?

1 Like
83

I don’t understand :stuck_out_tongue:

I think that the answer is yes?

84

So when I go to extend the 4 belts I don’t normally have to fully extend them to get the pins in. What you are saying is I should go until the machine won’t let me go anymore. Correct?

1 Like
85

Ahhh yes!

Yes, you want to fully extend them until the machine won’t spool out anymore. There will be extra to make it easier to get the pins in.

86

After extending it all the way now it does move. A note should be added to the user guide to make sure to extend all the way.

I click on left, down, and left.

When I clicked left it went x and y negative not directly x negative.

There was also quite a substantial amount of slack generated in the belt.

PXL_20240315_202105073
PXL_20240315_2021050731920×3413 724 KB

[MSG:INFO: Extending all belts]
[MSG:INFO: All belts extended to center position]
[MSG:INFO: Took measurement at waypoint 0]
[MSG:ERR: Position error on Bottom Left axis exceeded 1mm, error is -190.533mm]
[MSG:ERR: Position error on Bottom Right axis exceeded 1mm, error is -52.650mm]
[MSG:ERR: Position error on Top Left axis exceeded 1mm, error is -127.279mm]
[MSG:ERR: Position error on Top Right axis exceeded 1mm, error is -408.261mm]
[MSG:ERR: Position error on Top Left axis exceeded 1mm, error is 2.039mm]
[MSG:ERR: Position error on Top Right axis exceeded 1mm, error is -318.232mm]
[MSG:ERR: Position error on Bottom Left axis exceeded 1mm, error is 311.137mm]
[MSG:ERR: Position error on Bottom Right axis exceeded 1mm, error is 40.489mm]
[MSG:ERR: Position error on Top Left axis exceeded 1mm, error is 52.380mm]
[MSG:ERR: Position error on Top Right axis exceeded 1mm, error is -189.760mm]
[MSG:ERR: Position error on Bottom Left axis exceeded 1mm, error is 194.452mm]
[MSG:ERR: Position error on Bottom Right axis exceeded 1mm, error is 19.912mm]
[MSG:ERR: Position error on Top Left axis exceeded 1mm, error is 48.651mm]
[MSG:ERR: Position error on Top Right axis exceeded 1mm, error is -185.556mm]
[MSG:ERR: Position error on Bottom Left axis exceeded 1mm, error is 189.948mm]
[MSG:ERR: Position error on Bottom Right axis exceeded 1mm, error is 16.908mm]
[MSG:ERR: Position error on Top Right axis exceeded 1mm, error is -8.970mm]
[MSG:ERR: Position error on Bottom Right axis exceeded 1mm, error is 84.153mm]
[MSG:ERR: Position error on Bottom Left axis exceeded 1mm, error is -1.009mm]
[MSG:ERR: Position error on Top Left axis exceeded 1mm, error is 11.560mm]
[MSG:ERR: Position error on Top Right axis exceeded 1mm, error is 5.819mm]
[MSG:ERR: Position error on Bottom Right axis exceeded 1mm, error is 114.870mm]
[MSG:ERR: Position error on Bottom Left axis exceeded 1mm, error is 1.009mm]
[MSG:ERR: Position error on Top Left axis exceeded 1mm, error is 34.933mm]
[MSG:ERR: Position error on Top Right axis exceeded 1mm, error is -5.198mm]
[MSG:ERR: Position error on Bottom Left axis exceeded 1mm, error is 2.504mm]
[MSG:ERR: Position error on Bottom Right axis exceeded 1mm, error is 52.757mm]
1 Like
87

Progress!

I will add that right now, thanks for the feedback :+1: :+1:

This sounds like the position of the anchor points is off in the config file. Which ever set of points we’re using, let’s switch to the other set.

1 Like
88

As part of the calibration process should the belts be extended fully prior running calibration? What that might mess with the calibration numbers?

89

Yes, they should. But also I don’t think that the calibration process will begin unless the belts are extended so that probably isn’t the issue.

That does seem like the kind of thing that could mess with the numbers.

90

Perfect. I’ve sent it on it’s calibration way. At least now with the belts 2 foot shorter the first two moves are the only ones I need to tend the belts on.

1 Like
91

MMM… just got home from getting the kid and expected the calibration to finish. The last message from grbl was [MSG:INFO: Took measurement at waypoint 14]. The machine just stopped where it is and clicking on “Test” doesn’t do anything.

$TEST
$TEST
$TEST
$TEST
?
Connection error

Guessing it got disconnected from wifi after sending the ? prompt from the dashboard. Or maybe my computer went to sleep.

1 Like
92

Let’s try this version:

It will let us configure the number of calibration points so we can do a smaller number to get results faster

93

Ok flashed 0.64.3 and started the calibration routine. To get it extend enough belt I had to alter some settings.

Maslow_vertical: false

Maslow_calibration_offset_X: 1000
Maslow_calibration_offset_Y: 1000
Maslow_calibration_size_X: 11
Maslow_calibration_size_Y: 9

Maslow_tlX: -31
Maslow_tlY: 2900

Maslow_trX: 3700
Maslow_trY: 2700

Maslow_blX: 0.0
Maslow_blY: 0.0

Maslow_brX: 3700
Maslow_brY: 0.0

Maslow_Retract_Current_Threshold: 1300
Maslow_Calibration_Current_Threshold: 1300
1 Like
94

I’m most of the way through running it myself to double check everything.

95

It froze at waypoint 18, retracting belts, and trying again…

1 Like
96

I just ran it and got the same correct anchor point locations so while there might be a bug it isn’t fully broken in some way.

Is the computer falling asleep by any chance?

Maybe let’s try a smaller number of test points so that we can get to an answer quicker?

97

It isn’t. I just set it for 3 hours sleep.

I started the calibration and I heard the motor drive sound, but then it didn’t do anything. This was the last grbl message.
[MSG:INFO: Point: 89 (850.000, -350.000)]

I’m going to pull the power for 60 seconds and retry.

1 Like
98

Came out to check on the machine again. Looks like it froze at [MSG:INFO: Measured waypoint 18] again.

Without refreshing the webpage I went to the main UI to issue a command and got a response.

$$
$10=1
ok

Looking at the developer tools in Chrome on a refresh I do see a 503 service unavailable for the macrocfg.json. I’m not sure if that means anything.
http://192.168.1.39/macrocfg.json

1 Like
99

Changed it to 18 points and sent it.

Maslow_calibration_size_X: 6
Maslow_calibration_size_Y: 3

Output

Fitness: 0.055684736598822 in 4600 cycles
Calibration complete 
Calibration values:
Maslow_tlX: 24.664473879990812
Maslow_tlY: 2151.150077870132
Maslow_trX: 3911.629935320362
Maslow_trY: 2440.9919958094615
Maslow_blX: 0
Maslow_blY: 0
Maslow_brX: 3991.7538908209926
Maslow_brY: 0
1 Like
100

I wonder why it’s always getting stuck at point 18.

Where is that point on the grid, is it somewhere special like right in the middle?

If you plug in the coordinates from that 18 point run and the do retract → extend → take slack → move does it move normally?