SAFIRE Systems Engineering Tutorial
Contents
1. from the context menu Select the Active state as the destination and click OK CREATE SECOND SBUS IDLE STATE INPUT In the Idle state an incoming Deact_Rq signal requires sending Deact_Ind to Master and Slave without changing the state of the SBUS The new input handler should be at the same level as the first input handler that you just created 1 Right click on the existing AC Po input symbol and select Insert Right gt INPUT from the context menu 2 In the Input dialog set the signal name to Deact_Rq and the gate name to ANY 3 Insert an output symbol under the new input sending Deact_Ind to the Upper_1 gate 4 Insert another output symbol after the first sending Deact_Ind to Upper_2 5 Inserta NEXTSTATE symbol with No State Change as its destination 6 Save changes Powered by SAFIRE Sytems Engineering Tutorial C ight 1990 2007 SOLINET GmbH All righ d SAFIRE SE names are trademarks EE e Page 16 Pure Signaling Specifications subject to change without notice SOLINET 9 ti for H e Net kal The Idle state should now look like the following screenshot SBUS Idle state SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 17 All product names are trademarks of their respective owners Specifications subject to change without notice Powered by SAFIRE Pure Signaling SOLINET IMPLEMENT SBUS ACTIVE STATE The Active state2. Insert gt Connection from the context menu The Connection dialog appears with fields for selecting the instances and gates to be connected On the left side select Master as the first instance Lower will be selected automatically as the gate On the right side select SBUS as the second endpoint Upper_1 will be selected automatically as the gate Add another connection that connects the Lower gate of the Slave FSM to the Upper_2 gate of the SBUS FSM Save changes The high level structure of the tutorial application is now complete Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 14 SAFI RE All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networks SBUS BEHAVIOR In this section states within the FSM types will be created Within each state a flow diagram will be created to describe the FSM s behavior upon receiving signals CREATE SBUS STATES 1 In the FSM Types view on the left side of the Editor open the SBUS_T node by double clicking it 2 Right click on the STATES node and click Insert gt STATE Name the new state Idle 3 Create a second new state named Active DEFINE SBUS START TRANSITION The START transition of the SBUS should put the SBUS in the Idle state 4 Right click on the START symbol and cl
3. state 1 2 3 In the Active state insert an input symbol for the Data_Ind signal After the new input symbol insert a new output symbol sending the Data_Rq signal via the Lower gate After the output put a NEXTSTATE symbol at the end of the action list with the value No State Change Insert another input to the right of the first input for the Deact _Ind signal In the action list of the new Deact_Ind input create a transition to the Idle state Slave_T Active state The Slave_T FSM type is now complete Save the project and return to the system view Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 20 SA Fl R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networks MASTER FSM TYPE The Master FSM will start the tutorial action by sending the first signal Each response from the SBUS will trigger another signal output from the Master causing the application to run in an infinite loop CREATE STATES The Master FSM type will need three states Act Data and Deact The state names reflect the name of the signal expected in each state 1 Double click the Master_T FSM type to edit it 2 Add the three new states SET START TRANSITION At system startup the Master FSM should send an Act_Rq signal then transition to th
4. will handle Activate and Deactivate signals and will also pass Data signals from one gate to the other Reuse the input handlers from the Idle state making minor changes 1 Copy the Idle state s input nodes and paste them into the Active state 2 In the Active state reset the NEXTSTATE for both inputs Below the Act_Rq input there should be no state change Below the Deact_Rq input there should be a transition to the Idle state 3 Insert a third input symbol to the right of the existing inputs In the Input dialog set the signal name to Data_Rq and the gate name to Upper_1 4 Right click on the new input symbol and add an output symbol In the Output dialog set the signal name to Data Ind Set the gate name to Upper_2 5 Below the new output symbol add a NEXTSTATE symbol with the value No State Change 6 Right click on the new input symbol and select Duplicate from the context menu A copy of the input symbol and its action list will be added to the flow diagram 7 Edit the duplicate input setting the gate to Upper_2 8 Edit the duplicate output setting the gate to Upper_1 STATE Active SBUS T Active state The SBUS_T FSM type is now complete Save the project and return to the system view Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 18 SA F R E All product names are trademarks of their respective owners Pure Signaling Specifications
5. you step by step in the creation and execution of a Finite State Machine FSM called the SBUS Although the SBUS is simple this tutorial will give you a chance to use all of the core tools of the SAFIRE environment First you will create a new system project in the SAFIRE Organizer and create the SBUS FSM in the SAFIRE Editor To exercise the SBUS you will create two other FSMs Master and Slave within the same system The Master and Slave processes will send signals to each other through the SBUS After compiling in the SAFIRE Organizer you can run the new system in the SAFIRE environment observing it with the SAFIRE Tracer and SAFIRE Animator PREREQUISITES The tutorial requires familiarity with Windows and programming It does not require previous knowledge of SAFIRE tools the SDL language or finite state machine terminology The tutorial assumes that the SAFIRE software and license files have been installed on your computer and the appropriate software sharing device has been attached For help in resolving installation issues please consult the Installation Manual Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 5 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networla SBUS APPLICATION DESIGN REQUIREMENTS Suppose there are t
6. Active state The flow of signals among the three processes is summarized in the following message sequence chart SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 8 All product names are trademarks of their respective owners Specifications subject to change without notice Powered by SAFIRE Pure Signaling SOLINET el VO Ss Act_Rq Act_Ind Act_Ind Data Ho Data Ind Data Ho Data Ind Deact_Rq Deact_Ind Deact_Ind Message sequence chart for the SBUS system SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 9 All product names are trademarks of their respective owners Specifications subject to change without notice Powered by SAFIRE Pure Signaling SOLINET Solutions for Innovative Networks CREATE A PROJECT Before creating state machines a SAFIRE archive must be created to contain the internal code A SAFIRE system project will be created inside the archive START THE SAFIRE ORGANIZER All SAFIRE tools are launched from the Organizer including the Editor and the compiler so the Organizer must be launched first 1 gie o o NOD Select Programs gt SAFIRE Professional nnnnnnnn gt SAFIRE Organizer where nnnnnnnn is the appropriate SAFIRE version number from the Windows Start menu In the Select an archive dialog click the Create button The Create New Archive
7. Deactivated In SAFIRE a group of signals is called an interface In an FSM each gate is assigned a specific interface and a gate can send and receive only the signals listed in its interface Two gates may be connected only if they have the same interface In this step of the tutorial an interface containing these six signals will be created first Later this interface will be assigned to the gates of our FSM types 1 In the Editor right click on the INTERFACES node of the SBUS1_APPL system and select Insert gt INTERFACE from the context menu Name the new interface SBUS INTF 2 Right click on the SBUS_INTF interface node and select Insert gt SIGNAL from the context menu In the Name field enter the signal name Ac Ho 3 In the same manner create the other five signals within SBUS_INTF 4 Save changes Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 11 SAFI RE All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networks CREATE STUB FSMS Following a top down development style three top level FSM types should be created for use in the system In this section the stub FSM types are created They are complete on the outside but empty on the inside Later in the document the internal states and behavior will be specified CREATE PROC
8. ESS TYPES A process type for each of our 3 processes should be created Later after defining other parts of the system return to the process types to define their state behavior 1 Right click on FSM TYPES and select Insert gt FSM Definition Name the new type Master_T 2 Create two more process types named Slave_T and SBUS T 3 Save changes CREATE GATES FOR MASTER_T AND SLAVE_T The only way to send a signal from one FSM to another is via a channel A channel connects two gates that have the same interface An interface has already been defined so now the gates must be defined Master_T and Slave_T need one gate each leading down to the FSM connecting them Note that same gate name can be used in two different FSM types 1 Edit Master_T by double clicking the FSM Master_T node in the FSM SBUS1_APPL structure tree 2 In the Master_T window right click on the GATES node and select Insert gt GATE 3 Name the new gate Lower because it will send signals to a lower layer in this case the SBUS From the dropdown list select the SBUS_INTF interface Save changes Return to the system by clicking the Up button in the toolbar Edit Slave_T by double clicking on it Add a gate to the Slave_T process type Name the gate Lower and select SBUS _INTF as its interface Save changes Return to the system by clicking the Up button in the toolbar NOOA Powered by SAFIRE Sytems E
9. LINET IMPLEMENT DEACT STATE The Deact state is also similar to the Act state The input handler accepts the Deact_Ind signal sends the Act_Rq signal and transitions to the Act state This forms an endless loop At runtime this endless loop can be halted by pausing the SAFIRE runtime using the Pause command in the File menu STATE Deact Master_T Deact state The Master_T FSM type is now complete Please Save SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 293 SA F R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice Powered by SOLINET Solutions for Innovative Networks ERROR DETECTION SYNTAX ERRORS If the source file was modified outside the Editor or an old file has been opened that is no longer accepted by the latest SAFIRE version the Editor might not be able to read the file Also in certain circumstances it is possible to create an incomplete specification in the Editor If the Editor cannot parse the source file it will refuse to open the file Instead it will offer to attempt to build the offending project in the Organizer The Organizer output window will display the filename and line number where the syntax error is found After correcting the syntax error in a text editor reopen the project to check it again SEMANTIC ERRORS If there is a semanti
10. SAFIRE Systems Engineering Tutorial Version 19 02 SOLINET Solutions for Innovative Networks SAFIRE Systems Engineering Tutorial Version 19 02 Copyright 1990 2007 SOLINET GmbH No part of this document may be reproduced in any form without written permission from SOLINET GmbH Specifications subject to change without notice All product and company names are trademarks of their respective owners All rights reserved SOLINET GmbH Tel 49 0 711 1398 0 Mittlerer Pfad 26 70499 Stuttgart Germany Fax 49 0 711 866 1240 Email Info SOLINET com Web www SOLINET com For technical support please contact Support SOLINET com Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 2 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative N tworlal Table of Contents INMOOUCUON E 5 e 5 ebe enger Eed 5 SBUS Application RT E 6 Requirements E 6 System EEN eege 7 Create a EE Eden 10 Start the SAFIRE Organizer ae ee 10 Create and Edit a System Project AAA 10 Greate an e E 11 Greate Stub FSMS E 12 Create Process Types seeteeegegetereerdeteriergeetegeegteueeEegEeCeeeNeeebeEeCgeEeeegbeglueEEe 12 Create Gates for Master_T and SIVE T net 12 Create Gates for SBUS_T wcccccccctscscccccssctscesscccessecececesecesccccevesesenecenencccscssw
11. c error in the program the SAFIRE compiler will not be able to compile it In this case the output window of the Organizer will display a list of compilation errors Double clicking on an error message will open the file in the Editor at the location of the error Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 24 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for lnmovative Networks RUNNING THE SBUS APPLICATION BUILD PROJECTS Before executing the system the projects must be compiled for the SAFIRE Runtime 1 Switch to the Organizer application 2 Select the SBUS1_APPL system project 3 Click build button in the toolbar or right click on the project and select build 4 In the Build Options dialog leave all the options unchecked and click OK 5 The Organizer will compile the project and report success or failure in the output window at the bottom of the application window 6 The status icons next to the SBUS1_APPL project should turn green and in the project list on the right side the status should change from Out of date to OK ee SBUS1_APPL ee SBUS1_APPL Status icons before on left and after on right a successful build If the build failed read the error message in the output window and consult the Error Detection section of this
12. dialog will appear Enter Tutorial as the archive name Enter C or any other path you wish as the archive path Set the build mode to SAFIRE Only because this tutorial does not require any C code Set the user mode to Single User Mode Click OK The Create New Version dialog will appear Leave all fields blank and click OK The Organizer will create the archive and open it CREATE AND EDIT A SYSTEM PROJECT A system project can be executed For the sake of simplicity in this tutorial a unique code will be created within a single system project 1 Right click on the ROOT folder and select Create gt System from the context menu 2 Inthe Create New System dialog enter SBUS1_APPL in the Name field 3 Select the new SBUS1_APPL system and click the Edit button in the Organizer toolbar The project will be opened in a SAFIRE Editor window Powered by SAFIRE Sytems Engineering Tutorial C ight 1990 2007 SOLINET GmbH All righ d SAFI RE D Ee are trademarks of their SE Page 10 Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networks CREATE AN INTERFACE The Requirements section above describes six signals that can be sent or received by an SBUS Act_Rq Request from upper layer to SBUS Activate Data_Rq Send data packet Deact_Rq Deactivate Act_Ind Indication from SBUS to upper layer Activated Data Ind Data packet received Deact_Ind
13. document RUN THE SYSTEM From the Organizer the compiled system project can be launched in the SAFIRE Runtime Select the SBUS1_APPL system project in the Organizer Click run button in the toolbar or right click on the project and select Run In the Run dialog check the Enable System Trace checkbox Leave the other checkboxes unchecked for now and click OK a add Two new application windows will appear one for SAFIRE Virtual Machine and one for SAFIRE Tracer The Virtual Machine window allows system configuration The Tracer window displays messages representing the signals sent and received by each FSM in a given system Note that this system sends messages without pausing between them Tens of thousands of messages per second may be sent using all available CPU time To restore normal computer operation pause the system 1 Restore the Virtual Machine window from the taskbar Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 25 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET 2 Select the SBUS1_APPL system in the Virtual Machine run time window Note that the Tx and Rx columns showing the number of signals transmitted and received per second contain high values 3 Select Pause from the System menu The numbers in the Rx and Tx columns will drop to ze
14. e Act state 1 Insert an output under the START symbol sending the Act_Rq signal via the Lower gate 2 Inserta NEXTSTATE symbol after the output symbol and set it to Act IMPLEMENT ACT STATE The only signal handled in the Act state is the Act_Ind signal which should cause a transition to the Data state 1 Insert an INPUT into the Act state with the signal name set to Act_Ind There is only one gate in this FSM type so the default ANY GATE option is OK 2 Insert an OUTPUT under the input symbol Send the Data Po signal via the Lower gate 3 At the end of the new input handler set the next state to Data See screenshot below Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 21 SAFI RE All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Master_T Act state IMPLEMENT DATA STATE The Data state is similar to the Act state The input handler accepts the Data_Ind signal sends the Deact_Rq signal and transitions to the Deact state STATE Data STATE Deact Master_T Data state Powered by SAFIRE Pure Signaling SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved All product names are trademarks of their respective owners Specifications subject to change without notice Page 22 SO
15. esesenenoneees 13 Create and Connect Instances EE 14 Create FSM Wl E le 14 Create GONNEGIONS saneren hesta ens ids hensen ide hensen drinnen trinten etende 14 SBUS BERAMO E 15 Greate SBUS States eene EE 15 Define SBUS Start Transition sissecccsinecsdecdencsceciescasecdeacadecdvecadedivecstacivacstadivacstacivanans 15 Create First SBUS Idle State Input 16 Create Second SBUS Idle State Input 16 Implement SBUS Active State enn 18 ER RK EE 19 NELE eege 19 Set Start E e een 19 Implement e TE 19 Implement Active State ENEE 20 Master FSM e 21 Create DIMES eieiei Eegeregie 21 Powered by SAFIRE Sytems Engineering Tutorial SAFIRE De Page 3 Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networks DEE Start FASO zoden geogr dende bande eege eege 21 Pl MER EE 21 Implement Data Eeer 22 Implement Deact State E 23 EOP STS AE E EE 24 OL EE e EEN 24 Semantic Ge 24 Running the SBUS Applicaton nr eren sneren eeen 25 Build Ge 25 R n the SY SU EE 25 View Messages in the System Tracer ee 26 Shut Down the System ext asosncoopssordeussenndanidobedonidunsaadodanidentaugaedidodadonnbentadedasededatene 27 Powered by SAFIRE Sytems Engineering Tutorial SAFIRE Al product names are iademarks of thelr respective owners Page 4 Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networks INTRODUCTION OVERVIEW This Tutorial will guide
16. ick Insert gt NEXTSTATE 5 In the NEXT STATE Editor select the Idle state and click OK The start transition is now complete 6 Save changes SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 15 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice Powered by SOLINET Solutions for lnmovative Networks CREATE FIRST SBUS IDLE STATE INPUT In the Idle state the SBUS should respond to an incoming AC Po signal by sending Act_Ind to Master and Slave and then changing its state to Active 1 7 8 9 Save changes To go to the Idle state select the Idle state in the tree view Alternately right click on the START state s NEXTSTATE symbol and select Go To Definition from the context menu Right click on the Idle state node and select Insert gt INPUT from the context menu In the Input dialog set the signal name to Act Rg set the gate name to ANY and click OK Right click on the INPUT Act_Rq node and select Insert gt OUTPUT from the context menu In the Output dialog click Signal select Act Ind in the Signal dropdown list select Upper_1 in the Gate dropdown list and click OK Add another output symbol after the first one sending the Act_Ind signal to the Upper_2 gate Right click on the second output symbol and select Insert After gt NEXTSTATE
17. ngineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 12 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET CREATE GATES FOR SBUS T SBUS T needs two gates one for each FSM connected to it 1 Edit SBUS_T by double clicking on it 2 Add two gates to the SBUS T process type Name the gates Upper_1 and Upper_2 and select SBUS_INTF as the interface for both gates 3 Save changes Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 13 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for lnmovative Networks CREATE AND CONNECT INSTANCES The FSM types are ready to be instantiated and connected CREATE FSM INSTANCES For each FSM type a single instance is required 1 2 3 4 Within the BEHAVIOR BLOCK node right click on FSM INSTANCES and select Insert gt INSTANCE Enter Master in the Name field select Master_T in the FSM Type list and click OK Create instances of the other two FSM types Slave of type Slave_T and SBUS of type SBUS_T Save changes CREATE CONNECTIONS Now connect the Master and Slave instances to the SBUS 1 5 Right click on the CONNECTIONS in the Editor tree view and select
18. racer Not capturing File Edit View Capture Filter Configure Help Bled Deja sel alslalsl a7 E1 2 3 e u m XX 9 12 10 38 417 Rx SBUS1_APPL SBUS Upper1 417 Tx SBUS1_APPL SBUS Upper1 417 Tx SBUS1 APPL SBUS Upper 417 Rs SBUS1 APPL Master Lower SBUS_INTF SEUS INTE SBUS_INTF SBUS_INTF Rx Rx Tx Rx Tx Rx Tz SBUS_INTF SBUS_INTF SBUS_INTF SBUS_INTF SBUS_INTF SBUS_INTF SBUS_INTF Slave Lower SBUS Upper1 SBUS Upper Slave Lower Slave Lower SBUS Upper 2 SBUS Upper1 418 418 418 418 418 418 418 SBUS1_APPL SBUS1_APPL SBUS1_APPL SBUS1_APPL SBUS1_APPL SBUS1_APPL SBUS1_APPL SBUS_INTF Data Ro HEX Ox00000000 00 00 00 04 O00 O00 O00 0D _ a PO be 81925 SBUS1_APPL messages captured by the System Tracer SHUT DOWN THE SYSTEM Act Ro Act_Ind Act_Ind Act Ind BE Ind Data Ro Data_Ind Data Ind Data Ro Data Ro A Data Ind w gt Tx To shut down the system completely the SAFIRE Virtual Machine must be ended To do this simply close the SAFIRE Virtual Machine window The System Tracer window will close automatically Powered by SAFIRE Sytems Engineering Tutorial SAFIRE Pure Signaling Specifications subject to change without notice Copyright 1990 2007 SOLINET GmbH All rights reserved All product names are trademarks of their respective owners Page 27
19. ro sbus4_appl sxij SAFIRE Virtual Machine Sven Configuration Debug Help Stop Contin Restart Statistics Exit Pausing a system in the Virtual Machine window The system execution can be continued later if desired VIEW MESSAGES IN THE SYSTEM TRACER The System Tracer shows all messages in the system In SAFIRE a message is the transmission or reception of a signal at an FSM gate By default a given signal will appear twice in the System Tracer once when it is sent and once more when it is received The first message will have the keyword Tx in its header the second will have Rx In the Tracer the capture of messages can be started and stopped independently of the system under observation To stop capture click the stop button in the toolbar When the Tracer is stopped one can scroll up and down in the window to look at any message It is also possible to search and to apply a filter to captured messages For more information open the Tracer user manual by selecting Help gt About in the Tracer window To restart capture click the start capture button in the Tracer toolbar Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 26 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networla All Systems SAFIRE T
20. s expect to receive Indication signals but cannot send them and expect to send Request signals but cannot receive them As a connector a third device is needed to translate Requests into Indications and to send Activate and Deactivate Indications to both devices This third device a software bus will be called the SBUS SYSTEM OVERVIEW SYSTEM PROJECT The first project of this tutorial is a system project a top level project that can be executed in the SAFIRE environment The system will contain three processes an SBUS a Master and a Slave The Master and Slave processes will be connected to the SBUS SBUS PROCESS The SBUS process will have two states Idle and Active The initial state will be Idle At any time upon receiving an Activate Request signal from either side the SBUS will send an Activate Indication signal to both sides and sets its own state to Active Powered by SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 7 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice SOLINET Solutions for Innovative Networks At any time upon receiving a Deactivate Request signal from either side the SBUS will send a Deactivate Indication signal to both sides and sets its own state to Idle In the Active state upon receiving a Data Request signal from one side the SBUS will
21. send a Data Indication signal to the other side In the first version of the SBUS simulation for simplicity s sake there will be no actual data in the data signals In more advanced SBUS versions we will enhance the data signals with a parameter an octet string carrying arbitrary data MASTER PROCESS The Master process cycles from one state to another in a simple fashion sending a signal then entering a new state in which it awaits the next signal At the start the Master process will send an Activate Request signal then enter the Act state In the Act state the Master process will wait for an Activate Indication signal then send a Data Request signal and enter the Data state In the Data state the Master process will wait for a Data Indication signal then send a Deactivate Request signal and enter the Deact state In the Deact state the Master process will wait for a Deactivate Indication signal then start the cycle again by sending an Activate Request signal and entering the Act state SLAVE PROCESS At the start the Slave process will enter the Idle state In the Idle state the Slave process will wait for an Activate Indication signal then enter the Active state In the Active state the Slave process will wait for two signals If a Deactivate Indication signal arrives the Slave process will enter the Idle state If a Data Indication signal arrives the Slave process will send a Data Request signal and enter the
22. subject to change without notice SOLINET Solutions for Innovative Networks SLAVE FSM TYPE The Slave FSM type is simple It exists merely to exercise the SBUS CREATE STATES The Slave FSM type will need two states Idle and Active 1 Double click the Slave_T FSM type to edit it 2 Add the two new states SET START TRANSITION At system startup the Slave FSM should transition immediately to the Idle state 1 Insert a NEXTSTATE symbol into the Start transition and set it to Idle IMPLEMENT IDLE STATE The only signal handled in the Idle state is the Act_Ind signal which should cause a transition to the Active state 1 Insert an INPUT into the Idle state with the signal name set to Act_Ind There is only one gate in this FSM type so the default ANY GATE option is OK 2 Within the new input set the next state to Active Slave_T Idle state SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 19 SAFI R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice Powered by SOLINET IMPLEMENT ACTIVE STATE In the Active state the Slave should reply to an incoming data indication by sending a data request The Slave should remain in the Active state because this behavior should recur until the Slave is deactivated In response to a Deact Ind signal the Slave should enter the Idle
23. wo devices Master and Slave simulated as finite state machines FSMs in SAFIRE You wish to connect the two FSMs The real Master and Slave devices would be connected by a cable To simulate the cable a third FSM the SBUS should be created Structure of the SBUS system The Master and Slave devices send Request signals Act_Rq Activate Request Deact_Rq Deactivate Request Data_Rq Data Request The Master and Slave devices receive Indication signals SAFIRE Sytems Engineering Tutorial Copyright 1990 2007 SOLINET GmbH All rights reserved Page 6 SA F R E All product names are trademarks of their respective owners Pure Signaling Specifications subject to change without notice Powered by SOLINET Solutions for Innovatie Network Act Ind Activate Indication Deact Ind Deactivate Indication Data Ind Data Indication Both devices send data by sending a Data Request signal and receive data by receiving a Data Indication signal Before the devices begin transferring data one of them must first send an Activate Request signal then both of them must receive an Activate Indication signal as confirmation that data transfer can begin At any time either device can end data transfer by sending a Deactivate Request signal which should be confirmed by a Deactivate Indication signal to both A direct connection between the Master and Slave will not work Both processe
Download Pdf Manuals
Related Search