Advanced Search

More screen shots:
I don't understand where is the proper place in MesaCT to set XYZ axes PWM mode, assign pins for it, assign pins for respective encoders. Curious why in CT, under "Firmware' tab -> 'Mesaflash' tab: there is no options available - not possible to pick firmware file, not possible to verify existing one, 'Add firmware' not working (no reaction at all).

I know PID tuning will be from LinuxCNC but it's not starting at this stage.

For the third time with some more detail. To replicate
1. Install Linuxcnc 2.9.4 (rip should be fine but I used the ISO)
2. Install the Qtplasmac sim to the config folder
3. Open the sim to confirm its working
4. Close the sim
5. Install Linuxcnc 2.10 or run from another RIP folder
6. Open linuxcnc 2.10
7. Open the previously installed sim.
8. Upgrade message should be displayed
9. Repeat 6,7 The upgrade message will be displayed again and Linuxcnc exits without error message. 

I just wanted to test an upgrade from the 2.9.4 ISO to use 2.10 before asking a customer to upgrade his working system. I now know the workarounds but I don't think the bug will bite on a live system

FYI, I have just posted an upgrade script to go from 2.9.4 to 2.10 in the Installing Linuxcnc section that shows what I want to achieve. Becasue Linuxcnc does not maintain a buildbot on Linuxcnc.org, some changes to  the apt folders are required to point to the buildbot2 repo. We follow the Debian standards for APT in the ISO so there is some data in subfolders that needs removing.
Ref: forum.linuxcnc.org/9-installing-linuxcnc...n-2-10-master-branch

Happy like a kid started tweaking with Mesa:
1. connected, powered and check if visible - all ok
2. mesaflashed used to write bin file from PCW - all seems ok, i can sie PWM instead of stepgens (screen shot attached)
3. installed MesaCT 2.1.7
4. built config as in attached screenshots (grrr how to paste photos into the text here???)
5. run LinuxCNC and crash as per screen shot:(


 

rodw wrote:

Yes, there are over 20 messages saying it upgraded but not one message saying it got an error and failed during that upgrade attempt.

That's because it didn't fail, at least not in the eyes of the try/except handler.

You can see I tried several times tying to get to the bottom of it, each generating a message.

The issue is that on two different PC's, the upgrade to a sim install failed without reporting an error which left me in the dark.

I don't know what you mean by "the upgrade to a sim install". Could you please elaborate?

You seem unwilling to actually test such an upgrade process and instead want to blame my installation.

I wouldn't say I am unwilling, even in the absence of steb-by-step directions from you as to how to reproduce what it is you are experiencing, I took my own steps to try to duplicate your issue:

I removed the package version I had installed, added the secret buildbot, and installed master for bookworm. I then launched linuxcnc by typing linuxcnc in the terminal. Navigated to Sample Configurations > sim > qtplasmac > qtplasmac_l_metric, and clicked OK. It worked fine with no update messages. I repeated for a RIP installation, it worked fine with no update messages.

The thing is that this issue has been solved by the aforementioned commits, and a sim config never needs to be updated, as it has the necessary changes. So it leads me to the conclusion that something went wrong in the process of going from 2.9.4 to 2.10.

Are you copying the config and trying to make a usable machine out of it? Or are you trying to actually simulate your machine?

If it's the latter, there's a way to simulate your actual table.

As Tommy says connect the alarm output on the drive to to joint.N.amp-fault-in
You may need to invert the signal with the not component. I know I had to.