Messages

1041

General Mach Discussion / Re: Mach3 Customization/Macro Programming Documentation

« on: August 23, 2009, 12:51:08 PM »

simpson36:

   I understand your point, but understand mine, I was NOT critizing the author, he asked for comments I gave him mine. In my OPION (and we all know the saying), most users here are machine hobbiest. Who dont know VB scripting (the cypress version). All I was saying was make if for people who dont know anything. Perhaps you came to this site, and already knew programming. When I came here, I did not and had to learn, it was a tough climb using the "manuals". 

Further I and VMax (Terry), are not slamming anyone here or arguing over that one specific word that was just an example.  I just didnt want New people to mach3, and we where ALL new at one time. 

Ray: Thank you for what you are doing, since my comments are not appreciated, I will bow out of this thread. Look forward to your completed work!

Let me ask, would you also consider an "functional Grouping" format, i.e.  Modbus functions, Output functions, Input functions, G Code functions, Wizard functions, etc.  and put code that relates to that typ of operation(s).  If I am a new person, I would only know I want to turn on an output for instance, I would not know it is called ActivateSignal, I could look under the function groups and find quickly what I am looking for.

scott

Scott,

Functions and variables are already listed both alphabetically (along with their long descriptions) and by function (with short descriptions), so it will be very easy to find the function you need, if it exists.  Many names are also being changed, to make them more clear.  For example, *all* Modbus functions will have bames now starting with "Mod".  All spindle control functions have names starting with "Spindle", etc.  Where there are functions to write and read variables, they will be named identically, except for "Set" and "Get" prefixes.  So, rather than the current SetFeedRate() and FeedRate(), we'll have SetFeedRate() and GetFeedRate().  Many old/obsolete/redundant functions are being deleted.  OEM codes will all have pre-defined symbolic names, making their function clear.  We're looking at adding named macros, and shared variable space as well.  Scripts will be able to "include" other files, so common definitions can be shared without cutting and pasting the same code into multiple macro files.  (Take a look at my probing macros - This change alone would reduce the lines of code by almost 90%)  Existing scripts will still run, in a new "legacy" mode that understands the "old ways", but there will be so many improvements in the "new way", and the code will be so much more readable, that people should WANT to use it for all new code.

Regards,
Ray L.

1042

General Mach Discussion / Re: Smooth Stepper reset

« on: August 23, 2009, 11:58:47 AM »

Jeff,

Thanks for your comments.  It seems that you & I are living parrallel lives regarding the SS. 

I have experienced all of the USB noise related problems that you mention. 

Currently I am having a problem with my spindle motor triggeriing a reset.  Noise filters in the plug in are ineffective.  I'm going to check out the line filter you mentioned but, sometimes it's pretty hard to route the USB cable in the manner in which you describe.  Enclosure size/configuration can make it a real challenge to kick this USB noise thing. 

