Mesa Configuration Tool

HansU wrote:

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:
  
  
• 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

JT wrote:

Backup text changed to be clearer what the function is.

:+1:

JT wrote:

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`

JT wrote:

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.

JT wrote:

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.

This works now

JT wrote:

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.

In the display section e.g. there so many possibilities to customize the GUI which makes no sense to have this all in your config tool.
The config tool should provide a quick start to get the basic hardware running. Fine tuning can be done later.
Sure you can forget about the tool when you created your initial config. But would be nice to be able to make changes later with this tool without discarding all manual changes. For the HAL file I could imagine a special section of the file that is kept on re-generating. Something you know from other code-generators.

The custom.hal file is not changed by the tool when saving, it only creates it if requested and not in the configuration directory.

I'll have to ponder how to only change the values used by the tool... I do think it is possible and would be another huge benefit for using the Mesa Configuration Tool.

JT

JT wrote:

The custom.hal file is not changed by the tool when saving, it only creates it if requested and not in the configuration directory.

Oh yes of course. I forgot about that file.

PCW explained that to me but I forget the exact reason... I think it has something to do with pulse timing but may be wrong. And it does work without it but not as good.

JT