Version 4.14 - Issues to Report, Please post them here

[swissi]

Yes, I tested this out thoroughly in 4.12 before doing the update to double check it was working, as Keith warned that existing macros might not work with 4.14. Auto range selection was working fine in 4.12. After the update, I copied the M3 macro across and that killed it every time.

Would be nice to get the auto range selection working again but it's not something I expect to need much. However, you probably want to understand how a macro is able to kill the program so finally in the middle of a program.

Looking into it Muzzer

please find the edited version of the custom "muzzer" M3 that works with v4.14
mfunc3_414.mac

One change I would suggest is skipping all this code when you are graphing or searching. This is the current first line of code:

Code: Select all

IF #4202 || #4201 THEN GOTO 200

It will jump just to N200 and will go through all the rest of the code from there. I suggest to add a N6000 at the end and jump to 6000 instead of 200 like this:

Code: Select all

;-------
;M3 macro - Spindle CW
; Displays message to select auto spindle mode if it is not set
; See 13-8 M94/M95 Output On/Off etc
;-------
IF #4202 || #4201 THEN GOTO 6000
.
.
N5000                               ; In correct range and gears engaged now
M95 /62                             ; check de-energise HIGH solenoid
M95 /61                             ; check de-energise LOW solenoid
M94 /1                              ; spindle enable CW
N6000

-swissi

[martyscncgarage]

Marty - you asked me to post the report for the 4.14 install that was crashing with my M3 macro. I've attached it here and checked that it had my modified M3 macro. As I said, it killed the CNC12 program totally and dumped me back on the desktop when trying to start the spindle initially in low range but with a high set speed, which would require the macro to change back to high ratio. Replacing it with the default M3 macro has my 4.14 installation running sweet.

report_38D269594F9C-0110180512_2019-03-22_15-05-54.zip

Murray

So I understand this issue is resolved.
In your custom M3 macro, your were calling an M3, which put CNC12 V4.14 in a loop and forced 4.14 to exit, rather than calling the output to turn on the spindle and the appropriate time with in the custom M3 macro.

Why it it seemed to work in 4.12 is anyone's guess.
When a user creates their custom Macro, they need to use proper format.

If you need a custom Macro and are unsure how to proceed, perhaps create a new post on what you are trying to accomplish and the collective group can try and help.

Macros and PLC programming are not my personal forte' but there are plenty of other users that can chime in, including Centroid support when they have time.

Thanks Murray for posting your experience. Perhaps it will help improve the software. These sorts of experiences help us l learn from each other, and understand more what the software is capable of.

Marty

[TheKitMill]

Just upgraded the new version all appears to have loaded correctly, loaded my machine data but I lost the Pro version I had. It now shows that I only have free version. Is there an additional step I need to take to restore proper version

Thanks

[Gary Campbell]

Yes, you need to import the pro license just like you did the first time.

[martyscncgarage]

Just upgraded the new version all appears to have loaded correctly, loaded my machine data but I lost the Pro version I had. It now shows that I only have free version. Is there an additional step I need to take to restore proper version

Thanks

Import the license.dat file in the CNCM/T directory you made a copy of before you did the new 4.14 install. Otherwise locate the original license file they sent you

[Muzzer]

Yes, I tested this out thoroughly in 4.12 before doing the update to double check it was working, as Keith warned that existing macros might not work with 4.14. Auto range selection was working fine in 4.12. After the update, I copied the M3 macro across and that killed it every time.

Would be nice to get the auto range selection working again but it's not something I expect to need much. However, you probably want to understand how a macro is able to kill the program so finally in the middle of a program.

Looking into it Muzzer

please find the edited version of the custom "muzzer" M3 that works with v4.14
mfunc3_414.mac

Wow - thanks Keith! I didn't notice this until just now. I'll test it out when I get a chance and let you know how I get on....

[mlegary]

I came across an issue with the wizard on initial install where the relay board was not able to be controlled until customization of the outputs was made. It appears that if you leave the default outputs as is on initial install via the wizard that the relays may not operate.

After a brief bench test after receiving the unit, I wired my Leadshine drivers and a generic VFD to the Acorn.
I selected the Leadshine option and left the relay outputs default / as recommended, but changed other settings (axis related).

When I tried to control my VFD, the relays would not activate. After some time of triple checking my wiring, I finally decided to change one of the relay assignments (relay 8) to try manual commands to continue troubleshooting. I made the change in the wizard and save the settings. Once I saved the modified relay outputs the Acorn started to function as expected.

[martyscncgarage]

I came across an issue with the wizard on initial install where the relay board was not able to be controlled until customization of the outputs was made. It appears that if you leave the default outputs as is on initial install via the wizard that the relays may not operate.

After a brief bench test after receiving the unit, I wired my Leadshine drivers and a generic VFD to the Acorn.
I selected the Leadshine option and left the relay outputs default / as recommended, but changed other settings (axis related).

When I tried to control my VFD, the relays would not activate. After some time of triple checking my wiring, I finally decided to change one of the relay assignments (relay 8) to try manual commands to continue troubleshooting. I made the change in the wizard and save the settings. Once I saved the modified relay outputs the Acorn started to function as expected.

Thanks for reporting. Centroid is aware and hoping to release a software update that corrects this later this month.

[KD5FZX]

cnckeith.

I found a small mostly cosmetic but confusing issue in conversational frame function. It might have been reported before but here it is anyway.
If you change a frame to plunge straight down, then the plunge angle will be grayed out as expected, but if you save it and then open it again then it will show straight plunge AND plunge angle active.

[cncsnw]

On March 26th, Marty wrote:

So I understand this issue is resolved.
In your custom M3 macro, your were calling an M3, which put CNC12 V4.14 in a loop and forced 4.14 to exit, rather than calling the output to turn on the spindle and the appropriate time with in the custom M3 macro.

Why it it seemed to work in 4.12 is anyone's guess.

The intended design (at least in all past versions of CNC7, CNC10 and CNC11, as far as I know) is that if you call the same M function from within an M function macro, you get the default (built-in) action.

This should be the result any time there is M function recursion, whether it is direct or indirect. For example, if your mfunc3.mac calls M41, and your mfunc41.mac calls M3, then the latter should result in the default M3 action, rather than a recursive call to the first macro.

If this has stopped working as intended in CNC12 v4.14, then that is a bug that needs to be fixed.