Profibus, ENET and FX3U

[Paul Ked]

I've been wading through manuals and PDF's and trying all sorts of things to get this system working for the last 28hrs! I'm not after sympathy, just a little help, ANY help! The system is as follows: E910; FX3U-48MR-ES; FX3U-64DP-M; FX3U-ENET | | FR-5NP; FR-E540 | | Absolute Encoder | | FR-5NP; FR-E540 | | FX2N-32ER; FX2N-4DA; FX2N-4AD-PT; FX0N-32NT-DP I'm using GX Developer V8.30, GX Configurator-DP V7.00A Some, but only the ones I can remember at this moment, of the problems I've encountered are: MXChange doesn't recognise FX3U Can't plug my SC-09 lead into the FX3U port as the hole is too small for the plug! (using E910 in transparent mode) Don't have any GSD files for the Encoder No driver for the FX0N-32NT-DP in Configurator No communication with the ENET Adapter. I'm going to bed for a few hours to see if I can wake my 'fried' brain up but, in the meantime, if anyone can give me any help, even if it's only a teeny-weeny bit, then it would be most gratefully received. Many thanks in anticipation Paul Ked

[FNMdeJong]

From the flat side of the SC09 cable, you can carve with a knife some of the isolation off and it will fit. Not all cables have this problem. You have to search for the encoder GSD file on the internet. We cannot help you if you don't give us more information about this encoder. What type, brand and so on. As far as i know, i have tested it a few minute ago, the gsd files for the FX0N-32NT-DP is available in this GX Configurator v7. Just choose a PLC as slave and you will see it. What do you mean by 'No communication by the ENET adapter'. You don't have communication over the ethernet? Is it configured? What configuration is inside the module? With the setup software? Myself I don't use MX Change, so i cannot help you with this issue.

[Paul Ked]

Thank you. I'll leave the butchering of the cable until I need to talk direct to a FX3U! Most of my systems use an HMI so I can cope with the transparent mode for now. I managed to get the GSD file from the Pepperl web site (a ++ for them) I have found the GSD file for the FX0N-32, as you say, under PLC and not under I/O, will try this out. In the Modules it only gives options for word devices and not for the AD & DA Modules as in I/O???? The ENET module has been set up with defaults from FX Configurator-EN but I cannot communicate with the unit from this software. I've tried different speeds for the com port and ethernet connections with all combinations of GX Dev, E Designer, MXChange, GX Config Server programs running/stopped but still nothing.??? As I am new to ENET and Profibus I am trying to digest as much info as I can, anyone know a web site that can explain, in laymans terms, the basic requirements of these systems? Thanks again Paul Ked

[panic mode]

