MY lowrider connects and Z is set to +200

Hey guys,and gals, im cutting/working well with my lowrider, soon i will produce a project thread but anyhow, when i connect my Low rider 2 to my PC The Z axis is automatically set to 200 is this a homing function?

I am running dual endstop firmware, marlin rambo board…although my endstops are a mess and do not function and im still working with the G92 X0 Y0 Z0 at the beginning of all my gcode.

I am not really affected by this so far, i was just wondering.

Also does anyone have info on the z homing part of the firmware im using?
When i was trying to play with my endstops, the Z homes up? i think i also read that somewhere…
I think my end stop configure would need to home down… The Z endstops are installed on either end of the front X axistube, facing down…

So in reading the forums I have a guess about the sequence that gives you the 200 value for Z based on my reading on this forum (I don’t own a Low Rider):

With the Low Rider, the Z axis is homed up to square the axis. When it successfully homes, the current height of Z is set to 200. This is an arbitrary value in the firmware but I’m guessing at some point was set higher than the Z axis on a Low Rider can go. This high value avoid a soft stops when bringing the router down to begin cutting.

Somewhere your g-code you are triggering a homing sequence for Z. End stop switches are wired normally closed (NC), but I’m guessing that either your switches are not yet connected or were wired normally open (NO). When the homing sequence starts, it see NO switches and assuming it is at the home position. It will back off slightly (down) and then test again, and again it will find the switches NO and say it is homed and the Z height will be set to 200.

Again on the Low Rider, Homing (G28) goes up to square the axis. To find the top of the stock, a G38.2 g-code is used to probe downward.

Thanks for the fast input, im pretty sure your right on…

I will post the endstop status info soon as it is when i connect. It seems like it forgets whatever is connected cause im sure they are not wired right, one or two are stuck open or w.e from repeated knocks when the axis would drop or my fingers got hulk powers…

Any way hear is the code that i get when i connect through repetier host

18:50:20.396 : echo: Free Memory: 3344 PlannerBufferBytes: 1488
18:50:30.153 : echo:start
18:50:30.153 : Marlin 508DL
18:50:30.169 : echo: Last Updated: 2020-10-15 | Author: (V1 Engineering, Ryan, 508DL)
18:50:30.169 : echo:Compiled: Dec 27 2020
18:50:30.169 : echo: Free Memory: 3344 PlannerBufferBytes: 1488
18:50:30.332 : N1 M11034
18:50:30.332 : N2 M115
18:50:30.332 : N3 M10536
18:50:30.332 : N4 M114
18:50:30.332 : N5 M111 S698
18:50:30.432 : N6 T0
18:50:30.470 : N7 M8028
18:50:37.052 : DIGIPOTS Loading
18:50:37.052 : DIGIPOTS Loaded
18:50:37.052 : DIGIPOTS Loading
18:50:37.052 : DIGIPOTS Loaded
18:50:37.052 : echo:V82 stored settings retrieved (649 bytes; crc 36779)
18:50:37.306 : Cap:SERIAL_XON_XOFF:0
18:50:37.322 : N8 M220 S100
18:50:37.322 : N9 M221 S100105
18:50:37.322 : N10 M111 S6
18:50:37.322 : Cap:BINARY_FILE_TRANSFER:0
18:50:37.322 : Cap:EEPROM:1
18:50:37.322 : Cap:VOLUMETRIC:0
18:50:37.322 : Cap:AUTOREPORT_TEMP:0
18:50:37.322 : Cap:PROGRESS:0
18:50:37.322 : Cap:PRINT_JOB:1
18:50:37.322 : Cap:AUTOLEVEL:0
18:50:37.322 : Cap:RUNOUT:0
18:50:37.322 : Cap:Z_PROBE:1
18:50:37.322 : Cap:LEVELING_DATA:0
18:50:37.322 : Cap:BUILD_PERCENT:0
18:50:37.322 : Cap:SOFTWARE_POWER:0
18:50:37.322 : Cap:TOGGLE_LIGHTS:0
18:50:37.322 : Cap:CASE_LIGHT_BRIGHTNESS:0
18:50:37.322 : Cap:EMERGENCY_PARSER:0
18:50:37.322 : Cap:PROMPT_SUPPORT:0
18:50:37.322 : Cap:SDCARD:1
18:50:37.322 : Cap:AUTOREPORT_SD_STATUS:0
18:50:37.322 : Cap:LONG_FILENAME:0
18:50:37.322 : Cap:THERMAL_PROTECTION:1
18:50:37.338 : Cap:MOTION_MODES:1
18:50:37.338 : Cap:ARCS:1
18:50:37.338 : Cap:BABYSTEPPING:0
18:50:37.338 : Cap:CHAMBER_TEMPERATURE:0
18:50:37.353 : N11 T0*10
18:50:37.407 : echo:DEBUG:INFO,ERRORS
18:50:37.407 : echo:Unknown command: “M80”
18:50:37.407 : echo:Unknown command: “M221 S100”
18:50:37.407 : echo:DEBUG:INFO,ERRORS

Yep. Totally normal.