Mesa Configuration Tool

More
4 years 1 month ago #252179 by HansU
Replied by HansU on topic Mesa Configuration Tool
Some other annotations:
  • When I select a firmware like 5i25_7i85sx2 - shouldn't it be generally possible to select two daughter cards?
  • And these drop down menus are empty for me:

    Attachment not found

  • Backups - This could be understood as backup of the firmware because of the layout. Maybe change the text to "Enable Configuration Backups"
  • It creates some non-existing pins the the HAL file:
    Code:
    hm2_5i25.0.7i85s.0.1.analogena hm2_5i25.0.7i85s.0.1.analogout0-scalemax hm2_5i25.0.7i85s.0.1.analogout0-minlim    hm2_5i25.0.7i85s.0.1.analogout0-maxlim   hm2_5i25.0.7i85s.0.1.analogout0
  • In Axes I have to provide values for the PID controller. I think the config generation shouldn't fail I don't provide PID parameters in case I don't want to use a PID controller.

Please Log in to join the conversation.

More
4 years 1 month ago #252202 by HansU
Replied by HansU on topic Mesa Configuration Tool
And the error message could be improved to be more helpful.
I did some changes in the INI file, and mesact came up with:

Code:
File <string> line 1, in function <module> Error: name 'YES' is not defined ["NameError: name 'YES' is not defined\n"]

It would be nice if gives me a line number e.g.

Furthermore in [DISPLAY] isn't "MIN_VELOCITY" kind of deprecated and should be replaced by" MIN_LINEAR_VELOCITY" ?

Edit:

The problem was that I inserted `HOME_IGNORE_LIMITS = YES` but the tool uses "True" for that.
According to the docs it should be YES/NO.
The same for "HOME_USE_INDEX"
"HOME_IS_SHARED" has to be 0/1 according to the docs.
Maybe LinuxCNC accepts True/False as well, but I think you tool should at least accept the values from the docs .

Please Log in to join the conversation.

More
4 years 1 month ago #252256 by HansU
Replied by HansU on topic Mesa Configuration Tool
I discovered another bug:
1. open wrong INi file (one that has not been created with that tool)
2. when opening the correct INI file, it fails with the error message from my last post.

Please Log in to join the conversation.

More
4 years 1 month ago #252260 by JT
Replied by JT on topic Mesa Configuration Tool
I'll take a look at these as soon as I'm back up and running.

JT

Please Log in to join the conversation.

More
4 years 1 month ago #252263 by HansU
Replied by HansU on topic Mesa Configuration Tool
Commit 2856f614c7344279b0e23974c6ddcdba04794c81 "add output invert for 7i96s"
produces the following error message with my config:
Code:
File machine.py line 122, in function daughterCardChanged Error: name 'MAIN_BOARDS' is not defined ["NameError: name 'MAIN_BOARDS' is not defined\n"]


Furthermore it would be good if unknown key value pairs (like "BACKLASH = 0.01") are not removed when generating the config. Maybe you can add a special section for that? Or remember the lines which didn't correspond to a supported value and print them when generating? This would also allow to keep comments.

Please Log in to join the conversation.

More
4 years 1 month ago #252269 by JT
Replied by JT on topic Mesa Configuration Tool

A comment on the commit "fix checking for linuxcnc version I hope"
If I set the localization to en, then it works for me. But with German locale if didn't work because your query gives this:
Code:
$ apt-cache policy linuxcnc-uspace linuxcnc-uspace:     Installiert: 1:2.8.3

Not sure how to get this fixed multilangual.

Good news I have Debian 11.5 installed on my dev PC but can't change the display resolution so on to Debian 12 in the morning.

I have an idea to test when I get my dev PC back up and going.

JT

Please Log in to join the conversation.

More
4 years 1 month ago #252299 by JT
Replied by JT on topic Mesa Configuration Tool

Commit 2856f614c7344279b0e23974c6ddcdba04794c81 "add output invert for 7i96s"
produces the following error message with my config:
Code:
File machine.py line 122, in function daughterCardChanged Error: name 'MAIN_BOARDS' is not defined ["NameError: name 'MAIN_BOARDS' is not defined\n"] Furthermore it would be good if unknown key value pairs (like "BACKLASH = 0.01") are not removed when generating the config. Maybe you can add a special section for that? Or remember the lines which didn't correspond to a supported value and print them when generating? This would also allow to keep comments.
 
I just pushed a fix for the missing variables.

What section would key value pairs be in that are not LinuxCNC specific? BACKLASH is a joint specification which could be added to the tool easy enough.

JT

Please Log in to join the conversation.

More
4 years 1 month ago #252305 by JT
Replied by JT on topic Mesa Configuration Tool

A comment on the commit "fix checking for linuxcnc version I hope"
If I set the localization to en, then it works for me. But with German locale if didn't work because your query gives this:
Code:
$ apt-cache policy linuxcnc-uspace linuxcnc-uspace:     Installiert: 1:2.8.3 Not sure how to get this fixed multilangual.
 
I changed the way I check for LinuxCNC version that should be language agnostic so if you can test that on your PC with the German locale and let me know if you get the correct LinuxCNC version.

JT

Please Log in to join the conversation.

More
4 years 1 month ago #252306 by JT
Replied by JT on topic Mesa Configuration Tool

Some other annotations:
  • When I select a firmware like 5i25_7i85sx2 - shouldn't it be generally possible to select two daughter cards?
  • And these drop down menus are empty for me:

    Attachment not found

  • Backups - This could be understood as backup of the firmware because of the layout. Maybe change the text to "Enable Configuration Backups"
    • It creates some non-existing pins the the HAL file:
      Code:
      hm2_5i25.0.7i85s.0.1.analogena hm2_5i25.0.7i85s.0.1.analogout0-scalemax hm2_5i25.0.7i85s.0.1.analogout0-minlim    hm2_5i25.0.7i85s.0.1.analogout0-maxlim   hm2_5i25.0.7i85s.0.1.analogout0
      • Code:
        In Axes I have to provide values for the PID controller. I think the config generation shouldn't fail I don't provide PID parameters in case I don't want to use a PID controller.
At this time I only have the code base for one daughter card... in the future I'll work on two daughter cards.

Also only some boards are coded to allow reducing the number of stepgens etc.

Backup text changed to be clearer what the function is.

I'll have to see why those pins are created for the 7i85s, can you attach your ini file?

Mesa cards need the PID so it's required.

JT

Please Log in to join the conversation.

More
4 years 1 month ago #252335 by HansU
Replied by HansU on topic Mesa Configuration Tool

Backup text changed to be clearer what the function is.
:+1:

I'll have to see why those pins are created for the 7i85s, can you attach your ini file?

It still complains about when opening the config file: `Error: name 'MAIN_BOARDS' is not defined`

Mesa cards need the PID so it's required.

For what they need a PID for a simple stepper config? I removed the PID component and it still works.
See attached files.

Please Log in to join the conversation.

Time to create page: 0.079 seconds
Powered by Kunena Forum