aggattapauer

MrPLC Member
  • Content count

    129
  • Joined

  • Last visited

Community Reputation

2 Neutral

About aggattapauer

  • Rank
    Sparky

Profile Information

  • Country Italy

Recent Profile Visitors

4547 profile views
  1. Memory adressing

    objects %Mx are totally independent since that area is concerned to discrete signals only objects %MB-W-D-F are referred to the same memory instead %MF0=%MD0=%MW0+%MW2=%MB0+%MB1+%MB3+%MB4
  2. Schneider compacts

    Wait for few months (january??) and with new Unity version you'll able to IMPORT LL984 logic also in M340 platform (more suitable for old Compact than Quantum). Import means you could open and program LL984 directly in Unity. Now this "sixth language" is supported by Unity V6.0 only for Quantum platform
  3. follow the user manual indications. Search for "UNY USE 107 10 V20E" in gogle to download the guide.
  4. Schneider compacts

    Yes Compact PLC are obsolete. I suppose you are referring to Compact 984 cpu (which one? 120, 130, 145?). Schneider Electric has something for you. As far as I know they have different option (hardware and software replacement) with newest M340 or also with Quantum. Call to your local agency.
  5. priviet LD1 [%MW0;=16#0106] 01 SEND/RECEIVE 06 NUMBER OF BYTES OF THE MODBUS STRING [%MW1;=16#0300] 03 OFFSET (ANSWER) 00 OFFSET (TRANSMISSION) [%MW2;=16#0103] 01 SLAVE ADDRESS 03 READING WORDS [%MW3;=16#0000] 0000 START ADDRESS [%MW4;=16#0004] 0004 NUMBER OF WORDS TO READ LD1 AND %MSG2.D [EXCH2 %MW0:11] FROM MW0 TO MW4 TRANSMISSION + MW5 TO MW10 ANSWER THE ANSWER WILL BE: %MW5 = 16#0103 ECHO OF THE FIRST WORD TRANSMITTED %MW6 = 16#0008 00 BYTE ADDED (OFFSET = 3RD BYTE OF THE ANSWER) 08 NUMBER OF BYTES OF DATA IN THE ANSWER %MW7 = 16#XXXX FIRST WORD %MW8 = 16#YYYY SECOND WORD %MW9 = 16#ZZZZ THIRD WORD %MW10 = 16#WWWW FOURTH WORD
  6. Modicon Micro Communication

    Tomson did you try to contact your local Schneider Electric? There you should find all answers to your question. Anyway post here all that you need. User manual
  7. Proworx 32 Proworx 32 Contact your local Schneider
  8. Help!

    If I remember well XMIT function has 16 registers the tenth register should be a "Pointer" in which you should define the first word (4x ) address (decimal value) of the Modbus Function call. For example if you have XMIT registers from 400100 to 400115 if you set 200 in 400109 it means that at address 400200 you'll find the first "object" of the modbus communucation string. The modbus string is composed of 5 registers: 400200: Number of function code (modbus) 400201: Number of data to read or write 400202: Slave address (1-247 ... 0 for ALL) 400203: First address slave data register (offset decimal value without 4x) 400204: First address master data register (offset decimal value without 4x) Please verify well what I said because probably I'm not exactly remembering this function
  9. The M340 Modbus Plus Proxy allows the M340 PLC to communicate with legacy Modbus Plus devices TCSEGDB23F24FA
  10. ProWORX NxT to Unity

    It supports import of Modsoft, Concept (also hybrid), ProWorx NxT and ProWorx32 applications. Notice that this release does not convert but import !! In effect LL984 will be considered as 6th language of programming. The release Unity Pro XL V5.1 supports only Quantum PLC. In the future (next year ??) will be delivered a new version supporting also M340. Chad_B you must contact your Schneider technical support because as far as I know unity v5.1 is delivered only on direct request to Schneider.
  11. I need to manage several field devices with Foundation Fieldbus communication. I have to use Modicon Quantum HSBY controllers. I think Profibus DP is better, but actually I don't know why choosing one or other protocol since devices would be basically the same. Any suggestion from world out there?
  12. Operating System V6.2 fixes the following issues: _Processors TSX572623 server resources are frozen if EF Read_Var or Write_Var are sent out on Ethernet to absent equipments _ERR led is not managed when CPU is in HALT. _The max number of communication modules can't be reached with TSXP57453A _%SW53 is not refreshed by the NTP server when the date and time of CPU are not valid _Premium: If MAST task is stopped, PLC stays in RUN state _SCY21601 is not reconfigured after an extract / insert of the device Operating system V6.1 (files TSXP57xx3V61.bin)allows CPU to program blue PCMCIA flash memories and fixes the following issues : -When the PLC is used as a Unitelway slave and sends WRITE_OBJECT requests to the master, in case the master disappears , the PLC gets a 16#000B report (lack of system resources) rather than a time-out. -R_NTPC fails to get datas from a TSXETY5103 in slot 10 or above. -In few cases , a TSXETY120 may fails to restart after power recycle -When the power supply is not equipped with a battery, the CPU doesn't restart in RUN mode after a cold start even this option has been selected in configuration. -Crash PLC using upload OLE request wirhout PLC reservation Review . Operating system V6.0 doesn't exist for TSXP57xx3M CPUs Operating system V5.9 (files not yet available) fixes the following issues : -TSXSCP111, TSXSCY21601 : the first Input_char command after a STOP/RUN doesn't receive the characters -ERR LED still blinking even if the the system bit %S67 ( battery low ) has disappear -Using TSXMRPF004M in slot 1, CPU stays in ERR blinking after a Power Cycle and after updating database symbols -PLC crash when reading an Asi-V2 object from XBTL installed on TXBT -Erroneous message associated to %S118 bit (only in german) -When Spanish language is configured in PL7 for Diag Buffer, defective FIPIO node are not shown in the XBT-F Operating system V5.8 (files not yet available) fixes the following issues : - Transfer freezing during " line adaptation " if TER port configured in ASCII, with parity - Diag viewer : bits %S15, %S18, %S19 et %S20 status not always refreshed - CPU crash (led TER, ERR and IO lit) and SW124=H'9100 when using diagnostic screens - PL7 viewer : acknowledges alarms not yet displayed - IBY100 equipped with GPX3 :unconsistent input data Operating system V5.7 (files not yet available) fixes the following issues : -TSXMFP032P : Transfer aborted after several tenths transfers (TSXP571x3 only) -TSXIBY100: Lost of PCP requests (all) -PC <-> PLC application transfer locked if using XIP driver (all) -Crash CPU during application transfer if HMI accesses simultaneously to FIPIO objects (TSXP57x53 /TSXP57x823 / TPCX57353) This firmware evolution is synchronized with an hardware one : -Add a filter to microprocessor RS485 input to avoid loss of communication with terminals (CCX, XBT, ...) connected on TER ou AUX Operating system V5.6 (files not yet available)provides compatibility with TSXMRPC007M cartridge and fixes the following issues: - Warm Stand-by , fluctuation of PID output between 2 values in StandBy CPU - Process loop : bit %Mwxy.i.7 :X1 set to 1 if bipolar measurement and function generator - Process loops : out_inf and out_sup parameter values swapped each other - Process loops : LOCAL mode untimely selected when modifying multiplexed HMI table (%MW3704) - Process loops : Save command using bit %Mdxy.i:X23 does not succeed - INPUT_CHAR function : Time out and activity bit not badly managed - Limitation of TSXETY modules : 3 instead of 4 (TSXP57453 and TSXP574823) - TSXCTY2A/4A modules : error bit is set to 1 for 200ms after powered on - TSXCTY2A/4A modules : preselection command has no effect after module powered on - EF REAL_STRING : uses 16 bytes instead of 15 (resolution 8006) Operating system V5.5 (files not yet available)provides compatibility with UNITY PCMCIA cartridges and fixes the following issues: - Regulation : RESET action modified when changing Physical units to normalized units - %SW13 (network/station address) forced to 0 after application download - %SW49 not updated when PLC powered off more than 2 days Operating system V5.4 (files not yet available)fixes the following issues: - READ_PARAM and WRITE_PARAM instructions failed (this bug affects V5.2 and V5.3) - OUT_MAN parameter cannot be written from application - READ_PCMCIA instruction cannot access to first 64K zone in a TSXMFP264P cartridge if CPU is double slot one - SAVE_PARAM and RESTORE_PARAM instructions fail when used with AUTO SELECT loop - Analog modules may not be reconfigurable ON-LINE (this bug affects V5.2 and V5.3) - Regulation : tracking mode on auto-select loops may be difficult to use Operating system V5.3 (files not yet available)fixes the following issue: - communication locked between MONITOR Pro and a TSXFPP20 PCMCIA CARD in the CPU Operating system V5.2 (files not yet available)provides a new functionnality : -Data archiving services (EF SET_PCM_EXT, WRITE_PCM_EXT, READ_PCM_EXT) and fixes the following issues : - Grafcet : CPU goes on ERR when only one active step is configured -Regulation : bits %MWxy.i.2:X4 et X8 are set to 1 when modifying parameters KP, TI in a cascad loop Operating system V5.1(files not yet available)fixes the following issue: -Processor crash on power off/on of extended racks. -Processor crash after programm download if com family EF is updated . -programm is lost after power on if %S94 was activated .
  13. what's the matter?
  14. Due to typology of the communication of course you can't communicate with more than one device at the same time on the same line. Modbus RTU is Master-Slave protocoll. it means that only the master could manage any request and each time only the related slave could answer. I think you could manage indipendently the two SCY so you could control two motors at the same time. I think you are able to command all devices in the same line by a broadcasting command (address 0), but no-one will answer. If you had used a master canopen card on the CPU you could have managed all 17 devices on the same bus faster and better.
  15. Modicon Premiun RS485

    first, who is the master?? second, which protocol?? Is it right for what?? In such a way you are technically writing 1450 Hex (or 5200 Dec) in the register 103 of PLC. But has no meaning if you don't explain clearly. Basically in order to implement a communication with an instrument you have to: estabilish the connection and you say RS485 define the protocol = normally in such a case PLC is master and I suppose is Modbus so Modbus RTU master configure protocol (the same for both master and slave(s)) prepare an exchange data list (managed by the master) = data read/write address, memory map develop the software for reading/writing = usually function named READ_VAR or WRITE_VAR (if you had an ethernet module, through a gateway like TSXETG100, you could have used I/O scanning services) So I suppose you need to study how to use that function for PREMIUM and study how Modbus protocol works. Begin to search for READ_VAR function in h elp of PL7PRO then post all your doubt.