Where do I look for other errors? Motor status is GREEN, Pogram status is GREEN.
I remember that this is an issue with the BCO error in EXT mode of INTERBUS I posted earlier. No other errors have not found, strange is because the robot in manual mode T1 and T2 operates and performs all the movements. I also know that if I want to see in real time what are the Cartesian coordinates in all fields displayed UNAVAILABLE.
Maybe you have an idea for a test? somewhere in the options I can see all errors?
I have no idea what to do next...
Error - "The point could not be created" - what im doing with it wrong?
-
technologINV -
July 18, 2013 at 11:34 AM -
Thread is marked as Resolved.
-
-
Any active errors are displayed in the message window at the bottom of the KCP screen. Any errors that remain after hitting "ACK ALL" are the ones that need to be addressed.
Program status should not be Green unless the program has started running. If the program has just been selected, it should be Yellow. Green indicates active execution.
The Submit status should also be Green.
In T1, select program, run until BCO is achieved. Then switch to AUT, press ACK ALL, turn on motors, then examine state of indicators and messages. Try pressing Step Go and see what messages occur.
-
In T1, select program, run until BCO is achieved. Then switch to AUT, press ACK ALL, turn on motors, then examine state of indicators and messages. Try pressing Step Go and see what messages occur.I did it and the robot began to work in AUT!
Now I need help to program inputs / outputs. Inputs and outputs are implemented on the plug x13? I do not have schedules and do not know where to look for a responsible plugins. Has anyone any information about this?
I need as much information about the inputs and outputs -
mmmm...X13 is SafeRobot connection.
Not sure if this is applicable as it's for a KRC4.
-
These are pictures of my inputs / outputs, I do not know how to connect and which wire is responsible for what, where can I find out?
-
The I/O is on X11. If you have any electrical drawings it should show you where.
I only think I've hard copies of any documentation.Sent using Tapatalk 4
-
These are my schemes to plug x11
Any ideas? which is responsible for the contact input signals from external sensors and which pin for output for external sensors? -
Mmmm.. looks like your KRC hasn't any discrete I/O.
The only way is to add a bus system and remote I/O. There should be a devicenet connector on the MFC which would be the cheapest way to go.
Sent using Tapatalk 4
-
Wow... that robot's been cannibalized.
Well, X830 appears to be an Interbus card connection, though I'm not familiar with how it might terminate down at the lower bulkhead. Not on X13, though. It almost looks as if there was additional hardware inside the cabinet once that might no longer be there. Can you trace the cable coming from X830 and see where it goes?
X801 is empty, but may be the simplest option. Configuring DeviceNet is certainly simpler than Interbus, for the novice user.
Either way, you will probably need to buy I/O slave modules to connect to the robot.
-
Mmmm.. looks like your KRC hasn't any discrete I/O.Hmmm nice...
Can you trace the cable coming from X830 and see where it goes?I will check it
I add x13 connector diagram, please check it.
-
Can you trace the cable coming from X830 and see where it goes?X830 going to:
X15
X12A
X12BI added photos this
-
It appears that some of the fast-measurement inputs are wired to X11. And some I/O are wired to X13, although I am uncertain exactly how -- I do not see any Interbus I/O modules inside the cabinet to break out the bus I/O into discrete I/O.
The Interbus also appears to be available on the X12 connectors.You can test the X13 outputs using an electrical meter and check for voltage (should be 24VDC) when the output is activated.
However, the problem is this: if the X13 I/O come from the Interbus, your Interbus currently does not work. Interbus requires a complete loop -- the original owner of this robot would have had a cable running from X12A, out through various other devices, and eventually looping back to X12B. And the robot software is configured to look for all of those devices.
It should be possible to adjust the Interbus configuration to work with your current hardware, but only if the Interbus I/O modules for X13 are still present in the controller cabinet. The difficulty lies in knowing what the addresses of those modules are. Also, a "loop" cable from X12A to X12B will likely be required.
-
I checked all the pins at the junction of x13 and there is no tension, as if the connector does not work, also tried to give the voltage at the terminals and there is no response ...
What do you think I should do now? taking into account that I am a novice, and I know only the basics of function? -
Without being able to go through the cabinet hardware with a fine-tooth comb, I really can't say how to get the X13 I/O working.
I think the simplest route would be to ignore the Interbus entirely and use the MFC card's DeviceNet. This will require purchasing one or more DeviceNet slave modules, and the correct cabling. Fortunately, DeviceNet setup is fairly simple and straightforward.
-