RickyQ

MrPLC Member
  • Content count

    43
  • Joined

  • Last visited

Community Reputation

1 Neutral

About RickyQ

  • Rank
    Sparky

Profile Information

  • Gender Male
  • Location Houston
  • Country United States
  1. CJ2M 33 Ethernet/IP problem

    hard wired 24v relay is definitely the best  / safest way to go about it. the problem is not really that the EIP comms keep going, its due to the fact that the menory area the EIP card is sending is stale from the last cycle. i believe there is anTag Data Link Start/Stop Bit in the diagnostics area, maybe play with only turning this high while scanning and see if it resets on its own like some reserved areas.
  2. cj1w etn21

    yes, check that the node set on the rotary switch matches the last octet of the IP address configured on the card. Post some captures of both sides!
  3. Sysmac Studio Improvement Request

    been waiting for this!  
  4. Variable length strings in PMRC to REAL

    i answered my own question. nevermind :D
  5. Dear PMCR experts, i have a question. I need to read a variable length ASCII string that represents a float via 232, i can get the data with PMCR but i am wondering if there is a way to programmatically parse this thing into a real. Say you receive 2 frames over serial with delimiters of 0D0A: Frame 1: 0D0A12.120D0A Frame 2: 0D0A95525.54D0A Now, if i just move the bytes over to a CJ, whether i choose to move them in ascii or hex i cannot use a standard instruction to FLT the binary. in Frame 1 i would have 5 bytes of data and for frame 2 i would have 8 bytes of data. if i move them in hex i would have half but i am still looking at bytes that represent char values and not a floating point encoded number. Any ideas? Can i do this with protocol macro?
  6. PMCR for WITS

    WITS is a standard protocol used in oil&gas, stands for: Wellsite Information Transfer Specification it's basically an ascii stream on rs232 they use && and !! as delimiters and the records even though fixed in size are variable length. sample record: &&\r\n RRIIDDDDDDDDDDDD\r\n !!\r\n && 80070.0 80084.161 80090.004 80100.004 8012109.551 80130.000 80176.808 80181229.000 80222902.303 80231878.568 !! i'm thinking of doing this in structured text to avoid PMCR, but wanted to check if someone had a working parser.
  7. PMCR for WITS

    Do any of you fine gentleman have a working sample of a PMCR for a WITS stream? THANK YOU!
  8. Does anyone have a sample of a working forward_open to a wago EIP coupler? I am developing this in .net, even a WireShark capture would be great! Thank you.
  9. Does anyone have a sample of a working forward_open to a wago EIP coupler? I am developing this in .net, even a WireShark capture would be great! Thank you.
  10. ETN TCP/IP Socket Speeds

    I agree, I never measured the time to read the socket without the FB. it’s a question of going into the standard FB and hacking out the unnecessary stuff!
  11. What does this symbol mean?

    What is the data type of your D on this instruction? it requires a UINT, it looks like you have a string with the equivalent of ii in ASCII or maybe #6969? The ' ' is how cx-prog denotes "Strings"
  12. CJ2M connected by ethernet to Yaskawa A1000 Inverters

    Can you take a picture of how the drive is connected to EIP? i am also interested in how to change parameter of VFD over EIP
  13. If you happen to have an omron PLC around, you can format the card with cx-programmer if you plug it into the omron CPU.
  14. ETN TCP/IP Socket Speeds

    Confirmed that the function to recv data from etn to mem area of plc has a 40ms run time.
  15. EtherNet IP Integration

    Since you are mostly doing p2p you should be fine, however, as you put more and more devices online i would multicast to improve overall performace. Once you go multicast I would recommend you get a managed switch that supports IGMP. I have seen unmngd switches get overwhelmed by multicast traffic. Point to point basically means that if your plc needs to send the same data to multiple devices it must send the data to each device one by one. In multicast mode the plc (or devices) only send the data once and listeners that need this data subscribe to the multicast group. Igmp will help the switch determine who the subscribers are and only forward the traffic to the appropriate port. Hope that helps...