IRB 4400 reinstall of baseware thinks its an IRB 6400

[Robotic Metallizing]

I have the original key disk and had some trouble installing baseware. I talked with ABB and they sent me the baseware 3.2 rev. 56 to try installing, reason being when i kept getting to disk 4 with the baseware version that came with the robot the teach pendant would display "teach pendant communication has been lost" and wouldn't restart or do anything for that matter. I had back up copies of the disks and tried using fresh floppies without any kind of luck.

Now, with the new baseware things seem to install pretty smoothly.... that is until i get to disk 4. I insert the disk, it installing accordingly and reboots the controller. When the start up is complete I then get a prompt asking to choose an install mode, as per ABB recommendation i choose silent. Next thing i know the teach pendant displays IRB 6400 and continues loading rapid, system config so on and so forth. Why is my IRB 4400 loading 6400 configuration files??? ABB doesn't know at this point and I'm in a real pinch to get this robot back up and running as temporary as it may be until the SMB can get replaced.

Has anyone ever encountered this problem??

Aside from

10002 Program Reset
10007 Program Started
40223 Execution Error
10020 Execution Error State

I also get the following error...
hijts.c 8595 sys_get_stored_obj

which is described as an internal error and instructs to report the error with the following code and describe the circumstances. I already described the circumstances so here's the code.. hijts.c8595 sys_get_stored_object status:-1

Hopefully somebody out there has some kind of idea what going on or maybe i should try query mode to install?

[0lda]

copy your keydisc on a new formatted floppy disk

[Robotic Metallizing]

I'll give it a shot not sure why that would make a difference though

[Fabian Munoz]

Why dont you try Query option ?
Maybe there it would ask you for robot type

[Robotic Metallizing]

Hi Somar,

Thanks for the reply... I will try that as well, I did do easy query yesterday and the robot still loaded IRB 6400. If I go through query type install is there a way i can get all of the details on the robot from a key file such as what options are installed? Where would this type of information be documented? The robot has been with the company longer than I have so I do not know its history. Thanks!

[Fabian Munoz]

HI:

I'm just going by memory, but, try to read the key file, I think you'll see a bunch of symbols but also you may  see 4400 or 6400 or similar to give a clue

[Robotic Metallizing]

Hi Somar,

Thanks for the response. I checked the key file, probably the first thing I did. They fey file has the s/n of the robot I'm working with and the option "L" denoting the extended arm installed. Still no luck using other copies of the key file as I'm under the assumption that the original somehow became corrupt. Any other ideas?

Regards,

Robotic Metallizing

[0lda]

copy your keydisc on a new formatted floppy disc.

[luetin]

If you think it's caused by a corrupt keydisc you can order a new one from ABB, it's pretty expensive though.

Another idea is to build a updated system with the robinstall software, sometimes it doesn't ask for the key disc and you just need a backup to work with.

[hjgts8]

Hi just a quick question if you know the software key i.e xxxbrfgh94yu4ls9 couldn't you just use a robinstall CD and generate the baseware on a computer and send it across via ethernet? Also if you have the key number I would of assumed that you would not have to request a new key from ABB, just a new disc that utilises that key.
      I'm not sure if you can access the flash disc of your robot, but you may also be able to upload a backup to your laptop and interrogate the moc.cfg file and backinfo.txt file to answer some of the questions you have about altering the robot arm from IRB6600 to that of an IRB4400. I recently have had to alter robot arms from IRB6600/2.8's to IRB6600/2.55's and also different payloads and after using robinstall I have grabbed an old backup and changed the two files listed above to make my old program work................................. Without having access to a non encrypted copy of baseware I cant help you any further, its just food for thought.....