bonjourdaisy

MrPLC Member
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bonjourdaisy

  • Rank
    Newbie

Profile Information

  • Country Canada
  1. Hey guys, I haven't been able to do much testing on this so I'm wondering if anyone else has looked into it. Basically I'm wondering what the purpose of the IP settings on the General Tab is for in the Module Properties window. Is this the IP that is used initially while doing a download to the PLC? I did a little bit of testing and assigned the General IP to something garbage and then connected my PLC. It then used like DHCP and assigned me a proper IP. Then when I went online, my IP tab was bubbled Manaully configure IP settings. So I'm wondering if DHCP is enabled by default originally? Here are the two tabs I'm talking about:
  2. Thanks for the response, sir. Just to clarify, when you say DeviceFailure are you referring to something other than the DeviceFailureRegister? I know that there is also a DeviceFailure bit which is kind of a general fault indicator for your network, rather than the DeviceFailureRegister which contains a bit for each node on the network. Yeah I'm wondering if to be safe I should monitor the GSV EntryStatus, ActiveNodeRegister as well as DeviceFailureRegister. If any of these are indicating a problem, trigger a shutdown. Thanks again.
  3. Hey guys, I've got one that maybe someone here might have some insight on. Basically, we're monitoring the DeviceFailureRegister (S register for DNET scanner module) to detect loss of comms to certain nodes. What I'd like to know, is what happens if the DNET scanner module itself fails? Am I guaranteed to obtain a fail in my DeviceFailureRegister? I've playing around with the emulator a bit and it seems to trigger the DeviceFailureRegister to basically indicate all nodes have failed when I have a module fault. But the thing is, I'm still not certain. As I understand it, this DeviceFailureRegister is an "S" register that I'm reading from the DNet scanner at my RPI. So my concern is that if I lose a connection to the module, the DeviceFailureRegister may not reflect a loss of comms to that node (ie the DeviceFailureRegister bit for that node may not have changed since I no longer have a connection to the module anymore). Does anyone have any insight on this issue? I'm using devicenet to control this motor so I'd like to know if this is reliable way to monitor my entire connection to that motor driver (from the CLX processor, to the DNET scanner, and then to the motor driver). Much appreciated.
  4. Fault Codes

    Just a quick one for you guys: Does the major/minor fault codes for a module other than a processor mean anything? I know that the GSV can't grab that type of information from modules so I was wondering why it's in the "Module Properties" page. For example, see below: https://dl.dropboxusercontent.com/u/16119840/Untitled.png Does the major/minor fault codes mean anything in this window? Or do they just reflect the processor major/minor fault codes.
  5. RS485 Common Mode

    No love for RS485 I guess!
  6. RS485 Common Mode

    My issue comes down to wiring concerns for RS485. I've read quite a few stories where drivers can be fried if the common mode voltage between RS485 devices begins to exceed a certain level (I think it's 7V or something). I guess what I'm confused about is what is the common of an RS485 driver? A lot of devices I see have three wire (SIGN+,SIGN-, and GND) so the commons of my differential signal is pretty much the same between devices (I'm assuming that for these types of devices, the signal GND is my circuit common?) But then I get into issues when there is no GND port for an RS485 device... what then? How I determine the common voltage between devices at this point? Is my source GND at that point my circuit common? But then that adds more questions: if that source is isolated from the others RS485 drivers, then I have zero relationship between commons. I'm just really confused as to how the signal is measured between RS485 devices when there is no common. And more generally, what is the circuit common of RS485 drivers. I've definitely had one experience where I was using an RS232-485 converter and it ended up frying my PLC because there was a signal ground unconnected. So I'm really trying to get a better understanding about this topic. Any insight would be really helpful to me at this stage. Thanks.
  7. I appreciate you finding that for me. I must have been searching for the wrong term. Thanks a lot.
  8. I'm not sure if anyone can help me with this... it's kind of a shot in the dark. Basically I'm confused how Unity Pro executes MAST sections. Lets say I have multiple sections in my MAST>>Sections folder (as in pic). Does test execute and then test2? Or is there some sort of switching between CPU time. I can't really seem to test this with my current PLC knowledge. I tried figuring it out myself but still can't seem to come to a decisive answer. Much appreciation! https://www.dropbox.com/s/iz8hapeqtni60qk/PLC.png