All Activity

This stream auto-updates   

  1. Past Hour
  2. @triee For use FX PLC to Modbus Slave you should check that how data from PLC (X, Y, M ,D) mapping to Modbus Address (40001, 40002, 40003, etc). Please shown us your model and link to manual to check how to setting it.
  3. Today
  4. Yesterday
  5. cant some one explain my problem fx2n modbus

    before ANY serial communication can take place, same settings must be used on ALL participants. that means that data size, baud rate, parity, stop bits etc must be same. is this the case? what are the settings of other nodes? all nodes must have unique ID. is this the case? what are IDs of all nodes? program need to initialize module settings. you do this part and assign ID node number 1.  so far so good (assuming those are correct values). but that is only one line... you still need to write code to read data, write data, calculate checksum etc. and all of this code is missing. so... unless someone posts sample, you have more work to do.
  6. Sysmac Studio Function Block Guide/Manual

    Its not as good, but its something... W504-E1-09_SysmacStudio_Ver1_Op_Man.pdf
  7. Has anyone had any luck adding Allen Bradley EtherNet/IP devices to the IO tree in Codesys using the EtherNet/IP scanner module from Codesys??
  8. Sysmac Studio Function Block Guide/Manual

    Dear I say it, but F1/help does have similar...  
  9. Last week
  10. I'm not a Mitsubishi guy, I'm a Modbus guy, so my comments are from the Modbus world. Several observations. RTU and ASCII are totally different protocols Modbus ASCII and Modbus RTU are totally different protocols in terms of byte size, message formatting, timing, and error checking. If you don't believe me, here's a vendor telling you the same story https://www.icpdas-usa.com/documents/modbus-RTU-to-modbus-ascii-conversion.pdf cases in point: Byte size ASCII is 7 bit, not 8 bit. That confuses the UARTs that handle the serial data. You need a UART that can handle 7 bit ASCII data. Yours does not appear to want to do so (8 bit only) Message formatting Modbus RTU uses a timing delay and a start bit know what to start a message Modbus ASCII uses the colon character. A device handling RTU has no means of generating a colon at the beginning of message or recognizing a colon character in a reply message. error checking Each message uses error checking ASCII uses LRC RTU uses CRC These two error checks are totally incompatible with one another.  A bad error check results in an exception message and the message is discarded. Incompatability The differences between Modbus ASCII and RTU message formats make them incompatible protocols - neither can deal wth the other. Commercial gateway/converters solutions Either you can do your own coding using whatever tools Mitsu offers for that PLC or you can buy a commercial converter/gateway solution. Modbus ASCII is relatively rare nowadays (it was designed for telephone modem communications), so the only dedicated Modbus RTU-ASCII gateways that also combines a serial conversion, 485-232, that I know about are Cel Mar (Polish) https://cel-mar.pl/en/rs232_rs485rs422_asci_rtu_1040pc1.htm?idk=5#poz Equustek DL-4000 MMX (Canadian) https://www.equustek.com/dl-4000-mmx-modbus-rtu-modbus-ascii/ This is not an endorsement, I've never used either and I'd want to confirm that the software for the DL-4000 MMX would run on Windows 10. There are several Modbus RTU-ASCII gateways that are RS-485 on both sides, which would require a 485/232 converter on the ASCII side, as well. There might be other gateway/converters out there, but be aware when searching that there are Modbus RTU-to-(generic)-serial ACSII converters that are not programmed specifically for Modbus ASCII that offer no real advantage over roll-your-own coding, (they're for non-Modbus ASCII serial, like propritary datalogger serial protocols). The market is now primarily Ethernet-serial protocol gateways (RTU timing requires the use of Modbus-specific gateways, not generic Ethernet-serial gateways).   In fact, one such vendor suggests doing Modbus RTU - ASCII conversion using Ethernet: https://ipc2u.com/support-service/faq/protocol-gateways/modbus-rtu-to-modbus-ascii/    
  11. I'm not a mitsubishi guy, I'm a Modbus guy, so I can't comment on your ladder. Several observations. CRC error 99% of Modbus is half-duplex "2 wire RS-485" which means that handshaking is not used.  That's why the "handshake control" feature should not be checked (first graphic, upper right), because 2 wire RS-485 has no provision for the RTS signal (a separate pin on RS-232). Checking "reverse CRC" is probably why your 3rd graphic shows an invalid checksum.   If the checksum bytes are reversed, the the checksum is wrong.  Uncheck the "reverse CRC" feature.   Not a valid Modbus reply In the first graphic, the single byte response, A7, makes no sense whatsoever.   A valid Modbus reply message, even an error-exception code reply is a formatted message with at least 8 bytes.     "Read Holding Registers" or "Read Input Registers"? In the first graphic, the "Read Holding Registers" is selected, with a Function 4.   In Step 3, the 2nd byte in the message [04h] "Data Out" message confirms that the Modbus message is requesting a read of the "Input Registers", which is what Function Code 04 does. Input Registers are a different set of registers than Holding Registers in a slave.  Some few slave devices map the same information in the Input Registers to the Holding Registers, but many do not.  A source of confusion is that Input Registers are identified by the leading numeral (3)xxxxx, whereas Holding Registers are identified by the leading numeral (4)xxxxx. So Function Code 03 (read Input Registers) reads the (4)xxxxx memory area, but Function Code 04 (read Holding Registers) reads the (3)xxxxx memory area. The graphic shows what I consider a misrepresentation because it allows Function 04 to be incorrectly associated or identified with Holding Registers.    The bottom line is that the query is polling the slave's Input Registers, (3)xxxxx, with Function Code 04, and if that's what you want, fine; or maybe you need to poll with Function Code 03 instead if you need to poll Holding registers   Unreadable graphics I'm sure there's critical information in the graphics of manual pages that you posted, but it's your problem and if you can't take the time to format the graphics so they're readable, you can't expect readers to jump through hoops to do so. Who's Master, Who's Slave? By definition, Modbus RTU Masters can not communicate with another Modbus RTU master. The text about connecting to weinview hmi - most HMI's operate as Modbus master so that actions like pressing a soft switch on the HMI immediately sends the status change to the PLC without waiting for a PLC master to poll the HMI for changed states.    I had assumed that the first set of 3 graphics were Modbus Master setup pages for the Fx2n PLC.   If the Fx2n is a Modbus Master, can the Weintek HMI be a Modbus slave?   Parity The rule for serial RS-485 communications (which is one of the hardware comm links used by Modbus RTU, the other is RS-232) is that the parity settings for all devices on the link MUST be the same.   The Modbus Spec says that devices MUST have Even Parity, but there are no Modbus Police to enforce the specification, so occasionally there are vendors who use only No Parity.   But most allow a choice of even, odd, or none Parity. But you have to match the parity settings for the Master and all slaves or you have garbage network that won't work.    
  12. The modbus rtu must be even parity ?
  13. can give me example ladder i want connect with weinview hmi
  14. Can you give me the right example ladder
  15. Can you give me example ?
  16. Yes , what do you think any problem with my ladder?
  17. Panelview C400

    Hi everybody... I have a Panelview C400  that was running OK, but CCW asked me to upgrade the firmware. After download the new firmware, and follow exactly the flash procedure, the HMI reboot, make the autotesting and then keep in boot without load the SO... How to reset to factory defaults?? or downgrade the firmware?? or anything to help me to solve this issue??? Thanks in advance... Yony
  18. Cqm1

    CQM1 was discontinued years ago. Due to go in the bin.
  19. real to integer number

    well... read manual and use instructions that your plc does have. for example check chapter 4.15.3 in FX programming manual: http://dl.mitsubishielectric.com/dl/fa/document/manual/plc_fx/jy992d48301/jy992d48301j.pdf
  20. Help Installing GX Developer on Windows 10

    Civet It took a act of congress but they finally put my PC in safe mode and it installed. Thanks so much Brian
  21. Failed Uploading the Logic from GE PLC RX3i

    Hi Everyone, I'm in a maintenance team in a factory, I need to upload an existing PLC program for backup purposes. The existing PLC is (IC695CPU310) (With only two serial ports 1 & 2). I don't know in which version the program was developed and downloaded to the PLC but the factory was established in 2009, so I used PME Ver. 7.5 (to be sure of having a newer version). I have installed the PME in a laptop with Windows XP SP3 which have a built-in serial port. I used the Horner Electric mini converter cable (HE693SNP232A) to connect with the PLC port 2. I was able to go online but the LED of port 2 in CPU was not steady on all the time, it was on for most of the time but going off for a short time frequently. I put the CPU in stop mode and I could successfully uploading the hardware configuration but when I tried to upload the logic it goes to offline mode and gave me the following message: "Failed to upload or process Symbolic Memory Table. Please contact technical support". Then I connected the PME with port 1 (RS232), the LED of port 1 was steady on. When I started uploading the logic, most of the subroutines were uploaded subsequently but could not complete the uploading. Before completing the upload I received the following message: "Machine Edition Executable has encountered a problem and needs to close" and then PME was closed automatically. Anyone can help on how can I resolve this issue ?
  22. hmi weintek and plc mitsubishi

    I've posted what I think you are looking for in a excel document.  Hope it helps PLC Example.xlsx
  23. Thank you Michael. That's what I wanted to know. The info would definitely help.
  24. Safety IO Modules on NX-EIC202

    With the NX-EIC202 (EtherNet/IP comms adapter), you can never do distributed safety I/O.  Each NX-EIC202 / NX-SL3300 (or 3500) node would be like a stand alone safety controller with an EtherNet/IP connection for status only.   The NX-SL3300 can only use the Safety I/O that is on the same NX-EIC202.  If you want to do distributed safety on EtherNet/IP (CIP Safety) you need to use the NX-SL5*00 controllers and the NX-CSG320 (or NX102). This is what I would suggest for you: The NX-SL5500 can do both CIP Safety and FSoE.  So, mount the NX-SL5500 to the NX102-9000.  Use one of your EtherNet/IP ports on the NX102 to communicate with the robots.  You can do both CIP Safety and standard EtherNet/IP connections (for control signals to the robot and status signals from the robot) from that port.  The rest of your safety on the machine will be on the FSoE (Fail Safe over EtherCAT) side of things.  Connect an NX-ECC202 with the NX-SID800 and NX-SOD400 modules and the rest of your regular IO using the EtherCAT port on the NX102.  You can distribute much more safety I/O on this network, it is faster and easier to configure.   Notes: The NX-SL5500 supports only 16 CIP Safety connections (that means 8 robots, 1 connection in and one out). The NX102 supports 32 standard EtherNet/IP connections.  These are not consumed by the CIP Safety Connections.  Therefore, you would likely use 1 in and 1 out per robot for control of the robot.  If you had other EtherNet/IP nodes that you would have 16 regular EtherNet/IP connections remaining (on the port you are using) after 8 robots.
  25. cant some one explain my problem fx2n modbus

    The response is a single byte. You should be getting back a response with 10 data bytes 3 header bytes and 2 trailing check sum bytes. Similar to the following: [01h] [03h] [0Ah] [00h] [01h] [00h] [02h] [00h] [03h] [00h] [04h] [00h] [05h] [24h] [CFh]
  26. Crimson 3.0

    Red Lion has an excellent support line.
  27. Is there a manual or guide for Sysmac much like one that was made for CX Programmer? Here is the version of the manual I am referring too, I wonder if there was one for Sysmac Studio somewhere. http://forums.mrplc.com/index.php?/files/file/308-cx-programmer-ver5-introduction-to-function-blocks-guide-r121-e1-01/
  28. real to integer number

    How i can do this on mitsubishi fx-1n CPU which do not support INT instruction ??
  29. Load more activity