Advanced Search

Having 0 in the middle of the table is the old way of doing things and will most probably cause you trouble.
As for homing on the positive side, as mentioned above, invert the value by adding or removing - in front of it, for
HOME_SEARCH_VELOCITY
might also have to change
HOME_LATCH_VELOCITY
and pretty sure
HOME_FINAL_VELOCITY should be negative value.
Then you have
HOME
And
HOME_OFFSET
to play with, depending on where the 0 should be.

axis direction is correct, and doing what PCW said fixed it straight away! I was so close just the wrong one haha! So thanks PCW!

Next problem is getting zero to now be the centre of the table looking at my .INI file is what I thought you would do but its over shooting the centre by about 30mm and then the axis gets locked out.

I want the machine to hit the home button (Which its doing now thanks again) And then move the the table centre and say THIS IS ZERO looking at my .INI file how far of from that am I? Hopefully I'm on the right path at least I'm going back to keep playing with it.

Thanks again guys progress has been made

So I stumbled across this video of the MX1500...

And caught a couple of statements from the gent running the machine that intrigued me.

• 7:50 - "I took the Speedio manuals from [garbled] and told Rob: Give me M298"
  • M298 appears to be 'accuracy mode' in the Speedio control, and not just G64 path blending.  The little online discussion I can find suggests on-the-fly editable accel/decel settings which are coupled with path blending... and possibly S-curve settings.
  • Has Pathpilot now got S-curve or some similar magic under the hood?
• 14:00 - jog during an M1 program pause. "I didn't realize we put that in three versions ago...And Rob just said I added that in."
  • This sounds rather useful, no?

Wonder if Pathpilot's look-ahead has been extended to rotary axes?
Have they already cracked the S-curve nut Grotius and friends have been agonizing over?
How far has Pathpilot diverged from LCNC?
Would it even be possible to merge some of the wizardry which appears to be happening in Pathpilot?

Not that I'd be remotely competent to do any of the backstage work, but I wonder if any of the LCNC devs could do something with a current copy of Pathpilot source code...

HOME_SEARCH_VEL is what you would negate to change the search direction.

Also check that the axis direction corresponds to the tool movement.
linuxcnc.org/docs/stable/html/user/user-...chine-configurations

So currently HOME_SEARCH VEL is set to 1.500000

If I Change that to -1.500000 or +1.500000 I should see change in direction? Ill go try both of those right now and report back

Thanks

The first move is done at:

HOME_SEARCH_VELOCITY

So changing the sign of this value will change the
direction of the first move in the search for home.


linuxcnc.org/docs/html/config/ini-homing.html#_home_search_vel
 

You can also call entire subroutines:

or custom MCodes:

photos didn't work? 

Hey guys me again, before I start .ini file is include and two pics of the machine so you can see position of the switch understand me (pic of cat is how I feel right now)

So as the title says my Home switch is set up on the right side of my table, and I'm trying to set up 0 to be the centre of my table. I have edited my .INI file so that min is  -111.5 and max is 111.5 (As my max travel is 223 so that should put zero smack bang in the centre... I hope?)

Problem is the machine keeps looking for the homing sensor on the wrong side of the table as in it travels in the wrong direction. I've read a few other posts and someone said that a - or + in front of the HOME_LATCH VEL will change the direction it looks for the home in? But changing that seems to not do anything.

The only way I got this to work was flipping all axis in the gui editor then it works flawlessly but... then all my parts are mirrored which I don't want.

Thanks again guys, as always hopefully Im missing something super easy -_- 

 

If using HALUI, then you have up to 64 commands, but IFAICT one command per INI line.
if using Qtvcp/Qtdragon there are more options.

Spent some time reading up how to flash this thing and... it works! Thank you very much! Problem solved.

Also, I'm surprised I've been running it this whole time with no issues. 

Nicely done, maestro, thank you.

Very nice build, thank you.
Reminds me, i have a mac pro with cnc controls in it somewhere in the shop, pretty sure it is under the main table (out of 11 tables).
Are those 4590 made by Bosch/rexroth ? I had plenty of those, now i have some very short parts! The best thing is they work with M8 nuts/bolts perfectly and the aluminium is very high quality as you can tighten and loosen those bolts hundred of times without issues, in the same place!

warreng wrote:

Pardon my ignorance... Based on your comment I presume that the servo tuning is stored in the servo drives?

I have had the understanding that I DO want the LinuxCNC feedback loop in order to make a [more] closed loop system which is more better than having the control completely blind to the position (or loss of position) of the motors.

Seen this after i already replied above.
Yes, in position mode the loop is closed in the drives, so the tuning is done on the drives.
Since LinuxCNC can do steppers with feedback and loop closed in LinuxCNC, it is much better to use the drives as is as they are already tuned there, and tuning steppers with feedback is much, much easier than analog servos.
Another good thing is there is no fear of motors running at full speed if any mistake is made during wiring and tuning in analog mode as the drives have no control over motor speed in that mode, they do whatever is required from the analog input.

7i96S + 7i85 or 7i85S and add a 7i84 if you need more IO.
Later, when you do feel confident to dip your toes in analog territory you only need to get a 7i83.