Messages

21

Mach4 General Discussion / Re: The great screen debate

« on: August 24, 2015, 08:59:36 AM »

The problem with having the cycle start button run both G-code and the MDI is that the MDI does not clear after execution.

Therefor, if the operator does not remember to clear the MDI, it will execute again when Cycle Start is pressed.

The multi-line MDI is probably my favorite new 'screen feature' and it would not be nearly as useful if it had to be cleared each time you want to run G-code, especially if it contains a multi-line routine that is run before or after the G-code.

If semantics are the issue, then the buttons could be renamed "G-Code Run" and MDI Execute" or something similar. This way, whatever pre-conceived notions there may be about what "Cycle Start' should do are moot.

In addition to the above arguments, there is the issue of multiple MDI entry points and multiple 'Cycle Start' buttons. How many of each should there be? What would the correct interaction be between them? Should Cycle start check all of the mdi? What if there are different commands in mdi1 and mdi2?

22

HiCON Motion Controller / Re: HiCON Integra - MACH4 - Servo Spindle - Assigns spindle as slave

« on: August 23, 2015, 09:40:17 PM »

Spoke too soon.

Newest firmware and plugin from 08/21

Servo motor assigned as spindle. Mach4 starts fine and MACH config mapping shows 4 axis motors and one spindle motor

Run any G-code

Rechech mach config - mapping now shows motor4 slaved to axis 0 (X axis)

23

HiCON Motion Controller / Easy questions on continuous rotation axis

« on: August 22, 2015, 02:45:49 PM »

HiCON Integra

Documentation states that any axis can be set up to spin while retaining normal operation as well.

Two questions that the documentation is not clear on:

1) can this be done with more than one axis at a time?

2) What is the G-Code axis identifier for the Spindle axis?   i.e. doc shows (something like) "S200M3" and "G1A30"  What axis letter is the Spindle in G-code?

Note: I could experiment with this and perhaps stumble on an answer, but I would like to know that I am doing it the correct way and not just by luck.

Thanks!

24

HiCON Motion Controller / Re: HiCON Integra - MACH4 - Servo Spindle - Assigns spindle as slave

« on: August 22, 2015, 02:39:04 PM »

Update:

Mach4 V2 2630 exhibited no movement at all. No jog, no MDI and would not run G-code

Mach4 V2 2651:

Jogging is working

MDI is working

G-code is running (better than ever - not hanging on spindle codes and so on)

The BONUS plan:

'M' codes for spindle codes seem to be working now.

The arbitrary re-assignment of servo spindle motor to slave on axis 0 is not happening in bench testing. I have not put this new setup on an actual machine with encoder feedback from the spindle motor.

If any of this changes, I will post another update.

25

Mach4 General Discussion / Re: Mach4 Macros to enable outputs in an order

« on: August 22, 2015, 10:19:29 AM »

Since you are a student, I will offer some general guidelines that you might consider in all of your scripting.

What I see that is of concern in your scripting is the use of long delays. This method can cause problems ranging from inconvenient to disastrous.

There are facilities in MACH4 where you can define whether the action should complete or not before the CNC controls continue, but making the CNC wait on your script may solve a timing problem with your script, but cause problems wherever the CNC control's attention has been diverted from.

If you have tasks that require waiting on some action to occur, it is a better practice, in my opinion, to set up a counter and let the program pass thru rather then stop and wait. In this way, the system is not starved for what may be critically important attention.

In practical terms, with MACH4, I would put your script in the PLC and set up a counter  . . .  here is a verbose example:

Instead of

Do something
Wait some amount of time <- this is potentially a problem maker
Do the next thing I want in this script

Do something
Increment a counter
Has the counter reached 1000?
No: go on your merry way and do other important stuff
Yes: Do the next thing I want in this script

Functionally, there two methods result in the same action, however in the second method, the system continues to run and cycle thru all of the other scripts.

.25 seconds is a long time, but even if you have short delays, if they are sequential, they will 'stack' and you might end up with a very long period. By looping thru, you can have literally hundreds of scripts running and not 'pause' the system in a significant way.

There are better ways to scan for state changes, but trading in the delays for counters is the biggest step in the right direction.

26

HiCON Motion Controller / HiCON Integra - MACH4 - Servo Spindle - Assigns spindle as slave

« on: August 22, 2015, 09:20:01 AM »

HiCON Integra, new with latest (2.72) firmware. Mach4 2580 (Plug-in Target) Latest Plug-in 1.08.13b



