I know this is an old thread but thank you for the responses everyone. Sounds like it *can* be done but the "preferred" method is the imprecise way with the arrow marks.
Posts by JankyPLC
-
-
So I tried that, thought it would be the holy grail of usefulness, but it comes with some major limitations. The biggest one and a deal breaker is that once you turn that on, you can no longer Load VAR or VarName files back into a controller if they've been modified.
My preferred method of programming when I need to do a lot of setup is to configure all my P,D, and I Vars and their names in the text files then Load them back into the controller. No go with aliasing on, so back to comments it is from the sounds of it.
-
Hello,
DX200 controller has the option to display IO Names in Job. Can be turned on in Main Menu->Setup->Function Enable->General I/O Name Disp. On Job.
This essentially displays the name assigned to that specific Input or Output in the job like a comment would be shown, to the right of the line the input or output is used on.Is there a similar setting for Double vars or Position vars? I've been just adding comments above each line when I write my jobs but its tedious to comb through every job to update them if you ever change the name or assignment of a Pvar for example.
Thanks in advance!
-
Tried searching but search term must be 4 characters. Does anyone know of or have created any UDTs or AOIs for controlling or interfacing with DX200 or YRC1000 controllers over E/IP? Tried googling this but all that comes up are MLX related results.
I created my own UDT for IO mapping I did between robot system IO and robot physical IO but still had to do quite a bit in the PLC as far as start, stop, reset, calling jobs, etc logic. Also had a multitude of MSGs reading and writing position variables, error texts and other robot information. It would be nice to package some of that to make it easier to integrate repeatedly into projects. Just curious how you all accomplish these tasks in your projects with E/IP communication. do you have AOIs, UDTs, just write routines, keep it all in the robot ladder and issue nothing but a start command? -
You can map them via the ladder both inputs and outputs to physical IO or over ethernet. I believe one of the manuals covers this, maybe the ladder manual or the ethernet IP manual? If you look in the ladder you will find physical IO already mapped to the robot job IO using BMOVs, you can used this same thing to map over ethernet IP. Make sure you don't double map to any outputs twice or it will error.
Alternatively you can CIP MSG write and read most data in the controller including bytes - Inputs/outputs, position variables as arrays of ints or dints, system information, alarm messages as strings. This opens up a world of communication possibilities. I want to say all of that info is in the Ethernet IP manual. -
Does anyone know if Motoman has a tool to set the home position if encoder data is lost or a motor is swapped, similar to KUKAs Electronic Mastering tool that inserts into each axis and lines up the marks on its own?
-
We have an R30iA that was integrated by a company who is now out of business. I'm trying to find the weight of the EOAT but am not sure where to look. In Motoman robots there are tool data files that contain this info. Is there an equivalent on a Fanuc controller? Would anyone be kind enough to point me in the right direction how to find this info? I do not have access to all the manuals unfirtunately (surprise surprise).
-
You may want to contact Yaskawa on the issue to see what they recommend, condensation forming on boards may be an issue with how tight everything is in these cabinets. You'd want to figure out the BTU output of everything too. Might I suggest, if you do add an air conditioner, going with a compressor based model. Dollar for dollar they tend to be a much better value.