Posts by brianb

Look up in your manual on how to do a group exchange... Otherwise...

Menu, 1 Utilities, 2 Group Exchg
Select your original program and name your new program
Under Group Selection, you'll want to copy the original group to your new group by knowing what your original group is. Line 1 will show you your groups available to the right of the program name. So if the original group is "2", go to line 4 and cursor over to New Grp [0] and change that to whatever group you want.

Essentially, you're copying your original program and creating a new one through this feature. Once this is done, then delete the original and rename the new program.

Do an all of the backup prior to this in case you screw something up...

We swapped out the optical cable that goes from the amplifier to the backplane and that resolved our issue...

My alarm screen is displaying:

SRVO-223 DSP dry run (9,1)
SRVO-058 FSSB 1 init error (2)

Just an FYI, this cell consists of 3 LR Mates with the same software packages. The other two arms had no issues with the software load.

Also, is it worth reloading software?

Quote from Dalin

thanks for replyin.....

-the fuses FS1,FS2,FS3, FUSE1,FUSE2, works right......
-there Is port CFR8 instead of CFR7 and when i start the robot controller after disconnecting it , no alarm pops up; it still says just SRVO 223 and SRVO058
-the SVEMG led is lit red always even if i push/release the e-stop on the controller
-the OPEN led led is not lit at all anytime
-the ALARM led is not lit at all, eventhough it shows thers alarm showin on the TP
-i pulled out the optical fibre comm cable and restarted ; still says the same error

Display More

I have the same issues as quoted above on a brand new LR Mate (R30iB+). Nothing looks out of the ordinary and I checked my fuses. Robot has not moved yet and the software was just installed as well.

Any help on this would be greatly appreciated!

I've ran into the same situation with mig robots that use fronius as a welding power supply. I just have to make sure that my welders are on prior to turning on power to my controllers. Maybe it has something to do with communication across the system...

Not sure what your process does so my situation may not even relate to yours.

Quote from 95devils

The alarm relates to Robot 1. 8001 (R1)

Open [Lincoln Setup], then reboot. The previous alarm (8001 [21]-[24]) was ignored. You cannot weld or touchsense until this is resolved.

Open [Arc Welding] > [Lincoln Setup]. Follow the instructions on screen, then reboot the robot controller.

Mind telling me what alarm (8001 [21]-[24]) is?

Any idea what is causing the following alarm?

ALARM 8001 TASK#0
Open [Lincoln Setup]
[20]

This is on an ArcWorld cell with dual arm robots, Lincoln PowerWaves, STT Modules, and DX200 controllers. The cell has been in operation since January at a customers facility and this is the first time that I've scene this alarm. Any help would be appreciated.

Thanks,

BTW

This is occurring on two different weld cells (both dual arm and angle config) with very similar programing practices.

beanluke:
Both groups are set to the proper angle...

retobor:
Prior to me sending out a distress call, we did run the manual payload IDENT and also manually entered in our own values which were nearly identical. We also received our values from the manufacturer that provided us with our welding equipment. So we're assuming that data is correct.

