So you have an ArcMate 100iB connected to a Miller Autoaccess 450 and cannot set outputs?
What a cool coincidence.
What do you expect on answering to an 8 years old thread with that llittle informations?
So you have an ArcMate 100iB connected to a Miller Autoaccess 450 and cannot set outputs?
What a cool coincidence.
What do you expect on answering to an 8 years old thread with that llittle informations?
On first look:
- you don't have to connect the safety signals to normal I/O. The safety signals are connected to safety I/O automatically. You can do it, but only for reading them in KRL, if you want to have a look onto them in the user program.
- change the "Operator safety acknowledgement" to external unit.
- you must reintegrate/depassivate the interface with a raising edge on the signal ACK_REI in the PLC program. EDIT: You can call the standard FB/FC "ACK_GL" for depassivating.
What are the tradeoffs between chemical and wedge/sleeve anchors?
This is a question of the construction of your floor, the kind of concrete, or other stuff.
Did you try another input, not always no 3?
This line with [in] is some kind of Syntax describing. Always use the part from Example. May be the slash has to be a backslash.
As far as I understand the doc, there must exist a file on MC: with name 'list' that contains the names of TP programs that will be loaded.
Think it's not a good idea to name the own procedure the same name of the external routine.
Edit: forgotten ':' after MC. And changed / by \
You should provide your faulty code, so someone can correct it. That's easier than writing whole code from scratch.
You don't need an external resistor. There are builtin resistors.
Use the lower part of the schematic. So the rest of DaveP's suggestion should be OK.
Don't you think that, after more than a year, the problem has been already solved?
Register at Fanuc crc, then you can download the manuals you need.
https://crc2.frc.com/. or for europe
1. Where can i download OfficeLite softeware?
You must purchase it from Kuka.
1. You can attach pictures direct to the post, so we don't have to waste time downloading and unzipping.
2. It sounds like you open and close the server frequently, I would open the server once, and then listen to messages in a loop.
3. Think disabling messages does what the name says, it disables the messages, but doesn't disable the fault, the fault will happen anyway, but you don't get a message about the fault.
Read the referred thread. It's not that difficult. Try to access $ov_appl, normally it should exist.
See RE: Setting robot speed from PLC
Instead of using a group input use a single bit attached to your button to change the value of $ov_appl.
.. Your robot may not support more than 1024 I/O -- $IN[1025] and $IN[1026] are special inputs from back when KRCs did not support anything above 1024. Once the I/O ranges were expanded on later KSS versions, $IN 1025 and 1026 were kept as-is, which makes those bits unusable for I/O...
128×8+1=1025
Mapping into those two special bits (1025, 1026) is not allowed.
No clue about what you really mean. Haven't looked into you zip file. You can post pictures here as attachment, not as zip,so we can see them direct without wasting time downloading and unzipping.
Nope, it's kind of inconsistent what kuka does here.
The number direct behind INB / OUTB / INW / OUTW / INDW / OUTDW always are counted as bytes.
The reason would be, that if it was depending on kind of IN / OUT you can't map it bytewise.
Calculate 63 * 8 + 1, and you have the beginning I/O number on the robot.
Read the complete thread!
Be more precise, read and follow: READ FIRST...
Oh okay, but if i remove the INI fold, it will prevent to start the program with a LIN movement that's it?? or i will not be able to do any manual movement with the Robot? (Including PTP movement).
Yes and no
It will prevent to start the program with a lin if you select it manually, but not when it is called from an external program, that called the INI.
You will not be able to start any movement without the INI if you selected it manually, but it won't be a problem if you stop the program after it was called by another one that has called the INI.
Usual workaround is to use something like:
IF $MOVE_BCO then
INI
ptp $pos_act ; for allowing LIN movement at beginning
endif