MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

27 Excellent

About photovoltaic

  • Rank
    System Integrator

Profile Information

  • Gender Male
  • Location Some Igloo
  • Country Canada
  • Interests Dirtbiking, Microcontrollers, Snowboarding, Locksport

Recent Profile Visitors

840 profile views
  1. Yes, but the PLC doesn't initiate it. You can program LW100 to take the value of say D100 using a data transfer object in the common window. Make the source D100 and the destination LW100. You'll need to give it a trigger bit so it runs constantly. I would map the 1 second clock pulse from the PLC to a bit that the HMI can address and then it will constantly update LW100 with the value of D100.
  2. Did you try these settings in the card parameters?
  3. Electrician

    That looks right yes
  4. NX1P2 data exchange with another Omron PLC

    Just noticed your mention of them being in different projects. In this case you will have to add each target device manually by IP address in the Ethernet/IP connection settings and manually add the tags to the target variable. Not a big deal. This will still be much easier than a UDP socket or FINS
  5. communication between simulated plc

    The simulator can't communicate with anything
  6. Electrician

    You'll want to use PRV2(883) function. Set it for RPM calculation mode and assign 807 as the pulses per revolution
  7. Electrician

    I can think of about 6 additional pieces of information that would be needed for anyone to help you.  
  8. NX1P2 data exchange with another Omron PLC

    Try this one. 1.25 NX1P2 and NX102 EIP.smc2
  9. NX1P2 data exchange with another Omron PLC

    I am on 1.47
  10. NX1P2 data exchange with another Omron PLC

    Your easiest options are socket services (raw data basically), Modbus TCP, FINS TCP (there are a few caveats here), or Ethernet/IP. I highly recommend the Ethernet/IP route. IO_Rack posted some good info on this above. With both PLCs in the same project it will make setup fairly simple. I have an example project with an NX1P2 and an NX102 communicating that I stripped everything out of linked below. You'll want to look at the global variables for each PLC and the Ethernet/IP setup for each PLC (Tools -> Ethernet/IP Connection Settings).   NX1P2 and NX102 EIP.smc2
  11. Go online with the PLC and do a compare and merge from the EtherCAT section(right click on the master). This will tell you the device, version, and whether or not you have the correct ESI file for it.
  12. There is another way to extract bits in Sysmac using a Union datatype but I find the addresses easier. The HMI will only read/write tags specified in the HMI application
  13. Yes, in this case you can treat it as an integer on the NB and address a BOOL[16] array in the PLC.
  14. If you don't need to use it as an integer yes. But if this is the case you may as well not bother addressing it with AT at all and just use bits or a BOOL array. Using the address is only for the purpose of bit extraction in this case - like when you receive a status word from a device and need to pick out the bits.
  15. How to control VFD speed Via HMI?

    can you share it? The simulator in Sysmac is a great debugging tool