MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About vds

  • Rank

Profile Information

  • Country Australia

Recent Profile Visitors

228 profile views
  1. Hi! This is a strange issue where an older version works as expected but newer version does not... (logic changes only... hmm...) Intuition says it's not logic related but some other obscure setting such as firmware version. Get your PLC guys to check the version of Studio/RSlogix being used and see if there is a PLC firmware difference, eg Version 20 vs 21 vs 24 (check major and minor versions) etc etc... While they're at it, get them to check ethernet module versions are also configured identically between the working and non-working project - see screenshot...   good luck! vds
  2. software information

    If you have RSLinx Gateway or Professional, you can use MS Excel with a DDE link to read N registers etc. With RSLogix 5000, there is a tool for reading and saving all tags to a CSV file but I don't remember an equivalent for SLCs. good luck! vds
  3. Micrologix with 2 ethernet

    Hello, depending on what you are trying to do with the second Ethernet port, one option may be to use the serial port of the MicroLogix in Modbus mode (master or slave) then use an off the shelf Modbus/RTU to Modbus/TCP or EthernetIP converter to push/receive your data via Ethernet connection - your consuming/producing device would need to support the relevant protocol on the Ethernet side... there are plenty of converter/gateways eg, Moxa, ADFWeb, RedLion etc etc good luck! vds
  4. Help: Basic Program Question

    I politely disagree - the CTU instruction will itself look for a rising edge on the enable. The only true way to fix this is to use a short de-bounce timer - but...well ... that's an "advanced" instruction for this exercise...  cheers! vds
  5. ASCII Comms issue

    Oops typo on rung 5, EQU instruction should be comparing for 4 not 3...
  6. ASCII Comms issue

    Hello, Please refer to attached sample code - sorry I don't have RS500 with me so have prepared sample in RS5000. Hopefully it is descriptive enough - is uses a state machine to shuffle along the different steps, then returns to the beginning. Regards, vds   ASCII.pdf
  7. ASCII Comms issue

    Hello, It's been a long time since I've done anything ASCII related, but here are a few comments: 1. Try synchronising your reads and writes more logically in a sequence. Currently your trigger to Write is completely disassociated with the ACB and ARD. This might cause some timing issues if a write and a read execute simultaneously. You could try something like: Step 1 - issue AWT instruction. Step 2 - wait for AWT.DN bit + ?2? second delay (delay long enough for device to reply). Step 3 - perform ACB instruction Step 4 - upon ACB.DN, check buffer length >= 62 and perform the ARD instruction. Step 5 - Go back to Step 1 2. If you know your response should start with a particular pattern, you can check for that pattern using additional ASCII functions such as AEX etc - Refer to chapter 10 - http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1747-rm001_-en-p.pdf   Good luck!  
  8. Tag description to string

    Hi! I've done this in the past by doing a tag export to CSV file to get the comments, then using an excel spreadsheet and DDE (with RSLinx) push the tag comments into the specified string tags. This is obviously a very manual thing and in my case only needed to be done once, so if you're looking for a dynamic way, then this won't do it for you.. I'm not aware of any other way to do this... Good luck! VDS
  9. Totalizer using AB 1400

    Take a look at these discussions - you need to integrate your actual value at period interval:   vds        
  10. Troubles with AOI PFlex 700

    Robert,   Not sure where that AOI came from, but it looks like it's asking for the Input and Output structure which is created automatically when you add a drive into the network tree.. see screenshot below where I added a Powerflex 700 drive under the ethernet module and called it "Drive". This creates 2 Global tags, called "Drive:I" and "Drive:O" of data types "AB:PowerFlex700_Drive_Parameters:I:0" and "AB:PowerFlex700_Drive_Parameters:O:0" respectively. I believe this is the datatype being expected by the AOI as there are parameters similar in names as per your image above. Try changing the tag "fg" in you AOI to "Drive:I" and "gh" to "Drive:O"... [note - substitute for correct drive name in your I/O tree]...   good  luck... vds  
  11. PLC Program for 5 sensors

    This should work as described:
  12. Need help

    Hi, see wiring diagram below.. (pg 165  -http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um058_-en-p.pdf) have you wired 24 VDC+ to "DC-0+" and "DC-1+?" have you wired 0 VDC to "RTN OUT-1" and "RTN OUT-0" If that is all OK, then as Armadillo said, you may have a problem with the internals of the module - try using a different/spare output? good luck! vds    
  13. Allen Bradley ACD File

    It's 11,488 pages... won't let me upload that size file - hopefully Armadillo has sorted you out. vds
  14. Major Fault

    Hi, Please check that your "MESSAGE_WORD_RESULTS" array is at least 32 elements. This array will hold the bit numbers that are different. If you have, for example, a result array length of 5, but there are 6 or more bits that differ (between the Source and Reference words), the Major fault code you described will be raised. see page 626 onwards: http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm003_-en-p.pdf good luck, vds