Help, strange change

A Former User

you might have updated the firmware and/or duet web control?

in any case, there was a discussion a while back on weather it was in use as dc42 was considering refactoring it out for a future version. it would seem it has come to pass, or will come to pass in another future version.

gnydick

I reverted just that line and the weird thing is

DOES NOT WORK
M671 X-16.16:-16.16:331.5 Y0.0:‭256.0:128.0 S7.5

DOES WORK
M671 X-49.21:-49.21:372 Y0:256:128 S7.5

dc42

@gnydick said in Help, strange change:

DOES NOT WORK
M671 X-16.16:-16.16:331.5 Y0.0:‭256.0:128.0 S7.5
DOES WORK
M671 X-49.21:-49.21:372 Y0:256:128 S7.5

When you use the line that does not work:

If you run M98 P"config.g", do you get any error messages relating to that line?
If you send M671 without parameters, does it report the values from that line?

PS - the long comment on that line as included in the config.g file that you posted causes it to exceed the maximum supported line length, but unless a bug has crept in recently, that shouldn't matter because the comment will be discarded.

gnydick

@dc42 thanks, I'll try those things.

gnydick

Specify 1, 2, 3 or 4 X and Y coordinates in M671

I don't have the long comment in the file currently.

gnydick

I just retyped the line at a different position in the file and it works.

Would you like me to attach the original file? It appears to be some strange parsing bug or maybe a non visible character in there?

A Former User

@gnydick said in Help, strange change:

I just retyped the line at a different position in the file and it works.

If you run M98 P"config.g", do you get any error messages relating to that line?

running the config.g file will likely tell you what goes, wrong, moving the line in the config could suggest the problem lies elsewhere and that the file isnt parsed in its entierty.

dc42

@gnydick said in Help, strange change:

Specify 1, 2, 3 or 4 X and Y coordinates in M671

Perhaps an invisible character? If you attach the file I will take a look at it. We may be able to provide a better diagnostic in future firmware versions.

gnydick

here's the file. config.g

The commented out one fails to be processed correctly even though a seemingly identical configuration is in effect on another line.

dc42

Here's a hex dump of part of your file:

The line that doesn't work has extra bytes E2, 80, AD between Y0: and 256. That sequence isn't valid UTF8.

gnydick

@dc42 That'll do it. No idea how that got in there. Any ideas?

dc42

Can you remember what tool you used to write that line? Online configurator, DWC system files editor, or another editor (which one)?