Homing not working but E Stop In is ?

Just going back thought what you said last night when I was sleeping...

I also thought it would be good to be able to 'manually' tell the machine it was Home.

You can't actually tell the system that it is at home. You tell it to initiate the homing sequence, There is only one home position.

I might be getting in a little bit over my head and Andy will know more but Master branch now includes axis offsets which may let you set a reference point that is offset from the home position (eg the axis offset is added to the commanded position when code runs). But the whole homing scenario in master has been changed due to the merging of the Joint axis code which in turns makes the concepts of joints and axes totally independent. So in my case, running master to control a joint axis gantry machine with two joints, the only homing option I have is "home all" as I can't home one side of the gantry (a joint) independently.... I'm only new a this, but I think that the better approach moving forward is to just "home all". To me that is part of my startup sequence. (Power up, out of estop, turn on, home all).

rodw wrote: Just going back thought what you said last night when I was sleeping...

I also thought it would be good to be able to 'manually' tell the machine it was Home.

You can't actually tell the system that it is at home. You tell it to initiate the homing sequence, There is only one home position.

I might be getting in a little bit over my head and Andy will know more but Master branch now includes axis offsets which may let you set a reference point that is offset from the home position (eg the axis offset is added to the commanded position when code runs). But the whole homing scenario in master has been changed due to the merging of the Joint axis code which in turns makes the concepts of joints and axes totally independent. So in my case, running master to control a joint axis gantry machine with two joints, the only homing option I have is "home all" as I can't home one side of the gantry (a joint) independently.... I'm only new a this, but I think that the better approach moving forward is to just "home all". To me that is part of my startup sequence. (Power up, out of estop, turn on, home all).

Yes I completely agree that "Home All" seems like the way to go. To be honest I didn't realise there was such a thing when I first started designing my machine. I just assumed (I know... never assume!!) that I could press "Home X" and then let the machine do the business. I suppose, for me, I can still set the machine to home on the z axis and then when it's high enough just press the Home X and Home Y together (assuming it will do that).

I suppose I'm trying to get the functionality of the machine to suit the interface that I've built. Which is a bit back-to-front but would be good if it was do-able. Now I've got the buttons working and I can see how the different values affect the homing then I'm hoping I can come up with something that will suit. I could always install a single "Home All" button at a later date.

I'm not sure what you mean by "master branch". Is it referencing the software at github or something? I also don't know the difference between Joints and Axes (but I'll be looking it up tomorrow when I get home from work).

This whole project started with a mate buying me an Arduino Mega for Christmas and then me thinking what I could use it for. I've never programmed an Arduino before. I've also never used Linux (all that stuff via Command Prompt sudo bash blah blah etc), I've also never had any CNC experience, nor have I used breakout boards, stepper drivers etc etc... it's been quite a steep learning curve up to this point but, an enjoyable one!

I'm just extremely thankful that there are forums like this and, on those forums, there are people like you and Andy. It makes the whole journey both feasible and enjoyable! Thanks

This forum has to be the most helpful and friendliest I've ever been on and Andy, really is a legend. He's tireless, helpful, makes you think and is happy to help anybody. I started my CNC journey with an Aduino too by building a rotary table controller.

Master is the unstable development branch which will become V 2.8. Version 2.7 is the current stable release. I think of a joint as being a motor (there can be multiple joints in an axis - eg on each side of a gantry or maybe the Z on a knee mill where the motors on the knee and the head add together on ths Z axis).
Up until V 2.8, with trivial kinematics machines (eg conventional XYZ mills, lathes and gantries as opposed to hexapods and robots), there was a 1:1 mapping between the axes and joints (X=joint 0, Y=joint 1, Z=joint 2). That means you can home a joint and the matching axis will be homed which is how you have set up your control panel so don't dismay!

Before I started with LCNC, somebody wrote a better Joint Axis module (JA) which has now been merged into the 2.8 branch. This made changes to the homing sequence to simplify squaring of a joint axis gantry. It also removed the 1:1 mapping between joints and axes. So now the X axis could be Joint 9 if you wanted. This had some additional side affects the developers missed but I think most of them have been fixed in the last couple of months.

I've had too much to learn to learn much about Gcode yet, but I think there is a way to set the starting point of a part similar to how you envisaged you would set a home position. Maybe somebody could chime in and explain how to do that.