On a side note... These iD's have been doing some things that I haven't seen in older models before. Such as noise/clunking sounds in J1(Fanuc did admit to us that sometimes these robots do not get properly "broken" in because they're too busy to do it) and that our position gets adjusted/moved somehow (no idea how) and we have to touch up our UF's.

I'll keep everyone updated if I figure something out.

Thanks!

100iD robot
R30iB Plus

So I'm having numerous issues with disturbance excess (mainly J4), and on occasion, collisions when running thru my weld programs on a dual arm weld cell. These alarms and/or warnings occur during a weld (in dry run or in actual welding) and when exiting a weld. I have the program cleaned up as much as possible with using J or L moves in the right spot and at the right speed. As far as the collisions go during a weld, my travel speed is only 18-25 in/min. All in all, it's a very simple weld program with no heavy moving.

Some other notes that I have checked to eliminate my disturbance excess':

-Not using any ACC motion
-I have proper voltage to the controller
-Payload settings are correct (as far as I know)
-Speed settings for wrist motions are low
-Axis for is not near singularity

So, assuming that my payload is set up properly, which I've double checked and what not, what am I missing?

Also, the base that both robots are sitting on are attached to a common base at an angle of 45 degrees and roughly four foot off of the ground. The arms travel down to the part that's on a headstock/tailstock that sits below and out from the base of the robots. Will my payload settings be affected if it is configured with J4 parallel to the ground and not parallel to the robot base that is at 45 degrees? If so, should the payload configuration be set with J4 parallel with the robot base?

I could use some help as my only fix right now is to reduce the collision sensitivity to 80-90% in the affected areas.

Hope this makes sense. Any help would be greatly appreciated!

If its a background program, you'll need to stop it from running prior to any editing.

MENU, SETUP, BG LOGIC

Not sure if this is what you were asking but...

TPSi Robotics Push Welding System
WFi 25 wire feeder
TPS 500i welder
Ethernet/IP

So far, just a digital input lets me know if the crashbox has been unseated or not.

Thanks!

Prior to the weld start, insert a line and write this...

$WVSCHEXT[##].$AZIMUTH=90

After the weld, insert a line and write this...

$WVSCHEXT[##].$AZIMUTH=0

The "##" will be your weave schedule that you want to change. Changing it to 90 will make the weave run parallel with the weld. Just don't forget to change it back once the weave end has been executed. Use this way when you want to use the same schedule on multiple welds and to be able to temporarily change the azimuth.

That's what I originally thought but I don't have (that I know of) somewhere to connect an EE cable coming from the controller to the crashbox.

I'm using a fronius crashbox on an R-30iB controller, 120iD robot.

I want to integrate the crashbox (which I've never used before) on my arm into the system and have the cell throw a fault and stop the cell when a collision occurs. Ideally, I'd like to throw the actual SRVO alarm that a collision detect has occurred.

The only signal that I get is a digital input (that I know of) that will turn off when the torch becomes unseated and will turn back on when it gets reseated. The only thing that I can think of is using a UAL inside a background job that will pop up a message on the screen and stop the cell.

Anyone have any ideas or have used a crashbox before.

Thanks in advance!

DX200 ArcWorld...

I was going through and running my weld programs while adjusting my speeds on my MOVL's. When I'd select a specific MOVL and cursor over to the speed to select and adjust, the speed would be highlighted but I was unable to change the speed from the keypad. It seemed as if I inadvertently disabled the numerical keypad and this prevented me from changing my speeds. Everything seemed to work properly with the exception of the numerical keys. Is this possible? Would there happen to be a short key that I happened to unknowingly hit to disable this or did it coincidently freeze up?

To resolve the issue, we cycled power and it worked after that but it still doesn't explain why it happened.

Thouhts?

So I definitely know that there is plenty of information on here but I'm hoping I can get some specific questions answered. On top of that, I have already found some useful information on the material handling manual...

I have to define four different user level passwords that each have specific request to allow/prevent a user from performing certain functions.

User #1 can only jog the robot and perform touchups. He/she can not do anything else besides that.

User #2 can only jog the robot and nothing else.

User #3 will be the setup option so I think I have that covered.

User #4 will be the same as user #1 as well as having the ability to remaster.

My goal is to not allow any manual robot movement unless a user is logged in. So how can I restrict manual movement while in manual mode with the tp on and the cell in T1 and no one logged in?

Any help would be greatly appreciated!

Did you renumber your points simply by cursing over to the point and then changing them or renumber your points thru the feature "renumber" under the EDCM (F5) button?

Also, are these regular points or position registers?

Regardless of how or why this happened, did you take an all of the above backup prior to doing this? You can always reload any programs that have been effected.

Quote from SHIFT_Lock

Next step is to establish a pulse on each axis. To do this put the robot in group 1 Joint and then go back into the MASTER/CAL screen as mentioned before. Select option 4 for Single Axis Mastering and then Starting with Joint 1 move this axis back and forth a few times (I’m not sure on how many degrees exactly) and the put a 1 into the SEL column to replace the 0.

I'm not sure what the manual says but I've always moved each axis 20 degrees in each direction. Never had any issues that.