Posts by Alex H

I have run into the same porblem several times (with local and normal procedures)

it happend so many times for me that i started to just comment out the procedure calls even when I am just copying parts of a path

it´s annoying but i got used to it and it´s at least not a massiv pain to circumvent

Quote from Joan Murt

Because there are lots of points and I want to get it done automatically plus without changing the tool data.

on the graphical side of Robotstudio select all the needed positions and then open rotate from the right-click

keep reference on local and rotate around z, now each point will rotate in it´s place set amount around z axes

with good nameing or all positions singled out in a few paths i can rotate 100s of positions in a couple of seconds and with rotateing the positions you don´t have to touch you tool

it´s just not automatically, but few seconds manual work should be Ok

mayby i´m missunderstanding something but why don´t you just rotate the points around z the 90° you need?

cause from my understanding of your questions that seems to be what you want to do

you said project so what data did you open and was the project already on the other persons RS?

so did you use a .rssln or .rsstn or .rspag file?

I am asking cause I have similar problems with useing different windows users on the same machine.
One user can work without problems, while the other one needs to use a pack'n'go every time the first user did any changes.

So just copying solutions or stations doesn´t work for me, even when i am not even copying but a p'n'g always works

its pretty much the same, you just need to declare the new robtargets as VAR or PERS

cause a CONST is ... constant

I like to use PERS_istant but it needs to be initialised, with a VAR_iable its not needed

MODULE Test

  CONST robtarget pRobTarget10:=[[10,10,10],[0,0,0,1],[0,0,0,0],[9E+09,9E+09,9E+09,9E+09,9E+09,9E+09]];
  PERS robtarget pCenter10:=[[0,0,0],[0,0,0,1],[0,0,0,0],[9E+09,9E+09,9E+09,9E+09,9E+09,9E+09]];
  PERS robtarget pCenter20:=[[0,0,0],[0,0,0,1],[0,0,0,0],[9E+09,9E+09,9E+09,9E+09,9E+09,9E+09]];
  VAR robtarget pCenter30;

PROC Test()
  pCenter10 := pRobtarget10;
  pCenter20 := pRobtarget10;
  pCenter30 := pRobtarget10;
ENDPROC

ENDMODULE

about the robot choice

the priceing for Fanuc is pretty much all the time the cheapest, as long as you exclude options

it feels like a Fanuc can only move from A to B without any paid options and the option feel expansive

another point I experience here is that the hardware isn´t that reliable, we have at least every quarter Fanuc service here replacing motors up to half an arm on our paint robots, the ABB and Kuka we have run in worser environments without much more then the regular service

(the software side at least seems to be reliable, but feels like its straight out of 1980s )

a big point i would consider is the possiblities on offline programming (i hate to shut down production cause I need to set up a new product)

for instance on ABB you can open and edit the program files in any texteditor or use ABB Robotstudio to set up your path in 3d and fill in the logic in the included editor and test it with the controller running on your PC (and many more applications for ~1.500€ per year license)

Fanuc Roboguide and Kuka OfficeLite + Kuka.Sim would be somewhat comparable, don´t know if Cloose offers something in that regard

before i would fiddle with the connections i would at first just reset the FP (hole in the middle of the backside of the FP) and if that doesn´t help reload the FP image

thats what helped me most of the time

to reload the image press and hold the stop button+1st programmable button on power up

without downloading the zip, one question

have you set up the right configurations for the points?

(right click the point in the path and points list -> configuration)

with that i could fix similar problems in the past

the inline forms are setting their speed and acceleration themself
so settings by prior expert code will just be overwritten

so change the acceleration on the ILF itself (PDAT)

with a bit of luck you go to "Select System" and select the shown system corresponding to what was the last time running (name would be the same as in a backup) and then use "Restart Controller"

with bad luck you bricked the system and have to set up a now one from a backup and install it

and with even more bad luck you mayby need a new cf card as well

I would add ABB GoFa or SWIFTI (why the hell do we now need stupid names instead of logical number combinations) for you to look at, even as i have no experience with them as they are pretty new.

It would be comparable to the FANUC offering (GoFa is more like a CRX and SWIFTI like a CR).

Colored blocks marketed as programming but be able to use RAPID completly or just to make new blocks.

And ABB means Robotstudio, wich is in my opinion the best software from the robot manufacturers.

first step should be replacing the RDC1 against a RDC2

we had the strangest problems with a system from around that timeframe, while the problem

you describe was just the first that appeared

since we changed to a new old stock RDC2 the system runs fine, its even running so good that

we didnt had any reason to shut down the system to check wether calibration will be kept or not

so from personal experience i can just say that a RDC1 is troublesome and the research we did

beforehand indicates that the problem with loosing calibration will be fixed too with a RDC2

dont know how your program is structured, but in robotstudio you can change the name for all robtargets in a position

rightclick on the path in the station and pretty much at the bottom of the list you find the rename position option

in that you can define a index and what kind of increment you want (1, 10, 100)

thats all that i need to use most of the time

or do you want to encrypt the whole module, so nobody other then you can modify it?

if you want that ABB can encrypt a module for you