Messages

1261

Mach4 General Discussion / Re: Current tool ==

« on: January 16, 2021, 05:03:06 PM »

Hi,
the Lua script tests, or rather asks the question, 'What tool is in the spindle right now? If it is the same as the new tool
requested....then Mach does not have to do anything'

There are two interpretations about tool numbers in Mach4.

1) Tool number is required tool.
  For example:
 M6 T14
 requires that tool number 14 be fitted to the spindle.

2) Tool number is the next required tool.
  For example:
  M6 T14
 will put the new tool in the spindle but load tool 14 into the toolchanger.

This last example may seem strange but is common on production machines. A production machine may have a carousel of 20 or more tools,
and  one more tool is loaded into the toolchanger. In order to speed the toolchange you want the required tool already in the toolchanger
already.  Thus the instruction is that tool 14 be shifted from the carousel into the toolchanger ready for the next M6 and therefore the speediest
of toolchanges.

Craig

1262

Mach3 under Vista / Re: New setup for USB board by BSMCEO4U-PP Bitsensor

« on: January 15, 2021, 10:59:07 PM »

Hi,

The switch inputs IN1 to IN4 are passed directly to Mach3, and then handed back to the controller as needed

Incorrect, the index signal must be processed immediately. If Mach 'hands it back' the instructions have to propagate through the
motion buffer, hundreds of milliseconds delay........way WAY too slow to synchronize threading.

There was  very extensive discussions about this on the forum 10 years or so ago when external motion controller manufacturers were
trying to get their devices to support single point lathe threading.

Craig

1263

Mach3 under Vista / Re: New setup for USB board by BSMCEO4U-PP Bitsensor

« on: January 15, 2021, 12:36:17 PM »

Hi,
single point lathe threading is a process that is enacted by a realtime motion controller.

The spindle index signal not only provides a pulse for the controller to work out the spindle speed, which
is in turn displayed by Mach, but it needs it to synchronize the z axis so repeated cuts of the same thread
are in the same 'groove'.

Mach alone cannot do that. The communication delay between the index signal (as presented to the controller)
and Mach receiving it will be several milliseconds at least. Mach would then have to decide when to move
the Z axis and communicate that back to the controller, another several milliseconds of delay, and that command
has to propagate through the motion buffer, maybe several hundred milliseconds more delay. The combined delay
means that all synchronization is lost.

Mach's original motion controller was the parallel port, and the parallel port driver was and is a very clever attempt
to have a Windows PC (a non realtime computing system) enact a realtime controller. Not withstanding its quirks
and limitations it does pretty well, to whit it makes a fair job of single point lathe threading. That means that the
parallel port could receive an index pulse and the port driver could calculate the exact instant that Z axis movement
need to commense and issue the pulses to the Z axis driver at that instant. It didn't have to refer to Mach, like
the 'general manager upstairs'........it could do it immediately, or realtime.

If instead of using Machs parallel port driver (as motion controller) you use an external motion controller, and in this
thread, the RnR/Bitsensor board it is the external board that must synchronize the cutting, and to my knowledge
the RnR/Bitsensor board does not have that capacity.

Craig

1264

Mach3 under Vista / Re: New setup for USB board by BSMCEO4U-PP Bitsensor

« on: January 13, 2021, 01:11:32 PM »

Hi,

I personally don't plan to go to Mach4, but anyone willing to document their frustrations in setting it up, will be welcome to send me the procedure for publishing.

I've been using Mach4 for six years, and yes there is a learning curve to set it up but thereafter it is light years ahead of Mach3.
This thread lists some of the many improvements:

https://www.machsupport.com/forum/index.php?topic=42891.0

Craig

1265

Mach3 under Vista / Re: New setup for USB board by BSMCEO4U-PP Bitsensor

« on: January 13, 2021, 01:05:44 PM »

Hi,

As far as I know, the Bitsensor board is compatible with Mach4. It just doesn't have a manual for saying how.

Incorrect, it does not have a Mach4 plugin.

Craig

1266

Mach4 General Discussion / Re: Nooby in need of help!

« on: January 13, 2021, 12:34:30 PM »

Hi Steve,
the  PMDX-424 sounds like a fair choice, does it support hardware THC controllers?

Craig

1267

Mach3 under Vista / Re: Mach 3 bluescreen

« on: January 13, 2021, 04:39:25 AM »

Hi,
have you read the thread about Windows 10 updates screwing up Mach3? There is a fix but there was a time when an MS
Windows 10 updates stopped Mach3 from running.

I haven't really followed it as I haven't used Mach3 in six years and Mach4 works seamlessly with updates.

Craig

1268

Mach4 General Discussion / Re: Nooby in need of help!

« on: January 13, 2021, 04:33:47 AM »

Hi,
if you are trying to make a plasma then I think you may struggle with the UC100. It is USB connected and very prone
to electrical interference. Keep the USB cable as short as possible.

The UC100 does not support any hardware THC controller.

Ethernet connected controllers are much better for plasma tables. The Ethernet SmoothStepper is Ethernet connected but in addition
supports the TMC3in1 hardware THC controller.

At tis time I believe the Ethernet SmoothStepper and the Hicon Integra are the only Mach4 ready controllers that support high
dynamic range hardware THC controllers. In absence of hardware THC support you'll have to rely on the Mach4 THC script solution,
albeit at much less dynamic range. Even there your UC100 will struggle as it has no analogue input with which to monitor the arc voltage.

Craig

1269

Mach4 General Discussion / Re: Nooby in need of help!

« on: January 13, 2021, 04:23:04 AM »

Hi,
you can't really use SoftLimits without Homing your machine first, and by that I mean Homing to some defined and repeatable position,
which means you can't HomeInPLace.

When you have HomeInPlace enabled for an axis the moment the axis is homed it just sets the machine coordinates to zero (or the offset if you
have programmed it) right where it is. Therefore your SoftLimits for that axis are meaningless. SoftMin and SoftMax are distances to the
the axis limits from the Home position.

Lets say today you Home your axis, using the HomeInPlace facility, with the axis exactly halfway. Your SoftMax and SoftMin would then be +nnn inches
and -nnn inches say.

Tomorrow you turnd the machine on and Homed in place but this time the axis is near to one end. With the same SoftMax and SoftMin from yesterday the
machine will happily sail off the end of travel in one direction and fail ExceedSoftLimit in the other.

SoftLimits work only if you Home your machine to exactly the same place every time. Other than that you just have to turn SoftLimits off altogether.

Craig

1270

Mach3 under Vista / Re: Mach 3 bluescreen

« on: January 13, 2021, 04:07:01 AM »

Hi,

but i also got bluescreens with a laptop with a parallel port,

Machs parallel port will not run reliably on laptops at the best of times. The fact that you are using a parallel port suggests you must have
32 bit Windows 7 or earlier installed as OS....why?

A UC100 is an external motion controller and allows you to escape the necessity of 32 bit Windows 7 or earlier.
Why don't you get yourself a nice little Windows 10 laptop and run Mach3 and the UC100 on that?

Craig