A cylinder isn't a tire😉. Tires are mounted on rims and then f. e. on cars.
Why don't you use the endless screw direct?
A cylinder isn't a tire😉. Tires are mounted on rims and then f. e. on cars.
Why don't you use the endless screw direct?
Good old try and error.
Make the program with acceleration distance before triggering the printer.
If matrix code looks fine -> OK, if not - > make the distance longer.
Of course the post of acili17, Mom you didn't describe any problem, sorry for being not clear.
You hijacked a 7 year old thread, with a problem that has nothing to do with the original post.
You should have opened a new one.
Just an annotation:
Interrupt off 10
should be first line in Abort_sealing().
The terminator in master side is on and the terminator in slave side is off. I run that transfer configurator program and make a transfer entry(side 131) and modify iosys.ini-> pfbms and pfbms.ini, but i don't understand clearly how should i make it properly.
On each end of the Profibus the terminator must be on. So if you only have a connection from master to slave of the robot on master AND slave terminator has to be on.
Don't use mapping, set MAPPING_USED to 0. With mapping you multiply the fault sources (I never ever used mapping).
Use following entry in iosys.ini for connecting I/O in both directions.
In pfbms.ini [SLAVE] section setting
makes slave connection more robust.
Post your NCM-Manager project.
Robot program can be interrupted at (and may be inbetween) any line of the program.
That sometimes makes synchronisation a bit fiddly.
In your first post you mentioned the number 392869920 (for kuka, these are mm) and this means, that you are actually talking about 392.7 km. What kind of robot is that?
This value was an intermediate result in the calculation. The initial value was 1402 mm, that's a normal robot.
, I think WV software can be used for robot simulation too.
Definetly no.
At least you need WoV for configuring the profinet and i/O. When profinet and i/O is working, WoV is not needed for further programming, but some people find it useful.
You should switch the hmi language to English, and then post the error messages again.
Post screenshots and other things here in the forum, not on external links, those will be broken after a while, and nobody can comprehend the thread.
Did you use a Kuka USB drive?? The manual is warning for failure if not.
Joking aside:
I would try to copy the installation files to drive D of the robot and do installation from there.
Procedure of Profinet configuration changed over time.
What are the version numbers new and old?
SJX made a different approach.
Make a connection from Master connector to Slave connector on Robot. Then configure the robot as master to the slave part of the robot.
The HMI is not used at this test configuration. It is only a test if cabling and principle work flow of configuring is correct.
But about the original? What happens ?
Nobody can tell you what happened for shure. Windows doesn't delete anything without confirmation, but:
Windows creates a hidden folder 'system volume information' and sometimes makes a speed test with writing \ deleting some new data on the flash. May be something has gone been wrong during that process. Or the robot has problems with the folder 'system volume information'.
If you really need to change trajectory on the fly during an active movement, you will need RSI. What yoh are trying doesn't work, because the path planner already has planed the path before you change the values in sps.sub.
... and I know the answer is going to be to use the USB... which I don't have.
No, he has no image.
Call Kuka hotline. I see no other chance.
Try to change the line in pfbms.ini to:
WAIT_FOR_SLAVES=1
But if it is true, that the Turck Panel uses the EXOR hardware, then I doubt that you will be successfull with controling the panel with the Kuka bot. Had a short look onto the documentation of EXOR, they use a special FB for communication to the panel. So I think the panel will use a higher protocol, not only I/O. But Kuka Profibus only supports simple I/O protocol.
Edit: After reading some sheets from Turck: It may be possible that you must configure the display with Codesys before using the profibus module.
First thing I would do:
Compare all files of an old (working) backup, with the actual one. Using Windiff, Beyond Compare. ..