Spindle Orient - No motion

I feel like I am missing something right under my nose.  Spindle runs as expected in velocity mode.  But I'm trying to get spindle orient to work and I am having no luck.  MDI (after homing) produces no motion on M19 command.  I have trien M19 Rx.x and M19 Rx.x Qx Px but nothing happens. 
Had configuration shows SpinEna and SpinOut are producing outputs.  All output signals seem to be working in both Vel mode and Orient Mode.  Mus and Or2 signals working.  I just don't know what I'm missing.  Maybe someone can point out my error.  Appreciate the help.
Some of the Hal and Ini files have been compiled from other LinuxCNC users

Maybe I should also mention my VFD is a Hitachii Wj200 vector drive. The spindle is a vector duty motor 20:1. I did wonder if the orient is not putting out a strong enough signal to the drive for it to register a signal. But then again, the SpinOut signal is 800 and still has no motion. In velocity mode the spindle will turn at less than 200 rpm.

If the Hitachi is responding to a 200rpm velocity command then the orient output should also work - i.e. it's not a 'not strong enough signal'

I'll take a look at your hal and see if I can find something.  I'd post mine but it's a mess right now and would likely confuse you.

First
Move your addf to a line after the motion-controller line.  I remember reading somewhere - I think from PCW - that the sequence you addf components is critical.  Don't know if this is the root of all your woes, but mine is like this and it works.

Next,

Why is this in there?  Your near component should be working to get the spindle-at-speed to trigger.  I don't know if this would bugger up the orient output but unless you've got a good reason I'd comment this out for testing.

Optional:
Edit your HAL file so the [TUNE] values are in the hal file and not in the INI file.  Like this:

Reason for this is that you can edit hal pin values on the fly in halshow while tuning the PID and everything else.  If they're set to follow the INI file values, you can't edit them in halshow.  Once you've got everything tuned up you can un-comment and adjust the 'final' values in the INI file.

Try those two things and see what happens.  You know how to open halshow and watch what's going on while you're testing?

Thanks. I will try these fixes when I get home and report back.

I tried those fixes, but no luck so far. I'll keep at it. Let me know if anything else comes to mind. Thanks.

Aha, the problem was user error. I forgot when I set up my VFD, I was using separate outputs in the hal file for FWD and REV instead of enable/DIR. So the enable signal was working, but it wasn't going to the VFD. Now the orient kicks the VFD on, but it just starts for a half a second and quits. The spindle just coasts to a stop. So now to figure out that issue.

jroddds wrote:

The spindle just coasts to a stop. So now to figure out that issue.
 

Once you get that figured out you may find that orienting the spindle with a VFD isn't great without a brake or alignment pin.  VFD'd aren't servos - although that WJ200 has some nice features - and they can't hold a position very well without dithering.  I got pretty close with my GS3 VFD, but wound up having to make an air-actuated alignment dog on the top of my spindle to hold steady it for the ATC drive dogs.

Have you tried homing the spindle using the built-in feature(s) in the VFD?  I have a WJ200 on another piece of equipment but I've never tried using the 'simple positioning' mode described in the manual.  You might play with that a bit if LCNC's orient function gives you fits.

It probably wouldn't be too hard to connect some of the WJ200's digital I/O to LCNC and let the VFD do the homing and report all-good to LCNC.