garypeme
MrPLC Member-
Content count
11 -
Joined
-
Last visited
Community Reputation
0 NeutralAbout garypeme
-
Rank
Sparky
Profile Information
- Country United Kingdom
-
Hi Guys Sorry I haven't got back to you sooner. Colin, I have wired the cable kind of like option A but the connection required for the modem I am using is a 25 pin type. Anyway comms are successfully working now. There were two problems... 1. One of the leased line wires was open circuit. 2. Modem wasn't correctly configured. Thanks for all your help
-
Hi Guys Update of my progress today... Still not managed to achieve successful comms via modem (sorry I didn't mention this in my original post), but i can get comms if i connect directly to my laptop running the Fix DB using the cable as detailed in the manual and by andybr. FYI Colin i have set the anoumous protocol switch to mode 1, just a guess but it appears to work. Also as mentioned here no PLC code required. To clarify the required system... A1S PLC <----- 9 Pin - 25 Pin Serial Cable <------- Racal 3223 Modem --- 4 Wire LL --- Racal 3223 Modem <---- PC running iFix (MIT driver) I have verified all cables involved and they are ok. iFix Driver configured correctly with correct com ports etc. The modems are dialling and connected to one another (CD indication on), the SD and TD lights flash iFix end but nothing PLC end. LL has been verified by telecoms company but this is all I can think is causing the problem? Thanks for all your feedback thus far
-
Panic Mode, thanks for your reply... 1. PLC has onboard C24 interface. Part number is A1SCPUC24-R2. 2. iFix 3.5 via 232. 3. 9600/8/1/no parity/no flow control. 4. Standard DB9 caable. 5. 5m. 6. Yes. 7. It appears to fail the loop back self test indicating it has failed the 232 comms check. 8. I have code in the PLC to handle the C24 interface. Is this required. I have the mode thumb wheel set to protocol 1, is this correct, and what is protocol 1. There are also options for protocol 2, 3 and 4. Your help is much appreciated
-
Hi I am having real problems getting the above to work. Cable appears to be ok, code to manage c24 part of program. Does anybody have any suggestions and/or general tips for dealing with these interfaces? Thanks in advance Gary
-
Thanks for that! All seems to work, great!
-
Hi Ken Thanks for your reply. Have procurred the KT PCI card for PC and the FactoryLink Drivers. Are you saying that I will not require any DH+ comms code (ie MSG instruction) in my PLC as the PC will handle all the reads and writes? So all I would need to do PLC end is address the PLC correctly and just have my user program required for the test (lots of block transfers)? Cheers Gary
-
Thanks for your suggestions. In response to WayneS attached are the MM+ files. If somebody could convert them to ACSCII format then I believe I can import it into GX IEC Developer or GX Developer. MM.zip
-
Hi I am imminently going to be performing a FacoryLink SCADA Driver trial. This trial will consist of communicating to one PLC5 and one SLC504 over DH+. Given my lack of experience with DH+ I was wondering if anybody had any tips/guidance. I believe I am required to place MSG instructions in the PLCs, but what do I define in the destination address given that I am communicating with a SCADA system, not another PLC? Also, can anybody tell me what the difference is between a Classic PLC5 and Extended PLC5. Your help would be greatly appreciated.
-
Hi I have an old A1SH PLC program that was coded using MM+. I would like to upgrade it to GX IEC Developer v4, but the problem we have lost our copy of MM+. Does anybody know where I can source a copy of MM+ from? Thanks in advance Gary
-
Thanks for the advise. Unfortunately all these settings are correct which is supported by the fact that I can successfully achieve comms (connection test passed) with the older FX2N.
-
Hi I have an issue communicating to a new FX2N plc. I have GX Developer-FX v8.25 installed on a Win XP SP2 machine, and I am using the standard red cable (??-09) to communicate. When connected to an old FX2N (I am new to MItsubishi so I have no version/firmware info, do they even have this?) I can monitor, write etc, everything you would expect. When connected to the new FX2N I cannot communicate. Any ideas? Thanks in advance.