Jojo712

MrPLC Member
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jojo712

  • Rank
    Sparky

Profile Information

  • Country Singapore
  1. ModBus and Altivar Invertors

    Hello Peter, We're still on the process of completing the installation for a new machine that have Schneider ATV312 inverters using MODBUS communication. I used Protocol Macro for the MODBUS communication. And as Bob said, it can be difficult at first but after some time and testings then should be OK . I just find the communication speed (specifically feedback for change of value) to be slow even at higher baud rate as the machine have only 1 CS1W-SCU-31-V1 to communicate with 16 E5CN Temp Controllers and 2 ATV312 which will be increased to 7 units by next week.
  2. CX-Supervisor improvement requests

    I guess there isn't any chance yet that CX-Supervisor will be available on the Asian Market. It's still not available from the Omron distributor here in Singapore.
  3. Hello Bob/Dick, Thanks for the information. I will try this approach on the next project as I can't put additional cards in the PLC anymore. Cheers.
  4. Hello All, I'm still working on our project which involves serial communciation between OMRON PLC, Schneider ATV312 inverters and OMRON E5CN Temperature Controllers. The OMRON PLC and the devices are communicating already although I have to add 5 more units of inverters in to the loop. My biggest concern is the speed of communication between the OMRON PLC and the devices. At present, it takes about 5-7 seconds (sometimes can reach up to 10 seconds) for the current cycle to complete. The cycle starts from changing the value (SP of ATV 312 or E5CN) in the HMI/SCADA, sending the value value to PLC, PLC sending the value to the device, PLC read the present value and then finally PLC sent the present (changed) value to the HMI/SCADA. What is the optimum/minimum time required between prtocol macro commands? That is to send the write command to a device and then send again a read command to the device to check if the change is successful or to send read command from one device to another. Is there an existing good practice or standard flow chart to improve or optimize communication between PLC and other devices connected through ModBus serial?
  5. CX-Protcol MODBUS Serial Communication

    Hello Guys, Thanks a lot for the all the information specifically for the Trace Tool in the CX-Protocol and the Multiway Software (by the way, is this an official OMRON software?). I was able to see what's happening and found out my mistakes. Just want to share the things that I learned from this experience: 1. Data address is not correct. - I have used the address 8503 in the CX-Protocol transmission because it's the address that works for the ModScan software. CX-Protocol and Multiway both use the address 8502. 2. Data address must be in HEX format - I have tried using the HEX format before but I was using the address 8503 and convert it to 2137H so there's also no response from the VSD when I was using he Multiway software. When I used the address 2136H (8502) then I was able to set the frequency reference of the VSD. 3. RS-485 port of the CS1W-SCU31-V1 is reverse polarity of the RS-485 port of the PC/Notebook serial COM - In short if I can communicate with the device through Multiway or ModScan using exactly the same cable I used for the CX-Protocol/SCU31 then the cable is not correct for the CS1W-SCU31. Even the label of the adapters indicate that pin 1 is A+ and pin 2 is B- but for CS1W-SCU31, pin 1 is negative and pin 2 is positive. Now I can finally communicate with the VSD by CX-Protocol (using MODBUS format) through the CS1W-SCU31 but when I tried to connect to either ModScan and Multiway using the same cable then I get no response. It's most probably the same reason why I can't communicate with the Hellas rectifiers on my previous project using HELLAS configuration software but then I was able to connect with the rectifiers using the CJ1W-SCU31 and protocol macro. On that project, I ended up doing all the rectifier settings using protocol macro instead of the HELLAS configuration software. At least now I now that the RS232 to RS485 converter that I bought before (on that project) is working because I was able to use the same converter in this project. I thought it's because of this converter that's why I was not able to communicate with rectifiers. Thank you all again for sharing your time and information.
  6. CX-Protcol MODBUS Serial Communication

    Hello Bob, Thanks for the link. I have already downloaded the Multiway softaware from an OMRON Europe site. It's a great tool and was very helpful to analyze the problem. Thanks again for info about the Multiway software, it's a cliche but I wish would have known and used this tool before it could have saved me from a lot of headache like this.
  7. CX-Protcol MODBUS Serial Communication

    Yes, the trace works. I was able to see the data that was sent and data is in corrrect MODBUS format. Send message [33] slave address in hex; [10] MODBUS write instruction; [85] [03] data address (Schneider defined addreess); [00] [01] one word; [02] two bytes; [nn] [nn] data ivalue in HEX; <C> check code. Recieve message is just the same data (loop back data). I think there should be another data for the ACK reply from the slave. The message data format I used for the VSD is the same message data format I am using for the temperature controllers. I'll search for Multiway. Thanks.
  8. CX-Protcol MODBUS Serial Communication

    It seems the MODBUS software that I have now (ModScan) can only run as Master, it always need a device address in order to communicate. As for the Trace tool, I was not able to activate it yet. Even if I am connected to the PLC through the SCU the command is always grayed out. By the way the model of the Schneider VSD is ATV312H037N4. Thanks.
  9. CX-Protcol MODBUS Serial Communication

    I am currently using the MODBUS setting: Baud rate = 9600 Comm parameters = 8 bits, Even parity, 1 stop bit. One thing I found odd is that the Schneider communication manual states that the VSD reference frequency address is 8502, but if I am using the ModScan I must use the address 8503 in order to change the speed. Anyway, I tried both addresses 8502 and 8503 but I still got no response from the VSD.
  10. CX-Protcol MODBUS Serial Communication

    I have not tried yet the reverse way, I thought the ModScan can only act as MODBUS Master. I will definitely try this setup also and will also use the Trace Tool. Thanks a lot for the advice.
  11. Hello All, I am trying to connect 2 Schneider variable speed drives to an OMRON CS1W-SCU31-V1 using CX-Protocol. I also have in this communication circuit 16 OMRON E5CN Temperature controllers. I can already communicate with the OMRON Temperature controllers but have no luck/success with the Schneider VSD's. The protocols I am using now was taken from the ModbusPM Protocol Macro. I used this PM before on another project to coomunicate with Hellas Rectifiers and I was able to communicate these rectifiers with no problem in communication just some setting/config issues on the Hellas rectifiers. My plan was to use Port 1 of the SCU31 for the temperature controllers and then Port 2 for the VSD's. I have tried communicating with the temperature controllers on both Port 1 and Port 2 and did not encounter any communication issue. I can send the setpoint value to the Temperature controllers and I can see the changes on the units. however when I tried again to connect the VSD's on any of the 2 ports I have no response from the VSD's. I have the tech gusys from Schneider double checked my settings for the VSD communication and all communication setting parameters are correct. I also connect the VSD's to the ModScan software using the same junction box and cable that I am using to connect to the CS1W-SCU31 and I am always able to connect to the VSD via the ModScan software. I can change the reference frequency thru the software and can see the change in the VSD's. Is there any other cases or issues like this with CX-Protocol or CS1W-SCU31? I think my biggest problem is that I don't get any error message from the CX-Protocol or CS1W-SCU31, so I can't figure out where or what to do next. Any comment/help will be highly appreciated. Many Thanks in Advance
  12. Finsgateway 2003 problem

    Thanks. Actually, I used first the Kepware OPC Server and yes it's a walk in the park to set-up the Kepware server and OMRON communications. However, I encountered so many issues with iFIX specifically with arrays and the use of DR data types wth OPC driver. I'm using iFIX version 4.5 and I can't write to the array elements conesecutively. If there's only one element involved in the script then there's no problem but if more than 1 then I have to use delay subroutine before writing to the next element. And I can't write to the DR tags by bits, totally, even though it's stated in the iFIX electronic book that this is possible. I consulted these issues with the local tech support and they recommended to use the iFIX OMF Driver to communicate directly with OMRON through the ethernet.
  13. Toolbus to Host Link

    Hello, Is it possible to change the setting of the OMRON peripheral port from Toolbus to Host Liink? I already changed the communications settings mode from Toolbus to Host Link in the PLC Settings window but when I tried to connect to the PLC it's not successfull. I also verified that the setting is already transferred to the PLC. Then when I changed back the PC setting back to Toolbus I was able to connect again to the PLC even without changing back communication mode in the PLC from host link to Toolbus. Many thanks in advance for any information.
  14. CX-Supervisor improvement requests

    Is CX-Supervisor available in the Asia-Pacific market already? I was using CX-Supervisor before when I was working for a Swiss company and we were already using ethernet communications way back then. Now, in this company I'm currentlyworking we are using OMRON PLC's but using GE Fanuc iFIX and it's very hard to use the ethenet communication between OMRON and iFIX since their(iFix) ethernet driver is still based on the FINS Gateway middleware which is not supported and/or sold by OMRON anymore.
  15. Finsgateway 2003 problem

    Thanks for the information, PMCR. Yes, I know it should be purchased from OMRON and I do trust that it should work as a replacement for FINS Gateway. It's the SCADA software that I'm using now that I have doubt with. With all the hassle that I am now getting with iFIX trying to use Ethernet and OPC, I would like to try first if SYSMAC Gateway will work with IFIX. Until now their tech support group is saying that the OMF (Ethernet) driver of iFIX is only works with FINS Gateway. Because we will only need the SYSMAC Gateway for the iIFIX SCADA software, I think it's just the right time to change the SCADA software that we are using for on our next projects because it does not work well with OPC servers (too much delay) and it needs an obsolete middleware to connect to the ethernet. I was using CX-Supervisor before (on my previous company) the connection through the ethernet is simple and so is the connection to the OPC Server even from another vendor (or maybe we'll try also Wonderware).