kaare_t

MrPLC Member
  • Content count

    2306
  • Joined

  • Last visited

Everything posted by kaare_t

  1. A-Series internal clock, using it

    Hi there! What kind of instruction do you want (which instruction did you find for the FX)? What do you want to compare, and what kind of result are you looking for? Which programming tool do you use (Medoc, GX Dev., GX IEC Dev.)? Guess you already know, but if you're programming an A-series, I would recommend reading the instruction set for that specific series
  2. Ethernet Heart Beat Code

    What's the problem with the cycling M? Is it Citect or your PLC code? There's nothing wrong with the method you are describing, and in many situations it's the only possibility.
  3. FX and Profibus Async message

    Sorry man. I've checked at work, and also a couple of other companies we work together with, but it seems like no one has used acyclic communication with the FX3U profibus master. Sorry for the "false hope" in first post and good luck!
  4. FX and Profibus Async message

    I'll check with some people tomorrow, will let you know!
  5. FX and Profibus Async message

    I assumed that Mitsubishi actually had a function block / program example for acyclic transmission for the FX3U. Veganic: Where in the Mitsubishi web-site did you find the IEC function blocks for FX3U and acyclic transmissions you mentioned? Sorry panic mode, it doesn't seem like Mitsubishi has any working example for acyclic transmission with the FX3U-64DP card. I can check if anyone at work has ever made a program for this kind of communication, and if so, I will send you the code. As mentioned, I haven't worked much with Profibus, so I'm not sure if I understand exactly what you need. Could you please explain exactly what you need to do, so that I can ask "the correct" questions at work tomorrow (and get the correct code if there is any)?
  6. FX and Profibus Async message

    Hi. I haven't worked with the FX3U and Profibus, but I have GX IEC (7.01 / 7.03), and I could export the Mitsubishi function blocks as IL if you would like. I'm not sure if you can use it as IL in GX Dev. (or do you have any other idea?).
  7. problem interfacing fx3u with fx3u-4da-adp

    Learned my lesson!
  8. problem interfacing fx3u with fx3u-4da-adp

    Well, not to be rude but you could at least take a quick look in the manual before posting "strange" behavior! Here's a snap-shot of the error section in the FX3U/FX3UC "User's manual [Analog Control Edition]" Manual No: JY997D16701 Manual_DA_ADP_Error.bmp
  9. interfacing Fx3u with various additional I/O

    If you look at the front of the 8AD, you have a led "24V" - This indicates if the external 24VDC is present. In other words, if this led is not lit, then the external 24VDC power supply has failed. You also have a led "POWER" - This indicates if the 5VDC (supplied in the ribbon cable) is present. In other words, if this is not lit, then you have a problem with the 5VDC on the bus/ribbon cable. The 8AD module will not draw 24VDC power from the ribbon cable. OK? -By the way; you can test the 24V led by simply disconnecting the external power supply from the 8AD.
  10. problem interfacing fx3u with fx3u-4da-adp

    Didn't you set up channel 1 to be a voltage output?Do you still have the error when you disconnect everything (except the power supply) on the DA-ADP?
  11. interfacing Fx3u with various additional I/O

    If the extension block/special unit has an 24VDC power supply connection, then that specified unit will not draw 24VDC from the ribbon cable.One small but important addition to any other previous post: FX3U-16 / FX3U-32 = 400mA available FX3U-48 and above = 600mA available
  12. problem interfacing fx3u with fx3u-4da-adp

    If you haven't connected anything else (than the fx2n-16ex-es/ul, fx2n-8ad, fx3u-232-bd and fx3u-4da-adp) you should be OK regarding power supply, but you don't have much left! I always use an external power supply. Have you connected the output wiring of the DA? If so, try to disconnect the output wiring and see if you still have an error.
  13. interfacing Fx3u with various additional I/O

    I'm not really sure which version you would need to program the FX3U. Mitsubishi added support for the FX3U quite some time ago, but I'm not sure at what excact version number. I think you'll have to pay for an upgrade, but then again; you will get the newest version available.... The FX3UC is simply a "Compact" version, but it's the same CPU. There's no difference in programming the standard or the compact type. In fact, when you select the PLC type there's no option for selecting FX3U OR FX3UC. The selection is "FX3U( C )" pretty much the same as the selection "FX2N( C )"! However, there's some differences when it comes to the physical layout and/or extension modules: -There is no screw-terminals (is "screw" the correct word???): You have to use a cable from the main unit to some kind of connection unit. -You cannot connect any of the BD-cards: You have to use ADP modules only (you can use 2 communication ADP modules). -You need a converter if using modules on the right hand side: The bus-connector on the right hand side does not match the standard extension modules (e.g. FX2n-8AD). You have to buy an extra module, I think it's called "FX2N-CNV-IF" - I'm NOT sure if this is the correct name, but you need an extra module. You can take a look at Mitsubishi's information: http://www.mitsubishi-automation.com/index.html Just click on the "Compact PLC", and then check out the differences between FX3U and FX3UC
  14. interfacing Fx3u with various additional I/O

    Hi. Regarding your initial question: It doesn't matter which order you put the modules. Personally I prefer to put the digital modules (e.g. FX2n-16EX-ES/UL) first, then special modules (e.g. FX2n-8AD). The digital modules do not interfere or change the adressing of the special modules. To start with the digital modules: They will start at the first octet after the last unit. I don't remember the last output of the 128MR, but say that the last output is Y57. Then the first output of the first digital extension would be Y60. If the last output on the PLC is Y67, then the first output of the first digital extension would be Y70...... The same applies to any additional extension modules, you start at the first octet after the last digital output. The special modules (on the right hand side) will have module adresses, and they start at 0 as always even if you put any digital extension in front of them (you can adress any special module as you would have done without any digital extension). The ADP modules are quite easy to use. If you have analog modules (AD, PT, TC...), each module has it's own area in the PLC, with direct access. You should check the manual to check which data you can modify (to set up the module as you would like), and which data you can read/write the actual values from/to. If I remember it's: Module 1 = D8260-D8269 + M8260-M8269 Module 2 = D8270-D8279 + M8270-M8279 Module 3 = D8280-D8289 + M8280-M8289 Module 4 = D8290-D8299 + M8290-M8299
  15. Series Q communication Cable

    Hi. Q_Cpu_Cab.bmp
  16. QJ71MT91 Question

    Hi. If you plug in your slave and wait "long enough", will the MT91 card to start to communicate with the specified slave again? SYN, RST, FIN have nothing to do with ModbusTCP. They are control flags and are part of the basic TCP/IP stack. They are used for establishing, maintaing, teardown connections. In other words, first the MT91 will establish a TCP/IP connection (SYN is the first message in this sequence). If the MT91 card receives a correct TCP/IP response (with an SYN+ACK flag), the MT91 will respond with ACK and a TCP/IP connection is established. Then the ModbusTCP communication will begin. Therefore, the SYN messages are normal and they should not affect the Modbus communication itself. If you plug in the slave, and wait "long enough" the Modbus communication should operate as normal again.
  17. QJ71C24N Configuration

    Hi. I'm not very familiar with GX Developer (and the instruction you are refering to), however one of the inputs of this instruction should be HeadAddress. Your head address depends on the modules you have in the slots prior to the C24 card and their specific IO points (16bit/32bit......). If you have got the switch settings OK (in the I/O assignement), you can look at the start IO. You probably have something like "0040", "0050", "0060" - this depends on the modules prior to the C24 card. The head address is the same as the start IO address, except for the last number: 0040 = Head Address 4 (H4) 0050 = Head Address 5 (H5) 0060 = Head Address 6 (H6) .......
  18. QJ71C24N Configuration

    Hi. I use GX IEC Developer, but I'm pretty sure that you have the same possibilities in GX Developer. "Switch Settings" can be found under PLC Parameter -> "I/O assignement" -> "Switch Setting". These are soft-switches, and you can set parameters according to the manual for QJ71C24N. You have 5 soft-switches, and if I remember correct, Switch1/2 are for channel 1, Switch3/4 are for channel 2 (channel 5 are for station numbers if you are using the built-in MC protocol). You cannot set receive (or send) parameters (e.g. EndCode/StartCode, Byte-/Word-Mode, Binary/ASCII mode) in the soft-switches. Look for buffer-memory assignement in the manual, and use TO/FROM instructions to initiate the card during start-up. I think you only need to access 1 or 2 buffer memories to set the card for either fixed length, or StartCode/EndCode.
  19. Q-series PLC

    1: For multitasking and/or time-critical applications, you could run multiple CPU's....... 2: You say that you are running some part of the program every second, what do you mean? Are you setting a fixed scan-time, or are you running some tasks/program-parts every second? How do you call these program-parts? 3: Already answered...!? 4: Where's the problem? In Citect or in the PLC? 5: I'm using GX IEC Developer. I'm not sure of the options in GX Developer, but in GX IEC Developer you can select "MacroCode". If you enable MacroCode, the function block will be inserted as any other code, and the actual compiled code will look like you did not create a function block. You can look at this by right-click the selected network, and press "Show Melesec Code". If you de-select "MacroCode", the function block is inserted as a sub-routine with a call to that specific code.