How do they compare to ABB for welding application?
What's their support like in North America?
Posts by Capin
-
-
Still looking for feedback on Cloos robots...
-
You should start with offline simulations focus on cycle times robot vs. human then you can do the math to figure ROI, hourly rate etc....
Your integrator will help with this. -
The easiest way to resolve that is to load your other part modules into the controller when you are creating a new module or routine the software will prevent any commands from becoming ambiguous.
Hopefully you don't have hundreds of part modules? -
-
ABB 440L, IRC5 controller how do I adjust the nozzle voltage? currently only showing 17v I don't use the wire for searching but it reads 24v a few years back a tech raised the nozzle voltage to 49v but lately I have been getting can not locate part errors when searching with nozzle.
-
Anyone familiar with this integrator Cloos or Qirox robot if so what are it's advantages/disadvantages as compared to Fanuc or ABB for welding application?
-
One of our robots is using a Lincoln 655 with a R22 feeder been running 3 shifts for 9 years now zero problems!
-
We have a 2400 on an S4 controller it's not being used, the robot is in great shape the controller not so great. I would like to change it to IRC5 could you guys give me an idea of what it cost?
-
Guys what's the yearly fee for license renewal on Robot Studio
We have an older version 5.12 hasn't been used in years I would like to get it going again & upgrade to 6.03
-
Wolf is our integrator, I have our part modules backed up its the entire HD with OS that I'm concerned about on both the cell controller and main. I need some type of system imaging would prefer to back up to an external HD
-
We have an ABB 4400L with an IRC5 controller and a 2 station IRB 750K positioner for welding, a while back the HD in our cell controller died no problem we got a new cell controller and upgraded our system in the process.
Problem: we have over 100 parts we weld on this machine so putting those old modules back into a new system is as most of you know time consuming.
I realize if we had redundancy we would still be running under an old system but it was working great, however the new system with Windows 7 & Robotware 5.15 is better.
I'm surprised there is no redundancy built into these machines? Like the hard drives in a mirrored raid array so if one fails the other takes over.
I have to figure out a way to compensate for a computer component failure.
Would a couple external USB HD's be the answer?
The motherboards in the cell controller & Main are low end and I doubt they offer any protection which I find strange? -
Enable to FALSE
no random nonsense yet!
-
-
Here's a pic from the pendant, is there something we could change here to stop the random TorchClean;
Like Enabled to FALSE?
I don't want to totally disable the TorchClean: I have it at the end of each weld module we weld parts that take about 15minn ea and we will do sometimes 40 per day.
But here's a question if I did comment it out in service routines would I be able to run it from the cell controller? I don't necessarily need to run TorchClean after every part I could run 2 or 3 pieces then do TorchClean from the cell controller, but requardless its this random TorchClean that I need to stop! -
I'm gonna bump this hoping someone can help, still having this issue?
-
Thanks Yolo
But I'm not seeing a problem?
I think its going to take an experienced programmer to find it?
-
Here is a recent backup I looked in RAPID/TASK1/PROGMOD/mService.mod
I don't see anything wrong? -
Been having a strange problem while welding in auto robot will perform random TorchClean;
There is no pattern to it sometimes it will happen 10 times a day other days maybe 3
It usually occurs when I press the index to weld button at the cell controller, but other times it will run at the end of a program which means it runs twice due to the fact I have a TorchClean; at the end of each weld module?Something is a miss PROC, MOCC, SYS ect... just don't know where?
4400L IRC5
IRB 750K 2 Stn positioner
New WCC Win 7 -
Robbie
Your going to end up with something that looks like this.
As far as conflict is concerned if you're referring to the tracking data in Program Data there should be no issues?
Are you at KPI in SD?
ActCurrUnit;
PDispOff;
MoveJ Pth01_1741_p1, v2500, z20, tWeldGun\WObj:=obTemp;
MoveL Pth01_1741_p3, v5000, z10, tWeldGun\WObj:=obTemp;
MoveL Pth271_1741, v5000, z5, tWeldGun\WObj:=obTemp;
ArcLStart Pth01_1741_p4, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trCenterline;
ArcLEnd Pth01_1741_p5, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trCenterline;
MoveL Pth01_1741_p6, v1000, z5, tWeldGun\WObj:=obTemp;
ArcLStart Pth01_1741_p8, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
ArcLEnd Pth01_1741_p9, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
MoveL Pth01_1741_p10,v5000,z5,tWeldGun\WObj:=obTemp;
MoveL Pth31_1741, v5000,z5, tWeldGun\WObj:=obTemp;
MoveL Pth281_1741, v5000,z5, tWeldGun\WObj:=obTemp;
ArcLStart Pth41_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
ArcLEnd Pth51_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
MoveL Pth61_1741, v5000, z5, tWeldGun\WObj:=obTemp;
MoveL Pth71_1741, v5000, z5, tWeldGun\WObj:=obTemp;
MoveL Pth81_1741, v5000, z5, tWeldGun\WObj:=obTemp;
ArcLStart Pth91_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
ArcLEnd Pth101_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
MoveL Pth111_1741, v1000, z5, tWeldGun\WObj:=obTemp;
ArcLStart Pth141_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
ArcLEnd Pth151_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
MoveL Pth161_1741, v5000, z5, tWeldGun\WObj:=obTemp;
MoveL Pth171_1741, v5000, z5, tWeldGun\WObj:=obTemp;
MoveL Pth291_1741, v5000, z5, tWeldGun\WObj:=obTemp;
ArcLStart Pth181_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
ArcLEnd Pth191_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
MoveL Pth201_1741, v5000, z5, tWeldGun\WObj:=obTemp;
MoveL Pth211_1741, v5000, z5, tWeldGun\WObj:=obTemp;
MoveL Pth221_1741, v5000, z5, tWeldGun\WObj:=obTemp;
ArcLStart Pth231_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
ArcLEnd Pth241_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
MoveL Pth251_1741, v1000, z5, tWeldGun\WObj:=obTemp;
ArcLStart Pth311_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
ArcLEnd Pth321_1741, v1000, sm_3125S, wd_3125S\Weave:=wv_3125S, fine, tWeldGun\WObj:=obTemp\Track:=trHieght;
MoveL Pth331_1741, v5000, z5, tWeldGun\WObj:=obTemp;
MoveL Pth341_1741, v5000, z10, tWeldGun\WObj:=obTemp;
MoveJ Pth351_1741, v5000, z20, tWeldGun\WObj:=obTemp;
! Step Through No Motion
ENDPROC