It's been a long time since I touched an S4C control, so the suggestion may be off-base.
Have you tried pressing the Misc key then look for the text Production?
It's been a long time since I touched an S4C control, so the suggestion may be off-base.
Have you tried pressing the Misc key then look for the text Production?
Over the years I learned, I am not certain of the reliability of my learning , that when errors were encountered.
SYS HALT ERROR - from servots.c,1346
SYS STOP ERROR - from ipolts.c,2792
there was a problem with the measuring system. I recall that the sys halt stuff was a problem in the axis computer, cabling, or SM Board.
Also, this text
94-01-01 10:03:22 type = ERROR id = HARDWARE code = 8001
arg 0: 1.000000 arg 1: 0.000000 arg 2: 0.000000 arg 3: 0.000000 SYS FAIL - from c25.c,1326
indicates a hardware fail. (Good old 8001 code, in S3s that was REALLY bad)
Perhaps SKOOTER or LEMSTER will weigh in.
Spitballing here:
Try only:
3HAB2317-1/13
3HAB2331-1/00
3HAB2319-1/08
Perhaps contact with ABB is order to ensure the PROMS being used are correct.
It looks like someone was kind enough to send you ABB WebConfig info about your system. The mention of S4 TopHat indicates this was a GM robot at some point.
Is the positioner integrated with the ABB control (if yes, HOW is it integrated?), what version of control, what version of RobotWare?
It's difficult to supply answers of any value without that information, as a start.
S4, not the ancient days, but creeping into the description of 'olden' days.
Not sure it is dependent on robotware (or whatever the REAL early '...ware' was named) but take a look in the system motor calibration parameters for fields indicating Valid comm (commutation) Offset and Valid cal (calibration) Offset and ensure the YES/NO fields are YES.
Look >> HERE <<
There are both fully licensed and disabled licensed RS in this facility. Only the fully licensed version displays the RAPID Call Stack.
If you have the fully licensed version and you don't see the call stack you may be able to recover it by invoking the Default Layout.
PS — I think %"ProcName"% is referred to as late binding.
Make sure RS is on the RAPID tab. That's the only place I see it.
If you right click on the RAPID Call Stack tab (as can be done to LOTS of tabs!) you can break it out of the tabs and resize/place it/them wherever you wish.
Don't know about the safemove aspect, but here is a really hacky possible RAPID work-around.
Create a virtual input(s) and a output(s) on the virtual bus and cross connect the outputs to the inputs for affecting axis speed limitation. E.g. vdi_SpeedLimAx6, vdo_SpeedLimAx6. Also, there will need to be a system input, or SOME system inputs, parameter added for the Limit Speed action.
Next find your problem code spot and right before it insert this.
IF OpMode()<>OP_AUTO THEN
SetDO vdo_SpeedLimAx6
SpeedLimAxis ROB_1, 6, 20;
ENDIF
Maybe make it Procedure with data or a function ...?
Yes, it is advised to reset the slowdown, by resetting the output, somewhere in your code, say in a housekeeping routine.
As indicated above it is a hacky solution.
Or wait for the better answers wiser techs than I will suggest.
Experiment at your own risk!!
Poking around where Massula indicated, this was found:
<?xml version="1.0" encoding="utf-16"?>
<ProcessDefinitionDocument>
<MoveInstructionDescriptions>
<MoveInstructionDescription name="MoveAbsJ" motionType="Joint" informationText="">
<InstructionParameterGroups>
<InstructionParameterGroup>
<InstructionParameter name="Conc" dataType="switch" accessMode="In" optional="true" />
</InstructionParameterGroup>
<InstructionParameterGroup>
<InstructionParameter name="ToJointPos" dataType="jointtarget" accessMode="In" optional="false" pointType="ToJointPos" />
</InstructionParameterGroup>
<InstructionParameterGroup>
<InstructionParameter name="ID" dataType="identno" accessMode="In" optional="true" />
</InstructionParameterGroup>
<InstructionParameterGroup>
<InstructionParameter name="NoEOffs" dataType="switch" accessMode="In" optional="true" />
</InstructionParameterGroup>
Maybe try ' "false" ' ?
The answer is likely going to be call your local ABB and schedule service.
There is very, VERY little ABB shares about internal errors.
One tactic you may want to try is (1st) If possible make a backup!!! Next, clear out your event logs, restart and look for events in the same time frame.
Good luck.
Hello,
Is there a way to prioritize background task execution?
One of a few tasks is much more important than others in the RW 5.15 systems on the production floor and any manner of keeping that one task getting as much cpu time as possible is the goal.
Thanks!
Another couple possible causes:
Potentially high-end stuff.
You may want to look into tuning your servos. It is not an easy thing to do until its been done many times.
Download ABB's TuneMaster app and check it out, it's free.
What type of digital IO, discrete (voltage) or networked?
Ethernet/IP outputs have been simulated here and have been accepted by the connected PLC. However, this example is not a welding system.
If I remember my S4C+ history (nowadays almost ancient history ) A3 is not an axis designator, but position in the cabinet. I think C+ controls had nearly all multiple motors connected to the various drive units, 6400s 3 2 axis units, 1400s 2 3 axis units and a dummy box for air flow, maybe
4400: Hint A3 drives axes 3 & 5
Thank you so much for that info. I will try to pull the hard drive if there are really no other options.
Should I presume that you are saying that there is no sort of scanner that is built in that will let me do this?
Regrettably your presumption is correct, at least as far as my knowledge goes. Lemster, Skooter or someone else may have more thorough knowledge about this than me.
To repeat, the likelihood of success, using my described suggestions, is very small.