first: "read first"
second: you messed up something completely.
Could you send the "magic glass ball" to answer your questions?
Posts by MOM
-
-
@staff members:
there is also another idea:
post the chm file as zip file (password protected)
Everyone participated can get the password to recover the zip file to the chm file
"wir schlagen damit zwei Fliegen mit einer Klappe"
(kill two birds with one stone)
What you are thinking about this idea?
PM <sorry for edit, just changed typo from 'stuff' to 'staff'>
-
ok now a bit more information:
robot-forum.com/attachment/30524/
@staff members:
can I actually upload a chm file or would this cause any problem?
-
first of all: thanx for all the feed back I got so far!
I checked about half of all the threads listed here.
There are different problems mentioned:
Hardware problems:
mainboard, mfc, vga and kcp
connection problems:
x19 and kcp
These problems will be covered in other posts
AND MORE IMPORTANT:
Ignorance of checking and following the documentation!
The kcp is the main screen for kr c1x, kr c2x!
The kcp is also the main monitor.
Therefore: you cannot change
type of monitor
resolution
If you add another monitor all what you have to do is
call sm.com in autoexec.com for some types
change the property of kvga2 device
The additional monitor is just an extension of the main monitor (and only must display this screen)
(BOF size is 640x480)
-
can you send a screenshot for both robotd showing the complete hmi.
Maybe just the manual override is different
-
I understand the problem and I will look thru my very old documents to find a better schematic.
-
-
No I have not done read2_pilot. I was talking about the first space mouse
-
kukas first space mouse (during developement) was connected via the sbc to kuka KR C32
-
Here a short description of the KVGA V2.0
-
first of all you have a kr c2 (soyo 133). Right now I can also see the isa slots. I think the problem is the resolution you set. You must have 640x480 as resolution (must be set for KCP and not for your monitor)
(also number of colors)
-
-
it is also better to use metal film resistor rather than carbon film resistor
-
I found another reason which could cause your problem.
Do you have windows 10 and vmware workstation 15.5?
You have to use vmware workststion 15.1 otherwise it will not work
-
ok,
my first draft:
-
In the next few days I will present a mind map on how I think the chm could look like. Any advice is welcome
-
-
Do you have an idea on how many i/o's are actualle have available?
According to one of your picture at least 4096 I/O!
As panic mode said the corresponding ini files would be very helpful
-
do you have a screen shot about your output modules?
-
what driver you are using?
windows driver or the driver on KUKA cd?
