Posts by SomeTekk

    See if there is a momentary difference in potential between A1 and A2 on K3 when the joystick is deflected.


    If there is a flicker there's something wrong with K3. Since the coil didn't energize the system can not detect the brake signal via the aux contacts.


    If not, tracing the brake release signal will need to be done starting with the Panel Board.

    Could you please describe what characteristics you are looking for in a seeming pseudo-hybrid task?


    Also, is there something undesirable about 2 motion tasks?

    Using pure guesswork, I am wondering if the instruction WaitTestAndSet might be of use for your project.

    A LOT more crass than Lemster's solution (provided your system has multitasking) would be to monitor the group input you have with a background task (monitoring activated by a persistent Boolean variable & using the desired robot for the task's Use Mechanical Group) in a WHILE DO loop then stop once the condition is met.


    WHILE bMonitorActive DO

    WHILE GInput(gi_LaserValue)>nDesiredHeight DO

    WaitTime 0.001;

    ENDWHILE

    StopMove;

    bMonitorActive:=FALSE

    WaitTime 0.001;

    ENDWHILE


    Yes, this is only a snippet.

    The Error Handler idea I posited will do that.


    So this is the basic search scheme, Box 1 - Box 1 — Box 2 - Box 2 |Home , correct?


    You can combine the Cases so the iterations try that way.


    nFailCount=1 & 2 can retry Box 1, nFailCount=3 & 4 can retry Box 2, then on the fifth fail the DEFAULT action of operator intervention occurs.


    Test ...


    Case: 1, 2

    ... Box1

    RETRY

    CASE: 3, 4

    ... Box2

    RETRY

    DEFAULT:

    ...

    Better Rapidteers than me will have superior ideas.


    Add a counter to your Error Handler that increments each time the specific error occurs then Use a Test Case instruction for your conditions.


    IF ERRNO=ERR_WHLSEARCH THEN


    INCR nFailCount


    TEST nFailCont


    CASE 1:


    ...


    RETRY:


    CASE 2:


    ...


    DEFAULT:


    nFailCount:=0


    TPWrite "part not found!";

    TPReadFK reg1,"Robot go home?",

    "YES","stEmpty","stEmpty","stEmpty","NO";

    IF reg1 = 1 THEN

    TPWrite "Robot going home!";


    Don't forget to reset your counter before the first search.

    Eli –


    Find the Operating manual IRC5 Integrator's guide (3HAC050940-001) and investigate Chapter 8 Calibration.


    Section 8.5 explains SMB memory.

    IF you are asking about ABB IRC5 controls, see below. If not, as much correct data as can be supplied is helpful provided you are seeking info regarding ABB robots.


    It is suggested to consult the IRC5 Parameter manual regarding Auto Condition Reset


    Control Panel > Configuration > Topics > Controller > Auto Condition Reset > AllDebugSettings > Edit


    If Reset is set to YES then the following conditions are reset when switching to

    auto:

    • The Program Pointer (PP) is set to Main module for all tasks if call chain does

    not originate from Main routine.

    • All tasks are enabled.

    • All stopped background tasks are started.

    • Simulation of all simulated I/O signals is removed.

    • Speed is set to 100%.

    • RAPID Spy is deactivated.

    If Reset is set to NO, then none of the above conditions are reset automatically.

    If a service routine is running and PP was manually moved to another routine

    before the service routine was called, then the above does not apply. Switching to

    auto will then be rejected.

    Off the cuff stuff as an untested experiment (lots left out):


    PERS string PeskyModuleName {x}:= ["", ... ""];


    For i FROM 1 to dim (PeskyModuleName) DO


    IF NOT ModExist (PeskyModule{i}) THEN

    StartLoad (PeskyModule{i})... ;

    WaitLoad (PeskyModule{i})... ;

    ELSEIF ModExist (PeskyModule{i}) THEN

    EraseModule PeskyModule{i};

    StartLoad (PeskyModule{i})... ;

    WaitLoad (PeskyModule{i})... ;

    ENDIF

    ENDFOR


    Insert Error handling


    Cheers! :weissbier:

    FYI - It seems like there is an errno you can build a handler for pesky Unload issues:

    ERR_UNLOAD

    The file in the UnLoad instruction cannot be unloaded because of ongoing execution within the module or wrong path (module not loaded with Load or StartLoad).


    This is right out of RS 2022.2 documentation.

    It is advised to consult the attached PDFs as well as the pasted text.



    Populate the stick text:
    * Run "InstallSFDService.bat" first time only

    * Run "UFloppyManagerV131_OEM.exe" This starts the driver utility.

    * - From this screen you can double click any virtual floppy and interact with the contents.

    * - You can also right click & format any USB stick you put in your computer. Make sure you know which one you're formatting if there's more than one!


    ** To populate the USB stick with install disks:

    ** - Open "My Computer" and navigate to your floppy drive.

    ** - Insert your first floppy - the key disk for example

    ** - Edit/Select all

    ** - Edit/copy

    ** - In the UFloppyManagerV131_OEM program, double click a virtual floppy. This will open a new instance of Explorer (my computer)

    ** - Edit/paste.

    ** - VERY IMPORTANT - CLOSE THE NEW INSTANCE OF Explorer (my computer) THEN RIGHT-CLICK THE SAME VIRTUAL FLOPPY AND SELECT "SAVE".

    ** - It is suggested that you keep a separate USB stick for the install disks. Put the key disk on floppy 000, and disk 1 - X on floppies 1- X.



    ---------------------------------------------------



    README file:

    64 bit windows instructions:


    Run InstallSFDService.bat


    Run UFloppyManagerV131_OEM.EXE


    Use FloppyManager


    Run UninstallSFDService.bat when finished


    Error code: c - happens when user tries to copy a folder, rather than the contents of a folder

    disc.1 for example, rather than the contents of disc.1



    MFG Notes:

    UFloppyManagerII V1.30/V1.31


    UFloppyManagerII V1.30/V1.31

    Update information :

    1.Support long filename format.

    2.Support 2000/xp/server2003/vista/win7/server2008 32/64 bit operation systems for any privilege accounts.


    Usage information:

    Under Vista/Win7 64bit OS and Guest privilege user,must running the QH_UFDD\InstallSFDService.bat file at first time by Administrators privilege,otherwise the UFloppyManagerII.exe will not working.

    First of all, good luck! Incorrect commutation is an invitation to disaster, including destroyed motors and other equipment.


    Based on a hasty review of different era ABB robots' manuals it may only be possible to commutate external axes. From a C+ manual:


    The robot motors are commutated on delivery.

    Commutation is only for external axes.

    For more information about commutation see the External Axis Manual.


    Older than C+ look in the manipulator's Product Manual.

    1st, there isn't some third party cable, or cable reel, used is there? If so try an ABB cable.


    2nd, if you want to reflash the pendant as DAMO suggests, have someone cycle power to the control WHILE the stop AND programmable button number 1 are held down. It is suggested to hold the two buttons down until red text indicates


    Image is not present. Downloading start.


    Release the buttons and wait for the pendant to complete the reflash. Alternatively the reset button on the back of the pendant may be pushed whilst holding stop AND programmable button number 1 down and wait for the red text.