Search the Community

Showing results for tags 'kepserverex 6'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 4 results

  1. Hello everyone I have a FX3U mitsubishi PLC with a fX3U-ENET network adapter and I want to connect this PLC to the KEPServerEX 6 system but it marks me communication error, they are inside the same network and it has port 5010. mitsubishi 500p1.500b | unable to read from address block on divece. the divice reported an invalid address an error.| address block = 'M3008' to 'M3023'. mitsubishi 500p1.500b | unable to read from address block on divece. the divice reported an invalid address an error.| address block = 'M3000' to 'M8015'.   I need you help.   
  2. We're running KEPServerEx 4.5 with the AB drivers to interface with a Siemens WinCC HMI. All we've done is change the L61 processor with an L72 and then KEP shows the incorrect values for the tags. We stick the L61 back in and all is okay. The Device properties haven't changed as the L72 is part of the ControlLogix 5500 family. The IP address is the same as well as the project name, etc. I've checked the properties against the KEP manual and all is okay. The manuals I have don't mention editing a device in KEPServerEx. I feel we've missed something. :hmmm: Any thoughts?
  3. I have a panelview plus 700 terminal installed with Kepserver Enterprise V5.13.213.0. Will it work with Kepserver Enterprise V5.7.90.0 installed in my PC? Please help me. Thank You.....
  4. PLC->OPC->Labview

    Hi, I have been trying to communicate between a PLC(Mitsubishi FX3U) and Labview (using Data Socket) through a KEWserverEX OPC-server (using a RS232C COM Port cable). I have been successful at that by using baud rates ranging from 9.6kbits/s to 115.2kbits/s, with average reading time into Labview ranging from ~40ms to ~10ms (of course depending on baud rate) per value. However, this is too slow for our purposes, and we need it to be in the area of 1-3 ms per value. Are there any tricks to decrease the reading time between the PLC and Labview, or do we perhaps need an ethernet module? Kind regards Bjørnar