Posts by Reboot

some time has passed and I too had come to this conclusion, thank you all the same for your help. now it works more sensibly even if managing the seventh axis during palletization remains more problematic than a normal robot

Personally, even if I know that the configuration is saved in the backup, I always make a backup of the safety configuration.

At least if I have to restore only that one I'm faster.

Goodmorning everyone

i am having some problems with the 7 axis of a yumi 14050

I try to perform a classic palletizing scheme but in some points the robot tries to go to the calculated position by rotating the axis 7 excessively and to stay in the trajectory it rotates axis 1 sending it to the end of the stroke.

is there any way to limit or even disable axis 7?

or some other idea to avoid this behavior ...

>> SYSTEM_ID:

14050-xx

>> PRODUCTS_ID:

RobotControl Version: 7.2.0

RobotOS Version: 3.0.0

FlexPendantSoftwareUpdate Version: 1.4.0

Robots Version: 1.2.0

Wizard Version: 1.2.0

this is interesting
 2021-11-11 13:03:55 Cb_mirror.c 388 Warning, application software don't match HW, application running.

for the others I would advise you to check the internal panel power supply.

do you have a compact or standard cabinet?

Thank you.

in the end I could not define the DN-GENERIC but I solved it by adding the unit description to the EIO file

(#EIO_UNIT_TYPE

good evening

I am trying to configure a hilsher devicenet/modbus coupler on an S4 M2000.

I have the io / plus option so I should be able to do it but I don't remember if and how to declare a DN generic

can anyone help me?

or you could create an event routine with the start / restart event that sets the override for you

Sure you can do it safely but you need at least the multitasking option

in retrospect ... the robot loses calibration when it gives this error?

it often happened to me with krc2 that the temperature error was related to the drive,

in this case the power module.

I would try to check if the cables from the cabinet to the robot are not damaged, check the plugs and any damaged fruits.

then eventually you could try to change the RDW or DSE card

normally they are satisfied with the serial number, however I do not see anything strange. they will want to be sure of the installed options being an outdated robot

more than possible I would say it is sure.

I'm not sure I understood correctly but have you loaded the parameters (syspar) of one robot into another?

Yup. if you buy the master / slave option you will also be provided with a socket that must be mounted on the main computer

yes if you buy the slave only option you don't need hardware. only software option

if you buy the profinet slave option it's just a software option and you choose which port to configure it on, normally I use lan 3.

otherwise the profinet master / slave is supplied with a card to be installed on the main computer. the GSDML file can be found in the robot disk

I generally do a function for subroutines that I don't want to show to the operator, they are not viewable as they are not routine but at least if I have to make a change quickly I can do it

it would appear to be a short circuit or voltage drop problem.

I would check if the cables are intact and if the power supply has problems

Quote from Lemster68

Also, please check that the behavior is or is not the same in world and base jogging. If it is not, then you should look into the baseframe of your moc.

I agree with the suggestion and I would risk a system reset to remove any doubts

something similar happened to me with a used robot. in the end, after various checks, we discovered that an extension had been installed on axis 4 of an incorrect size and for that reason the kinematics did not respond correctly