@DavidF I would get the latest Grbl (v1.1f 2017-08-01 Release) from https://github.com/gnea/grbl/releases and set your required homing Z then XY if you want to match my firmware and compile to your Nano and see if it shows the same issue.

These would be the only changes necessary:
config.h;
#define HOMING_CYCLE_0 (1<<Z_AXIS)
#define HOMING_CYCLE_1 ((1<<X_AXIS)|(1<<Y_AXIS))

cpu_map;
#define X_LIMIT_BIT 1 // Uno Digital Pin 9
#define Y_LIMIT_BIT 2 // Uno Digital Pin 10
#define Z_LIMIT_BIT 4 // Uno Digital Pin 12

I should have time to do this next week but since I'm not seeing the issue I would still have to send to you for testing and feedback.

@tucker298 Yes, plug and play. The boot loader should be pre-installed, the only Nano's I've purchased where this wasn't the case were the unsoldered bulk variety (but for less than $1 each I wasn't bothered).

@icejoker You may have installed LaserAxe or other controller firmware.

This is the default firmware for Eleks systems:

If you were in the Custom firmware menu then you need to be careful and only load what is compatible with your machine, in this case I think you may have corrupted the Nano. As I said that can be fixed but you will probably need to use Arduino IDE to reload the boot loader. You could try the Clear EEPROM option and then load the default, it may work depending what firmware you have installed.

@Dominykasssx Load the correct firmware and it should work.

can you tell me your mana controller vision? if it is V3.1 , than you can buy our bluetooth module

@Firematt97

Buehler.......Buehler....