Pictures are not loading.
Pictures are not loading.
Gavin suggested we load a different BIOS to see if the port comes alive.
phoenixbios version 4.06 rev 1.05-08.1688.01
Don't load this but i just will leave it here for reference. I need to dig deeper.
We need to secure the BIOS version you are currently running. I am unsure how to do that.
BIOS - how to do get it back to "Kuka normal". (The battery went flat while in storage )
We read this thread a few days ago and it looks like the info we need.
Re read page 36
We need to clarify the function of the " Power On/Off "
Chris please read this thread and post from Panic Mode.
Gavin is coming over Thursday night to help. Fire up the BBQ.
Any other suggestions, hints or tips welcome as we are flying blind.
If you guys come to Australia, come over and join the BBQ. No one has COVID, the beer is cold and the BBQ is hot. Remind us to take some photos.
Chris, we need to try this.
Chris and I live about an hour apart so getting time on this is tricky.
The issue is the ethernet port does not light up. I haven't worked on this stuff for years so I'm guessing we need to configure the port and that might be a bios change.
Note, ignore ip address on PC as we were trying various addresses we found in .ini files before it dawned on me the lights on the ethernet port were out.
Thanks heaps, Dave
We kicked this beast into life. It's of the hobby Arduino CNC mill.
In a wild ride of desperation we are trying to replicate the Alema computer.
If we can get the ethernet to work.
Reminder, this was turned off for many years. We have updated the little battery on the motherboard.
No lights are on.
A picture is worth a thousand words.
To clarify the above, The factory has the cable and socket on the KCP for the 6 way mouse and buttons but the factory did not populate the header pins on C13 for the cable.
We have been using an external mouse and I want to solve one issue at a time and not introduce complexities but here we are.
I have purchased this header pin to populate the C13 position 20 (21?) location (Right now it is just solid solder in the 6 holes.) I fear there might be more to the circuits and firmware than just adding the header pins but it is worth a shot.
What worked? What did you have to change?
We made the mistake of assuming the hard drive status.
We fixed a fair bit by removing the 7 axis for the 3rd time. (I want to laugh but i cannot...... well I can now but talk about frustration ) It came back when we reverted back to 7 axes when loading the original hard drive image.
Yes, three times, but in our defense we did make mistakes when we did the first and second 7th axis removal so we started again with an original HD image.
Interestingly we used the notes from page 3 of this thread to remove the 7th axis.
I am taking a recreation day to visit Chris on Friday and we will go through this methodically.
What are the chances someone has the KCP cable pin out diagram?
We have been digging around.
The Alema computer (That we do not have ) must of had significant control of the Kuka. One of the cables from the KCP to the main control board C13 cannot be mounted as the header pins have not been populated on the C13 board in the factory. As a result the 6 way mouse and tactile buttons do not work. We have been using an external mouse to configure the PC.
Apologies for the poor quality photo. the connector is mounted somewhere low on the board in I think location 20.
More in next post.
I'm writing from memory so I might make a mistake.
Under the monitor tab.
Pretty sure this is associated with Cross3.
I see 3 red I/O radio buttons.
Effectively not enabled X 3.
Guess it's communication from the remote Alena computer we did not receive with the purchase.
Working on a work around.
We are so close.
Third time lucky, we removed the 7th axis as it was part of the original setup and getting back to basics brought it back.
Does anyone know what Cross3 is?
It looks like a sub folder....
We are back to 5km travel restrictions and limits on reasons and time duration to be outside. So I cannot get to visit Chris for a few days / weeks.
I too have had production lines down for the craziest of reasons. It is the needle in a haystack and why we get paid as you soon discover only a few people can work this stuff out.
We are wired differentky and that is OK.
hard drive ribbon cable was loose.
Now back to the error message....
So I'm over at Chris' house.
Chris has been struggling with the screen as it would not boot.
I said it'll be a connector as everything has been shuffled around the workshop.
30 seconds of my arrival, and I spotted this cable was not fully home. Poor Chris is very embarrassed as he had the hard drive out to back up.
Any updates, I'm getting the same error on my KR210 (KRC205).
This is a hobby / possible career for Chris.
For me I am just trying to help him along the way as I used to work on PLC / VFD and Motion control systems but have never really worked on Robots.
Getting to Chris is an all day event and finding a free day has been difficult. (Sorry Chris)
And if you find a solution please let us know. I hope to be back there soon and we will share all of our results good and bad as we want to repay the amazing folks on this forum.
In about 12 hours we will all meet again to clone more hard drives and step through the process one more time.
We're waiting on some extra hard drives to arrive from eBay to clone, before we make a new attempt at getting it to run / move.
Overall we have leaned a lot today. We only got 3 hours on the PC and the reboots take forever.
Thanks again from me. Dave
What I did:
There where some fragments in machine.dat of the 7. axis, I set them to default. Deleted all files of Alema.
Deleted user variables of Alema from $config.dat
Set bases and Tools to default.
Set SPS.Sub to default (deleted Alema stuff)
I am blown away with your generosity of time to look into this. Just calling Chris to arrange a visit. Of course he is not answering.
He is about a 1 hour drive away so i need to confirm he is home but I am so excited.