kaare_t

I don't have the manual you have, however there's a difference in the generic CPU protocol of the FX-series, and the MC protocol used by extension cards for the FX-series (e.g. BD cards). Since the FX1S doesn't support any BD cards, you have probably hooked up the screen to the CPU port. The CPU protocol is not publically available, hence you should upgrade your PLC to something that supports a BD or ADP card, and you can set up the MC protocol. Or if you prefer you can reverse-engineer the CPU protocol....

Password cracking is forbidden in the forums. Please don't ask questions about this......

Check out www.modbus.org. Here's a driect link to the specifications: http://www.modbus.org/specs.php

Did you remember to power off/on the PLC after changing the parameters?? Sometimes it is not enough to do a remote reset, you have to physically power the PLC off/on.

Can you post up images of the PLC configuration and the HMI Driver configuration?? Did you update to the latest drivers in E-designer??

Hope that solves the problem

Your problem is that on the built-in ethernet port of the UDE CPU you haven't configured the port to accept writing. Please select the following:

I don't have the GX Configurator MB package installed, but your problem is that you have an old version of GX Configurator MB (your version does not include QJ71MB91). You should contact your local rep. and ask for an upgrade of the GX Configurator MB package.

In your picture: You need to set up an Intelli. Card in PLC Parameter -> I/O Assignement to be able to configure the card via GX Configurator MB

I've modified the GX IEC Developer project (see attached picture): You have to modify the parameter number/value to the ones you want to change in the inverter. Then you can trigger each sequence by setting the flags high, which in turn moves your data into the common area and sets the "Wrte" signal on the FB. I've also attached your program example which I have modified to your spec. GX IEC Developer MbInvFx_Updated.zip

How many inverters do you have??

True, but I would really consider upgrading to GX Developer / GX IEC Developer / GX Works 2 so that both the program and the PLC is "up to date"....The FX0N is quite small, so conversion shouldn't be difficult. In addition we have GX Converter which can convert old MEDOC projects.....

What software do you use? What hardware do you have (FX3G-BD or ADP?)? Check out this link for the latest function blocks, and make sure that you have the newest available: http://www.beijer.no...12578A10041048B

If I understand you correctly, you have a NPN sensor (Negative-Positive-Negative). Then you will have to connect the COM terminal to 24V, and connect a wire between X0 and your sensors input.

Not sure if I understand what you want to know. If your friends code works, why not simply use his code?

Not to argue with anyone, but I would avoid the FX1N since it's in it's end of the life cycle (will soon be replaced), therefore I would use a FX3G instead. In either way you will have to convert the program, and you will have to check the wiring so why not go with the newest CPU!!??

I think (someone correct me if I'm wrong) that the FX0N is discontinued, so you will need to replace it for a new one. Again, I don't think there is an absolute direct replacement when it comes to the terminal layout, so most likely you will have to disconnect the wires and connect them on the new unit. The names on all the terminals should be the same, so it's no problem to use a FX3G as replacement and simply connect all the wires to the corresponding names. Someone correct me if I'm wrong.

You can program the Modbus protocol yourself using ladder code, but this is not a trivial task. Let me know if you want to program the protocol yourself, I can point you to the correct Modbus protocol specifications. Another alternative is to use GX Works 2. They have made some functionblocks that you can import into your GX Works 2 project, and you can simply link the function block to your desired devices. Check out this link: http://www.beijer.no...12578A100423B88

There's no built in functionality for the Modbus protocol in the FX1N. You should consider changing the PLC to a FX3G to be able to use the built in functions of the ADP cards. If you really want, and have the knowledge you can program the protocol yourself using ladder in GX Developer. You could also consider going to GX Works 2 and use freely available function blocks to implement the Modbus protocol in a FX1N.

Why would you want to have all the updates till 8.89?? In my opinion you should just upgrade to 8.89 and be done with it..... You can open your old programs in 8.89 and the newest version is the version with the least amount of possible bugs. Regarding the future you should really consider GX Works 2 wich replaces GX Developer (and possibly iQ Works wich is the complete package of the iQ software). You can open GX Developer projects in GX Works 2.

What protocol do the inverter use? What programming software do you use? Do you have the possibility to post up the manual for the inverter?

I almost always use battery backed bits for sequence handling when making new programs, and I always take care to ensure that the correct bits saves their state, AND that the other bits are resetted during power up. However, when modifying old programs it's a bit different since you never know if the bits are correctly initialized in the event of a power down/up. There's nothing wrong with using battery backed memories, just ensure that bits which need to be resetted during power up are actually programmatically resetted during power up since they won't automatically reset themselves.

In cmd, write "ipconfig /all" and copy the "answer" and post it here so that we can check the settings....

Make sure you get a pricing for a "U" series CPU (e.g. Q03UDE) since they are the "newest". In addition, all the new "U" series that has the "E" in it (like Q03UDE) has a built in Ethernet port. They are also pretty "cheap" considering that you get a very good CPU and the Ethernet port. For the FX-series, you can add Ethernet support by adding the FX3U-ENET, however the FX-series does not have anything that can support ModbusTCP. When it comes to communication I would almost always say that you should use a Q-series PLC since the FX is pretty slow on the FROM/TO instructions because of the limited backplane bus. However this does not apply if you are using serial communication via the ADP modules since they mount on a different bus on the left hand side of the main unit, and don't use FROM/TO instructions. The FX CPU is pretty fast as long as you don't use too much FROM/TO which affects both communication time AND scan time! The FX-series has CC-link too, but note that the module mounts on the right hand side and will affect scan time a bit. If you could provide a small specification of what you need it would be really helpful for us to help you. Like a list of equipment you are considering to buy.

For single machines/projects I almost always use a Q PLC. The reason for this is that the possibilities are "limitless" in case you figure out you need a function while in the middle of the project, or after the project. In essence it almost always saves engineering time since you can simply do/program exactly what you want, while with the FX-series you might have to do time consuming work-arounds. If you are talking about several identical machines then you can justify the added engineering time with the low cost of the FX-series, but once again; if it's one machine I would go for the Q-series. Just my opinion.