Was not able to resolve either via support from Fanuc or RobotWorx. Ended up purchasing ethernet ip adapter and offloaded IO to external PLC.
Complete.
Was not able to resolve either via support from Fanuc or RobotWorx. Ended up purchasing ethernet ip adapter and offloaded IO to external PLC.
Complete.
(RESOLVED) We purchased the R784 Ethernet IP option. After 2 days begging Fanuc for the PACs codes, we it installed last night, Ethernet IP configured and we now have access to IO, for no other reason at this point than to actuate a single electronic gripper. So Roughly $1000 for a PLC (which we already owned), $1700 for the software option, all for 2 rungs of code in a PLC program. Overkill and waste at this point, but will be scalable for phase 2 of the project (motor controllers, etc.)
The advanced package includes a few other items. RemotePC iPendant is one of the extras. If you don't need that then the basic is fine.
Thanks so much! And after being on Fanuc chat support for over 2 hours, you beat them to the answer.
Giving up on the digital IO on our LR Mate. Just cannot make it work and there is so much conflicting information that resolution seems impossible at this point (worked with Fanuc support as well as Robotworx). We would eventually be adding a PLC anyhow. So I'm recommending to the group that we just add Ethernet IP software option to the robot and be done with it. At this point, basic boolean IO is the only thing we will be doing. Eventually some motor controllers will be added to the PLC. But even then, very little data will pass between the robot and PLC. Can anyone who has used both explain any reason to go with the Advanced EIP package (R887) instead of saving money and going with the stand alone IP Adapter (R784)? PLC is an Allen-Bradley Compact Logix. Want to be able to add the "Ethernet-Module" to the ladder logic in Studio 5000.
Display MoreA couple options you could try.
1. Don't connect your external supply to the Fanuc IO at all. Only use it for 24 and GND on the schunk. For gripper open close just use the robot DO powered from the internal Fanuc supply.
2. Same as 1 but put a relay in between the robot DO and Schunk open/close and use the external to power the signal open/close.
Option 2 is a little safer bet.
Unfortunately, I can't read 24v from any of the outputs no matter what I have tried. When I lay a meter on Fanuc IO 0v and the output, actuating the output does not show 24v on the meter. Am I missing how Fanuc IO is supposed to work? Is there a different direction I should try?
Thanks for the response byrol . Sorry for the delay in responding. This issue is still unresolved. I've worked with RobotWorx (where we purchased the device) as well as Fanuc support. I must say that the support is lacking. Based on a combination of information from both sources, that the 24vdc power on the digital IO was not sufficient for the gripper. Therefore, to supply my own power, I would apply external 24vdc to the DOSRC2 on the TBCV4 (Pin 2 of the phoenix contact on the converter board) and external ground/0 to the 0vdc on the TBCV4 (Pin 3). This worked with a very low power 12vdc power supply (I'm cautious of smoking something important). When the Output was turned on via the TP, I was able to read 12vdc between the output and 0v on the TBCV4. But when we replaced the power supply with the correct device, the power supply tripped and shut down because it read a short between DOSRC2 and 0V. I'm at a loss at this point. I threw a little hissy fit and told them to quote the Advanced EIP so I could just move the IO to my Compactlogix. After a quote of $3750, I think I'll give it another go. Thoughts?
Below is what I submitted to Fanuc support prior to trying, suggesting what I was about to try. Their response was "My answer is that yes to the extent that your device must also meet the power requirements of our outputs."
In my day job, I'm responsible for programming and support of paint and part loading robots. Integrators have always handled the install. For a side business, I have picked up a refurbished LR Mate 200iD. The LR mate came equipped with an A20B-1009-0690 that appears to be interfaced with the CRMA 15/16 slots of the main board. If I understand correctly, this afford some I/O outside the standard robot IR on the aux port of the arm. However, I can't find any documentation on this board for pinout schematic. I have an electro gripper with 4 pins: 24vdc, common, Open, Closed.
I've found a few things on the CRMA 15/16 schematic, but not how it translates to this board. This board has 8 rows of 11 pins (push release). But I can't seem to find a schematic showing where each pin maps back to the CRMA slots. Thank you for any help you can provide as we fill in gaps I normally lean on integrators for. It is a fun journey. But I find out something new every day that I didn't know I didn't know.
It is in the engineering bulletins on the CRC site. You just have to check it occasionally.
Exactly what I needed. Saves me from wasted DL and install time for no beneficial feature (for me). Thanks!
ROBOGUIDE V9S adds support for new features and robots in V9.40P/10, V9.30P/15, V9.10P/33, V8.30P/60,
and V8.20P/35 software:
What's new in V9S:
Support for V9.40P/11, V9.30P/15, V9.10P/33, V8.30P/60, and V8.20P/35 virtual robots.
Some time ago, while on Fanuc CRC chat, I relayed a problem that I was experiencing. They asked me why I wasn't running Revision M, which fixed the problem I was describing. The short answer is that I didn't know there was a new revision. I'm currently running version R and see that S is available. It would be nice to see what is new to each version without having to download and extracting the entire package. Is this information listed anywhere?
Thanks for the options folks. Unfortunately, if it isn't possible to assign the values directly to a Jog frame, my method is certainly double (and requires less manual entry....I do stupid things some times.).
As for user frame, it isn't an option because of limited number of Frames. And if I program one program, and later change the frame values, bad things will ensue. This is why we use Jog Frames. They don't tie to the program and let me reset per program. Perhaps I'll investigate a KAREL option.
I use jog frames to manually program our paint robot. We have hundreds of product configurations that all hang at different orientations. Jog frames allow me to quickly orient to the part currently hanging to fix issues. When starting a new part, I create a "FRAMEXXX" procedure for that part which consists of 3 points for my teach prob (steel teach point 8" from paint gun) for Origin, X, and Y touched off on the base of the product. So when I go back and forth between my various model procedures, I can pull up this FRAME procedure and use the points to reset the jog frame for that part. Once the points have been set, it would be nice to push this data programmatically to a frame procedure, rather than having to run the FRAME programs and manually moving the robot to record the 3 points to the jog frame. Thoughts?