smahon1966

MrPLC Member
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About smahon1966

  • Rank
    Sparky

Contact Methods

  • ICQ 0

Profile Information

  • Location IRELAND
  1. DASMTEthernet and Q0nUDECPU

    How to get a CPU with built-in ethernet to communicate with the DASMTEhernet DA server from Wonderware. (I started this as a plea for help, but got it working so I decided to post it anyway for others to use) 1. PLC: Configure a TCP - MC Protocol connection for the built-in Ethernet port using any port except for the reserved range (5000 to 5009). 2. DA Server: Configure a TCP connection to that port and use the IP address and network 0 station 255 as the PLC address e.g. 192.168.1.1:N0:255
  2. Mitsubishi PLC connection with PC problem

    First you must get the USB working. Plug in the USB cable. Open Device Manager in windows and you should see a yellow exclamation mark (!) beside a USB device. Right-click to update drivers and look on your installation CD to locate the drivers. You may get a warning about driver certificates and you must choose to trust the driver or the installation will not complete.
  3. Alternatives to Step 5

    Thanks for the suggestions. I'll check them both out.
  4. Alternatives to Step 5

    Given the outrageous price of Step 5 software (in Europe anyway), can anyone recommend a good third party solution? FasTrak seems a good product, but is still quite an expensive option.
  5. SW#IVD-GPPQ GPP

    Tried that with both software products, beginning to suspect the card is busted.
  6. F1-F2 upload(transfer)

    I'm still maintaining a number of F1 and F2 projects for customers. If you're having trouble translating the code, help is at hand.
  7. SW#IVD-GPPQ GPP

    I'm having a problem formatting a Q1-MEM SRAM card in a Q2ASCPU. The QnACPU manual states that it must be formatted using SW[]IVD-GPPQ. Does this mean I can't format it with either GX-Dev or GX-IEC-Dev?
  8. GX Works 2 - Renaming Variables...

    Sorry, don't know the answer for this one.
  9. How to load special registers (W, R) on AnSH CPU?

    If they are W registers, then the values may be originating in other PLCs on a MelsecNet network. You would need to establish which PLC acts as the network master, check which W registers are assigned to each slave on the network, and check the program in each slave to see how the values are written into the W registers. If the PLC is not participating in a MelsecNet network, then the W registers just act as spare D registers.
  10. CC-Link clarification needed

    First of all your 'K4M532' question. Most PLCs can store data as single bits or as 16-bit registers, but there is sometimes a need to move groups of bits where the group size required is less than 16. Rather than allow you to move any size of group, the early Mitsubishi PLCs provided a way to move groups of 4, 8, 12, 16, 20, 24, 28, or 32 bits. To move 1 group of 4 bits, say [M100 to M103] to [M200 to M203] use the command MOV K1M100 K1M200, K1 means one group of 4 bits. So, K4M532 means move 4 groups of 4 bits (i.e. 16 bits) starting at M532 ( up to M547). This structure is a legacy from the days before arrays etc... As well as data registers in the PLC CPU, each special function card has its own set of registers called Buffer Memory Registers (BFMs). The TO/FROM commands transfer data from the PLC CPU to and from the BFMs. You need to know the header address of the card, which is not simply the slot address. If you have a 32 way input in slot 0 (X00 to X1F) and a 32 way output in slot 1 (Y20 to Y3F), then a CC-Link in slot 2 will have the header address H4, because the next I/O number would have been X40 or Y40. In your case you've identified the card as being at header address H14. For CC-Link each station writes relay devices to an output buffer at 160hex ( to 1DFhex). For CC-Link each station reads relay devices from an input buffer at E0hex ( to 15Fhex). The master's output buffer data becomes the slaves input buffer data, and vice-versa. Your command "TO H14 H167 K4M268 K1" writes 16 bits (M268 to M283) to BFM 167hex in the card. Your command at the other end would be "FROM H10 HE7 K4M502 K1" Turning on M268 in the master turns on M502 in the slave. The same is true for the following 16 bits, so M275 turns on M509, and M283 turns on M517.... P.S. CC-Link is a typical master/slave network. If the slave sends data back via its local BFM 167hex it is read by the Master from its local BFM E7hex. Any other slave monitoring the dat exchange can read the data sent from the master to the above slave by reading its own copy of E7hex and can see the data sent back from the slave to the master by reading its own copy of 167hex.
  11. GX IEC local variables

    In terms of scope of reference, GX-IEC local variables are local in the sense that they can only be references in the body of the POU in which they are declared. So, you can have a local variable with the same name, but holding different values, in multiple POUs. The reason they are persistent over time (i.e. keep their values between scans) is because the variables are stored in PLC devices that happen to be persistent over time. From my own PC programming background I tend to use local variables only for variables that could be destroyed at the end of the POU without any problems; if I need to retain the value I make it an addressed global. This is just a matter of personal habit, it will work either way.
  12. Siemens part numbers

    Is there a list or database of Siemens part numbers and the significance of the 4 or 5 letter suffix; e.g. what's the difference between 6ES5460-4UA12 and 6ES5460-4UA13? Or (as I suspect) do I have to contact Siemens in each case and hope for an answer at some point in the future?