Help with QTplasmaC

HOME_SEARCH_VEL and HOME_LATCH_VEL are different for [JOINT_2] and [JOINT_3]

phillc54 wrote: HOME_SEARCH_VEL and HOME_LATCH_VEL are different for [JOINT_2] and [JOINT_3]

I can't see the wood for the trees

I have changed them to 10 and 2

Still get a remediate F error joint 3

Maybe try changing to these values in joints 2 & 3 , these are the numbers PncConf comes up with.

phillc54 wrote: Maybe try changing to these values in joints 2 & 3 , these are the numbers PncConf comes up with.

Code:

FERROR = 10.0 MIN_FERROR = 1.0

No change unfortunately

I am plumb out of ideas Clive. It may be an idea to start a thread in another section like this one as it may get more attention.

phillc54 wrote: I am plumb out of ideas Clive. It may be an idea to start a thread in another section like this one as it may get more attention.

I have done a few gantry machines without issues. It worked fine with PlasmaC.

I will try to do some halscope plots to see what's going on.

Thanks for the help

Clive S wrote:

phillc54 wrote: I am plumb out of ideas Clive. It may be an idea to start a thread in another section like this one as it may get more attention.

I have done a few gantry machines without issues. It worked fine with PlasmaC.

I will try to do some halscope plots to see what's going on.

Thanks for the help

If you said this and I missed it, I apologize. But if you had a working PlasmaC configuration, why not just use this method to get to QtPlasmaC:

linuxcnc.org/docs/devel/html/plasma/qtpl...tml#qt_modify-config

Just took a peek at your config.

For Joints 2 and 3 (Y) you have STEPGEN_MAXACCEL at 1250. Whereas for Joint 0 (X) you have it set to 2500.

I remember when I was chasing a following error in the past, PCW had me raise the stepgen_maxaccel values. Try making Joints 2 and 3 STEPGEN_MAXACCEL match what you have for Joint 0. This could be why you can jog in X but not in Y.


It's impossible for me to say why your config for PlasmaC worked without seeing it to compare to the QtPlasmaC config you've been hand editing. Is it possible for you to post that here?

Why dont you create a 3 axis 4 joint machine with axis working first. I agree it is a bit confusing but, plasmac started in world mode with the 4 joints showing then you home and it changes mode and you see the three axis.

QTplasmaC doesnt show that, I believe it is starting in world mode and shows the three axis and you can jog but will rack the gantry until you home all axis. If your ini and hal file is correct, it will home the tandem axis properly. Once you have a working 3 axis tandem machine then install QTPlasmaC.

IF you get a 3 axis machine in axis working, then run pncconf and create a different config and select the QTplasmaC options. select the basic stuff for tandem gantry machine, and then you can simply copy the axis/joint portion of your working 3 axis config over to this one and same with ini file not changing anything to do with QTPlasmac.
They did a great job with QTPlasmac keeping the QTPlasmaC stuff together at the beginning of the ini and at the end.

This is what I did until I figured it out.

snowgoer540 wrote:

Clive S wrote:

phillc54 wrote: I am plumb out of ideas Clive. It may be an idea to start a thread in another section like this one as it may get more attention.

I have done a few gantry machines without issues. It worked fine with PlasmaC.

I will try to do some halscope plots to see what's going on.

Thanks for the help

If you said this and I missed it, I apologize. But if you had a working PlasmaC configuration, why not just use this method to get to QtPlasmaC:

linuxcnc.org/docs/devel/html/plasma/qtpl...tml#qt_modify-config

Yes. I was aware of the conversion. But the problem was if it went wrong I would be without a working machine also the linux version with Debian strech I think is quite old I had updated it to 2.9..

I have also cloned the drive. Another problem was I also have to bring another machine (300 mile round trip) up to QTplasmaC

I think I am getting there now