Timeout Errors During Job Operation, and Manual Jogging

[trentonc...@gmail.com]

Hello,

I'm working on the pnp with the pontech folks and i frustratingly get many timeout errors that popup while trying to do any movement with the machine. 

the error:  "timeout waiting for response to m400 ; wait for moves to complete before returning"

i've attached the machine .xml

as a note, i believe javon tried removing/changing the timeout/wait period, and the error just popped up for the next command in the code. (i may be mistaken on this)

regards,
trent

[Jason von Nieda]

* Does this happen for every single movement? 

* Are the moves taking longer than 10 seconds?

* Is this a new issue, or has it been happening all along?

Jason

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/25ad8312-6d9a-4311-96a1-0dea6df96fef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Trenton Wilson]

Jason,

it does not happen every time, however it does seem to increase in frequency the longer/more the machine is operated.

This issue has been there as long as i've been running the machine.  I am not the one that originally set up the machine and dont like the idea of doing that if starting over isnt the only option.

moves are not taking longer than 10 seconds.  I can repeatably tell the machine to to something like "park" it immediately starts moving to park location and a few seconds in it either stalls and generates the error message, or continues moving in the direction it was traveling after generating the error message.

On Mon, Aug 15, 2016 at 4:16 PM, Jason von Nieda <ja...@vonnieda.org> wrote:

* Does this happen for every single movement? 

* Are the moves taking longer than 10 seconds?

* Is this a new issue, or has it been happening all along?

Jason

On Mon, Aug 15, 2016 at 4:05 PM <trentonc...@gmail.com> wrote:

Hello,

I'm working on the pnp with the pontech folks and i frustratingly get many timeout errors that popup while trying to do any movement with the machine. 

the error:  "timeout waiting for response to m400 ; wait for moves to complete before returning"

i've attached the machine .xml

as a note, i believe javon tried removing/changing the timeout/wait period, and the error just popped up for the next command in the code. (i may be mistaken on this)

regards,
trent

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+unsubscribe@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/25ad8312-6d9a-4311-96a1-0dea6df96fef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "OpenPnP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openpnp/eMs_8BJzCpw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openpnp+unsubscribe@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/CA%2BQw0jwEjRgjU4ij7Hj%2BgbwGSTSxA43PLKGjZB_tW15_a707gQ%40mail.gmail.com.

[Jason von Nieda]

Trenton,

Please do the following:

1. Stop OpenPnP.

2. Turn on driver trace logging: https://github.com/openpnp/openpnp/wiki/FAQ#how-do-i-turn-on-debug-logging

3. Start OpenPnP and run commands until you get this error again.

4. Stop OpenPnP and then send me the log file: https://github.com/openpnp/openpnp/wiki/FAQ#where-are-configuration-and-log-files-located

Thanks,

Jason

On Mon, Aug 15, 2016 at 5:06 PM Trenton Wilson <trentonc...@gmail.com> wrote:

Jason,

it does not happen every time, however it does seem to increase in frequency the longer/more the machine is operated.

This issue has been there as long as i've been running the machine.  I am not the one that originally set up the machine and dont like the idea of doing that if starting over isnt the only option.

moves are not taking longer than 10 seconds.  I can repeatably tell the machine to to something like "park" it immediately starts moving to park location and a few seconds in it either stalls and generates the error message, or continues moving in the direction it was traveling after generating the error message.

On Mon, Aug 15, 2016 at 4:16 PM, Jason von Nieda <ja...@vonnieda.org> wrote:

* Does this happen for every single movement? 

* Are the moves taking longer than 10 seconds?

* Is this a new issue, or has it been happening all along?

Jason

On Mon, Aug 15, 2016 at 4:05 PM <trentonc...@gmail.com> wrote:

Hello,

I'm working on the pnp with the pontech folks and i frustratingly get many timeout errors that popup while trying to do any movement with the machine. 

the error:  "timeout waiting for response to m400 ; wait for moves to complete before returning"

i've attached the machine .xml

as a note, i believe javon tried removing/changing the timeout/wait period, and the error just popped up for the next command in the code. (i may be mistaken on this)

