What is SPI[3] tied to?
Posts by jenesaisquoi
-
-
-
I figured it out. Turns out the information on the standard devices is wrong, could be outdated I suppose, either way, this is what I did:
Under the DeviceNet board list > [NEXT] > DIAG [F3] > QUERY [F4] > ADD_DEF [F3]
That pulled up all of the correct information about the valve pack that we’re using.
Once I added that device to the device list, that was all she wrote!
-
So my issue was that the Devicenet cable was to short, so the electricians decided to make an extension, but they wired it wrong. Now we've got that all taken care of. Now i have no more Devicenet errors, however, the valve pack status on the device list is showing "error" and the module status light on the valve pack is blinking....
-
Update:
I finally got it to work! I added SPO[1]=ON in the DCS Safe I/O connect
-
I read that post also, the plugs are already the opposite as shown in the picture.
-
I don’t have much experience with Devicenet, here is me setup.
I have a R-30iA controller, R-2000iB robot and I’m trying to set up Devicenet communication on a robot end effector. The robot communicates with the PLC via EithernetIP and that’s all good, I just can’t get the robot talking to the end effector. The valve pack we are using is a Numatics G3. The robot has a list of standard devices and there is one for the valve pack we are using and that’s where I got the info for vendor ID and stuff.
I’ve tried setting it up as rack 81, but it faults out as soon as it set it ONLINE. I then tried to set it up as rack 82, it takes a few seconds before giving me the follow error DNET-060 Xmit timeout: Network flood. On the valve pack itself it says valve/output power off.
Does anyone know where I went wrong?
-
What is controlling your safety signals? Do you have a PLC?
Because if you do, the the PLC should send you a CSI that you tie to SSO[5]. For example SSO[5] = CSI[5]
I don't typically use SPI's in DCS
-
This is how I have my DCS safety IO setup (see attached). In my case, the safety signals are being controlled by the PLC.
If you're really hard pressed to jump it out, you can set SSO[5] = ON (JUST MAKE SURE YOU PUT IT BACK WHEN YOU ARE DONE TEACHING)
-
Our setup is different (see attached)
-
Does your robot have PMC?No, it does not have a PMC
If I remember, that reamer has a sourcing and sinking switch. Is it set properly?I believe so, I did what the manual told me to do anyways. It does give me a second setting though, I'll give that a shot.
-
I'm using an R-30iB controller that controls a Tough Gun TT3 Torch Reamer, (I've only ever seen reamers controlled by the PLC) but I've set up the reamer per the owner's manual. The robot can see the input signals from the reamer, but when I turn on an output, nothing happens. Also nothing happens when I use the buttons on the reamer itself for manual operation.
My question is, is there something in the robot that needs to be enabled in order for the reamer to function? Maybe something to do with safety?
Any help would be appreciated.
-
You can go into your digital I/O screen, highlight the desired output, and turn it ON or OFF from there. I believe it's F4 to turn it ON, F5 to turn it OFF.
-
So we got it to work, the PLC guy had to change a setting on his end
-
I'm guessing it would look something like this
IF DO[xx] = ON JMP LBL[1] --- just make sure to use a DO that's not being used anywhere else. You could probably use an RO as well.
Insert new master data
JMP LBL[2]
LBL[1]
Insert old master data
LBL[2]It's still going to be time consuming, but it should be easier than programming from scratch
-
1. What PLC? CPU Ethernet/IP port or communication module? What module, if any?
2. Is the robot a scanner or adapter?
3. What RPI?
3. Why the robot port1? The manual clearly says, that the port2 is optimized for fast protocols.1. 1756-L72S GuardLogix 5570 Safety Controller.
2. The robot is an adapter, PLC is the scanner
3. RPI is set to 20
4. I know the manual says to use port 2, but this is the customers standard.... -
What do you have your regulator set to? Maybe you need to increase the gas flow to the nozzle. You should have 35 to 40 PSI coming out of the nozzle.
-
I'm pretty sure that alarm on your PLC relates to one of the cards in your PLC rack not being setup on the correct firmware to communicate with the PLC properly.I mentioned that to the PLC guy says that's not the issue.
It's a new system with 3 year old robots. We've changed the location of the robot on the network, but to no affect.
-
If this is a new system, you might have to purge it for a couple of minutes to get the air out of the line, or you could have a leak somewhere.
-
I haven't tried swapping anything. The PLC has a electronic key mismatch fault...