Resolver Output

LAIR82 wrote:

I just realized something,

When I have the pin "setp hm2_5i23.0.resolver.00.index-divisor 2" enabled linux will not come up,.

That sounds like I messed up the patch. (as I said, I can't test this code, I don't have the hardware)

dmesg ought to say what is going on.

However, you do want to be careful about which version of LinuxCNC you are trying to start.
The desktop shortcut will (I think) try to start the "installed" LinuxCNC version, not the "run in place" version.
(you currently probably have 2 versions on the drive)

The way to test the newly patched version is to open a terminal:
. ./scripts/rip-environment
linuxcnc

Then pick the config in the config picker.

LAIR82 wrote:

If I post the dmesg would that help?

It's certainy worth a try.

It is 2.6.0 coming up though when I have that pin disabled in my hal.

So, disable, and look in "show hal config" or type halcmd show param in the terminal, and see if the parameter exists. (and if so, what it is actually called).

If it isn't there, then perhaps you missed a bit of the patch, or I messed up, or the version you are running is base 2.6, not the patched version.

If you start from the command line then you will probably be told what has gone wrong.

LAIR82 wrote:

on the actual patch, the first file that gets patched is the hostmot2.9, file is that file supposed to be located at:
a/docs/man/man9/hostmot2.9 or should it be
a/src/docs/man/man9/hostmot2.9

linuxcnc-dev/docs/man9. There is no linuxcnc-dev/src/docs folder.

You need to run git am from the same folder location that git format-patch was run, otherwise the patch won't work. In this case git format-patch was run from the linuxcnc-dev folder, not the src folder.

Also, there is nothing in the hal parameters regarding index-divisor.

In that case it seems likely that you are not running the version of linuxCNC that you think you are running, unless there is a problem with my code, but that should have shown up in the compile stage.

I see nothing wrong in the dmesg, was that a successful or unsuccesful start?

LAIR82 wrote:

So I should put the patches in the src folder inside the linuxcnc-dev folder?

No

(Actually, it doesn't matter where the patch files are as long as you give the correct path to them, but you need to issue the patch command from the linuxcnc-dev folder, not the src folder so it is easier to just put the patch file there.)

LAIR82 wrote:

I deleted that "0001-fanuc-style......" patch from everywhere on my computer it was, and it is still coming up though.

That is because git remembers what it was doing when it went wrong, and is waiting for you to tell it that you fixed it.

I would suggest that you recover the tool change patch then:

cd ~/linuxcnc-dev
git checkout master
git reset --hard origin/master
git pull
git am 0001-Fanuc-style-tool-change-for-Lathes.-On-Fanuc-control.patch
{ignore the whitespace errors}
git am 0001_Add_an_index_counter_for_multi_cycle_resolvers.patch.txt

cd src
make clean
./autogen.sh
./configure --prefix=/usr
{This makes an installed version, rather than run-in-place}
make
sudo make install

Then the icons/menus should start your new version.

(I have just tested all the above sequence (which is why the reply took so long). It ought to work for you too.