It says you can add steps, therefore there is nothing stopping you having 100 steps each 1% away, give it a try to see if it is working.
Posts by dexterv
-
-
This is a working link to the thread.
-
If you declare and initialize the variable in the DAT file accompanying the SRC it will keep the value of the counter but you must take care in situations where program was interrupted (e.g. the robot was reset) to start from the counter value you want.
-
If you create the variable and assign 1 to it every time the program is run it will always do CASE 2 since you are always adding 1 to it (1+1).
-
There are quite a few KR 6 700 robots in the configurations for VKRC (from sim pro) Just add the robot and when you are asked for a configuration scroll quite a bit down, I don't know which version you are using but there are configurations in 3.1. When you select the configuration, the controller in the virtual machine boots up and you can use generate and load.
-
It is not that important that you didn't find the correct robot during installation. What you need to do is follow the installation instructions and install VRC Manager - this is done on the virtual pendant: Start> Additional software>New... When you have the VRC Manager running shut down the robot - so that only VRC Manager is ON. In sim Pro click connect, enter the domain name of the VMWare machine (make sure you can ping between real and virtual machine) and when there is a connection you can pick the type of robot (configuation) to boot.
-
Hey, I am looking into what is the procedure to change the KSS version in OfficeLite, is there a download server where you get a new virtual machine image or do you update it like on an actual robot - if so where do you get the files from?
Additionally if we have a license which came with KSS8.3 can we use KSS8.5 for example? -
I am having trouble understanding the parity bit configuration for AEXT. I got from the manual that we are specifying the bit at which the parity bit will be sent (e.g. $IN[777]) . But then the manual states that for Odd parity the input is negative value, 0 if it is not to be evaluated and positive for even parity. If I set it to 0 it states error when displaying the AEXT signals is this correct? Also if I want odd parity on $IN[777] do I enter -777 as the value?
-
Thank you for the reply. I was theorizing in a very different direction, I thought it would work through some other means than EIP as a second layer of comms.
But what you said is most probably true. What bothered me was that the bit offset was up to 800 and with your explanation it clicked - the IO instances I set were 100 bytes long for the EIP and 100*8 = 800 bits, I changed them to check and sure enough for 200 bytes it was 1600. -
I am having trouble understanding the usage of the Bus error bit in the Local Slave configuration of EtherNet/IP. I read the manual and it states that the bit is send to the PLC in case of a bus error. Which sounds like something useful but I find the description in the manual to be very vague.
If there is a bus error how is the bit communicated to the PLC? Also in the manual the bit offset is a number between 1 and 4000 which leads me to believe it is the number of the bit in the IO space. But in WoV you cannot set anything above 800. I tried setting it to a high offset e.g. 600 killed the scanner and got Field bus error as expected, but nothing changed for bit 600.
Can someone share some wisdom what that bit is and how to use it?