I'll test another I/O module with the correct speed
Here the result: It was my fault, speed mismatch, now the 2MBD block has arriverd and it works!
I'll test another I/O module with the correct speed
Here the result: It was my fault, speed mismatch, now the 2MBD block has arriverd and it works!
Interesting, thanks
On interbus card you could switch from 2MBd to 500 kBd
Meanwhile, just as general info, if you want,
can you explain please how to switch the card between 500 kbsp and 2 Mbps?
Thank you
The couples is 2 Mbps but the Input module was 500 kbps,
so the problem was inline station speed mismatch as you noticed.
The card now is running at 2 Mbps, as the coupler,
nice to know that it can be switched to 500 kbps
out and good bye
Speechlessness... I'm waiting to test new parts (2 Mbps compatible), they are arriving monday, how can i answer this otherwise?
Are you here waiting for glorification?
This is the picture of the station, i removed the Input block and put an Output block 2MBD compliant, and it seems to work.
Humbly and gracefully thank you. Regards
Did you do a cold start or an io reconfiguration?
Yes, cold started many times
after swap the modules, did you reseted the PCI board power supply?
No, i'm not using the slave card, i have installed only the Master side, so power is not needed.
(500 kBit data transfer)
Mismatch in transferrate
OMG... Dumb error, thanks for noticing.
I'll test another I/O module with the correct speed ASAP!
I'm not able to take pictures right now,
but i can say that the product numbers are:
Coupler 2855745
Power module 2861195
Input module 2726230
Thank you
Are You also using an .svc file produced by CMD, or You bus configuration was done only with iosys.ini?
Only with iosys.ini (also because i never learned how to use IBS CMD software)
By the way there is no D LED (either RD or LD)
D LED is on the DI module
Also FO1 turns ON only if i remove the modules from the coupler and commenting the byte declarations in the iosys.ini file
Hello everyone,
i have a KRC2 running KSS 5.4,
i previously installed a profibus card IBS PCI SC/RI-LK
and i was using two cascaded IBS RL 24 DIO 8/8/8-LK-2MBD as remote I/O blocks,
i was able back then, really simply, to setup the iosys.ini by assigning
2 input bytes and 2 output bytes, this way:
Decommenting INTERBUSPCI=15
Adding in the [INTERBUSPCI] section
INB7=0
INB8=1
OUTB17=0
OUTB18=1
also setting the ibspci1.ini file by deactivating Slavering and activating Masterring, this way:
SLAVERING=0
MASTERRING=1
The system worked flawlessy.
Now i have to replace the I/O system,
so i removed the two external IBS RL 24 DIO 8/8/8-LK-2MBD
and i have to add a din mount I/O block with 16 digital inputs and no outputs.
In details i have here now in my hands a Phoenix Contact Inline Station composed of:
IBS IL 24 BK-LK-2MBD + IB IL 24 PWR IN + IB IL 24 DI 16
As configuration, i just removed the 2 output bytes from the iosys.ini file;
but KSS gives me this error: 8020 InterBus: bus error 1.?
And at the coupler module FO1 is off and FO2 is on
also D LED blinks at 0.5Hz on the Input module.
Reading the ibus.log file i can see the last line reporting
Open read data length (IO: 16 <-> Bus: 144)
So, anyone knows if i have to configure something more advanced?
Thank you
Ok, thanks you all!
Should be false.
Thanks! You are right!
I don't know why i was thinking at emergency stop while writing that parameter.
Anyways, now i can activate the on button after pressing the deadman switch,
and leave the off button always active.
But when i press the off button (Key4) without pressing the deadman switch it gives me those two errors:
Execution of Script "" aborted. Instruction 1 failed
So it is displayed, but still doesn't work.
Why doesn't this script work without enable switch?
Here is my .KFD
DEFTP CustomStatKeys
DEFSCRIPT Key3Pressed
SETVAR (FULLPATH[] "$OUT[65]", VALUE[] "TRUE")
ENDSCRIPT
DEFSCRIPT Key4Pressed
SETVAR (FULLPATH[] "$OUT[65]", VALUE[] "FALSE")
ENDSCRIPT
DECL STATKEY Key3 = { _
PICTURE[] "C:\KRC\TP\USERTECH\TEMPLATE\Bild1.ICO", _
STYLE #SWITCH, _
ENABLE TRUE, _
NEED_SAFETYSWITCH TRUE, _
NEED_DRIVESOK FALSE, _
NEED_PROSTATEO 63, _
NEED_PROSTATE 63, _
NEED_MODEOP 31, _
USERMODE 0, _
ONKEYDOWN Key3Pressed}
DECL STATKEY Key4 = { _
PICTURE[] "C:\KRC\TP\USERTECH\TEMPLATE\Bild2.ICO", _
STYLE #SWITCH, _
ENABLE TRUE, _
NEED_SAFETYSWITCH FALSE, _
NEED_DRIVESOK FALSE, _
NEED_PROSTATEO 63, _
NEED_PROSTATE 63, _
NEED_MODEOP 31, _
USERMODE 0, _
ONKEYDOWN Key4Pressed}
SET Key3 = {ONKEYDOWN Key3Pressed}
SET Key4 = {ONKEYDOWN Key4Pressed}
DECL STATKEYBAR KeyBar
SET KeyBar={STATKEY[3] Key3, STATKEY[4] Key4}
ENDTP
Display More
Ok thanks.
Do someone has OfficeLite 5.X demo to share?
I'm able to find only the 4.1.7
Thank you
Hello everyone,
i have a clone of my robot hard drive in a Desktop PC,
i'm trying to run KSS Office GUI like OfficeLite.
I succesfully reinstalled KSS with "Office PC" option selected,
but at startup, after hanging for a while at "KUKA_HMI -> Start 10%", it gives me this error:
"RTWLoadVxD( LPVXWRT (#0x1) - Device Driver could not be initialized (not found or wrong path)"
Is it the MFC driver not loading?
Is OfficeLite the only way to install and use KSS in a Desktop PC without a MFC?
Thank you
kuka_tab.mdb
kuka_con.mdb
ESCDiag.mdb
Those are system files to make KukaLogViewer work,
for example kuka_tab.mdb is the language package.
Anyways i solved!
If it is useful fore someone else, the log files are located in "Local\\KrcLog" that means "C:\Windows\System32\config"
They are files with .EVT extension, not .MDB
Use the menu "Open>Event log" to open them, not the KukaLog.mdb menu
The most important event log file to see old aknowledged errors is KrcLogS.evt
Yes of course;
reinitialized UserTech, BOF, and even cold rebooting every time
Hello everyone,
i'm using a KUKA KR210 with KRC2 running KSS 5.4 under Windows XP.
I had some problems with a servo drive that was giving some faults,
when the errors go away, it remains only a "common KSD-Error" warning to aknowledge.
Is it possible to recover a log from the previous displayed errors?
I would also see the old aknowledged warnings in case i aknowledged them without writing them down.
Is KukaLogViewer.exe useful for this case? I read that it can open log .MDB packages,
but i can't find, as i read in other threads, the KukaLog.mdb file in C:\KRC\DATA.
Should i have activated some kind of logger before?
Unfortunately i'm not able to find documentations about it.
Thank you
Solved! Thank you
I had to comment out the menu item that was previously declared in the [SOFTKEYS] section of the MenueKeyUser.INI file,
where the old autoextern Tech_Name was attached.
I made a new line for mine
I didn't get that MenueKeyUser.INI was necessary to make the technology work... Learning every day
The only problem now is that my Status Keys only work when the deadman switch is pressed
and they stop working when the robot is running in auto.
I wrote those parameters in the declaration inside the KFD
ENABLE TRUE, _
NEED_SAFETYSWITCH TRUE, _
NEED_DRIVESOK FALSE, _
NEED_PROSTATEO 63, _
NEED_PROSTATE 63, _
NEED_MODEOP 31, _
USERMODE 0, _
but it seems to not be enough (or maybe i'm putting the wrong values?)
I don't get it, from the manual 5.6.2.2 it should be correct to put 63 to select all, right?
I confirm that i have KSS 5.6.8 and 733MHz CPU, running XP
i read a lot the manual, but i didn't find a way to display a variable value (boolean) on the status keys,
are you experienced about this? Do you have a code example?
Thank you
Well.. This is why i'm asking
Since this is my first experience with UserTech
i'm not able to understand where "AUTOEXTERN.LEISTE1" was used in the previous installation, who is calling it,
and how to remove it