MPCNC Primo + ESTLCAM Plunge into wood (Too Far)

Ok, I am working on my first piece and I entered the starting GCodes from this site into ESTLCAM, I start it up and it sets X & Y using dual endstops. Then I set Z to the top of the wood scrap I am using using the clamps and metal piece. When I do this, start the router and click the button to have it start on the Rambo 1.4 I got from the shop here, it just dives in way more than the 2mm I set in ESTLCAM to start… In ESTLCAM the preview looks good, I do not see it plunging like that…

Here is an excerpt of the GCode, anyone have any thoughts about what silly thing I have done here?
I let it go the first time, it ripped the plastic off the bit and plunged down to the metal cuff so I may be a bit gun shy.

G90 ; Absolute positioning, just in case
G92 X0 Y0 Z0 ; Set Current position to 0, all axes
G00 Z5.0000 F500 ; Raise Z 5mm at 8.3mm/s to clear clamps and screws
G28 X Y Z ; Home in order, w/zprobe
G92 Z0.15 ; Account for probe thickness (set your thickness)
G00 Z5.0000 F500 ; Raise Z probe off off of surface
M00 ; pause for LCD button press
M03 S24000 ; PID, set spindle speed
G00 X0.0000 Y0.0000 Z0.0000 F2100
G00 Z2.0000 F480

;No. 1: Engraving 24
G00 X1.4423 Y0.6556 F2100
G00 Z0.5000 F480
G01 Z0.0000 F180 S24000
G01 Z-1.0000 F180
G01 Y170.2040 F480
G01 X100.3100 F480
G01 Y1.4491 F480
G01 X0.6488 F480
G01 Z-2.0000 F180
G01 X100.3100 F480
G01 Y170.2040 F480
G01 X1.4423 F480
G01 Y0.6556 F480
G00 Z2.0000 F480

Is it going up the proper amount for the G00 Z5.000 F500 line?

At times this has happen to me too. It always ends up after homing Z. The Z axis stepper power is turned off. When you turn on the router and it starts to move the vibration will cause the Z to drop. The 2nd Z code comand turns the motor to turn on and it works, except your z home is now way off. My solution to make sure it never happens is after z home; I jog z up .1 and down .1. Then I know for sure the z stepper is engaged. I really should look into this more, but its more fun to make chips. In my case I am useing a mega board and ramps 1.4 I believe.
I do know this was a random event, it did not happen every time. I was playing with making videos of the maching and just happen to record it failing, clearly seen the z drop as it move across the table.

Ugh thank you both, the culprit was discovered. I had entered the GCode starter in OctoPrint and ESTLCAM, thought I saved it and removed from Octoprint but not the case… So it had gone into a second calibration. I stepped through each command in the terminal which was useful.