Possible Gscreen bug

More
11 Jun 2019 00:58 #136524 by persei8
Replied by persei8 on topic Possible Gscreen bug
Not sure if you can see all the text I pasted. Just launch any gscreen sim config from a terminal and you will see what I mean.

Please Log in or Create an account to join the conversation.

More
11 Jun 2019 02:53 #136531 by cmorley
Replied by cmorley on topic Possible Gscreen bug
yes I know what you are talking of - it's a debug line I forgot to erase. fixed in 2.8 but has not been pushed up yet.

Please Log in or Create an account to join the conversation.

More
12 Jun 2019 13:05 #136722 by andypugh
Replied by andypugh on topic Possible Gscreen bug
Off topic:

Basically, in the INI file I have:
[TRAJ]
COORDINATES = X Y Y Z


I wonder how common that is? (it doesn't make sense)
If lots of configs have that then my update-ini script (as modified last night) will go rather wrong.
Probably best that I realised sooner rather than later.

Please Log in or Create an account to join the conversation.

More
12 Jun 2019 15:15 #136743 by Reinhard
Replied by Reinhard on topic Possible Gscreen bug

I wonder how common that is? (it doesn't make sense)

What's wrong with that configuration?
I have a gantry with turn-table and have coded: XYYZA

Please Log in or Create an account to join the conversation.

More
12 Jun 2019 15:23 - 12 Jun 2019 15:25 #136747 by bevins
Replied by bevins on topic Possible Gscreen bug

Off topic:

Basically, in the INI file I have:
[TRAJ]
COORDINATES = X Y Y Z


I wonder how common that is? (it doesn't make sense)
If lots of configs have that then my update-ini script (as modified last night) will go rather wrong.
Probably best that I realised sooner rather than later.


All my gantry routers that have two motors on y axis uses this.
IT is actually quite common. What doesnt make sense?

Your script doesnt deal with two motors on one axis. You would have to query the user when script runs then govern accordingly. you are talking about your upgrade script?
Last edit: 12 Jun 2019 15:25 by bevins.

Please Log in or Create an account to join the conversation.

More
12 Jun 2019 16:52 #136761 by andypugh
Replied by andypugh on topic Possible Gscreen bug

All my gantry routers that have two motors on y axis uses this.
IT is actually quite common. What doesnt make sense?


I suppose it depends if the [TRAJ]COORDINATES setting is used in your HAL file.
(And what it does, if it is).
Repeated letters are just ignored in initraj:
github.com/LinuxCNC/linuxcnc/blob/b948db.../ini/initraj.cc#L109
Where they just serve to decide which letters are valid in the G-code as far as I can tell.
halui uses it and _does_ count more axes if a letter is used twice:
github.com/LinuxCNC/linuxcnc/blob/a048d6..._intf/halui.cc#L1441
(I wonder if it _should_?)


Your script doesnt deal with two motors on one axis. You would have to query the user when script runs then govern accordingly. you are talking about your upgrade script?


It copes reasonably well with any existing config using gantrykins or gentrivkins, because those make it easy to determine that its a paired motor config.

Please Log in or Create an account to join the conversation.

More
12 Jun 2019 19:07 #136779 by cmorley
Replied by cmorley on topic Possible Gscreen bug
Andy I would say that most people would make the two lines the same?:

KINEMATICS = trivkins coordinates=XYYZ kinstype=BOTH
[TRAJ]
COORDINATES = X Y Y Z

And not know that the second line only sets what letter is valid.
Is there any time that the two lines would be validly different?
Ultimately should they be combined in the future?

Chris M

Please Log in or Create an account to join the conversation.

Time to create page: 0.128 seconds
Powered by Kunena Forum