Posts by Florida

    $OUT[4000] = ($ACCU_STATE==#CHARGE_OK) ; Output 4000 is on if Charge is ok

    $OUT[4000] = ($ACCU_STATE==#CHARGE_OK) OR ($ACCU_STATE==#CHARGE_UNKNOWN) ; Output 4000 is on if Charge is ok or unknown

    $OUT[4000] = NOT (....) ; Not will invert the status

    If a different WorkVisual Version has been used, it is possible that you get issues like that.

    Extract your project right click on the wvs file and select information.

    This will come up with project name, version, description, creation tool, modification tool and option packages.

    I run in this issue where someone modified a project that has been created with V4 has been modified with V6 and till then V4 was pretty much useless.

    I did, but I had the same issue even before changing the name. Same with the SmartPad issue.

    Please explain in detail how you changed the name. Did you perform the Reset SID of KUKA or did you just changed the name?

    During all your modifications, you may have messed some things up. A lot of actions like Computername. Shares, User and Rights have been changed and potentially made it worse. You have had a fully functional robot system before you started, right?

    Catalin Pop related to your post #22

    1. Did you ever tried to access the share with the IP-only in the address bar of the Windows Explorer? e.g. \\

    Please post a screenshot of the result!

    2. All the issues you have are maybe related to the following question: Did you change the Computer name???

    In post #22 even though I can barely read it, it shows \\KR70\Share

    Really bad that you can't ping it. Hard to tell if your IP is correct or not.

    Check C:\krc\roboter\config\user\common\knet.xml to see if it includes the entry:

    NonRealtimeIp="" RealtimeIp="" isLocalHost="true

    If so I assume, that something is not right with your User "KukaUser". Maybe the new User you created messed up something in the User Rights. And I don't know if a re-install can fix it. I would use KUKA Recovery and create a new HDD which I would use for testing. On this new Hard Drive, I would go to D:\KRC-Release and install the KSS again. If with the new HDD the system comes up with a working smartPAD connection, I would care about getting my Fieldbus and my programs back. Maybe create another Image in between.

    And only if all that is working properly and I have an up to date Image, I would look into the share and new User if really needed.

    It should work. Usually as long as the KUKA part number is the same, you can exchange the components. Possible issue you get is that the firmware on the older components has a (firmware) bug causing unwanted issues. I've had a problem on a bunch of controllers and only a firmware update solved the issue. And as soon as you change a component, you may install one with a different firmware.


    INB0=10, 18, x1 ; if 18 bytes are for RS485 (bytes 0-17)

    OUTB0=10, 12, x1 ; if 12 bytes are for RS485 (bytes 0-11)

    OUTB1=10, 13, x1 ; this is the next one...

    I agree with panic mode!

    The Devnet need to be changed a little bit:


    INB0=10, 0, x18 ; if 18 bytes are for RS485 (bytes 0-17)

    OUTB0=10, 0, x12 ; if 12 bytes are for RS485 (bytes 0-11)

    OUTB1=10, 13, x1 ; this is the next one...

    if you want you can write every single byte instead of using the multiplier:

    INB0=10, 0, x1

    INB1=10, 1, x1

    INB2=10, 2, x1

    INB3=10, 3, x1



    ;[DEVNET] DeviceNet on the KUKA MFC

    ; Entries in form 2 for driver dn2drv.o

    ; {address}=DeviceNet MACID


    ; Form 2:

    ; {token}{offset}={address},{byte}[,{multip}]


    ; {token} INB, INW, INDW, OUTB, OUTW, OUTDW

    ; {offset} byte offset of robot IO System

    ; {address} address of a peripheral device (0..m)

    ; driver specific information, see descr. below

    ; {byte} byte offset at this peripheral device (0..m)

    ; Offset starts with 0 at the every device

    ; driver specific information, see descr. below

    ; {multip} creats n dataobjects of {token}

    ; Example:

    ; INW4=10,0,x2

    ; Two words of the peripheral device with address 10 and

    ; up from byte 0 are mapped to the inputs 33-80.

    There is a good possibility that this RS485 device adds some Diagnostic data to the bus coupler. This would explain why the IO-mapping is off.

    Did you try it without IO assignment in IOsys.ini?

    Does it work again once you remove RS485?

    SmartPAD IP itself is

    I do have an older KSS Version, but I guess the following works on your smartPAD too.

    Turn the Keyswitch and press the menu button...

    in my case I see Buttons for






    6D Mouse


    Select Ping and by default it should show, if not type it in

    Now hit the button Start and check if it shows

    Answer from

    The PGNO-PARITY bit it's used to check if the PGNO sent by the host computer is odd or even? I read that the parity bit can have a negative value, 0 or positive. If the parity bit it's just 1 bit long how it can have a negative value?

    I assume if my I send a PGNO like 2 or 8 and the parity bit is set to 1 then it will return in some variable that the PGNO is odd like the one sent from the host computer?

    Can someone explain a little this concept I have some holes...

    According to the manual it doesn't care about PGNO_PARITY if PGNO_TYPE is 3.

    Now how does it work with the positive/negative number:It is configured as an Integer

    INT PGNO_PARITY=0 ;parity bit of ext. pgno

    so if you type in Output Number 666 it will look for a number greater than 0 (in p00.src)



    and write to the Boolean Variable P_RECV e.g. $IN[666] is TRUE, P_RECV will be TRUE
    if you type in Output Number -666 it will look for a number less than 0 (in p00.src)

    P_RECV=$IN[PGNO_PARITY*(-1)] ; -666 * (-1) = 666

    in this case it will write the status of Output 666 in P_RECV as well

    The difference is based on the positive or negative value that the following comparison is called with








    Would be nice to see a screenshot of the error message...

    I don't know how you share the folder, but right-click on it, select Properties, select Sharing, select Advanced Sharing and check if your user has access to the folder.

    under Share Permissions, mark your User, activate the checkbox (Allow) for Full Control, Change, Read...

    192.168.0.x Realtime OS Virtual Network Adapter visible in Windows and as an internal subnet visible in the HMI

    192.168.1.xy might be used by the KONI network

    172.16.x.x internal subnet visible in the HMI

    172.17.x,x internal subnet visible in the HMI

    Don't configure IP's in that area

    Don't have V8.6.

    Try to select Cold start in the Menu Shutdown

    Turn the robot controller off

    Disconnect Monitor

    Reboot Controller

    Wait 2 or 3 minutes until the green flashing light on the Cabinet door (top left) turns solid green

    Enable connection manager with the key on the smartPAD

    Click on T1 and on the robot name/controller name

    turn the key back to disable the connection manager

    and it should be ok!