Checked them all, all good. Even the little fuses that you can only access by pulling out the PSU and the devicenet boards. Checked fuses on the servo amp, on the door panel board. All good
Posts by EPeters1
-
-
it was working just fine until yesterday when suddenly it won't turn on. I have tried tracing the current and we have plenty coming in from main and going into the transformer. From transformer into estop unit i am getting 200 which should be good. From transformer into PSU i am getting 53 which seems low to me. From PSU i am getting 45 volts out on AC and nothing at all on DC. The PIL light is green but there is a red led on labelled ALM(assumedly alarm).
Swapped the PSU with an old spate but nothing changed. I have a few more i could try swapping with if it comes to it.
-
My understanding is when we bought it we had the ability to put it on every robot but these robots came in after it was applied to all the ones we had at the time and the guy who does that stuff would need to be flown in which sucks. I'll see about contacting fanuc and maybe they can send the stuff to me since contacting him has proved unhelpful. (hes the one who old me to just copy over everything haha)
-
Thats what I was thinking but hoped it wouldnt be the case. If I copied everything from a machine with password enabled (image files and "all of the above" file backup) and put it on a controller that did not have it enabled would that carry the password capability over? or would it not recognize those files?
-
We have 10 robots and we recently decided to set up passwords on them which has been relatively simple except tree of them do not have a password option. Is there a way I can take just the files that have the password software in them and copy them on to these other machines? If so, what files do I need? Or would I need to do a separate software install to get the passwords on them, I am hoping not that because the guy who does our software install work is part of a different branch of our company who lives in another country so getting him up here to do it would be a pain.
-
Figured it out. For anyone who might have their own questions/if I forget and come back here this is basically what you need.
<?xml version="1.0"?>
<!-- Password configuration file -->
<PASSWORD>
<!-- Level name -->
<LEVEL level="0" name="OPERATOR" lang="eg"/>
<!-- Screen access -->
<!-- SELECT -->
<SCREEN level="0" sp_id="23" scrn_id="1" access="1" rw_access="1"/>
</PASSWORD>
Potentially the sp_id number and scrn_id number might be different for different software versions or robots, I don't know but that worked for me.
-
I want to make a password level that is identical to operator level except that they can also edit Registers. How difficult is that? What do I need to know about xml to make that happen? Any resources and answers are helpful.
-
thanks so much. Personally i feel like it would be easier to have just a manual switch for the operator to use but at least we know our options now thank you
-
Two parts to this really. First, what exactly is background logic and what commands or steps does it take to actually make use of it.
Second, they want a light set up on each robot cell that is green when operating properly and red when there is an error in order to alert the robot techs to an issue. However, everytime the operator opens the door to the cell in order to change out parts for the next cycle it gives a gate open error and turns the light red which is a waste of time because nothing is wrong.
Can background logic be used to filter out this error so the light doesnt trip when the door is opened? Is there another, better way to set this up?
I dont want to set the robot to just ignore the door open signal for obvious safety reasons but we can't have false alarms every single time the door is opened during normal operation.
-
Alright, thanks, we will get some spares and keep them inside
-
Recently had to replace an estop unit in one of our controllers which wasn't a big deal because we had five old used ones sitting in storage but as i went through them one by one, in the whole lot only one of them worked. Are these units one of the first things to go bad? Does the fact that they have sat unused for about 5 years change anything? How many spares should we keep on hand? We have 10 robots right now that have been running for 5+years pretty much daily and I've only had e stop issues maybe twice so I find it odd that the ones that are running seem to have lasted better than those in storage.
Perhaps storage conditions matter? The ones that turned out bad were all in controllers stored inside an old shipping container behind the building so not directly exposed to the elements but still in more varied temperatures and humidity than those we have running inside the shop.
-
turns out the 200VAC fans were totally dead. Replaced them with confirmed functioning fans and it seems to be working now
-
RJ3 controller giving SRVO-043 DCAL alarm (G:1 A:1) and SRVO-043 DCAL alarm (G:1 A:2). Checked all my fuses and connections, fuses are good and all wires are in place snugly. Blew out all the fans to make sure it was cooling properly, measured the voltage and we are getting enough coming in. Changed out transformer, E-stop unit and servo amp one at a time and none of them made any improvement. I have seen people on here saying this alarm can be from aggressive movements in a program but it will trip even moving at 5% on T1.
I also have tried swapping out teach pendant cable and the cable that connects to the robot and the one that connects to the weld Equipment. Nothing has made any difference. The machine isn't new, its made from the remnants of other robots gutted for spare parts for other machines.
I am out of ideas, anyone have something else to check or swap out?
Appreciate it
-
It was the cable between weld equipment and robot
-
Rj3iB controller hooked up to a Fanuc Arcmate 120iB with lincoln powerwave 455m. The weld equipment hasnt been used in years and while i turn it on and lights are all green as soon as i try to feed the wire at all the Robotic Wire Drive LED flashes red in a sequence of 6 flashes, pause, 3 flashes, pause, 1 flash, pause, 1 flash, pause then back to green for a few seconds before repeating.
I plugged the robot into a different controller/weld equipment combination nearby and it worked perfectly so I know the robot and feeder themselves are working. It recognizes there is weld equipment and it is turned on because I don't get a weld EQ error, there is no error on the teach pendant at all, actually.
My theory is that the controller and the cabling is all fine because there are no teach pendant errors and the problem lies with the weld equipment. If I could figure out that flashing light then I think I would know what to do but no user manual for it has any way to decode the sequence and i can't find a service manual for a normal 455m (455m STT and 455m with PowerFeed10 I can find but neither has been helpful)
-
I don't believe you can change the way it moves as it is a macro. We moved the robot to a different position, one a bit closer, and ran it again and it worked.
Since we are planning on running it manually it shouldn't be an issue we will just move the robot manually to a viable space before calling the program but anyone wanting to run it automatically should take note that it needs a viable linear path from wherever it is to the reference point to function.
-
I got torchmate all set up, master worked just fine and then I went to use TM_ADJST to test it and nothing happens. No movement, no error, just sits there.
Update: I had been running it in T1, tried it in auto and it attempted to move but got a position config change error
-
had to swap out pulse amplifier which doesnt make any sense but it worked
-
Putting together an RJ3iB controller from some used parts, expected certain problems but this has got me clueless.
Had everything working properly for about a minute then got errors of blown fuses and FSSB error and LVAL error and i think a few others i was more familiar with. Powered down and checked fuses, mistakenly grabbed 1.5 A instead of 7.5 A fuses, dont know how I managed that but here we are. Pulled blown fuses and replaced them with the proper specification. Now when i turn it on it loads the files and gets to the "Starting System Software. please wait" part of the process and just stalls out.
Tried an INIT start, gets stuck at the same spot.
Tried to load img files, got stuck at SRAM 00
Swapped TP cable for one I know works. No change.
Swapped main board. No change.
7 segment LED sometimes has 0 or 1
I don't understand what is going on, I cant even boot up far enough to get an error code which is bonkers because it was functional for a brief minute this morning so unless a component spontaneously died then everything is confirmed functional.
-
those wires are way too thin for my skills and tools at the moment. Guess we do things the long way. At least I know its my only option now. Thanks.