Best practices with ini and PnCConf
16 Apr 2023 01:04 #269177
by rthorntn
Best practices with ini and PnCConf was created by rthorntn
Hi,
So I have a few things to get working (estop and charge pump) and I would like to use PnCConf for that but last time I used it (when I edited my existing config) my modbus spindle stopped working because PnCConf adds a bunch of spindle lines and gets rid of my [HALFILE = vfd.hal] line.
Is there a best practice here, I think I remember a checkbox in PnCConf to enable the spindle or something like that, maybe I need to disable that (to stop it adding a bunch of superfluous spindle lines)?
So I guess the question is, is there a way to preserve parts of the ini so they survive a PnCConf?
Thanks.
RIchard
So I have a few things to get working (estop and charge pump) and I would like to use PnCConf for that but last time I used it (when I edited my existing config) my modbus spindle stopped working because PnCConf adds a bunch of spindle lines and gets rid of my [HALFILE = vfd.hal] line.
Is there a best practice here, I think I remember a checkbox in PnCConf to enable the spindle or something like that, maybe I need to disable that (to stop it adding a bunch of superfluous spindle lines)?
So I guess the question is, is there a way to preserve parts of the ini so they survive a PnCConf?
Thanks.
RIchard
Please Log in or Create an account to join the conversation.
- tommylight
- Online
- Moderator
Less
More
- Posts: 19188
- Thank you received: 6430
16 Apr 2023 10:27 #269205
by tommylight
Replied by tommylight on topic Best practices with ini and PnCConf
Custom.hal does not get changed by PncConf, so put modbus stuff there, and make sure it is loaded by the ini file, it usually is.
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.068 seconds