[jimcooptcam77]

i've got both machines running with the parameter set back to 0. No errors yet, but sometimes it takes a few hours. honestly, i'll be surprised if this works.....my longest program has a run time of 1hr....there are only two rapid moves in the whole program...start and finish...but that's the one that errors out the most. (i hear you that there are just strange problems with the parameter set to 1 though)

Machine definitely bangs around a lot harder with parameter set back to 0.

[jimcooptcam77]

Took about 1.5 hours, but the machine just errored out; same thing. 187 - B servo error too large.

[Haastec2]

Now change the following parameters back to Haas factory defaults:
Then cycle power.

Parameter 302 FEED ACCEL MEDIUM 6000000
Haas Factory-Set value: 12000000

Parameter 303 FEED T CONST MEDIUM 4
Haas Factory-Set value: 3

Parameter 314 FEED DELTA V MEDIUM 75
Haas Factory-Set value: 256

Parameter 750 FEED T CONST ROUGH 1
Haas Factory-Set value: 3

Parameter 752 FEED ACCEL FINISH 3750000
Haas Factory-Set value: 6000000

Parameter 753 FEED T CONST FINISH 4
Haas Factory-Set value: 3

Parameter 754 FEED DELTA V FINISH 75
Haas Factory-Set value: 128

[jimcooptcam77]

Appreciate very much your help on this, and understand where you are going. Are settings are set to "finish" right now. The values i have in there now:

Parameter 753 FEED T CONST FINISH 4
Parameter 754 FEED DELTA V FINISH 75

were pretty carefully selected after doing some fine tuning with a Haas rotary specialist who came out from Haas US a few months ago. Bottom line is that the factory settings were not giving us a good finish...or good accuracy given the type of machining we do. Anyway, we will try these settings and see if the errors are eliminated.

I can't say for sure, but i don't remember ever having this error before the latest mandatory software upgrade. We were glad for the upgrade as the rigid tapping bug was as scary as it gets.....but if it possibly is the new software that's causing this, i'd much prefer to have to tap holes manually. The strangest thing about these errors is that they seem to have started with the new software upgrade, but they have really increased in frequency over the time.

Thanks again, and i'll have to let you know tomorrow if this change worked. Let me know if anything else comes to mind.

[jimcooptcam77]

We ran with the finish parameters changed back to Haas factory defaults:

Haas Factory-Set value: 6000000

Haas Factory-Set value: 3

Haas Factory-Set value: 128

And we we are still getting the 187 B axis alarm.

[Haastec2]

I have asked my applications department to see if we can set up a VF3SS with a TR160 to see if we can duplicate this issue. Can I get the current software version on both machines & Mocon 1, 2.

Also can you post a fresh copy of the current parameters & settings for both machines.

Thank you,

[jimcooptcam77]

Both mills have Version 17.01 on Mocon 1 and 15.02 for Mocon 2. Parameters and settings to be posted shortly.

[jimcooptcam77]

Here's the settings and parameters.

[jimcooptcam77]

We we're told by our HFO that another customer was a similar alarm and it turned out to be a problem with the A-axis cable. After looking in the alarm history we did find that one machine had two B-cable alarms a week prior.

Has anyone experience similar problems with cables or know of a simple way to check cable integrity, swap A and B, or change the wires altogether? Can the wires be replaced without sending the trunion back to the factory? We have a TR160Y trunion.

[haastec]

We we're told by our HFO that another customer was a similar alarm and it turned out to be a problem with the A-axis cable. After looking in the alarm history we did find that one machine had two B-cable alarms a week prior.

Has anyone experience similar problems with cables or know of a simple way to check cable integrity, swap A and B, or change the wires altogether? Can the wires be replaced without sending the trunion back to the factory? We have a TR160Y trunion.

Make sure you are closely working with your HFO regarding any troubleshooting you are doing. Since these are in warranty I would hate to see you loose your coverage because you experimented on your own. Let the service tech experiment, then it will be covered.

[jimcooptcam77]

We will. At this point we see it as highly unlikely that this is a cable problem on both machines. We are doing some testing on various parameters on this end, but will be waiting to hear if you have found anything on your end.

[haastec]

We will. At this point we see it as highly unlikely that this is a cable problem on both machines. We are doing some testing on various parameters on this end, but will be waiting to hear if you have found anything on your end.

Just to clarify, you are waiting for Haastec2.

He is an imposter I tell ya! (flame2)

# 2, 2, 2, 2, 2, 2......

[jimcooptcam77]

1 or 2, we're just glad for the help! So how long does it take you guys to set up the test machine?

[Haastec2]

We started to test your program on our VF4SS 17.06C software with a TR160Y, is been about 20minutes into your program no alarms yet.

[jimcooptcam77]

Excellent. If it's anything like our machines, you won't see the error for 1-2 hours at least.

[jimcooptcam77]

Just realized you said VF4. I wouldn't think that makes a difference, but just want to confirm you know we are running VF3-SS machines.

[Haastec2]

We left it running last night and is still running with no problems.

Next step to get the dealer involved, I want them to do a few things.

1. Update both Mocons software to current release version 17.05
2. Inspect/Replace the B axis cable.

The power & encoder Molex connectors these connectors can have a bad connection and can cause this alarm.

They have to inspect the female crimp connector with a Magnifying glass to see if the crimp has spread apart from multiple connecting & disconnecting during the assembly process.

I will contact the dealer so they can schedule a service visit.

[jimcooptcam77]

Ok, thanks for the quick help! Can all these checks be down with the TR160Y left on our table? If you think we will need to pull them off and spend significant time doing these checks, i might need to look into getting replacements in...we are under pressure here from the customer.

[Haastec2]

They should be able to do it without removing the TR160Y from the table.

[jimcooptcam77]

By the way, why do the two Mocon boards have different software versions installed? How do Mocon1 and Mocon2 divide or share the processing? Could simply swapping the boards in the panel provide us with useful troubleshooting data?