there is tons of resources on internet about both of them: http://en.wikipedia.org/wiki/Ethernet http://en.wikipedia.org/wiki/Profibus as on any network, each node is identified by node address (must be unique). bus networks require termination on bus ends (Profibus, modbus, DH+, devicenet, CC-link...) but terminators are not exactly the same (modbus uses RC element, profibus uses three resistor network, most of the others will be happy with just a single low value resistor etc.). it is normal to have node address 0 reserved for master while slaves will be numbered 1,2, 3 etc. terminators are often built into devices (masters and slaves) and if this is the case there must be switch to enable or disable terminator (disable for all nodes which are not on the ends of the far ends of the bus). to setup master (tell it how many slaves to talk to, what addresses slaves use and how many I/O points are mapped for example) one normally has to use some sort of configurator software. each device will have "datasheet" in form of EDS or GSD file. networks that use fixed mapping like CC-link will simply allow assigning more I/O blocks to same slave to cover the differences among slaves. unfortunately in they call everything "station" so this could mean node, node address or range of I/O assigned to a node but this is not a problem as long as one is prepared (avare of it). on ethernet addressing is a bit more complicated. it uses 4 bytes separated by dots when presented in decimal format. again, each node will have to have unique node number. ALL nodes on one subnet will have SAME subnet mask. subnet mask for small networks is usually 255.255.255.0 when converted to binary it becomes: 11111111 11111111 11111111 00000000 there are some rueles as what is valid mask. for example it must start with 1 and it must finish with 0. also all ones must be on same side. for example this is invalid mask: 11111111 11111111 11100111 00000000 but these are all fine (they meet the three rules): 11111111 11111111 11111111 00000000 ; 255.255.255.0 11111111 11111111 11111000 00000000 ; 255.255.247.0 11111111 11111111 11110000 00000000 ; 255.255.239.0 11111111 11000000 00000000 00000000 ; 255.192.0.0 To make a local network it is enough to get hub or switch, an connect few ethernet devices together using standard (straight) ethernet cables. this is hardware setup. devices can be anything with ethernet port (PLC, PC, HMI, microwave, VR helmet...). software-wise they need to be assigned proper addresses (IP and mask). we already know that IP address (equivalent of node number) must be unique. Mask is same size as IP address but it's same for all nodes on local subnet (it defines what range of addresses is considered local - if not local, must use routing). part of the mask which is "1"s indicates that this part (these particular bits) in IP addresses of the local nodes must be SAME on all local nodes. the rest of IP address bits is used to create unique address for each node. most common setting for small LAN is to use mask 255.255.255.0 and IP addresses like 192.168.1.1 192.168.1.2 192.168.1.3 192.168.1.4 192.168.1.5 etc. as we see subnet mask dictates that first three numbers must be same on all slaves. only fourth must be unique. if one of the connected nodes happens to have address like 192.168.2.15 or 192.169.1.15 or 190.168.1.15 etc. rest of the network will not be able to communicate with it and vice versa. for simple point to point connection (laptop to PLC for example or PC to PC) one can avoid use of hub or switch and just use crossover cable as hardware connection. well, this used to be like that - most new devices (specially switches and computers) have ability to use either straight or crossover cable (often called auto MDI/MDX where "I" is straight connection and "X" is crossover). Some addresses are reserved for special purposes (like broadcasting) and should not be used (like x.x.x.255 or x.x.x.0) Hubs are simpler devices that allow connecting of multiple devices to same LAN and as such are almost totaly replaced by switches. unlike hubs switches have some smarts allowing them to let multiple nodes have point-to-point connection at the same time (on hub, one talks, everyone listens). More expencive units are managed switches which allow additional control of the traffic, for example allowing for better performance thanks to filtering unrelevant traffic etc. ---- edit ----- the idea behind subnets is to shrink necesary address space for local subnets to avoid conflicts, improve performance and reduce missuse for example. there are some non-routable ranges of addresses for that very purpose (192.168.x.x and 10.0.x.x) but this is not important at this point. also addressing can be static or dynamic. static means addresses are fixed (manually assigned), dinamic is automatically assigned by some server which can be very convenient in some cases (large offices or internet users) but not all (servers etc.). if the IP address is the only way to identify device you are trying to work on remotely, stick with static addresses for now. you don't want to download new parameters or program to wrong PLC, HMI or nutrunner...

[Paul Ked]

Wow! Thank you Panic, a lot of writing that I can understand for a change. I'll keep soldiering on with it, but before I have another stint I'm doing stuff I know about! Thanks again Paul Ked

[Paul Ked]

Just an update. I think I've got the Profibus problem solved... My supplier had specified the FX0N-32NT-DP as the slave station and there lies the problem. It should have been the FX2N-32NT-IF which is for remote I/O and doesn't need a second PLC to control it! Unfortunately I have to wait for it to be sent over from Germany as they don't have stock in the UK. I'm yet to tell my client this, a stiff brandy before the call i think!!!!!

[FNMdeJong]

FX0N-32NT-DP is a different module then the FX2N-32NT-IF. You will find the FX0N module under the section PLC, because you need to connect a PLC with this module. For the remote IO (FX2N) module choose the section IO (FX2N Modular station) in the GX Configurator DP. They should be there since you have version 7.

[Paul Ked]

Thanks, I've got that now, just those silly people at my unmentionable supply company led me completely down the wrong track! Best regards Paul Ked