Configuration: All step/dir source is MACHxx

Motors 0 the 3 assigned to X,Y,Z,A   No encoder feedback

motor 4 assigned to spindle  -  encoder feedback on 4

Problem: Motor 4 gets randomly assigned as a slave to the 'X' axis. Attempting to delete it results in a wxLUA error referencing trying to delete an 'inexistent device' (or something to that effect).

Running the spindle results in what I assume to be a Plug-In error message (the source is not identified in the message) that states Motor 4 is disabled due to following error.

After this error, a check of the HiCON diagnostic shows 0 feedback and StepGen and very high (as would be expected) Command Pos and matching Following Error

Checking the MACH4 config after this message invariable shows Motor4 assigned as a slave on the 'X' axis. Motor4 is still shown as the spindle motor.

27

Mach4 General Discussion / Re: MACH4 - Modbus

« on: August 10, 2015, 07:43:24 AM »

FYI, I was having the same issue with very high processor usage . . . Joe

The slammed processor issue was only with MACH3 and had to do with the way it polls Modbus. Changing the Ethernet port (which is probably built into your MB) most likely is what solved the problem. A new/different driver may have also solved the problem as well as an ad-in NIC.

Modbus can 'respond' or 'loop' and in latter case, changing the loop frequency can solve the problem.

28

Mach4 General Discussion / Re: MACH4 - Modbus

« on: August 10, 2015, 07:37:05 AM »

The function type and register 'name' are not related.

The register 'prefix' is a starting point for your register names.

Mach4 uses that prefix to pre-populate the register names only as a convenience. You are then free to go back and edit these names as well as ass ancillary descriptions in a separate field is desired to help identify the register or put notes on what the register controls or where the data comes from or any other information that may save your butt a year down the road when you are trying to do some improvements or maintenance on the system.

The Register 'name' is important because that is what MACH4 uses to access the register.  If you have used Modbus in other applications and had to use only register numbers with a separate 'cheat sheet' to know what is in each register, you will love this feature of MACH4.

I have attached a screen grab of a section of one of my MACH4 Modbus Diagnostics. NOte that to access these registers in MACH you would use the actual name ex.

"modbus0/Encoder_Inturn_Switch"

Note also that on that register, I have added in the 'description' info on the source of the data (InTurn_Bit_OUT34-15) which identifies the var name and the pack bit number at the source.

In this particular application, there are about 40 registers, 3 of which are bit packed inputs and two are bit packed outputs.  loop time on this averages about 20ms.

3 words to describe MACH TCP Modbus:

Convenient

Stable

FAST . . .  no make that Wicked fast!

29

CS-Lab / Re: CMPIO/IP-S with MACH4 - new plug-in released - Servo Spindle still broken?

« on: August 07, 2015, 08:05:55 AM »

Another tid-bit, this time regarding the product return. Apparently it was my fault for not reading available information prior to purchase.

The previous communication from CS Labs stated that there is NO documentation on MACH4, their site says nothing except that the plug in is available, there is nothing in their FAQ about mMACH4 at all. Newfangled simply lists it among the other "great motion control boards" specifically for MACH4.

The 'Don't use this with MACH4' warning is part of the post sales support . . . I suppose.



to Automationtech., me

Dear sir,

I think your customer didn't read information about Mach4 as well as about CSMIO plugin for Mach4 before he bought the products.

Please inform if you want to return the product or keep it for further sale after you verify it's ok.

For us it's not a problem. It's our second return ever.
 

Best regards,

Aneta Rapacka Zachara

Marketing&Sales Manager

 
CS-Lab s.c. Poland

J.Wawak, A. Rogozynski, S. Paprocki

30

CS-Lab / Re: CMPIO/IP-S with MACH4 - new plug-in released - Servo Spindle still broken?

« on: August 07, 2015, 07:40:35 AM »

Their last plug-in was a couple of weeks ago.  I made work arounds for the main problem with the previous plug-in, but they don't work with the new plug-in and I am not inclined to spend time making another work around.

I could move forward with the earlier plug-in that I patched, but I don't care for CS Lab's attitude frankly. Imagining trying to get help from them down the road once I have these things installed in customer's machines is just not palatable, so I'm bailing now before I get any deeper into it.

While I wait to hear if Automation Technologies will take it back and refund, I have the thing listed here in the bargain basement. Great deal for anyone using MACH3 or who doesn't mind using a patched up plug-in for MACH4 while waiting however long for CS Labs to come around.