regards,
trent

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/25ad8312-6d9a-4311-96a1-0dea6df96fef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "OpenPnP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openpnp/eMs_8BJzCpw/unsubscribe.

To unsubscribe from this group and all its topics, send an email to openpnp+u...@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/CA%2BQw0jwEjRgjU4ij7Hj%2BgbwGSTSxA43PLKGjZB_tW15_a707gQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "OpenPnP" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/CAJSiL0TsZRCiTXk5FKnSTydqxFVsdmrm3cq7cZVHrGwju26wcg%40mail.gmail.com.

[trentonc...@gmail.com]

Jason,

I've attached the log file

[Jason von Nieda]

Trenton,

This is the logging configuration file, not the log. The log is in .openpnp/log/OpenPnP.log. Also, if that is your current log4j.properties file, please make sure to set log4j.logger.org.openpnp.machine.reference.driver to trace, not debug as it is now. This will give me all the logging data I need to see what is going on.

Jason

--

You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/6c7e16bf-c8c2-4412-9c0d-c0fa95705ce5%40googlegroups.com.

[Jason von Nieda]

Trenton,

I added some step by step instructions for getting the debug information together at https://github.com/openpnp/openpnp/wiki/GcodeDriver#asking-for-help. Hope this help.

Jason

[trentonc...@gmail.com]

Jason,

My bad. 

Here are the files from the folder.  It looks like i had turned on some debugging a bit ago.

On Monday, August 15, 2016 at 4:05:56 PM UTC-7, trentonc...@gmail.com wrote:

[trentonc...@gmail.com]

it looks like the smoothie board firmare is a bit old, so i updated and re-flashed, still got the timeout error issues.  Tried creating a fresh config file to no avail.

On Monday, August 15, 2016 at 4:05:56 PM UTC-7, trentonc...@gmail.com wrote:

[trentonc...@gmail.com]

Talking to javon, it sounds like it might have something to ith the gcode driver, as there ere not these issues ith the "open builds" driver, hoever the open builds driver apparently has some issues ith the z axis.  Belo is the portion of the machine.xml file for the driver that i believe as modified:

#<driver class="org.openpnp.machine.reference.driver.GcodeDriver" port-name="COM4" baud="115200" flow-control="Off" data-bits="Eight" stop-bits="One" #parity="None" set-dtr="false" set-rts="false" units="Millimeters" max-feed-rate="2000" timeout-milliseconds="10000" connect-wait-time-milliseconds="1000">
#         <command-confirm-regex>^ok.*</command-confirm-regex>
#         <connect-command>
#                G21
#                G90
#                M82
#            </connect-command>
#         <move-to-command>       
#                G0 {X:X%.4f} {Y:Y%.4f} {Z:Z%.4f} {Rotation:E%.4f} F{FeedRate:%.0f} ; Send standard Gcode move
#                M400 ; Wait for moves to complete before returning
#            </move-to-command>
#         <pick-command>
#                M808 ; Turn on pump
#            </pick-command>
#         <place-command>
#                M809 ; Turn off pump
#            </place-command>
#         <sub-drivers class="java.util.ArrayList"/>
#         <axes class="java.util.ArrayList">
#            <axis name="x" type="X" home-coordinate="0.0">
#               <head-mountable-ids class="java.util.HashSet">
#                  <string>*</string>
#               </head-mountable-ids>
#            </axis>
#            <axis name="y" type="Y" home-coordinate="0.0">
#               <head-mountable-ids class="java.util.HashSet">
#                  <string>*</string>
#               </head-mountable-ids>
#            </axis>
#            <axis name="z" type="Z" home-coordinate="0.0">
#               <head-mountable-ids class="java.util.HashSet">
#                  <string>*</string>
#               </head-mountable-ids>
#            </axis>
#            <axis name="rotation" type="Rotation" home-coordinate="0.0">
#               <head-mountable-ids class="java.util.HashSet">
#                  <string>*</string>
#               </head-mountable-ids>
#            </axis>
#         </axes>
#      </driver>

On Monday, August 15, 2016 at 4:05:56 PM UTC-7, trentonc...@gmail.com wrote:

[Jason von Nieda]

