Hello Guest it is April 14, 2021, 05:22:50 AM

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 »
This may best be answered on the BobCAD support site.  v21 is a bit older than what I'm using so I'm not sure I could answer even if I had tried this in my version (v28 as I recall) since there are great differences between the versions.


General Mach Discussion / Re: Mach3 Starting to behave erratically!
« on: January 09, 2017, 06:48:21 PM »
With it being such a large job, my guess would be mechanical.  Parts tend to wear out, although it could also be loose wires like Gerry said.  But motors and mechanical wear would be where I start after checking those wires.


Ah, yes. Calling it from within another macro then that makes sense. Did the additional changes you made paying the variable make it work for you?


First, you've made a classic mistake in that you do not need to use Sub Main... End Sub for the main part of the program.

Secondly and more to the question, when you "Call A" I think you need to pass the variable to the sub routine as follows:

Call A(t)

I'd have to dig back into my documents to see if there's anything more you need to do in the sub routine to accept the value, but this should help get you started in the right direction.

Hope this helps,

Stephen "Highspeed" Kruse

When swapping the Y and Z axis, are you swapping the driver and the motor (i.e. just swapping the driver inputs) or one component at a time?  There could be a mis-wired connection between the driver and the motor itself.  If you haven't already done so, swap the actual drivers between the Y and the Z both at the input from the breakout board (you are using one and not trying to run the drivers directly from the 25-pin connector, right?) AND the output to the motor.  If the symptom switches from one axis to the other, then it's the driver.  If not, check the motor wiring.

However, as was stated by TOTALLYRC, it's probably the driver as a mis-wired motor would usually have bad steps which you'd notice (usually by sound) or it could be a faulty breakout board.  Just something else to check before spending money on a driver if that's not the issue.

Stephen "Highspeed" Kruse

General Mach Discussion / Re: mach3 command line parameters
« on: November 14, 2016, 04:24:42 AM »
Hey Rich,  I may have misunderstood the original question and forgive me if I have, but I believe the OP was asking about command-line parameters to start the Mach3 program, not the g-code program itself.  In the post, he gives the example:

> c:\mach3\mach3.exe /p smoothstepper

This would start the program with a profile called "smoothstepper".  Are there other command-line switches such as this?  I'm curious to know about them as well.

That said, I love the document you've produced.  It's very informative.  I just wish I had the creativity to understand how I might use parameters in my code, but I am simply using a CAD program to create my g-code files.


VB and the development of wizards / Re: Macro only runs in editor
« on: October 20, 2016, 07:07:24 PM »
That'll do it too. Glad you got that figured out.


SmoothStepper USB / Re: Stepper glitches fwd and rev
« on: October 20, 2016, 02:53:19 AM »
Ah, yep. I can see how that would do it, too.

Thanks for following up with the fix.  It's in my notes now.


VB and the development of wizards / Re: Macro only runs in editor
« on: October 19, 2016, 09:30:18 PM »
As I understand it, the Sub Main() and End Sub are not needed.  When the macro is called it sees this as a subroutine and does not execute it as there is no call to run the subroutine.  Try taking those two statements out and see if that works for you.

Stephen "Highspeed" Kruse

SmoothStepper USB / Re: Stepper glitches fwd and rev
« on: October 18, 2016, 11:02:08 PM »
Sounds like a timing issue between the time the DIR line changes state and the time the first step pulse is sent.  Most stepper drivers require a minimum time  (5 micro-seconds on mine) from the time the DIR line changes before a step pulse can reliably be applied.  If the step pulse arrives too soon, the first pulse (or even two perhaps) will spin the motor in the wrong direction.  Since it is happening only when switching from forward to reverse, I'm guessing your system is probably using a low signal for the forward direction (active low) and a high for the reverse direction.  I say this because a system can often sense a low (ground/reference level) quicker than it can sense an applied voltage.

I'm not sure how to adjust this since my system is off-line at the moment, but perhaps someone else will chime in on what to change/set to adjust this timing.  But I'm pretty sure that is what is happening at the very least.

Stephen "Highspeed" Kruse

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