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 - brian98

Pages: 1 2 »
1
My version is Version R3.043.066

2
Full Solution:

I've now got a "brain" that works to prevent this problem.  It detects if the Step mode is active when the shift key is pressed.  If so, it causes a program "Reset".  This is a bit extreme but is necessary for me because the wiring for my speed control through the spindle VFD requires a Reset to halt the rotation completely.  If you don't have this problem, you can probably use "Offline" instead.  When building the brain, use the following:

Jog Continuous is OEMLED 14
Jog Increment is  OEMLED 15
Cont Shift Jog  is  OEMLED 58
Reset is ButtonPress 1021, or
Offline is ButtonPress 258

Don't forget to enable this new brain.  I called it NoShift.

3
VB and the development of wizards / Keystroke Trapping
« on: June 15, 2017, 05:12:18 PM »
Does anyone know of a way to read a keyboard keypress so it can be acted upon within Cypress basic.  I cannot find an "Inkey" function and don't see a replacement.  In particular, I'm looking for a way to see if the shift key has been held down.

Thanks for any assistance

4
When moving the axis using the arrow keys or buttons on the jogging control I've recently had a few times when the motion of the axis would not stop as I released the button.  Usually I noticed it right away and hit Escape in time to avoid problems.  Unfortunately last week I did not react in time and broke parts within the servo drive for my Z axis when the tool collided with my fixture.  This expensive problem has caused me to do some diagnosis.  I wish I had a full solution, but maybe this partial solution will help someone else.

The problem only happens when two things occur at the same time:  (a) the Jog Motion on the flyout window is set for step, not continuous; and (b) I have over-ridden the step action by using the shift key to high speed travel to the next point.  The problem of not stopping does not always occur under these conditions, but it has never occurred without both conditions.

So the temporary solution is to make sure the jog mode button is on Continuous before using the shift key!  I'm going to see if I can build a brain to halt motion if the shift key is pressed while the mode is Step, but have not done that yet.

For reference, I'm using Mach 3 with Smoothstepper.

5
Thanks for the advice.  Disappointing but at least there is a work-around.  I may see if I can build a "Brain" to do what I want.

6
I've configured my A axis as linear by unchecking "A axis is Angular" on the General Config page.  Nevertheless, when I give a code a move in the negative direction, the axis moves in the positive direction as if it were angular.  I have determined that if on the General Config page I uncheck the "Rot 360 Rollover" the axis behaves as I want a linear axis to do. 

Unfortunately, this means that I cannot use the Rollover feature on my B or C rotary axes.  This appears to be a bug in the Mach 3 software.  Does anyone have any comments or suggestions?

By the way, I have also found I can have the axis operate correctly as a linear axis even when the "Rot 360 Rollover" box is checked, but this requires going to Incremental Mode (G91) and out again every time I want to move in the negative direction.

7
General Mach Discussion / Re: Problem with Arc Center Location Error
« on: January 27, 2013, 03:44:04 PM »
Thank you so much, Hood.  That did indeed fix the problem. 

I'm not sure how the G16 got into the Init string but putting G15 in the string fixed the problem.  (Without the G15, just deleting the G16 did not seem to work - it kept reappearing.)

Anyway, now I can mill!  Also for reference by others, the IJ mode (General Config) has to be "Inc"

8
General Mach Discussion / Re: Problem with Arc Center Location Error
« on: January 26, 2013, 09:02:30 PM »
Again, thanks for your continued help.  Attached is the XML.  By the way, the problem occurs with two different machines using different XML's although they came from the same base.

Brian

9
General Mach Discussion / Re: Problem with Arc Center Location Error
« on: January 26, 2013, 07:39:07 PM »
Thanks for your assistance.  I extracted the bit of code and attempted to run it separately in case there was something else in the file that was causing the problem.  Got the same error.

Here's the entire file (all 18,758 lines).  The first problem occurs at line 7148

Brian

10
General Mach Discussion / Problem with Arc Center Location Error
« on: January 26, 2013, 06:13:04 PM »
I'm having a problem where Mach3 (v. R3.043.066) is giving me error messages "Radius to end of arc differs from radius to start".  As I understand it, this message is only supposed to occur if the error is more than 0.0002".  I've checked the math and my calculations show the error at almost 10x less (0.00003").  The code was generated by MeshcamArt and runs fine under Cutviewer but not when I actually try to cut the part with Mach3.  Here's an example of the issue:

X2.2058 Y1.2136
G2 X2.2737 Y1.4341 I0.7115 J-0.0985 F10.0

Is anyone aware of any other reason this error message might occur?

By the way, I have other similar G2 moves that work just fine in the same program.  This also cannot be a hardware issue as I am getting the error on loading the code into a computer not connected to the NC router.

Thanks for any advice.

Pages: 1 2 »