First thing I would check for this type of cnc machine:
- List of M-Codes
- Circuit diagram
Normally the outputs are controlled by cnc code (M-commands) directly; maybe start and stop as well (depends of cnc machine)
First thing I would check for this type of cnc machine:
- List of M-Codes
- Circuit diagram
Normally the outputs are controlled by cnc code (M-commands) directly; maybe start and stop as well (depends of cnc machine)
As I said:
Vmware Workstation 15.1 for all KSS 8.x.OL versions
My former setups:
Vmware Workstation 15.1: KSS 8.2.OL, KSS 8.3.OL, KSS 8.5.OL, KSS 8.6.OL
Vmware Workstation 15.5: KSS 8.6.OL
I checked the internet "vmware and hyper-v on same machine" and one result says:
Vmware 15.5.5 and Windows 10 2004 (see) vmware and hyper-v will work together
Therefore my answer to you would be like this: NO
All KSS 8.x.OL versions run under Vmware 15.1 (only KSS V8.6 run under Vmware 15.5.5 which could coexists wit hyper-v)
On vxworks side you do not need to install the driver for a network card. In vxworks.ini you specify in the bootline which card should be used and define the ip address of the network card.
On the windows side you have to install the dummy driver for this network card. If the windows driver is used for the card windows and vxworks will write and read from that card which ends in the error 10053
Kuka has a tool KsNetCfg.exe doing the installation for the vxworks side
On the mfc3 card you have an intel network card (this card is shown in your device list
mfc3 dummy is also on that list
everything looks ok
Auto acknowledge
What do you?
The 8416 was the network card for mfc 1.
What happens if you delete this entry? Will appear it again?
you can also check this one
I do not know the Servo Robot Laser - I only can tell problems found out with other laser sensors:
depending of the type of laser the wave length of the laser light depends of the temperature.
To avoid problems the wave lenght of the laser light and the filter has to match
Basically the problem is not j5 = 0! The problem is when j4 and j6 are parallel.
In your case it is not j5 = 0, but at a different angle
Question1 :
Trying to get info on OL versions. Goal is to be able to run multiple KSS versions for current crop of controllers (KRC4 and KRC5).
So far OL license was always matching specific KSS version and there is OL for KSS 8.2, 8.3, 8.5 and so on...
Recently there were hints and rumors of license option that would allow running different versions of OL.
Is there such a thing? Maybe a whole new product or bundle? What article number?
In the past I run KSS 4.1.OL, KSS 5.6.OL, KSS 8.2.OL, KSS 8.3.OL and KSS 8.5.OL at the same time.
First it is basically a question of you host system:
- memory KSS 4.1.OL 512 MB; all others 2048 MB (my host system had 16 GB of RAM)
- CPU
- HDD
KSS 4.1.OL License Key was generated by a kind of hardware checksum
others License Key was generated by using MAC Address and some other stuff
Personally I do not think that up to KSS 8.5.OL they would change the licensing - but who knows
To add:
what type of gas?
what type of wire?
To me it looks like a end/start point
Could you provide a better view at that point?
Do you have Office Lite as well? There you would have the smartPad
correct information ould be very helpful
KRC2\KR360_2\L240\FLOOR
according to post#12 you have a KR360L280_2 H C2 FLR ZH360
OK, I did crashed a tool and if the tool is part of the robot (check T06 and T07?) - ja, sorry: mea culpa!
Crashing tools or robots (in my opion) is simply brains (after a 20h day with al lot of coffee ) much faster than physics?
In other words:
STOP at the right time
saving minutes could cost you hours of time to recover
lesson learned:
destroying tool today could you cost 14 weeks to get replacement of the tool
My question here is: Is it possible to connect my "gripper_close" output to my "PLC_gripper_close" output so the PLC can read whether the signal is on or off?
If I understand this correctly :
KRC output "gripper_close" would be "PLC_gripper_close" output to the plc?
I would do it this way:
KRC to gripper: "gripper close" (output)
"gripper close" to plc "PLC_gripper_closeD" (input for plc)
(KRC "gripper close" to Gripper and PLC- PLC ("PLC_gripper_closeD") as input
Maby I missed something?
Actually I never crashed a robot
- I only crashed a gripper
- or some other tools (but this was not the question)
could you provide a picture of that plate and it would also very helpful to give more information about
- KR C? version
- KSS Version