That being said is is possible to design/build/modify a USB calble that has some sheilding (I don't think USB cables have any??).  Perhaps this might be the 'Silver Bullet'?

Sid

P.S.  Do you guys think we should move this topic over to the SS forum/section???

Where do you guys have your SS mounted?  I used to have mine mounted *inside* the PC case, and it worked perfectly in there, in two different PCs.  I now have it mounted inside my E-box, which contains *everything* - PC, servo power supplies, VFD, relays, and lots of other stuff.  And the SS is within inches of the servo motor wiring.  It works absolutely perfectly in there.  If you're seeing flaky SS operation, you must have something in your system that is radiating some serious noise.  You should find that, and fix it at the source, and your whole system will probably behave better.  It is very important to have your grounding right.  I think this is an area many people don't understand, and don't handle correctly, ending up with shields that carry signals or noise, ground loops, and other things that can cause very erratic behavior.

Regards,
Ray L.

1043

General Mach Discussion / Re: Smooth Stepper reset

« on: August 23, 2009, 11:53:52 AM »

Hi Jeff,

Is all that info that you just mentioned included in the smoothstepper instructions or something like that something "everyone" should already know?

I would think if noise was enough to stop the unit, there would be some sort of filter built into the line itself on the smoothstepper? Kind of like how they used the filter on a PC monitor cable?

Thanks,
Dave

Dave,

USB 2.0 runs at a 480MBit/sec data rate.  Any "filter" to remove external noise would also remove the signal.  Interfaces like USB simply can't work in noisy environments.  So, you have to fix the noise at the source.  Of course, that's *always* the best way to deal with noise problems anyway.

Regards,
Ray L.

1044

General Mach Discussion / Re: Need HELP Steppers Stalling on Shallow Moves

« on: August 22, 2009, 11:00:46 PM »

OK, ever since I converted my Bridgeport to CNC the X and Y axis lock up when trying to make shallow moves at the same time. So let's say when trying to go from Y0.2 X0.1 to Y8 X.2. I think it's because the machine is trying to move that shallow sliver of a move of X over such a long distance. I noticed it during drilling cycles originally. And before you ask I've tried everything slowing down the motor in motor turning and changing the accerlation down. The motors are more than strong enough 1200 oz. steppers at 150 IPM it can pull me across the floor without missing a step, but even then I tuned them down to 70 IPM as my top speed and of course it still happens.

Some things I noticed months and months ago when trouble shooting it, I readjusted my Y gibs, they were a little loose. I eneded up just forgetting about it and just altering my Gcode to make each move separately until it gets to where it's going. Instead of X2Y2 on one line I would say X2, [new line] Y2, just to be safe. The weird parts is I use this mill all the time doing very complex 3 and 4 axis stuff and it never messes up until I get to shallow moves on a drill cycle; that is until yesterday I was doing some pocketing where there were some extremely shallow moves and it messed up, luckily I was there to Feed Hold and resetup.

Any help would be appreciated. I'm just worried that it's going to mess up somthing real important.

"...the X and Y axis lock up..." - What does that mean.  You mean neither axis moves?  Or only one moves?  Or one axis may, or may not move the correct distance?

Regards,
Ray L.

1045

General Mach Discussion / Re: Smooth Stepper reset

« on: August 22, 2009, 10:55:16 PM »

I have wondered about this also.  When communication is lost to SS a disconnect and restart is required.

The SS does have connectors on board for a reset switch, but as far as I can tell they have no effect.

Unplugging the USB cable is the only thing that works for me to reset the SS.  That is why it is still on the shelf.

Greg

Greg,

How many computer peripherals do you have that you can just reset on-the-fly?  Any USB device will require a re-connect to re-boot it....  Besides, I've had to do that perhaps 3 times in the last year.

Regards,
Ray L.

1046

General Mach Discussion / Re: Smooth Stepper reset

« on: August 22, 2009, 04:21:24 PM »

I've been running a SmoothStepper for almost a year, and no such problems.  It has, perhaps twice, gone out to lunch due to a buffer under-run, but exiting Mach, dis-connecting and re-connecting the USB cable, then re-starting Mach got it going again.  And I believe that problem will be fixed in the new Plug-In Greg is working on.

Regards,
Ray L.

1047

General Mach Discussion / Re: Spindle Control

« on: August 20, 2009, 11:30:14 PM »

i believe that Jack (Minitech) has already got this nailed on my behalf.. using a

C19 from CNC4PC

not sure what that is but if jack says its good I believe him..

Thanks Jack!


Will still send info though as i am interested in seeing how this is done.

I hope it works better than the speed controls on the several C10 boards I've had. They have proven to be quite inaccurate and unreliable.  The Homann board works flawlessly, and very accurately.

Regards,
Ray L.

1048

General Mach Discussion / Re: Spindle Control

« on: August 20, 2009, 06:38:24 PM »

Go to HomannDesigns (www.homanndesigns.com) and take a look at their DC-03 spindle control I/F.  It works beautifully, assuming your spindle control has a voltage-controlled speed.  The DC03 provides two relays you can use as you like (usually FWD/REV or RUN/DIR), accepts PWM input from Mach, and provides a voltage output to the motor controller.  It is simple to connect, provides very accurate speed control, and is dirt cheap.

Regards,
Ray L.

1049

General Mach Discussion / Re: Changed My lead screws from acme to ball screws

« on: August 19, 2009, 10:41:45 PM »

Changes are not saved until you exit Mach3.  If you're shutting down without exiting Mach, it won't get saved.  Also, make sure your XML is not read-only.

Regards,
Ray L.

1050

General Mach Discussion / Re: Mach3 Customization/Macro Programming Documentation

« on: August 18, 2009, 10:42:35 PM »

"Assert an output signal". Why not just say "activate an output signal, or send an output signal. Seems to me that "Assert" will confuse the hell out of people. I've been writing VB code for many years, and when I first saw "Assert", I had to read through the description to make sure I knew what you were saying. Very confusing imo.

Gerry,

When defining the behavior of a piece of hardware of software, "assert" has a very definite meaning: it makes it clear that the output will be driven to its active state.  With a Mach3 output, this might mean it's driven to a logic high, or driven to a logic low, depending on how that output is defined in Ports&Pins.  But, whatever its active state, it will be driven to that state.  Assert has a very definite and unambiguous meaning, and is a term commonly used in technical literature, such as chip data sheets, to define such things.  If I read something was "activated" or "sent", I would not know what that meant, as those terms are quite ambiguous.  There may be a few new terms you'll need to learn to read this document, but once you do, you'll never have any doubts as to what a function does, once you've read its description.

Regards,
Ray L.