I fit up 2 parts before the break. I welded one without comarc. It welded perfectly. Then I copied the program and edited it to use comarc. Kept all the same settings, arc files, weaves. Justed edited in comarc instead of weaves alone. The second part is junk.
When I welded the first part I took the current output of my welds and edited into the comarc u/d for the second. The l/r was 0 for all welds. The comarc is causing the torch to climb the wall. In some cases over 1/2 an inch. In others less but still enough to cause cold lap in the toe. Every weld as well. Not just a few.
We have motoman returning on the 6th with a new comarc. I’m not sure if it’s the comarc or interference but there is something definitely wrong and my money is on the hardware. We were having issues before with it doing some strange things. In some instances during dry walk through, the robot would jump and trigger a stop. Very odd behaviour. Motoman came and looked at it. Said they had never seen this kind of behaviour before. They ended up dumbing down the sensitivity of the comarc and changing up the my weave frequencies. Some of my frequencies were too high for the weaves I had setup but I wasn’t using those weaves for any of the welds that were suffering from this jump issues but it was something motoman seen and criticize.
It stopped the jumping but I’m starting to think the two issues might have been related. We shall see. I know it’s easy to say it’s a process issue ( put it on the customer) but when you see behaviour that just isn’t normal and your tech guys haven’t seen it before and you have to send backups to Japan to get analyzed, maybe you should consider its more then just a setting and it’s possible it could be hardware. It blows my mind that they would think that dumbing down the sensitivity to correct an issue they’ve never seen before was the way to correct the issue. It doesn’t explain the root cause and that’s what they needed to address. Not just find a settings fix that masked the original issue.
