I tried to do do system initialization, and I'm afraid that I have wrong value on motion and servo mode.
Loading in the previous backup will restore that.
The backup you made prior to carrying out the system initialization.
I tried to do do system initialization, and I'm afraid that I have wrong value on motion and servo mode.
Loading in the previous backup will restore that.
The backup you made prior to carrying out the system initialization.
My question is, it seems like the K-ROSET isn't a total package, other software needs to be downloaded as well?
Incorrect.
It has ALL features available to design and program a cell including IFP design and programming.
The attached video shows programming and IFP implementation within KRoset instead of having to use KIDE or KTOOLS
Software such as:
- KIDE
- KTOOLS
Have been developed as standalone side tools and are separately available.
From memory KTOOLS requires purchasing and KIDE is a free application.
From a newcomer perspective, I would recommend either KRTerm or KIDE as they are both the official Kawasaki dedicated applications developed by Kawasaki.
KRoset has a perfectly usable IDE and can be used in parallel with KRTerm or KCWinTcp by selecting 127.0.0.1 and port 9105 (1st single robot)
KIDE also has a support forum here:
Sounds like the robot has had a collision as this error is not related to zeroing.
Is this error occurring regularly?
Is this occurring in repeat and teach modes?
Can you replicate this error in teach mode by manual jogging when the error occurs?
If this error is frequently occurring, then I suspect wrist assembly requires inspection for damage or repair, this error is not a zeroing issue, but mechanical.
So the MFP is functioning, just no display.
That could either be the backlight, the inverter board, both, possibly loose connections inside, capacitor (aging issues).
The backlight can be replaced, but not for the faint hearted, but from your results that's what it points to.
cguenther could you assist with this with your 'stock' at all?
benderservices send cguenther a conversation, he may be able to assist in some way here...
It's only idea. If I will have second c80 can i do backup from second robot and download to my c80? Can it repair my problem?
Not unless you know how to modify a Kawasaki backup to suit.
Assuming your 1GM is correct for the installed 1GB and variant of arm, go online with the controller, type in ZROBOT and go through the process to set the arm model you are using.
Welcome to the forum.........
Two battery assemblies exist:
1. SRAM battery for programs and user data (located on the side of the card rack inside the controller).
2. Inside the UX arm for encoder backup (located behind the black rear cover on the UX arm).
Both battery assemblies are current spare parts and considering the situation of that controller, I would recommend they get replaced.
You can power the logic without 3 phase supply.
You can supply a single phase supply to the AVR (you just need to make a connector).
If you do this, the logic will power up (you will get errors), but you can make a backup that way.
Whether the configuration is valid or not, no problem in setting it up as long as the hardware is functioning.
If you are in the UK, I can come and visit for a fee and get you going and provide some training if that's something you wish to discuss offline - send me a conversation request.
So I call to astor and tell about situation. They told me, they give me in future program/instalator something like this to change soft inside small board on PB. I don't remember but probably it is 1GM or 1HM board.
Get Astor in to resolve your problems as at the moment, since your #1 post, you have systematically taken the controller apart, sent all boards away for repair, had bad connections and now have an unusable controller, so from my perspective, you have a controller which is a box of nuts, bolts and circuit boards.
A previous backup would have resolved your latest alarm 100% guaranteed - if:
1. The backup was made prior to your #1 post (which i don't believe it was).
2. The hardware is correct and functioning and the 1GM board is correct.
3. The AS/SV firmware installed in the CPU board is correct.
Could be power block or MC unit issue.....although I'd be inclined to say MC unit from experience.
Go around ALL the connections to the power block and MC unit and ensure they are ALL secure, it may just be a loose connection.
Kawasaki have excellent harnessing and connectors where there is always a positive click, so give them a good old push, wiggle and tug.
The MC unit distributes power to the power block via internal K1, K2 and K3 contactors.
Discharge resistor is connected across an auxiliary of K3 which is in series with the P-N line, and is used to discharge the capacitor inside the power block when no motor demand is made and be switched out of circuit when motor demand is requested.
I would check:
- K1, K2 and K3 contactors for correct switching, good continuity and no 'coil creeping'
- K3 auxiliary is switching and good continuity.
- Discharge resistor connected to K3 auxiliary.
*** WARNING/CAUTION ***
If the discharge resistor or K3 auxiliary are faulty, the capacitor in the power block may not discharge.
Therefore a hazardous potential is likely to be present.
Please use a DVM on X302 (MC unit) across B1 and B2 and ensure the DC voltage has discharged to a safe value before disconnecting and removing the MC unit for inspection.
Never come across that before except where the harness as indicated in the manual was not seated correctly.
Sounds like a faulty unit to me as the fault transferred across.
Nothing else I could add unfortunately.
Imagine a youth and fresh programmer that decides to wipe out all the user part without do a copy of the CIO and then waiting for a week a good CIO to reload
We have all been there.
Just dive in and make changes without backup first....... + =
I put things at the end on numerical order. My OCD won’t allow anything otherwise.
get out of jail free condition. Scenario comes up, how to get out of it. Maybe I want this only active in teach but not play. Or an output to bypass a condition.
We have the same OCD, as this is what my 'inner voices' force me to do too.
Looks like I have an open book to explore without opening too many rabbit holes.
Many thanks for the clarification on my points.
Thank you 95devils, much appreciated.......
General question really regarding CIO part 2 (User).
Understandably, I can save the CIOPRG and reload it in, so testing is unlikely to permanently brick the controller.
Somethings I am about to play about with in anger and just thought I'd ask the forum first.
1. Is it safe to wipe the OEM supplied ladders in part 2 (User) without removing critical operational ladders?
- I just assume ALL IO exchange between user interfaces/fieldbus interfaces will stop working - no mapped Specific IO for automatic operations etc and GPIO exchanges etc.
- Will anything else likely to stop functioning with an empty part 2 (User).
2. Do people usually wipe part 2 and create their own specifically to the application or modify the OEM supplied to suit (I appreciate the path of least resistance is favourable)?
3. If you do modify the OEM supplied, do you usually just add the mods to the end, or do you sometimes have to delve into the rabbit hole and add the mods in the already existing ladders.
4. If you do plan to wipe it clean and create your own, are there any do's, don'ts or pitfalls to look out for or be aware of?
As always any advice/opinions/pointers are appreciated....
Load in a previous backup.
You can also try the 'Unknown Tool method' described in the AS Language Manual.
I call it the A+B method as that's all it uses.......2 points.
Works really well too, only drawback as it's described you need to unmount the tool to access the flange.
What is it with people wanting more elegant solutions.
If it works and ticks all your boxes........why is elegance so important....
KISS it...........Keep it Stupid Simple.
Good to hear, simple IO exchange when you have the fieldbus correctly configured and allocated is always the simplest method, but has it's limitations when it comes range values.
You could always try TCP/IP instead if you have a server setup for communicating that way, but that would take more than 30 minutes to get going but would work just as effectively.
Like I said AFAIK Arc welding firmware was never released for those series or arms as arc welding is usually applicable to small reach and low payload arms.
Maybe Kawasaki did some 'development firmware back in the day, but I never came across any.
Only just recently have they released arc weld firmware for higher payload robots, but this is incompatible to C and D controllers.
You need a training course buddy, as what you are asking here on the forum is all fundamental stuff covered in the most basic of training courses and to keep addressing these areas on the forum is no substitute.
So I suggest you read the operational manuals regarding BLOCK programming that your using as ALL of what you ask regarding stopping at each point is in that manual.
AS Programming is code language based which gives you more complexed, flexible and powerful instructions over BLOCK, but again, with AS you can achieve what you have written.
ACCURACY and CP SWITCH
Look into Aux 0802 which is used to prohibit editing and recording programs including loading.
Look into Aux 0897 and 0898 for setting auxiliary functions accessible based on operation level access.
Look into Kawasaki 'optional' taught program protection function.
These are the available and simplest features in Kawasaki.
However you could write a PC Task to control access with passcode and forcing interface panel pages (IFPDISP and MAINDISP commands) to be displayed, reducing access capability but this is a not a documented feature therefore you must code such measures in yourself.
And ashamed to admit I am Certified but, combination of switching between robot types as an integrator and using a new laptop forget some of the basics every now and again.
No shame at all, difficult to remember things when alternating between OEM's., I'm in that position at the moment between Kawasaki, Fanuc and Yaskawa.
Glad you got it sorted in the end and thanks for letting us know......
USB is not plug and play and USB drivers from Kawasaki for CS configurator are required to be loaded in before connecting.
Sometimes digital signature for driver installation is blocked by windows (usually message appears during driver installation) and you need to go into PC Settings to disable signature check.
This is an IT issue with windows, not the application.
Did you install the USB drivers for CS-Configurator?
USB drivers should have been supplied with CS configurator application from Kawasaki.
You should really have Cubic S training before using, as installation, configuration, setup, testing and verification of Cubic S safe operations are covered during training.