Hi Trenton,

A few notes:

* I'd suggest removing the comments from the Gcode. I'm not sure if that causes a problem; I've never tried it, but it's worth a shot.

* It looks like you have a lot of tabs or spaces indenting the commands in the XML. I'd suggest removing these. Look at the sample configs.

* Overall, the log file looks okay, and I don't see where a timeout is happening. Can you try clearing out all the logs, run the commands again and then send me just the log file that contains the commands that failed? It will also help if you send me the error message you get so I can try to match it up to a command.

Jason

--

You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/bf862452-fc28-4f31-96d7-2a09e10e83dc%40googlegroups.com.

[trentonc...@gmail.com]

Jason,

I added the comments/hash marks for posting the code, not actually in the machine.xml

i tried adjusting some tabs/spacing, though i'm not sure exactly hat your referring to.

i've attached the fresh log files as ell as the machine.xml file and log4j file.  The error message is as follos:
"Error
          Timeout aiting for response to M400 ; ait for moves to complete before returning"

[Jason von Nieda]

Trenton,

The logs and the error message both show that the comments are in the machine.xml and are being sent to the controller. Try removing all the comments and see if that helps. You can see that this is the case in the error message since it includes the comment.

Jason

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/10bda9f4-11e0-40f3-aac0-db3ceb14caf6%40googlegroups.com.

[trentonc...@gmail.com]

Jason,

I removed all comments present in the code, and still got the error, only the error message did not include the " ; ait for moves to complete before returning"

I did hoever just remove the M400 command entirely.  No issue, though i dont kno ho the machine is supposed to verify that it traveled to the desired location no.  perhaps the M400 command as in the rong place?

Looks like it as the easy obvious solution?  *shrugs  No i just have to figure out hy the machine likes to travel 100mm once hen i give it a .01mm jog command at startup.

Thanks a ton Jason.

[trentonc...@gmail.com]

Jason,

I'm getting  a couple more issues popping up running a test job.  the error messages are:

-"No Compatible, enabled feeder found for part ..." seems to randomly deselect the feeder, i manually re-select, only for the same thing to happen again, some time through the process
-"No defined transitions from cleanup for initialize" after trying to start a test job after sending the camera to board location.
-"timeout aiting for response m809", "timeout aiting for response m808"

On Monday, August 15, 2016 at 4:05:56 PM UTC-7, trentonc...@gmail.com wrote:

[Jason von Nieda]

Trenton,

The M400 not being there is going to cause you to run into further issues. I suspect the problem is related to the moving 100mm thing you mentioned. I addressed this in a previous message - not sure if it was to you or one of your team. You need to set the home-location coordinates in the machine.xml to tell OpenPnP where the machine is after homing.

The feeder getting disabled will happen if the feeder encounters an error for some reason. The most common is that the strip feeder thinks it's out of parts. If it's making a mistake, turn off the vision setting in the config for it.

Finally, are the typos in the error messages yours, or are they really showing up like that in the program? If the latter, we may need to investigate what is happening there. "timeout aiting for response m809", "timeout aiting for response m808" (missing w)

Jason

--

You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/35bd08cb-d05a-45cc-8276-ce7ef860c7d5%40googlegroups.com.

[Trenton Wilson]

Jason,

I'll try hunting for that previous message your talking about, i've joined the team very recently and may not have been around for it.

i'll try turning off vision and see if that improves things at alll

and the typos are actually all mine.  as luck ould have it, my "\/\/" and "cue"(phonetic) keys have died on me, havent had time to fix it.

On Wed, Aug 17, 2016 at 3:53 PM, Jason von Nieda <ja...@vonnieda.org> wrote:

Trenton,

The M400 not being there is going to cause you to run into further issues. I suspect the problem is related to the moving 100mm thing you mentioned. I addressed this in a previous message - not sure if it was to you or one of your team. You need to set the home-location coordinates in the machine.xml to tell OpenPnP where the machine is after homing.

The feeder getting disabled will happen if the feeder encounters an error for some reason. The most common is that the strip feeder thinks it's out of parts. If it's making a mistake, turn off the vision setting in the config for it.

