Your KCWin32 image is not very clear.
Have you set correct port number in options and are you sure cable is correct?
Your KCWin32 image is not very clear.
Have you set correct port number in options and are you sure cable is correct?
Is cable null modem cable?
With KCWin32 open and cable connected to front of controller.
Configure Com Port options to match Com Port no. (device manager of PC), no other settings required.
Power up controller.
What is displayed on KCWin32 application - Can you post image?
Without spare parts, it is difficult to troubleshoot further.
Can you download and run KCwin32 application from here:
You will need correct serial cable (null modem or just pins 2-3, 3-2 and 5 to 5) to connect to PC
yes i have access to spare parts
What spares do you have access to?
Do you have spare 1HP or 1GA/1HA?
1. Is X1 connection on controller door connected correctly?
2. There is small potentiometer adjustment on bottom of MFP, if you adjust this does screen appear?
3. Are there any pushed in pins in X1 connector/MFP connector?
4. Have you dropped MFP?
5. Have you another MFP you can plug in?
6. You should replace battery pack on inside of controller.
Please answer all questions:
1. Can you explain where you read in this forum the procedure to resolve this?
2. Do you know status of batteries inside controller?
3. Do you have any data sheets supplied with controller when you purchased it?
4. Locate red dipswitches and set 1 and 8 to ON and power controller up - post image of MFP display?
Download Zeroing and Motor Replacement Manual for R Series.
Then drive all joints to scribe lines and carry out section 2.1, followed by section 4.0.
If you cannot drive all joints to scribe lines first, carry out section 2.1 first.
Then drive all joints to scribe lines and carry out section 2.1 again followed by section 4.0.
Please create a new thread, this thread is now closed.
the fisrt time i have run the controller, i have sea error (1800) AC POWER OFF with a keyboard in the MFP screen only
I have read in this forum how resolve this problem with initialisation procedure
1. Can you explain where you read in this forum the procedure to resolve this?
2. Can you provide images of inside of controller?
3. Do you know status of batteries inside controller?
4. Do you have any data sheets supplied with controller when you purchased it?
Without backup, there is no way to recover controller to as you received it, it will require reconfiguring.
Yes, you should create new topic.
When using linear interpolation modes (Base, Tool), controller controls TCP along straight line.
JT6 will always rotate as controller is maintaining path.
TCP orientation should not change.
Are you saying TCP is also rotating?
Irrespective, when encoder battery is exhausted, unless correct procedures have been followed, then re-zeroing is probably required.
R Series zeroing manual can be found here:
Welcome to the forum............
Can you provide answers to the following:
- Image of inside of controller and rating plate.
- Status of controller before problems occurred - was it running ok, error free.
- What was last thing that happened before problem occurred.
- Can you confirm ALL harnesses internal and external are of good connection and secure.
- What specifically you have done to rectify problem - include ALL details.
- Have you access to spare parts.
- Do you know how to use KRTerm/KCWin32 app and connect PC to controller.
- Do you have controller file save - ie controller data backup before problem occurred.
- What is your current experience with Kawasaki.
In most cases this is down to installed firewalls blocking the Virtual Controller/PCAS applications from running, asproc.exe is the main application that requires allowing through firewalls for each virtual controller used.
It could also be that the controller and arm selected is not available due to license restrictions.
From an installed demo perspective (never experienced it before), I would assume this could purely be firewall related.
You can see the live status of io by typing in the keyboard or editing app:
io1 and enter (displays 1-32 and 1001 - 1032 and 2001 - 2032 signals)
io2 and enter (displays 33-64 and 1033 - 1064 and 2033 - 2064 signals)
Glad to hear it's working.......
The command ioboard_status still cannot find any board. But the input signal can be read by bits function now.
Yes, I am pretty sure this command is purely intended if you are using 1TW in conjunction with 1UR board.
If just using 1TW, then I think ioboard_status command is redundant and should not be available in my opinion - maybe a bug in the software...........
Like I said, Kawasaki IO can be frustrating when it is not supplied as standard.
Welcome to the forum.............
No problem.
When you have loaded the file in, connect up CN2 and CN4 and try sending IO.
Kawasaki is a pain in the neck for IO configuration if not just supplied as standard.
Then connect up your IO to 1TW board CN2 and CN4 and try sending some IO.