Yaml seems garbled

Uncategorized
1

Frustrating day trying to get set up had a belt bind and get chewed up a bit. Then I couldnt figure out why the machine would just rock back and forth about an inch when trying to run find anchors. Earlier in the day the extend distance had set itself to 0. I used the auto update feature to go to 1.24 from an experimental 1.23 build I suspect something had set the area of the workspace to 1mm.

Now the yaml seems to be scrambled. I am wiping everything and starting again. I don’t know if it matters but i have been passing control back and forth from my phone to the computer and back again.
Bad yaml:

maslow(2).yaml (7.0 KB)

new Yaml from current 1.24 update:

maslow.yaml (6.6 KB)
Not reporting as I need parrticular help at the moment just documenting in case other people are seeing the same thing.

2

Update. Seems to be working now. Find anchors running normally. No idea how yaml got scrambled but if your robot is rocking back and forth and not running find anchors check the yaml. the workable area had been set to 1mm.

3

Frustrating day. Halfway through a job it just drove itself off the edge of the table. No idea why. Things were going so well. Is it possible that if the webpage tried to reload on the computer or something that it it interrupted it?

Maslow-serial(49).log (28.8 KB)

4

If you do a compare files the EOL(End of Line) characters are different. This can happen when attempting to use a text editor to modify the file and is why it is suggested to modify the yaml file within the Maslow.

1 Like
5

It is working now, but I didn’t edit that one by hand only using the maslow dialogues.

6

Is that something that could be checked on boot / when the yaml is loaded?

7

If file is corrupted, you will get a series of errors in the log file as it attempts to load.

8

Does that include line endings?

Is the guess here:
line endings-> a ‘corrupted’ yaml / read and errored → default values being used that caused the issues?

I’m not sure what the ideal behaviour is if that’s the case?

9

I haven’t confirmed line endings are a problem. I do know that an incorrect spacing at the beginning of a line will cause an error on load. It will also report functionality which is not implemented in the current release, these can safely be ignored.
The default values for workable area are X=2440, Y=1220

1 Like