Is there a kinematics calibration guide?

If this value is off, it will affect the calibration as well.

I thought ā€˜motoroffsety’ was the distance between the chain motors and the top of the work surface. If so, it shouldn’t have anything to do with the z-axis kit on the sled. Just making sure you guys are on the same page.

2 Likes

Thank you for the log files.

Here is a much a simplified 131kb version with all of the extraneous stuff removed.

log.txt (130.3 KB)

2 Likes

Sadly, I don’t think the log file had all of your activity.

The only changes in the settings that I see are a change of

Motordistance from 2886.07 to 2870.2
Rotation Radius from 263 to 270

I don’t think these are enough to cause the issues that you saw.

1 Like

Those sound like the little test tweaks I did after I nuked everything and started over. Thanks for checking it out!

Should we have a button to delete the .ini file in Ground Control? It seems like a useful thing to be able to do.

We should have a button to rename it to .old_001 … etc. Hide it don’t kill it.

Thank you

3 Likes

I’m not 100% sure if the in file was the problem. It seems to have fixed it, but it could easily have been some other random thing.

2 Likes

Now that the settings are stored on the Arduino, there would need to be some coordination…

3 Likes

I find it’s easy to forget having changed something a while back that matters with changes made now. Removing the .ini file puts everything back to default, I usually save the old one and diff against the new to see what I’ve changed and want to bring back. I wonder whether showing the default values next to the setting name in the Settings pages would be worth while?

2 Likes

I think that would be a great first step. I’ve made an issue for it in #543

I’d go for .old_yyyymmdd plus maybe a serial # if one a day isn’t enough. That way they’d sort into chronological order; the files are so small in these days where 256GB is a small drive that hundreds of cackups would be a non-issue. I’ll skip the monster 10MB drive reminiscences

2 Likes

I’ve setup a system for the Windows portable GC.

C:\maslow

C:\maslow\backup

There is more to the structure but for this discussion this is what is relevant.

Each time the update is run it makes a back up zipping the firmware, the program directory with the log.txt and copying the GroundControl.ini each with a time date stamp as part of the filename. This allows multiple copies in the same day if required.

It then deletes the files downloads the current version of the firmware and Ground Control Portable and installs them and removes the install files.

This relies on Windows 10. It makes updating a single double click.

I’ve tested it on a few systems, so far it works on everything I’ve tested it on. I’m waiting to hear back from others. It’s a work in progress. Eventually it will run automatically when the updates are putout.

The point of the discussion is that using time and date in the filename makes it unique. This could be used in the - remove GroundControl.ini feature. My other suggested model allowed for 999 backups, in theory years worth. This is unlimited.

Thank you