Bryll

MrPLC Member
  • Content count

    349
  • Joined

  • Last visited

Everything posted by Bryll

  1. 315CPU to G120C

    Hi all, Need some help how to read and write data from a 315 2PN/DP to a couple of G120C drives. I have been searching Siemens website for two days now without finding any relevant information. The software used is Step7 V12 Professional Update 3. What I need to know is how the address map in the G120C looks. I know the start addresses for the input and output area of each inverter, but have no clue what is in these registers. You have to consider that I am a Mitsubishi guy, so please be patient
  2. 315CPU to G120C

    Great ! Thanks
  3. E710 HMI Firmware

    http://www.beijer.se/web/BExFilePileAUT.nsf/0/DBA3CB09E8B2972EC125728E005BA06F/$FILE/e700v501.zip
  4. Will it really work ? I once tried to change the settings (baud, parity, stop bits) from the operator panel during run, but the PLC needed to be restarted before each change would work. But, that might be another thing ......
  5. Profibus with FX3U

    I found the data sheets over the two modules and compared them. It seems that only the name is similar betwen them, so the function blocks from the compressor supplier was useless in this case. I'm almost done building my own blocks for the FX3U.
  6. Profibus with FX3U

    Just what I suspected. I have looked for any data sheets or similar documents to see the difference between FX2N-64DP-M and FX3U-64DP-M, but I can only find documentation for the FX2N-32DP module. Anyone here that knows where I can get documentation for the FX2N-64DP-M module ?? Edit: Found a data sheet
  7. Profibus with FX3U

    I have a FX3U-16MT/DSS I will connect the FX3U-64DP-M to. But will the function block (for FX2N-64DP-M) from the manufacturer of the compressor work with the FX3U system right off, or do I need to change it ?
  8. Profibus with FX3U

    I've been reading and investigating a little about the function blocks. The module the blocks are made for is a FX2N-64DP-M, it seems to be quite similar to the FX3U-64DP-M module.
  9. FX1S Connection Issue

    If my memory is correct should the SC-07 cable be used between a PC and the FX1S-232BD card. Edit: Sorry, the correct name is FX1N-232BD of the expansion card. It will fit FX1S and FX1N series PLC
  10. S7 300 Modbus TCP with a CP343

    Hi, What Fb's do I need to establish a Modbus TCP connection with Step 7 classic ? I have a S7-315 and a CP343 in my setup.
  11. A02J CPU

    Yes, you are right. I was reading Q02, perhaps time to buy reading glasses
  12. A02J CPU

    I think you should use the SC-Q cable on that CPU. SC-09 has a built in RS-232/RS-422 converter, SC-Q do not.
  13. EXCOM Protocol

    Hello, I have a delicate task in front of me at the moment. Communication with a couple of old Stalelectronic 700 control systems for refrigerant compressors. So I need as much information about the Excom communication protocol as I can get. This is an old protocol, but it's new to me. Anyone that have any info about it ? The info I found this far is that it's an ASCII protocol of some kind. I'm planning to use a FX3U CPU with a FX3U-485BD communication card, and use "Non Protocol" to built some library blocks to handle communication with the RS/RS2 instructions. Any better idea ?
  14. EXCOM Protocol

    The protocol is up and running I'm communicating with 5 different units, asking for 15 registers one by one from each unit. The protocol only allows me to ask for single registers, makes it very slow. But, at least it's working. Thanks kaare_t for your thoughts, much appreciated
  15. EXCOM Protocol

    I finally found the problem. When I selected "Use with EN/ENO" in the properties when I created a function block, did I miss that "Use MC/MCR" is also activated by default when selecting "EN/ENO" option. Guess how long time stupid spent to find it
  16. EXCOM Protocol

    I'm now testing my protocol, but I must admit that I've been more succesful with other things. The PLC gives me an Error at step 9469, with the code 6630 (SRET or IRET not found) When I look in the "Melsec Code Of Networks" can I see SRET at step 9469. I don't use any interrupts, so I should not need any IRET. Any idea ? Edit: This is how the code looks after I removed all other code, so the error is at step 3699 now. (* Excom_StalElectronic700: FX3U_Stal_Excom_Serial [FB] *) (* MELSEC code of NW #8 in Excom_Master_Ch1.Stal_Excom_Serial_Communication *) (* Code generated at 2014-03-21 14:25:19, 13 steps, 3513 steps for the whole object *) LD M3914 (* 3687 *) OR M3879 (* 3690 *) PLS M3877 (* 3693 *) RST M3906 (* 3696 *) SRET (* 3699 *)
  17. Batch Help

    Don't you mean FMOV ??
  18. Create Data Block

    Hi, I want to create a DB for registers and bits used to store values for modbus communication. How can I create a DB without optimized block access in TIA V11 or V12 (have booth installed) ? The plan is to use a pointer to address the arrays I create in the DB, but I can only create DB's without the option to switch off the "Optimized block access" attribute. Life was easier in Step 7
  19. EXCOM Protocol

    I'm now working on this project again. The customer stalled it a couple of times Since the protocol only accepts ASCII characters, do I need to convert my REAL data to ASCII. I have checked the "REAL_TO_STR" function, and it works as it should. The thing is that I need to break out the characters and put them in separate registers, so I can remove blank spaces (0x20) and put them in to the communication string at the correct place. Any good idea how to do this ?
  20. Q64AD scale range 4-20mA

    Sorry, my bad
  21. Q64AD scale range 4-20mA

    Try this block http://forums.mrplc.com/index.php?app=downloads&showfile=1011 It's easy to use and will do the job for you I made it for GX IEC Dev. but I'm sure you can use it in GX Works too
  22. If you instead of D13 type for example "Result" as identifier at the output of your MUL_M block and hit enter twice, the global variable definition window will appear. In this window can you specify the variable type and address. No worries to use an odd start address like D13, as long as you don't try to use D14 for anything else since this variable (DINT) will use two D-addresses. It will be a lot easier to follow the program if you use labels instead of direct addressing. When all this is done, use "Ctrl-Shift-M" to toggle between "Identifier-Mitsubishi Addr.-IEC-Addr" modes. I hope you understand what I try to explain here, I'm not very good at English.
  23. Don't know if this will work, since I tend to complicate things The result of the "MUL_M" instruction is 32 bits wide. If you create a 32 bit register in the global variable list with start address D13 am I almost sure it will work.
  24. Slow response between E1101 panel and PLC

    I normally use the E1000 panels together with FX3U-ENET. There do I have to specify the "Transmission target device IP address" to "255.255.255.255" to accept any IP address. Same thing with the "Transmission target device Port No", it's set to "65535" to accept any incoming port.
  25. Slow response between E1101 panel and PLC

    I suppose that you are using MC Protocol between the panel and the PLC via an Ethernet cable. From the MC Protocol manual: -- Group controller devices consecutively The devices from the controller are read most rapidly if all devices are consecutive. If the devices are spread out (e.g. 4, 17, 45, etc.) the updating is slower. Packaging of signals When the devices are transferred to the controller, all devices are not transferred simultaneously. Instead they are divided into packages with a number of devices in each package. To decrease the number of packages that have to be transferred and make the communication faster this number has to be considered. The number of devices in each package depends on the used driver. To make the communication as fast as possible the number of packages has to be minimized. Consecutive devices require a minimum of used packages but it is not always possible to have consecutive signals. In such cases the so-called waste between two signals has to be considered. The waste is the maximum distance between two signals you can have and still keep them in the same package. The waste depends on the used driver. Note! ASCII Strings and arrays are packed into one package for each object. --