It seems that I have crma 58, crma59 connectors on the mate controllers. Normally i could use these correct ?
yes that is true. I think it depends if you want to use male or female connectors? The wiring should be like this (see attached)
It seems that I have crma 58, crma59 connectors on the mate controllers. Normally i could use these correct ?
yes that is true. I think it depends if you want to use male or female connectors? The wiring should be like this (see attached)
Yes this is true profinet is the way to go for us, and a profinet card will be purchased in the future, but for now I would like to start with DI/DO. You are right we dont have the DI/DO card but, as I understood the r30ib-mate controller has a couple of DI/DO-s already built in as standard. I could use these DI/DO-s for starters, is this correct ?
These would be as in the attachment ?
Yes, with your controller there are these signals available too. I might be able to post some schematics if you have troubles wiring these DI/DO.
I would recommend buying molex profinet card for mini slot. There is a siemens profinet card available too, but we had some problems to set it up. Molex seemed easier to set-up.
If you have DI/DO card in robot controller (I doubt that), you could get away without using profinet card. 8 DI/DO signals should be enough to start the robot, but you need to have enough room in PLC I/O cards for that too. Profinet seems like the better option here, if you consider that your project could expand and you're going to need more signals in the future
I've done this only on newer controllers. Try to search for $NUM_RSPACE[GRP] system variable, you should be able to change that. I'm not sure what the maximum number for your controller is though. I hope this can get you somewhere.
Hello,
I've successfully used Cognex 7000 Series camera with profinet molex card (fanuc robot was master). We've used profinet because our whole system in that project was profinet-based. If you install Cognex insight explorer (camera config software downloadable for free online), there is a chapter in help documentation describing camera communication with Fanuc and other robot manufacturers.
Hey,
would you mind sharing how did you accomplish to do that? I'm interested in filtering log events too.
Hello,
is there a way to set up a default display setting after robot cold start?
For example, I want double display view, registers on the left, I/O on the right. I guess this can be done with a little bit of KAREL, but is there a way how to do that without it?
I believe you can map a macro to DI or FLAG in MENU / MACRO screen.
What is monitor condition instruction?
I was thinking about using the current position instruction, but using this do I have to create multiple zones within the whole cell?
For instance: current position is within cube #1, then create a safe home routine back? Doing it this way I may need to have quite a few zones. Is this typical?Thanks,
OK I see what you are trying to accomplish. You want an universal one button "return home" program. Your suggested approach is a rather tedious task to do and it's certainly off topic. I'm trying to figure out the most effortless way to do it too.
Monitor condition can be used to monitor some DI/DO/FLAG...whatever you want to check. First you need to create a "condition" subtype program, lets name it COND1 which is something like: WHEN "condition1" CALL SOME_PROGRAM_1.
Then in TP program you can use MONITOR COND1 to start monitor the condition, and MONITOR END COND1 to stop monitoring. The condition is evaluated in some background process.
For example: you are moving part from A to B. On the path from A to B you can use MONITOR instruction to assure that the part is present (on the whole path from A to B), and you can (for example) stop when the part is not present. It is a very naive example but I hope it sheds some light on the topic.
Thank you both for the answers.
Would this be the place to write checking logic for an auto home routine?
Or would this be better structured in the TP program?
Depends what kind of auto home routine you want to use. If you want to check the logic conditions for the entire program runtime, background is your best bet. You could also use monitor condition instruction.