Gantry hal example

26 May 2016 01:12 #75100 by dgarrett

LINUXCNC - 2.8.0~pre1-ja~joints-axes14~dcf1672

The version that synaptic retrieved is out of date and does not
include the most recent modifications to the update_ini script
that converts configurations.

There seems to be a problem with the way synaptic (or whatever
selects debs) chooses from the numerous scratch versions
available. Looking at

The current joints_axes14 debs are:
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~0e3ed22_i386.deb	16-May-2016 19:53 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~02ab263_i386.deb	13-May-2016 15:15 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~5e60946_i386.deb	14-May-2016 23:26 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~8a3bf49_i386.deb	15-May-2016 14:17 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~42d81ae_i386.deb	22-May-2016 13:45 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~45ccdfb_i386.deb	15-May-2016 22:29 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~608ad22_i386.deb	15-May-2016 12:04 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~925c0c2_i386.deb	16-May-2016 18:10 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~b481dfe_i386.deb	12-May-2016 17:01 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~ca2f492_i386.deb	20-May-2016 12:06 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~cc730c1_i386.deb	14-May-2016 21:16 	5.6M	 
linuxcnc-uspace_2.8.0~pre1.ja~joints.axes14~dcf1672_i386.deb	15-May-2016 09:13 	5.6M	 

It looks like the selection is the last deb in an alphabetic sort instead
of a more proper sort by date.

You can wget and install a deb. First walk the tree at:
to find appropriate OS/scratch-TYPE/ARCH

Example for wheezy/scratch-rtpreempt/binary-i386:
# get the deb from the link:

# install the deb:
sudo dpkg -i
26 May 2016 04:42 #75103 by seb_kuzminsky
It's true, the scratch debs aren't currently sorted in any useful way.

For release branches like 2.6 and 2.7 we can invent meaningful version numbers, since we have just a single branch to think about and since commits within a branch are naturally ordered. But all non-release branches are mixed together in the scratch component of the buildbot's debian archive, so there's no natural way to have ordering between the debs there.

We could do slightly better by having a per-branch commit number in the debian package version number, but automatic upgrades still won't work since they'd happily skip to a different branch in the scratch repo.

The best advise i can give right now is this:

You can list the scratch debs available by running:
apt-cache policy linuxcnc
Or, if you're on rtpreempt or vanilla kernels:
apt-cache policy linuxcnc-uspace

Once you know the version of the deb you want you can get it in and install it in one step, like this:
apt-get install linuxcnc=${VERSION}
For example:
apt-get install linuxcnc-uspace=2.8.0~pre1.ja~joints.axes14~42d81ae

I hope this helps a little.
26 May 2016 04:46 #75104 by mjohnsonsa
Does the latest version address the issue with pncconf not letting you proceed with the wizard when you select a tandem access? It ask you to select which stepper is master but does not appear to give you a method to do so...
26 May 2016 20:16 #75123 by mjohnsonsa
I followed your instructions and loaded the latest JA14. I ran pncconf and created a fresh profile. The machine will not home now, in order to not convolute this thread I started a new one with the symptoms and my config. The config is vanilla, no customizations beyond what was created with the wizard. Can you tell me if this is a bug in JA14?
27 May 2016 00:23 #75132 by cmorley
Pncconf nor stepconf have not been modified to work with JA configs.

I don't plan to until it's merged to master.

Maybe you can use pncconf then convert the config with Andy's script. - I doubt there will be great success unfortunately.

Chris M
27 May 2016 00:24 #75133 by cmorley

mjohnsonsa wrote: Does the latest version address the issue with pncconf not letting you proceed with the wizard when you select a tandem access? It ask you to select which stepper is master but does not appear to give you a method to do so...

What version of linuxcnc does this not work?
You should be picking X and X2 for master and slave for instance.
It certainly could be broken I haven't tested it in a long while.

Chris M
27 May 2016 02:32 #75138 by mjohnsonsa
No it seems to be working on the latest JA14 build, the only issue I have now is how to configure the limits on the primary and master so they work independently while homing. I think it is supposed to be much simpler than using the Gantry component but I cannot find any samples of how to make it work.
27 May 2016 02:38 #75139 by dgarrett
joints_axes14 update for wrongly placed HOME_ items:;a...3a498c7a9be9bcc9372e

Note: joints_axesNN branches have made minimal updates to
stepconf/pncconf to continue their support for identity
kinematics only.

Support for non-identity kinematics and advanced settings for
identity kinematics that 1) allow omission of axis coordinate
letters and 2) support multiple joints for a single axis
coordinate (gantry for example) are not currently available.

Nonetheless, pncconf/stepconf generated configurations are
often a suitable starting point for editing hal and ini files
to handle the less-frequently used configurations.
The following user(s) said Thank You: mjohnsonsa
27 May 2016 05:54 #75140 by mjohnsonsa
I have spent hours trying to figure out how to independently home my two tandem axis steppers in JA14. I have not figured out how to do it and I read the JA docs several times over. All of the examples use the Gantry component which is supposed to be unnecessary in JA. Can someone help me by either giving me the syntax and/or pointing me to an example done in JA of homing Y and Y2 independently?
27 May 2016 17:08 - 27 May 2016 17:11 #75167 by BigJohnT

Multiple joints don't home independent of each other, the both home at the same time or your gantry would rack. When the first side completes the homing sequence of search and latch it waits for the second joint to complete the search and latch operation then they both move to the home offset together. Home offset is where you can make minor corrections to the home switch locations to obtain a square gantry.

Last Edit: 27 May 2016 17:11 by BigJohnT.
Time to create page: 0.167 seconds
Powered by Kunena Forum