Hello Guest it is May 11, 2021, 01:31:58 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Highspeed1964

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 »
101
One additional question or two, are you using Mach 3 or 4 and what screen set are you using?  I'm using Mach 3 and the original 1024 screen set modified to clean it up a bit and added a set of LEDs on the Run Program screen to monitor the probe signal.

Highspeed

102
General Mach Discussion / Re: Motors are not operating correctly
« on: July 24, 2016, 02:12:29 PM »
Something I saw in another thread is that the arrow keys for the X axis would run reverse on the first press, but release it and press again and the axis would move in the correct direction.  Can you check and see if this is the case for you?  I know you said this was all running until the cleaning, but if it's the wireless keyboard it could do strange things like this.  (I don't think that other thread revealed any solution.)

Highspeed

103
Understand that, Dave.  I like having it that way too.  I've set up an M6Start macro that positions the spindle to a user defined location using the "Tool Change Location" DROs in the settings page and then prompts for the tool to be changed.  It waits for the tool to be changed and acknowledged then asks for an auto tool zero (with OK or Cancel buttons) and if auto is selected it moves to the Z location specified as above (the tool change is done at SafeZ if defined or 0 if not) and begins the probe move.  Cancel lets you do it manually.  Then press "Cycle Start" to run the M6End macro which positions the tool at the location it was when the M6 command was triggered in the program and continues on.

My advice to use a "do nothing" M6 macro is for troubleshooting to determine if it's a macro problem or a bug in the program.  I'll have another look at mine to see if jogging causes problems in the manual operation of the macro.

Stephen "Highspeed" Kruse

EDIT:  Reading through this post again, I just noticed that you did try blank macros already.  I'll have a go at it later today and see how it works out for me.  What components are you using for your electronics?  (Breakout board, motion controller, stepper drivers, etc.)

104
FAQs / Re: Zero Tool not reading allowance
« on: July 23, 2016, 09:59:08 PM »
Back up your .xml file and any screen sets you're using if not the default screen set.  Then after you reinstall, put the .xml file back and start up Mach 3 with that profile.  You should be good to go then.

As for the USB ports, not sure what to do there.  It could be an older (or even newer!) USB protocol and have incompatibility with the specific USB device.  For example, my new laptop has 1 USB 2.0 port and 2 USB 3.0 ports.  Fortunately, I have not found any older equipment that I use that is not compatible with the newer 3.0 ports so I'm ok.  I guess if you can live with it not being connected on the back port and use only the side ports you should be ok.

Highspeed

105
FAQs / Re: Sample gcode need larger scale
« on: July 23, 2016, 07:16:12 PM »
Hey JR,

Just came across this post.  I know it's a bit older than the other one we've been discussing, but I'll take a crack at this one too if it's still an issue for you.

The homing routine _should_ run the axis at a relatively slow rate until the switch is contacted, then back off a _slight_ amount until the switch is no longer active.  Setting the Home Offsets only updates the DROs to the offset value as I understand it.  It does not actually move the axis that amount.  I'd have to play with this to confirm, though.  But my machine also uses combined limit/homing switches (a limit switch at each end wired to the same input and configured for the same pin on all three inputs in the Config/Port & Pins screen on the Inputs tab) so it may behave differently if you have a separate home switch wired to a different pin than the limit switches.

Let me know.

Stephen "Highspeed" Kruse

106
G59P offsets are for moving the coordinates to a different reference.  However, this would not make a good choice in my mind for cutter wear compensation as it shifts all x y values the same amount.  So for example, you're cutting a piece on the low X or Y side of the part and your offset is adjust for a .002" wear on the tool, then cuts on the high X or Y side of the part would be even further off by an additional .002".

As I understand it, you would just adjust your tool radius in the tool table to allow for the wear on the tool.  Then your normal tool compensation would take this into account and be correct all the way around the part.

Take this with a grain of salt, though.  My knowledge on this is somewhat limited as I'm relatively new to milling and do not use tool compensation as my CAM software does this for me.  Of course I have to make sure the tool tables in THAT software are accurate, but either way it seems that the tables are the secret to mastering compensation values.

Stephen "Highspeed" Kruse

107
FAQs / Re: Zero Tool not reading allowance
« on: July 23, 2016, 06:48:42 PM »
One additional thought, you had asked if tool offsets could make a difference.  You could try putting a "G49" into the line with the G31 move.  G49 cancels any tool offset so if you still need those after the zero operation (in my opinion tool offsets and zero tool operations are pretty much mutually exclusive - at least in my limited understanding of these things) then you'll need the macro to account for the current offset and restore it at the end.

Highspeed

108
FAQs / Re: Zero Tool not reading allowance
« on: July 23, 2016, 06:05:14 PM »
Interesting, I'm using 3.043.066 and have had no issues with the Zero probing.  Being somewhat new to this myself, it's the only version I have used.

Regarding your earlier post that showed different readings for each try, is it possible that the offset was correctly set for the previous probe movement and the next one would show the reading in this new offset coordinate value?  Also, are you getting the message "Z axis is now zeroed" on your status line?

Finally, I see Gerry asked you to remove the lines pertaining to the ZProbePos variable and understand the reasoning behind this.  It is something I was not aware of.  However, I have a general coding question for Gerry.  Assuming one DOES use these lines in their code, shouldn't there be a space between the & and the variable name or is VBScript not so particular about that?

In any case, thanks for stepping in with additional help Gerry.  I'm sure we can get this solved for JR.

Stephen "Highspeed" Kruse

109
Try putting nothing in the M6Start Macro.  It will still pause if you have that option set in the General Config screen.  Then see if you still get the error after jogging.  If not, then there's definitely something in the macro that's doing it.  Otherwise, it may be a bug in the software.  I'm trying to remember if I have done any jogging in the M6 state as I have everything automated to go to a safe tool change location and then probe after acknowledging that is complete.  Then press cycle start and the spindle moves back to it's original location and continues on with the program.

Let us know if that changes anything.

Stephen "Highspeed" Kruse

110
General Mach Discussion / Re: newbe with 4th axis problem
« on: July 23, 2016, 03:46:49 AM »
Often time, the micro step setting on the driver is not readily available.  My particular driver for the 4th axis is printed in Chinese so I can't really tell what it's saying.  However, my X, Y, and Z axis drivers are clearly marked in English and I can tell it's set to 8.  So I figured I'd use that for my starting point and sure enough it was correct.

Reversing the calculations for the settings Cary finally came to:

6.6666 * 360 = 2400 Steps for one complete revolution of the axis
2400/6 = 400 Steps for one complete revolution of the motor
400/200 = 2 micro steps on the driver

So there you have it, Cary's machine has the 4th axis driver set to 2 micro steps.

In my case:

13.3333 *360 = 4800 Steps for one complete revolution of the axis
4800/3 = 1600 Steps for one complete revolution of the motor (my belt/pulley arrangement is 3:1)
1600/200 - 8 Micro steps on the driver

The math is correct as you indicated robertspark.  The confusion is that the micro step setting was unknown in Cary's machine.

Stephen "Highspeed" Kruse

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 »