Finally, are the typos in the error messages yours, or are they really showing up like that in the program? If the latter, we may need to investigate what is happening there. "timeout aiting for response m809", "timeout aiting for response m808" (missing w)

Jason

On Wed, Aug 17, 2016 at 3:43 PM <trentonc...@gmail.com> wrote:

Jason,

I'm getting  a couple more issues popping up running a test job.  the error messages are:

-"No Compatible, enabled feeder found for part ..." seems to randomly deselect the feeder, i manually re-select, only for the same thing to happen again, some time through the process
-"No defined transitions from cleanup for initialize" after trying to start a test job after sending the camera to board location.
-"timeout aiting for response m809", "timeout aiting for response m808"

On Monday, August 15, 2016 at 4:05:56 PM UTC-7, trentonc...@gmail.com wrote:

Hello,

I'm working on the pnp with the pontech folks and i frustratingly get many timeout errors that popup while trying to do any movement with the machine. 

the error:  "timeout waiting for response to m400 ; wait for moves to complete before returning"

i've attached the machine .xml

as a note, i believe javon tried removing/changing the timeout/wait period, and the error just popped up for the next command in the code. (i may be mistaken on this)

regards,
trent

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+unsubscribe@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/35bd08cb-d05a-45cc-8276-ce7ef860c7d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "OpenPnP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openpnp/eMs_8BJzCpw/unsubscribe.

To unsubscribe from this group and all its topics, send an email to openpnp+unsubscribe@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/CA%2BQw0jxAjRfEDDJ2notpPtg%3D4ZyM%2BmzZNXb4rOx%3DWg_XPvJLXw%40mail.gmail.com.

[trentonc...@gmail.com]

I did find this thread on this openpnp groups, but it doesnt seem to be the same problem... similar, but not.  My issue only happens once per axis hen first booting up openpnp, and not alays on 3 axis.

On Monday, August 15, 2016 at 4:05:56 PM UTC-7, trentonc...@gmail.com wrote:

[Jason von Nieda]

Trent,

Perhaps we'd have more luck if you record a video showing the problems? Could you record something showing startup, home, move and then any errors and post it to YouTube? I'm feeling like I'm having trouble understanding the scope of the issues.

Jason

--

You received this message because you are subscribed to the Google Groups "OpenPnP" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/dde87c2a-ae16-4e62-8ee3-cb8baf9353a7%40googlegroups.com.

[Jason von Nieda]

Here is the thread I was referring to: https://groups.google.com/d/msgid/openpnp/81b4b68b-c2b6-40bb-abeb-eca544892b07%40googlegroups.com?utm_medium=email&utm_source=footer

To summarize:

1. Make sure your home location is set correctly first. The moving 100mm issue needs to be resolved first.

2. Add M400 back to the machine.xml, since this is required for Smoothie. Otherwise you will get incomplete moves when picking.

3. Make sure all comments and extraneous whitespace are removed from the commands. Each command should be on a new line and there should be no extra whitespace around them.

4. If all that fails, please record a video showing the issue.

Jason

[trentonc...@gmail.com]

Jason,

hile you ere posting, i as fishing about in the smoothie board config file and changed some of the values of the acceleration values for the axis in an attempt to increase the z travel speed (very slo compared to the other axis).  After making those changes, I cant seem to replicate the issue funny enough.  If it pops up again i'll be sure to record as much as i can.  There might have been some conflicting values in there.

Home location is set 0,0,0,0 as usual,

i'll try removing all the hite space in the code so that there is no indenting of lines to present their position.

Thanks for your patience.

Regards,
Trent

[Jacob Christ]

Jason,

We think we are close on this one... You threw us a red herring by asking if moves take longer than 10 seconds.  Our moves were not taking longer than 10 seconds but we were using the 9deb48... version of openpnp which has timeouts hard coded at 5000ms (not 10000ms).

We have a butt slow shapeoko and sometimes the moves are close to if not longer than 10 seconds.  We are trying to move to the head which has timeouts settable in the machine.xml

Jacob

[Jason von Nieda]

Sounds good, let me know how it goes. Will be back at my desk in about 6 hours and can help more then.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/285e43af-ee0b-48ab-8506-c7af06b6928f%40googlegroups.com.

