Category: Plasmac
Just accept that I ran a Sim in Step 2 and it copied it to the configs folder
You tests prove nothing becasue you have not taken a sim installed under 2.94 then run it under to 2.10 (steps 5,6,7)
You are clearly not listening to the issue or following my instructions to replicate the issue. Tommy just goes off on a tangent on Item 2.
It seems neither Tommy nor I fully understood what you were doing in step 2. I follow now.
While waiting for clarification, I was attempting to replicate your issue and validate the process.
What I wanted to do is simply confirm using a SIM, things would work once I asked a customer to upgrade a live install on a production table over 1000 miles from me. Doing it on the sim found some issues. They may not apply to a live install.
Honestly, it seems like you’d benefit from learning how to simulate your customer’s actual machine. This guide explains how to convert a “live” config into a simulation config, which you may find more useful than the bog standard simulation config:
forum.linuxcnc.org/plasmac/43425-simulator-for-qtplasmac
I am done with this issue as I received enough information to solve the problem manually from Snowgoer's initial post.
It’s good you were able to gather enough information to solve the problem manually.
The core issue stems from the interaction between the .ini file and the .inc file, resulting in ini.combined. The changes
were correctly applied to that file, but the problem is that it’s overwritten every time LinuxCNC launches, so it applies the changes repeatedly.
I still maintain that this is an issue related to your setup/installation and/or an unintended use case. That said, I’m considering adding a check for “expanded” in the filename and display a warning if it looks like an older simulation config is being used. I’m also considering tweaking some of the messaging to clarify this process moving forward.
Thanks for being patient with me while I worked through this.
