Zuviel Werbung? - > Hier kostenlos beim SPS-Forum registrieren

Ergebnis 1 bis 5 von 5

Thema: Interface zu Transportsystem programmieren

  1. #1
    Registriert seit
    17.06.2015
    Beiträge
    1
    Danke
    0
    Erhielt 0 Danke für 0 Beiträge

    Standard


    Zuviel Werbung?
    -> Hier kostenlos registrieren
    Hallo,

    ich brauche die Schnittstellenprogrammierung zu einen Transportsystem von einen Lieferanten aus Italien.
    Ich benutze eine S7-300, über Ethernet wird eine Verbindung zu einen AGV-Master aufgenommen auf den ein SPS Manager installiert ist.

    Anbei der Text in der Spezifikation

    4. INTERFACING OF BAYS AND DOORS

    AGVManager supervisor is a type of software that is executed on the supervision PC and manages the missions of plant LGV's. It communicates with another software named PLCManager which is executed on the same supervision PC. PLCManager aims to implement communication with:
    · The PLC's of the plant (in this case with the PLC which manages the points of the plant where LGV performs the loading/unloading operations. );
    · the ADAM's of the plant (in this case those used for the management of traffic lights).

    A description of the interfacing between the LGV AGVManager plant supervisor and the PLC that manages the points of the plant where LGV's perform loading/unloading operations (called bays) is provided below. In the case of the plant, the new supply includes the following automatic bays:
    · Pick-up of Finished Product OUT_[A1]
    · Pick-up of Finished Product OUT_[B1]
    · Deposit of Finished Product IN_FP_1 [A2]
    · Deposit Finished Product IN_FP_2 [B2]
    · Pick-up of stacks of empty pallets OUT_EMPTY_PAL [C2]
    · Deposit of stacks of empty pallets IN_EMPTY_PAL [C1]
    managed by a single PLC, equipped with Ethernet card.

    The connection between the communication partners will be implemented through a wired Ethernet network.

    To exchange data between AGVMANAGER and the PLC, you will need to map a database area (DB) on the Siemens PLC where the Supervisor and the PLC will read and write.
    60 words will be mapped on the PLC DB. The first 30 words will be read by the AGVMANAGER Supervisor and in writing by the PLC S7-300; the next words will be written by the AGVMANAGER Supervisor and read by PLC S7-300.

    A database (DB) area will have to be mapped for each bay to manage.

    4.1 Exchange of Signals

    A description of the signals that must be exchanged between LGV and loading and unloading bays is provided below.

    From AgvManager to the Bay:
    Watchdog Output: signal used by devices that manage the bays in order to understand whether the AgvManager is active on the network
    Periodic signal with a period equal to 5 seconds.
    Request of Authorisation of Entry for Loading: it indicates that the LGV asks the Bay to provide its consent to enter in order to perform the loading operation
    0 = LGV DOES NOT ask for authorisation of entry
    1 = LGV asks for authorisation of entry
    Request of Enabling Entry for Unloading: it indicates that the LGV asks the Bay to provide its consent to enter in order to perform the unloading operation
    0 = LGV DOES NOT ask for authorisation of entry
    1 = LGV asks for authorisation of entry
    LGV in Bay Working Area: indicates if the LGV is with the forks in the working area with the pallet pick-up conveyor

    0 = LGV NOT in working area
    1 = LGV in working area
    Operation finished: indicates that the LGV has finished the pallet pick-up operation. When this signal is set, the LGV is still with the forks in the working area of the Bay
    0 = Operation NOT finished
    1 = Operation finished
    Mission State: indicates the status of the mission
    0 = Mission not under way
    1 = Loading mission under way
    2 = Unloading mission under way
    Table 1: description of signals from AgvManager to bay
    From the Bay to the AgvManager:

    Watchdog Input: signal used by the AgvManager to understand whether the device that manages the bay is active on the network
    Periodic signal with a 5 second period.
    Bay Banned: indicates that the bay is forbidden to function with the LGV. This signal must be normally high. If it takes on a low value, the Bay in question is not taken into consideration by the AgvManager for the scheduling of missions on it.
    0 = Bay Banned
    1 = Bay NOT Banned
    Bay State: indicates if the Bay is in normal automatic mode. If the value of this signal is low, it indicates that the bay is not in automatic or emergency mode.
    0 = Bay NOT in Automatic or in Emergency mode
    1 = Bay in Automatic mode
    Bay in Alarm: it indicates if the bay is in alarm.
    0 = Bay NOT in Alarm
    1 = Bay in Alarm
    LGV Load Call: it indicates to the AgvManager that on the bay there are pallets to pick up so that a mission toward the Bay can be scheduled.
    0 = Call NOT active
    1 = Call active
    LGV Unloading Call: it indicates to the AgvManager that on the bay there are empty locations where pallets can be unloaded so that a mission toward the Bay can be scheduled.
    0 = Call NOT active
    1 = Call active
    Authorisation to enter for Loading: it indicates that the Bay grants or not the consent to enter in order to perform the loading operation to the LGV after the latter has set the signal of Authorisation Request to Enter for Loading
    0 = Authorisation NOT granted
    1 = Authorisation granted
    Authorisation to enter for Unloading: it indicates that the Bay grants or not the consent to enter in order to perform the unloading operation to the LGV after the latter has set the signal of Authorisation Request to Enter for Unloading
    0 = Authorisation NOT granted
    1 = Authorisation granted
    Table 2: description of signals from bay to AgvManager
    4.2 Exchange Sequence of Bay Signals

    The signal exchange sequence during the unloading operation by an LGV vehicle of a load onto a bay is illustrated below.

    When it is possible to deposit the pallets on a bay (for example on bays of deposit of finished product or on the bay of deposit of empty pallets), the bay communicates that it is possible to deposit pallets, transmitting the following signals to the AgvManager:
    Bay - Bay Banned = 1 (Bay not banned)
    Bay - Bay state = 1 (Automatic)
    Bay - Bay in Alarm = 0
    Bay - LGV Loading Call = 1
    Bay - Authorisation to enter for Loading = 0
    When the LGV vehicle approaches the bay in call mode, it transmits the signal AgvManager - Request of Authorisation to Enter for Loading= 1.
    When the bay receives the signal AgvManager - Request of Authorisation to Enter for Loading=1, it checks the necessary conditions are met for the LGV vehicle to enter.
    If the conditions are met, the bay transmits the signal Bay - Authorisation to Enter for Loading = 1.
    Once this signal has been received, the LGV vehicle transmits the signal AgvManager - LGV in Bay working area = 1 to the bay that it now has to reset the signals Bay - LGV Loading Call = 0 and Bay - Authorisation to Enter for Loading = 1. = 0. In addition, when the bay receives the AgvManager - LGV in Bay working area = 1 signal, it must avoid any type of movement of the conveyors and anything that may interfere with the working area of the LGV vehicle.
    At the end of the operation, the LGV vehicle transmits the AgvManager - Operation Finished = 1 signal to the bay.
    Once the LGV vehicle has left the bay, the AgvManager resets all signals previously raised in the bay (AgvManager - LGV in Bay working area = 0, AgvManager - Request of Authorisation to Enter for Loading = 1. = 0 and AgvManager - Operation Finished = 0).

    When it is possible to pick up pallets from a bay (for example from the pick-up bay of finished product or on the pick-up bay of empty pallet stacks), the bay transmits the following signals to the AgvManager:
    Bay - Bay Banned = 1 (Bay not banned)
    Bay - Bay state = 1 (Automatic)
    Bay - Bay in Alarm = 0
    Bay - LGV Unloading Call = 1
    Bay - Authorisation to enter for Unloading = 0

    When the LGV vehicle approaches the bay in call mode, it transmits the signal: AgvManager - Request of Authorisation to Enter for Unloading= 1.
    When the bay receives the signal AgvManager - Request of Authorisation to Enter for Unloading=1, it checks the necessary conditions are met for the LGV vehicle to enter.
    If the conditions are met, the bay transmits the signal Bay - Authorisation to Enter for Unloading = 1.
    Once this signal has been received, the LGV vehicle transmits the signal AgvManager - LGV in Bay working area = 1 to the bay that it now has to reset the signals Bay - LGV Unloading Call = 0 and Bay - Authorisation to Enter for Unloading = 0. In addition, when the bay receives the AgvManager - LGV in Bay working area = 1 signal, it must avoid any type of movement of the conveyors and anything that may interfere with the working area of the LGV vehicle.
    At the end of the operation, the LGV vehicle transmits the AgvManager - Operation Finished = 1 signal to the bay.
    Once the LGV vehicle has left the bay, the AgvManager resets all signals previously raised in the bay (AgvManager - LGV in Bay working area = 0, AgvManager - Request of Authorisation to Enter for Unloading = 0 and AgvManager - Operation Finished = 0).
    The exchange of signals described is illustrated in Figure 6.

    [IMG]file:///C:/Users/k0921139/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png[/IMG]
    Figure 6: Graph of exchange of signals between bays and AgvManager



    4.3 Bay Memory Map

    For each automatic bay you need to define two Data Memory Blocks on the PLC:
    · DATA MEMORY READ used by the PLC which manages the bay to write and update signals and data for the PLCManager and consequently used by the PLCManager to cyclically read this information in order to have bay status always updated.
    · DATA MEMORY WRITE used by the PLCManager to write signals and data for the PLC that manages the bay. Thus the writing of signals and data is performed per event.
    The two Data Memory Blocks will consist of WORD data (16 bits).

    For each bay, the two Data Memory Blocks will be on the same DB of the Siemens PLC (a DB for each bay); thus for each bay you need to know:
    · IP Address of the PLC
    · DB number
    · Start Offset of the Data Memory Read
    · Length of Data Memory Read (number of words)
    · Start Offset of the Data Memory Write
    · Length of Data Memory Write (number of words)

    PICK-UP OF FINISHED PRODUCT OUT_ [A1]: DATA MEMORY READ

    Word 1 Watchdog Input
    0 for t= 5sec
    1 for t= 5sec
    Word 2 Bay Banned
    0 = Bay disabled (disabling ON)
    1 = Bay NOT disabled (disabling OFF)
    Word 3 Bay State
    0 = Bay in manual mode
    1 = Bay in automatic mode
    Word 4 Bay in Alarm
    0 = Bay NOT in Alarm
    1 = Bay in Alarm
    Word 5 LGV Loading Call
    0 = Bay NOT on Call for Loading
    1 = Bay on Call for Loading
    Word 6 Authorisation to Enter for Loading:
    0 = Authorisation NOT granted
    1 = Authorisation granted
    Word 7 Spare
    Word 8 Spare
    Word 9 Spare
    Word 10 Spare
    Word 11 Spare
    Word 12 Spare
    Word 13 Spare
    Word 14 Spare
    Word 15 Spare
    Word 16 Spare
    Word 17 Spare
    Word 18 Spare
    Word 19 Spare
    Word 20 Spare
    Word 21 Spare
    Word 22 Spare
    Word 23 Spare
    Word 24 Spare
    Word 25 Spare
    Word 26 Spare
    Word 27 Spare
    Word 28 Spare
    Word 29 Spare
    Word 30 Spare


    PICK-UP OF FINISHED PRODUCT OUT_ [A1]: DATA MEMORY WRITE

    Word 1 Watchdog Output
    0 for t= 5sec
    1 for t= 5sec
    Word 2 Request of Authorisation to Enter for Loading
    0 = LGV does not ask for the consent to enter the bay for Loading
    1 = LGV asks for the consent to enter the bay for Loading
    Word 3 LGV in the Bay working area
    0 = LGV outside the working area of the bay
    1 = LGV inside the working area of the bay
    Word 4 Operation finished
    0 = Operation NOT finished
    1 = Loading/Unloading Operation Finished
    Word 5 Mission State: indicates the status of the mission
    0 = Mission not under way
    1 = Loading mission under way
    2 = Unloading mission under way (FORESEEN)
    Word 6 Spare
    Word 7 Spare
    Word 8 Spare
    Word 9 Spare
    Word 10 Spare
    Word 11 Spare
    Word 12 Spare
    Word 13 Spare
    Word 14 Spare
    Word 15 Spare
    Word 16 Spare
    Word 17 Spare
    Word 18 Spare
    Word 19 Spare
    Word 20 Spare
    Word 21 Spare
    Word 22 Spare
    Word 23 Spare
    Word 24 Spare
    Word 25 Spare
    Word 26 Spare
    Word 27 Spare
    Word 28 Spare
    Word 29 Spare
    Word 30 Spare

    Vielen Dank schon mal im voraus...
    Zitieren Zitieren Interface zu Transportsystem programmieren  

  2. #2
    Registriert seit
    11.09.2007
    Ort
    Suedwestpfalz
    Beiträge
    917
    Danke
    81
    Erhielt 209 Danke für 192 Beiträge

    Standard

    Ist doch eine geniale Vorlage - der Ball liegt auf dem Elfmeterpunkt und der Torwart nicht da...

    Wo liegt eigentlich das Problem?
    Das Grauen lauert in der Zwischenablage !!

  3. #3
    Registriert seit
    30.10.2009
    Ort
    10 km vom Herzen der Natur
    Beiträge
    1.628
    Danke
    120
    Erhielt 340 Danke für 255 Beiträge

    Standard

    Du sollst eine Lösung liefern, keine dummen Kommentare!
    Gruß
    Michael

  4. #4
    Registriert seit
    12.04.2005
    Ort
    Black Forest
    Beiträge
    1.344
    Danke
    28
    Erhielt 131 Danke für 118 Beiträge

    Standard

    und jetzt

    Soll dies einer Programmieren oder wie ?

    „Eine Frage raubt mir den Verstand bin ich verrückt oder sind es die Anderen ?“

    Albert Einstein

  5. #5
    Registriert seit
    11.09.2007
    Ort
    Suedwestpfalz
    Beiträge
    917
    Danke
    81
    Erhielt 209 Danke für 192 Beiträge

    Standard


    Zuviel Werbung?
    -> Hier kostenlos registrieren
    Mal ehrlich, was ist denn daran schwer ein paar identische DBs mit 60Worten zu erstellen?
    Das Grauen lauert in der Zwischenablage !!

Ähnliche Themen

  1. TCP/IP Interface
    Von nimloth80 im Forum Sonstige Steuerungen
    Antworten: 0
    Letzter Beitrag: 28.02.2011, 11:59
  2. Interface Hart <-> PC
    Von drfunfrock im Forum Elektronik
    Antworten: 2
    Letzter Beitrag: 03.01.2011, 17:32
  3. Interface vs. Object ??
    Von Plea im Forum Programmierstrategien
    Antworten: 7
    Letzter Beitrag: 06.10.2010, 10:46
  4. Programmierstrategie für ein monoschienen Transportsystem
    Von drfunfrock im Forum Programmierstrategien
    Antworten: 6
    Letzter Beitrag: 26.10.2004, 16:58
  5. DP/DP Interface Specification
    Von Anonymous im Forum Feldbusse
    Antworten: 2
    Letzter Beitrag: 25.06.2004, 22:30

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •