I have three coaxial camera cables from Fanuc that connect into our SC130EF2 cameras part number: EE-7414-203-007 that are shorting right at the connection to the camera. They are supposed to be "FLEX" cables and yet here we are. The cables are only about 2 years old. Anyone tried to repair one of these? Fanuc wants a fortune to replace them.
Posts by Matthew Fuller
-
-
I could use some help understanding how slots work in Ethernet IP going from a FANUC to an Allen Bradley PLC using Studio 5000. In the Ethernet IP setup on the robot controller, I can setup multiple connections and we specify which connection by the associated slot.
In Studio 500 we add the robot which gives us 64 tags. In that setup there is a setting for Robot Slots and we can specify 1-4, 5-8,... etc but when I choose 1-4 I would assume each slot would have 64 bits assigned so 256 total... but only 64 actually show up. I tied the UOP I/O to the first slot using Rack 89, Slot1, Starting Point 1. That works great, but it basically takes up the first 64 tags in the plc software. I setup a second rack 89 connection on the robot to assign digital I/O, but I can't see any bits toggling on the PLC when I do that. If I use slot 1 for both digital I/O and UOP, then the first 20 or so of my digital I/O are basically mimicking the UOP status. I don't want that. I want separate I/O and more tags in the PLC... Any thoughts?
-
So interesting, my students (this younger generation) can't stand 10 key. But I see you're point. So I officially revise my suggestion to make it so that you can make 10 key or keyboard the default. Also agree that typing most of the comments using the ipendant tools on newer systems is preferred over all others generally speaking.
-
-
I magnet is only drawing 40 miliamps. So really nothing the RO can't handle. I'm almost done setting everything up, just need to solder the connector and should be ready for testing tomorrow...
-
yes I know, I'm seriously considering it. The plug adapters they send with the robot for the I/O up there are expensive and more difficult to figure out than they should be. I'm trying not to run external power all the way up the arm if I don't have to.
-
Default the TYPE under the SELECT screen to TP Programs or give the ability to create a default.
When setting up virtually anything where you are recording a point and then have the ability to move to that point... do not put the moveto right next to the record. In fact moveto should be consistently on F2 and Record on F5... Far Far away from each other.
Command instruction items should be more consistent. For example PR[i,j] jumps around all over the place in the instructions. Put it at the same level, same number every time. Same with many of the others that we use all the time.
I LOVE that the HOLD or PAUSE button on a Motoman is a big round button at the top instead of hidden in the middle of the teach pendant on a Fanuc. Got to get operators and maintenance people to stop E-stopping the robot to stop the process normally, and get them using the hold button. It would be better if it was large and in charge!
Should be more than one way to get out of a Controlled Start. Should also be able to hold down the Prev/Next keys and get out of it that way as well. Not intuitive at all for beginners.
On the teach pendant, just make the blasted keyboard come up automatically instead of having to cursor down to Options/Keyboard then F5. I know we're building on old software, but why not save people some time...
It's the little things that can make all the difference!
-
I was able to find a maximum output current rating of 0.2A for standard DO points. I'm assuming that Robot Outputs would be the same, but I never want to assume anything. Can anyone confirm that for me? I'm adding a small electromagnet to the end effector and I want to make sure I'm not going to overdraw it.
-
IF THEN is a cool new feature for 8.3. Basically if your conditional statement is true, then it will run anything you put between the IFTHEN and the ENDIF. If it's false then it skips to the ENDIF and continues on. You can nest IFTHENs inside of IFTHENs when needed. I have found that you can create more robust conditional statements overall with the IFTHEN. The part that's not quite as user friendly is the part in parenthesis. After you select the first part of your statement you have to hit INSERT (F1) to keep adding to it. Also notice that as you add more to the statement, an option appears on F2 to DELETE in case you start adding too many.
I use both standard IF and IFTHEN statements regularly depending on the situation. Just another tool in the toolbox!