Found a couple:
https://www.robot-forum.com/robotforum/fan…3052/#msg103052
https://www.robot-forum.com/robotforum/fan…79085/#msg79085
Re-read your post - these are probably more for doing the backup than the restore...
Found a couple:
https://www.robot-forum.com/robotforum/fan…3052/#msg103052
https://www.robot-forum.com/robotforum/fan…79085/#msg79085
Re-read your post - these are probably more for doing the backup than the restore...
Or is this just an alternative location for the batteries rather than the robot base?
No, the pictured machine has two sets of batteries - one in the robot base AND one inside the door. This machine has two robots. The other one has no external axis - or door-mounted battery box.
A few years ago, I used to get visits from the account manager at Servo Motors and Drives. They repair pendants, motors, controllers, etc. Found the business card - their website: http://www.servomd.com.
Another place - ex-ABB techs - is Industrial Control Repair. Website: http://www.icrservices.com.
As I recall, one type of motor was not repairable. I don't remember if it was Elmo or (probably) Yaskawa.
The *400 (2400/4400/6400) had a trailing arm where the *600 (2600/6600) could "reach over backward" (palletizing?)
R-30iA controller has batteries inside door on lower left corner.
There's a system variable that sets maximum speed - I'll have to look it up. Have you tried lower speeds to see what it'll let you run?
Here is a thread that touches on it.
I'm not seeing droppedpartinterrup...
TRAP trapDroppedPart
...
[color=red]DisconnectDroppedPartInterrupt;
What does this line (subroutine) do?
droppedPart is type intnum?
The Symbolic Constants in the OpMode function come to mind...
Not an answer to your question, but perhaps a direction to look.
I'm still looking for the RECORD instruction - my docs are for S4C+.
You have changed the batteries in robot base and the 7th axis batteries inside controller door?
These would normally generate a SRVO-087 or SRVO-065 alarm.
You might try this to reset alarm:
For the SRVO-062 BZAL alarm you need to go to MENU<SYSTEM<MASTER/CAL< and use F3 to RES_PCA and hit F4 for yes then FCTN<0<8 to cycle power on the robot again and this will get rid of that alarm. If Master/Cal is not available under your system variables window let me know and I can walk you through how to enable it.
Seems like I've seen that limit in one of the system variables. Check HERE.
New install, or has robot been running? We had a similar problem that ended up being a pin pushed back in the connector.
The label is in the top left front corner of my 6400 M96 cabinet. This robot has been refurbished, so it probably got a new tag then.
We had a similar project. Mostly, we just ignored the weld/glue stuff, although the vendor had an I/O mapped to a semi-automatic function that periodically interrupted the cycle. Our application required no grippers, so I can't help w/ that.
Then the out voltage from the battery socket 1 and 2 is 0.5VDC
Also, check batteries themselves. Sounds like you will be needing new ones.
I have several S4C+ machines on our plant network. Curiously, the IRC5 machines we had came without the software (PC Interface option 616-1) required to backup files remotely.
Precedence rules always give me fits... Parentheses help (in fact, they're required for mixed logic). Since you're gonna use it 3X, I'd set a flag=DI[197:UnloadOP20T1Chk1] OR DI[198:UnloadOP20T1Chk2] OR DI[201:UnloadOP20T2Chk1] OR DI[202:UnloadOP20T2Chk2], then use it with other conditionals. I know there are some background task mixed logic quirks I'm forgetting at the moment.
The Handling Tool eDoc has a section: 6.28 MIXED LOGIC INSTRUCTIONS
A few more tidbits:
Do the red LEDs on the processors & memory board go out? If so, try another teach pendant. When there are errors, the controller takes up to 2 minutes longer to boot. If the red LEDs stay on, then the operating system is not loading. You should try connecting to the serial port as suggested by Iowan as it should report where the boot sequence stops if it's getting that far. Can you verify the power supply voltages? Prints are in the manual With the power on, disconnect the controller batteries one at a time and measure, if they are less than 3.2V then the operating system may be corrupt. Let us know how it's going. There' other things to try depending on status indicators.Imaging didn't start until the 4.0 software / S4C+.
IRC5? (Not my strongest suit)
The "Jogging" page (or the jogging icon) should let you change modes. It may not help when stepping through a routine like BullsEye (never used it - hope to try it someday...).
Lacking a better suggestion, you might five ABB Tech Support a call/email.