Connection manager is mode change screen. To access it you need to turn mode switch to horizontal position (CW).
There you will see list of available robots. You need to click on one to pair it with your smartPad. That is the small robot button on the left. Radio button inside it must be selected (dot must be inside radio button).
You have to do this even if there is only one robot.... your screenshot shows that you did not select it.
Posts by panic mode
-
-
-
[size=1em]Thesis? That suggests higher learning... What are you studying exactly?
Trace data is just a file... Did you try looking at it? (inside)[/size]
[size=1em]Most files are very simple. All of them can be viewed in just about any application you like... [/size]
[size=1em]
As with any other file, first I opened it in a text editor (Notepad). That was enough to recognize what is going on. Looking at the file extensions and file sizes confirmed that my hunch was right. And in no time i had my own tool to view traces in Excel. Something like this would be sufficient to you. Later I ported it to C# to get more speed and automate few things that matter to me but that's another story.r64 simply means REAL 64-bit. entire file is just a list of r64 (double) values.
[/size]
-
It is not matter of just placing some jumpers.... X11 is a safety interface meaning you need to know what you are doing. placing jumpers instead of real safety devices can make the nuisance message(s) go away but you are violating standards and making robot dangerous.
-
-
you are still not being specific. what EXACTLY is meant by "movements are not continuously possible"? i can interpret that in several ways and don't have time to pursue every option. did you read READ FIRST topic?
-
maybe....
maybe all you need to do is release any pressed EStop button (on teach pendant, cabinet or elsewhere) and acknowledge message.
-
Looks like you may just needed to pair smartPad with controller. On a connection manager screen robot was not selected. That is screen where you choose operating mode.
-
[size=2]
DEF test()
DECL INT JFOR J=1 to 6
$VEL_AXIS[J]=100 ; init speed for robot axes A1..A6
$ACC_AXIS[J]=100 ; init accel for robot axes
$VEL_EXTAX[J]=100 ; init speed for external axes E1..E6
$ACC_EXTAX[J]=100 ; init accel for external axes
ENDFOR; specify anything else that may be useful
;$BASE = $nullframe ; world coordinate system
;$TOOL = $nullframe ; use flange as TCP
;$IPO_MODE = #BASE ; base is reference (stationary) coordinate system
;$APO = {CPTP 100, CDIS 100}; First command must be a complete PTP
; for example move ALL axes to their present positions
; they will not really move but at least BCO (SAK) will be done:
PTP $AXIS_ACT; and NOW that BCO/SAK is done, we can play....
; we can move SOME of axes if we like
PTP {A1 0,A2 -90,A3 90,A4 0,A5 0,A6 0}FOR J=1 to 5
PTP {A1 45}
PTP {A2 -70,A3 50}
PTP {A4 0}
PTP {A1 0 , A2 -90, A3 90}
ENDFORPTP {A1 0,A2 -90,A3 90,A4 0,A5 0,A6 0}
END
[/size] -
[size=2]1. Read pinned topic READ FIRST It will tell you key manuals and resources (and how and where to post) as well as what to share before asking for help [/size]
[font=verdana, arial, helvetica, sans-serif][size=2]2. When referring to other resources- be specific. What manual exactly [/size][/font]
[font=verdana, arial, helvetica, sans-serif][size=2]3. First motion must be PTP... a COMPLETE ptp. It must set initial pose of all axes. Your robot seem to have at least one external axis but you only initialize some of parameters for main axes (robot axes). [/size][/font] -
This topic has been moved to KUKA Robot Forum.
-
And fix your estop
-
If you are new to robots, why are you using T2 mode?
In manual modes (T1 and T2) it is REQUIRED to hold enabling switch or drives will not be on. Without drives on, pressing start key will produce messages you complain about.
-
[size=2]clear as mud... can you please explain how is that different from what you have now? what do you mean... exactly? be specific and explain what exactly you want to do and what is not working.[/size]
[size=2]you original post was about not being able to use smartPad. this is clearly resolved as proven by your images.[/size]
[size=2]Then you said robot cannot move,[/size][size=2] but images [/size][size=small]show smartPad with drives enabled, so should be ready to move. can you move it or not? Using smartPad...![/size]
[size=small][/size][size=small]the only message shown is about IOs on KEB not communicating. this is on EtherCat and has nothing to do with IP changes. don't recall from top of my head but in general faulty IO will prevent operation in auto (AUT or EXT). in which mode you plan on running robot? do, s your controller have any IO? more specifically does it have X12 interface or anything connected to KEB? if answer is yes, and you plan on using the IO, better make sure that it is configured and powered correctly. if not, you can remove KEB from your WoV project and this message will go away.[/size]
[size=small][/size] -
Yes
Yes
Define “it was working...” -
while holding enabling switch, you will see that "I" turns green on the top of the screen. this means drives are enabled. at the same time labels next to jog keys light up green as well (right side, labels A1, A2, ... A6). While drives are enabled you can play with jog keys and robot will move (your robot is already in T1 mode).
message you see on top of screen is about IO connection to X44. most likely you did not wire X55 correctly so IO's are not powered. This will not prevent you from moving robot in T1 but you do need to address it. -
It is a built in Oscilloscope... from smartPad use menu Diagnosis>Trace
This lets you record and analyze anything. Check WorkVisual manual and search for "trace".
Axis parameters are under NextGenDrive such as
IstPosition
IstGeschwindigkeit
IstBeschleuningung
etc."Ist..." means actual
"Soll..." means commanded value -
you are correct, i don't see this specific info either. range, speeds etc are listed everywhere but not acceleration.
this will be affected by many factors such as mounting (gravity), payload, number of axes (KR10R1100 can be 5 or 6 axis), type of payload etc.
[font=verdana, arial, helvetica, sans-serif]but why not just [/font]just measure it using own program or built in Trace tool?
-
we get a lot of requests for help, specially from people who assume too much.
it is rather annoying to see yet another post without usable information... no clue what you are calling "PLC" and "DRIVE" and "RED LED".please read pinned topic READ FIRST.
-
each robot should have KUE_WEG.SRC somewhere on C:\KRC....
this tries to move robot to end point so that wrist moves as little as possible.
Not sure what the program name means.... maybe "kuerzeste weg"