<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[SoliForum - 3D Printing Community — Home position config for smoothieware issue]]></title>
		<link>https://www.soliforum.com/topic/18263/home-position-config-for-smoothieware-issue/</link>
		<atom:link href="https://www.soliforum.com/feed/rss/topic/18263/" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Home position config for smoothieware issue.]]></description>
		<lastBuildDate>Sun, 27 Oct 2019 15:17:52 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151736/#p151736</link>
			<description><![CDATA[<p>Ill get back to you on that one but I should think there are coordinates respective to the size of the bed right?! Shouldn&#039;t there be a standard in the config/firmware files?! I&#039;m thinking that since there are no physical endstops other than x,y for home purposes that the config file text under endstops should maybe set to false or will that cause an issue with the homing endstops?! Maybe the max on these is set to high for homing?! my bed is 200x200x190mm</p><p>alpha_max_travel&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;500&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Max travel in mm for alpha/X axis when homing<br />beta_max_travel&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 500&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Max travel in mm for beta/Y axis when homing<br />gamma_max_travel&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;500&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Max travel in mm for gamma/Z axis when homing</p>]]></description>
			<author><![CDATA[null@example.com (markkcunningham)]]></author>
			<pubDate>Sun, 27 Oct 2019 15:17:52 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151736/#p151736</guid>
		</item>
		<item>
			<title><![CDATA[Re: Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151734/#p151734</link>
			<description><![CDATA[<p>Cool then they stopped using the proprietary endstops. So what what does M119 report when none of the axis are home?</p>]]></description>
			<author><![CDATA[null@example.com (carl_m1968)]]></author>
			<pubDate>Sun, 27 Oct 2019 04:36:02 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151734/#p151734</guid>
		</item>
		<item>
			<title><![CDATA[Re: Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151733/#p151733</link>
			<description><![CDATA[<p>That&#039;s funny because everything was working fine! I did reinstall the firmware to latest and edit the config file but nothing out of the ordinary</p>]]></description>
			<author><![CDATA[null@example.com (markkcunningham)]]></author>
			<pubDate>Sun, 27 Oct 2019 03:29:56 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151733/#p151733</guid>
		</item>
		<item>
			<title><![CDATA[Re: Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151732/#p151732</link>
			<description><![CDATA[<div class="quotebox"><cite>markkcunningham wrote:</cite><blockquote><p>pronterface M119</p><p>X_min:0 Y_min:0 Z_min:0 pins- (X)P1.24:0 (Y)P1.26:0 (Z)P1.28:0</p></blockquote></div><p>If that is with them homed then the switches need&nbsp; to be rewired as that shows the are open and not activated. If the switches are the stock optical switches they will only work with XYZ mainboard and no other board. You will need to replace them with mechanical switches or optical switches that are standard. If you get the same status not homed the that confirms the switches are not working.</p>]]></description>
			<author><![CDATA[null@example.com (carl_m1968)]]></author>
			<pubDate>Sun, 27 Oct 2019 02:34:14 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151732/#p151732</guid>
		</item>
		<item>
			<title><![CDATA[Re: Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151731/#p151731</link>
			<description><![CDATA[<p>pronterface M119</p><p>X_min:0 Y_min:0 Z_min:0 pins- (X)P1.24:0 (Y)P1.26:0 (Z)P1.28:0</p>]]></description>
			<author><![CDATA[null@example.com (markkcunningham)]]></author>
			<pubDate>Sun, 27 Oct 2019 02:05:21 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151731/#p151731</guid>
		</item>
		<item>
			<title><![CDATA[Re: Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151729/#p151729</link>
			<description><![CDATA[<p>So then you need to make sure your homing direction is set correctly. You also need to open a host and send and M119 command to the printer with the hotend homes manually and not homed and see what the status of the limit switches are. </p><p>If it is moving away from home to home then the homing direction or motor directions are wrong.</p>]]></description>
			<author><![CDATA[null@example.com (carl_m1968)]]></author>
			<pubDate>Sun, 27 Oct 2019 02:02:14 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151729/#p151729</guid>
		</item>
		<item>
			<title><![CDATA[Re: Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151728/#p151728</link>
			<description><![CDATA[<p>Home on a Da vinci is in the back right corner but for some reason it wont home in that location but rather takes off to the front and doesnt stop at all! the board is an Azteeg x5 all in one using smoothie. seems the coordinates are all out of wack.</p>]]></description>
			<author><![CDATA[null@example.com (markkcunningham)]]></author>
			<pubDate>Sun, 27 Oct 2019 01:41:49 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151728/#p151728</guid>
		</item>
		<item>
			<title><![CDATA[Re: Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151724/#p151724</link>
			<description><![CDATA[<p>Well for starters based on the min endstops since that is all that is enabled where should home be based oh the endstop locations? Is home in the front? Home is where are the endstops at as they dictate where home is?</p>]]></description>
			<author><![CDATA[null@example.com (carl_m1968)]]></author>
			<pubDate>Sat, 26 Oct 2019 21:26:19 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151724/#p151724</guid>
		</item>
		<item>
			<title><![CDATA[Home position config for smoothieware issue]]></title>
			<link>https://www.soliforum.com/post/151719/#p151719</link>
			<description><![CDATA[<p>My issue is when homing the extruder it goes to the front of the machine and keeps going and will not stop?! The config file seems correct yet its not working correctly!</p><p>Here is the config:<br />## Endstops<br /># See <a href="http://smoothieware.org/endstops">http://smoothieware.org/endstops</a><br />endstops_enable&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; true&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# The endstop module is enabled by default and can be disabled here<br />#corexy_homing&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;false&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Set to true if homing on a hbot or corexy<br />alpha_min_endstop&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1.24^&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Pin to read min endstop, add a ! to invert if endstop is NO connected to ground<br />#alpha_max_endstop&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1.25^&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Pin to read max endstop, uncomment this and comment the above if using max endstops<br />alpha_homing_direction&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;home_to_min&nbsp; &nbsp; &nbsp; # Or set to home_to_max and set alpha_max and uncomment the alpha_max_endstop<br />alpha_min&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # This gets loaded as the current position after homing when home_to_min is set<br />alpha_max&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 200&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # This gets loaded as the current position after homing when home_to_max is set<br />beta_min_endstop&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1.26^&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Pin to read min endstop, add a ! to invert if endstop is NO connected to ground<br />#beta_max_endstop&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1.27^&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Pin to read max endstop, uncomment this and comment the above if using max endstops<br />beta_homing_direction&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; home_to_min&nbsp; &nbsp; &nbsp; # Or set to home_to_max and set alpha_max and uncomment the alpha_max_endstop<br />beta_min&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # This gets loaded as the current position after homing when home_to_min is set<br />beta_max&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;200&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # This gets loaded as the current position after homing when home_to_max is set<br />gamma_min_endstop&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1.28^&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Pin to read min endstop, add a ! to invert if endstop is NO connected to ground<br />#gamma_max_endstop&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1.29^&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Pin to read max endstop, uncomment this and comment the above if using max endstops<br />gamma_homing_direction&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;home_to_min&nbsp; &nbsp; &nbsp; # Or set to home_to_max and set alpha_max and uncomment the alpha_max_endstop<br />gamma_min&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # This gets loaded as the current position after homing when home_to_min is set<br />gamma_max&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 200&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # This gets loaded as the current position after homing when home_to_max is set</p><p>alpha_max_travel&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;500&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Max travel in mm for alpha/X axis when homing<br />beta_max_travel&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 500&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Max travel in mm for beta/Y axis when homing<br />gamma_max_travel&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;500&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Max travel in mm for gamma/Z axis when homing</p>]]></description>
			<author><![CDATA[null@example.com (markkcunningham)]]></author>
			<pubDate>Sat, 26 Oct 2019 19:44:42 +0000</pubDate>
			<guid>https://www.soliforum.com/post/151719/#p151719</guid>
		</item>
	</channel>
</rss>
