fae-san

Attached is a program I wrote years ago in VB. It should help get you started. In todays world you might want to look into OPC and write your application that way so that if for no other reason, you can learn OPC. C24.32.zip

This is not such a strange thing to do. I have used index registers in the past for this exact reason, moving a special function module around. The Index works great with the U\G device too.

You can store your comments in the A Series CPU. You will need to setup the PLC parameters in the A Series CPU to allow storage of the comments.

John where are you located? There may be something available that can help you.

From the menu: Online\Transfer Setup double click the serial Icon on the PC side I/F.

MELSEC MEDOC

The FX1S has EEPROM memory fixed at 2k. When using the FX1N-EEPROM-8L only the loader function can be used. After using the loader function the FX1N-EEPROM-8L must be removed from the PLC. The loader function allows you to transfer programs To/From the PLC. When using it with the FX1S only 2k can be utilized since that is the maximum memory size for the PLC

FYI, FX0S and FX1S do not have memory expansion/optoins. Only the FX0N/FX1N and above have that. FX0S/FX1S has built-in EEPROM memory.

FX-EEPROM-4C FX-EEPROM-8C

I suggest that you normally use X/Y for your CC-Link I/O bits. It is very possible to run out of them with four networks. You can next use M's, B's D's etc. Using direct buffer memory access you will never run out of bits because you are not utilizing any of the PLC normal device memory. I was not saying that using 45 stations out of 64 on a network is inefficient. I was disagreeing with that comment. CC-Link is a network that covers everything from discreet control to a true control network. Using the GP.RLPASET command will solve the problems of setting more than four modules. If things are more dynamic in your configuration of the network this method might be the better way to go. If you need to exchange data with S7’s then I’d first look into Profibus or Ethernet unless I had a low amount of data to transfer. I do not consider data exchange in the E-Series terminal to be an efficient way to do this. It might be easier but it is no where near as reliable as using a network. Just wanting to make sure you are aware of the risks involved.

Here is a program that you can use as an EXAMPLE FX1N_v1.0.zip

First of all you can access buffer memory in all Q Series PLC's using the U\G device which also supports accessing bits, U\G.b. If your CC-Link network gets large you might want to consider this as you will run out of bits potentially. The easy setup for CC-Link is via CPU parameter settings. However, as you have discovered you can only set four modules in CPU parameters. Using the command GP.RLPASET you can set CC-Link parameters for any module loaded in the system. You can find this command documented in the CC-Link Master manual. 45 stations out of 64 not efficient…You have to realize what you are setting up here and the capabilities that CC-Link gives you. You can do everything from turning on a bit to programming your PLC over this network. As modules have more capabilities an increase of words and bits are required. CC-Link version 2.0 BTW doubles the amount of data that can be moved around on the network. E-Series data exchange using dual drivers is NOT very efficient. If the second CPU is loaded in the same rack then you can share data much more efficiently via shared memory or using special commands to read/write between PLCs. If second CPU is in another rack I suggest you look into using Ethernet, NET/H, CC-LINK or C24 to move data between PLCs unless you have a very small amount of data and it is not time critical. Dual driver data sharing is ok between dissimilar products when you have a low amount of data you are sharing.