Millport VMC1660 Centroid Upgrade (Leadshine EL7)

[KreiderMachine]

Looks like our TT1 isn't set up like the tt1b. We have a single contact going from pin 5, and a jumper from pins 3-7 in the connector. It triggers the mechanical input pin (input 19), but I can't seem to get the auto probe sequence to work.

Upon further investigation, it looks like it needs to see gnd at pin 4 in order to work. I'll try adding a solder bridge between pins 3 and 4 inside the plug shell.

Upon further further investigation, it looks like the older wiring harness (if which I re-used the final 3ft) doesn't use pin 4, hence the problem. Will fix this Friday.

[cncsnw]

You should have been able to just set P257 = 0, to tell CNC12 that there is no "detect" signal available for the tool setter.

However, wiring a jumper to pin 4 in the plug, so that INP772 is closed when the TT1 is plugged in, is a better solution in any case.

[centroid467]

I haven't done anything in the PID Menu other than the initial tune which outputs 'delay' values for each axis.

Is there anything further I should do here, or is that all handled in the Motion Studio setup process for the EL7's?

I also have the initial 'system test not run' message showing. Best to just disable this?

-H

You should do the PID menu delay autotune again after tuning the EL7 drives but that is about it. With the Leadshine drives, we did not manage to find an easy way to refine the autotuning results. The autotune results were satisfactory in the first place though.


I do not know what the state of the system test is for Hickory. We were intending to fix it or remove it for Hickory. I would defeat it or ignore for now.

[KreiderMachine]

This mill was handed back over to its primary operator this past week. Pending a few minor finishing touches and the customization of the wiring schematic to match this build more exactly, this project is complete.

Thank you SO much to each of you who provided support and feedback to me throughout this process. I'm sure you each run out of patience with us 'DIY' types at least once per day when coaching us through these builds, but please know that we are very grateful for the extra effort you put in, and to the company as a whole for offering products like these to the world. Genuine respect for and trust of your customers is a rare and valuable thing that pays dividends far beyond Centroid's basic business model.

[KreiderMachine]

We have noticed that there is an extremely high pitched noise, which I believe to be coming from the x-axis servo, most of the time it is active. The noise stutters when x-axis moves, and disappears when e-stop is tripped.

Any insight on this? I will begin comparing settings in motion studio between x and y/z axes as a start.

[KreiderMachine]

Do I need to do the ATC initialization every time the machine is used?

In the past, we only did this after a crash, but carousel position information was stored from session to session.
This does not appear to be the case after the upgrade.

In the process of investigating this just now, we power cycled the system after going through some successful tool changes, (normal shut-down procedures) and when we entered into CNC12 after rebooting, it gave a "possible ATC fault" error, recognizing that the carousel was in position 9, but thinking that it still had the previous tool (tool #3) in the spindle.

[centroid467]

You shouldn't need to initialize the ATC every time you start it up...

Can you post a fresh report?

[KreiderMachine]

I've been playing around with the m6 macro, and other than unnecessarily commenting out the sections that do not apply to our setup, haven't left any changes that affect the function of it. Original files are saved.

[KreiderMachine]

Sometimes the toolchange works, sometimes it crashes. We'll have to watch it awhile longer and see if we can identify a common failure condition.