[pham thang]

Help me!!

I have 1 first Open PNP project with 1 problem can't fix. My machine after homing, can't move any more by joging manual.

I don't know where is it from

Thank you

Vào 05:11:55 UTC+7 Chủ Nhật, ngày 21 tháng 8 năm 2016, Jason von Nieda đã viết:

[Jason von Nieda]

1. Turn on TRACE logging: https://github.com/openpnp/openpnp/wiki/FAQ#how-do-i-turn-on-debug-logging

2. Retry moving.

3. Send me the log file: https://github.com/openpnp/openpnp/wiki/FAQ#where-are-configuration-and-log-files-located

Jason

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/bb6f89e2-a89f-4972-8359-d58d93a8a611%40googlegroups.com.

[Trenton Wilson]

might be an issue with your endstops, and or the relation between where you've defined your homing location vs your zero position.

To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+unsubscribe@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/bb6f89e2-a89f-4972-8359-d58d93a8a611%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "OpenPnP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openpnp/eMs_8BJzCpw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openpnp+unsubscribe@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/CA%2BQw0jzrzjVSYM4ih_%3Dr4-7d0DfXHzeBxKoXP9L9kcmDQF2wCw%40mail.gmail.com.

[pham thang]

Dear Wilson and Jason

You are correct, have problem with my powered endstop configuration.

1.After changing the endstop configuration as below, we can move the axis after homing.

From

alpha_min_endstop                            1.24^          

alpha_max_endstop                            1.25v^

To

alpha_min_endstop                            1.24v 

alpha_max_endstop                            1.25v

But now i encoutered one another problem that after homing the axis not move correct way after joging +, instead of moving + way, axis move to - way and impact to min endstop sensor.

I don't know what is happening, maybe the powered sensor is not stable, or my controller PCBA...

Pls help to advise

Thank you so much

Vào 05:53:25 UTC+7 Thứ Sáu, ngày 10 tháng 3 năm 2017, Trenton Wilson đã viết:

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/bb6f89e2-a89f-4972-8359-d58d93a8a611%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "OpenPnP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openpnp/eMs_8BJzCpw/unsubscribe.

To unsubscribe from this group and all its topics, send an email to openpnp+u...@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

[Trenton Wilson]

Pham,

Sounds like you'll have to force a  home command or include that in the driver on startup so that the machine coordinates match the registered coordinates on the controller board.  We had a similar situation where the coordinates in the openpnp software would differ from the boards known coordinates such that when a move command was sent the board would interpret it as a different move in a different direction.  I could try and pull up the code if you need a sample.  But our solution was to add a reset all axis and home command before the connect command would initiate.

To unsubscribe from this group and all its topics, send an email to openpnp+unsubscribe@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/1de02533-d71a-4ede-b317-af5cee449680%40googlegroups.com.

[Jason von Nieda]

Hi Pham,

It could be that your motor direction is incorrect. Try changing "alpha_dir_pin 0.5" to "alpha_dir_pin !0.5". This will invert the direction on the alpha axis.

Jason

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/1de02533-d71a-4ede-b317-af5cee449680%40googlegroups.com.

[pham thang]

Dear Jason and Wilson

I tried to change the config file, do testing and realized that when the axis homing, the controller will record coordinate during touch on sensor (X0,Y0,Z0), then will retract 5mm and to be (x5,y5,z5), but the open pnp understand that current coordinate is x0,y0,z0. When i send 1 command "x0.1", instead of x axis move to 0.1, x axis go back -4.9 cause wrong direction.

I changed from x min=0 retract to 5, x min=-5 retract 5 and see that every thing is nice

I don't know my problem was fixed correct way or not?

Thang

Vào 21:48:37 UTC+7 Thứ Sáu, ngày 10 tháng 3 năm 2017, Jason von Nieda đã viết:

[Jason von Nieda]

Pham,

You can also set home-coordinate on each axis in machine.xml. This tells OpenPnP what the coordinate for that axis is after home.

Jason

To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/af9b333a-37e5-4f9a-8230-eb6f9a4aaba9%40googlegroups.com.