{"id":183424,"date":"2024-09-06T14:23:46","date_gmt":"2024-09-06T14:23:46","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/knowledge\/?post_type=topic&p=183424"},"modified":"2025-04-04T16:23:22","modified_gmt":"2025-04-04T16:23:22","slug":"traffic-light-control-with-scade-guest-article-student-cinvestav","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/traffic-light-control-with-scade-guest-article-student-cinvestav\/","title":{"rendered":"Traffic Light Control with SCADE (Guest Article – Student – Cinvestav)"},"content":{"rendered":"

Guest Article – Student – Traffic Light Control with SCADE<\/h3>\n

This article is a guest contribution from Cinvestav<\/a>. It was written by a student group as part of Masters-level, semester long SCADE academic program<\/a> course.<\/p>\n

It explains the design and simulation of a system that controls the traffic light system of a four-way intersection with emergency vehicle priority.<\/p>\n

If you are an academic and are interested in teaching an engineering curriculum backed by Ansys tools, please have a look at our Ansys Funded Curriculum<\/a> page.<\/p>\n

<\/p>\n

Summary<\/h3>\n

The Intelligent Traffic Light System project addresses the need for improved emergency vehicle response times in urban environments. By utilizing transmitters and receivers to detect the presence of emergency vehicles (e.g., ambulances or patrol cars) in specific lanes, the system dynamically adjusts traffic light timings. Specifically, it prioritizes the passage of emergency vehicles by turning the light green for the lane in which they are present, facilitating their passage through intersections.<\/p>\n

This project was developed with the ANSYS SCADE Suite software, and its principal objective is to demonstrate the feasibility and advantages of integrating intelligent traffic management systems to prioritize emergency vehicle access while maintaining efficient overall traffic flow. The system’s sensors detect emergency vehicles and adjust the light sequence accordingly, ensuring that emergency response times are minimized without disrupting normal traffic operations. Through this adaptive mechanism, the project aims to enhance urban mobility and safety, setting a new standard for intelligent traffic management in modern cities.<\/p>\n

System Description<\/h3>\n

System Interface<\/h4>\n

The system receives the signals of two sensors for each lane; one of them named as beforeSensor<\/code> as it is placed before its corresponding lane Traffic Light, when it is triggered, it means the presence of a new emergency vehicle in that specific Lane. The other sensor is named afterSensor<\/code>, referring to it being placed after its corresponding Traffic Light, when it is triggered, the system takes it as the exit of an emergency vehicle, not necessarily from its own Lane. In exchange, the system delivers the red, green and yellow lights of each Traffic Lane, always having one of those three lights on, but never having more than one green light on at the same time.<\/p>\n

Here is a simple diagram that explains the expected placement of traffic lights and sensors in the environment planned for the system:<\/p>\n

<\/p>\n

The next image explains the system’s interface, having already explained its inputs and<\/p>\n

outputs:<\/p>\n

<\/p>\n

System Behavior<\/h4>\n

The traffic light system incorporates sensors capable of detecting emergency vehicles and adjusting the traffic signal pattern to ensure that the emergency vehicle’s lane has priority over the other ones. This system’s behavior provides a solution for emergency response while preserving the normal operation when no emergency vehicles are detected. Some of the principal functionalities of the Traffic Light Intersection are:<\/p>\n

    \n
  • The system shall work on a 4-lane intersection with 4 traffic lights, one for each lane.<\/li>\n
  • The emergency vehicles shall use transmitters that the sensors placed on the street can detect.<\/li>\n
  • The system shall use sensors placed before and after the traffic lights to detect the presence of emergency vehicles in dedicated lanes.<\/li>\n
  • The system shall detect the presence of an emergency vehicle when it triggers a sensor placed before the traffic light.<\/li>\n
  • The system shall consider that an emergency vehicle has passed when it triggers a sensor placed after a traffic light.<\/li>\n
  • The system shall prioritize the passage of emergency vehicles by turning green the traffic light when these vehicles are present.<\/li>\n<\/ul>\n

    Architecture<\/h4>\n

    The system is designed with several interconnected blocks. Each block performs a critical role in controlling and coordinating the traffic lights, ensuring efficient traffic flow and appropriately prioritizing emergency vehicles. Internal communication between these blocks is critical in determining the current status of each traffic light and dynamically adjusting it according to traffic conditions and signals received from emergency vehicles.<\/p>\n

    The system architecture diagram shows how these blocks interact with each other to manage emergency vehicle detection, prioritization and synchronization of traffic light changes.<\/p>\n

    <\/p>\n

    Below is a diagram illustrating the existing components of the system and the relationships between their inputs and outputs. This diagram provides a clear view of how each block within the system interacts with the others, showing the necessary connections and data flows for its operation.<\/p>\n

    Each block in the diagram represents an essential part of the system, and their interactions reflect the logical sequence of operations that allow the prioritization of emergency vehicles in the intelligent traffic light system. By understanding these relationships, one can better grasp the overall design of the system and the mechanisms that ensure its efficiency and effectiveness.<\/p>\n

    <\/p>\n

    Software Requirements<\/h3>\n

    There are twenty Software Requirements, which have been categorized in the functions the software will have to fulfill under different circumstances. These categories are:<\/p>\n

      \n
    • Standard behavior: This section of requirements describes the normal state of the system in which no emergency is present, it details the behavior of each traffic light independently by using states.<\/li>\n
    • Single emergency behavior: This section of requirements describes the system when only one emergency is currently occurring, so the lane of this emergency must be prioritized.<\/li>\n
    • Multiple emergencies behavior: This section of requirements describes the behavior of the system when there are two or more emergency vehicles at the same time in different lanes, these emergencies are attended in order of their arrival, because these lanes must be vacated as quickly as possible, the time limit to pass is not as long as when there is only one emergency.<\/li>\n
    • Emergencies Attended: This section of requirements describes the process that is carried out when an emergency has finished: it can be either because an ambulance has already left a lane or the time limit for it to pass has elapsed.<\/li>\n<\/ul>\n

      Once the software requirement categories are specified, some examples of the requirements of each of them will be listed:<\/p>\n

      Standard behavior<\/strong><\/p>\n

      REQ TL_SB_01: When it’s booted for the first time, the system shall display red at the four traffic lights by default.<\/p>\n

      REQ TL_SB_03: While one of the traffic lights is on green or yellow light, the rest of the traffic lights shall maintain a red light until commanded.<\/p>\n

      REQ TL_SB_08: When there are no current emergencies and the system detects one emergency vehicle incoming, the traffic light that’s currently on green light shall change immediately to a yellow light and after 5 seconds it shall turn into a red one.<\/p>\n

      Single emergency behavior<\/strong><\/p>\n

      REQ TL_SEB_01: The system shall be able to detect in which lane an input sensor has been activated by an emergency vehicle.<\/p>\n

      REQ TL_SEB_03: The system shall be able to detect an emergency vehicle only once, even if the vehicle stays in front of the sensor for a long period of time.<\/p>\n

      REQ TL_SEB_04: When there are no current emergencies and the system detects one emergency vehicle, the system shall focus on setting the emergency lane into a green light.<\/p>\n

      REQ TL_SEB_05: While there is one current emergency, the time of each green light of all traffic lights shall be 80 seconds.<\/p>\n

      Multiple emergencies behavior<\/strong><\/p>\n

      REQ TL_MEB_01: The system shall register the lanes where there’s been an unattended emergency.<\/p>\n

      REQ TL_MEB_02: While there is more than one emergency, the time of each green light of all traffic lights shall be 60 seconds.<\/p>\n

      Emergencies attended elements<\/strong><\/p>\n

      REQ TL_EA_01: When a post-signal emergency vehicle is received and there are multiple emergencies, the traffic light currently in green shall change to yellow and then to red. REQ TL_EA_02: When a post-signal emergency vehicle is received and there are multiple emergencies, the system shall focus on the next emergency to attend and set the corresponding lane into a green light.<\/p>\n

      REQ TL_EA_03: When the time limit for emergency vehicles has elapsed and there are multiple emergencies, the system shall focus on the next emergency to attend and set the corresponding lane into a green light.<\/p>\n

      Software Model Description<\/h3>\n

      The next part of the article will describe in detail which operators were used to provide a solution compliant of the project’s system and software requirements.<\/p>\n

      Constants and Data Types<\/h4>\n

      DATA TYPES<\/strong><\/p>\n

      SCADE Suite’s data types can be broadly divided between two kinds: predefined and user defined.<\/p>\n

      The following table depicts the Traffic Light System user-defined data types:<\/p>\n\n\n\n\n\n\n\n
      Type<\/strong><\/td>\nDefinition<\/strong><\/td>\nEnum Values<\/strong><\/td>\n<\/tr>\n
      EmergencyState<\/strong><\/td>\nenum<\/code><\/td>\n[NORMAL, SINGLE_EMERGENCY, MULTIPLE_EMERGENCIES]<\/code><\/td>\n<\/tr>\n
      LaneNumber<\/strong><\/td>\nenum<\/code><\/td>\n[LANE1, LANE2, LANE3, LANE4, NONE]<\/code><\/td>\n<\/tr>\n
      LightType<\/strong><\/td>\nenum<\/code><\/td>\n[RED, YELLOW, GREEN]<\/code><\/td>\n<\/tr>\n
      Emergencies<\/strong><\/td>\nLaneNumber^4 (array)<\/code><\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      CONSTANTS<\/strong><\/p>\n

      Constant values that will be consistently used within a system are documented in this section, as depicted in the following Table.<\/p>\n\n\n\n\n\n\n\n\n\n\n
      Name<\/strong><\/td>\nData Type<\/strong><\/td>\nValue<\/strong><\/td>\n<\/tr>\n
      FREQUENCY<\/strong><\/td>\nint64<\/code><\/td>\n50000000<\/code><\/td>\n<\/tr>\n
      GREEN_LIGHT_DEF<\/strong><\/td>\nint64<\/code><\/td>\n10<\/code><\/td>\n<\/tr>\n
      SENSOR_MIN<\/strong><\/td>\nfloat32<\/code><\/td>\n3.5<\/code><\/td>\n<\/tr>\n
      TIME_LIMIT_MULTIPLE<\/strong><\/td>\nint64<\/code><\/td>\n10<\/code><\/td>\n<\/tr>\n
      TIME_LIMIT_SINGLE<\/strong><\/td>\nint64<\/code><\/td>\n15<\/code><\/td>\n<\/tr>\n
      YELLOW_LIGHT_DEF<\/strong><\/td>\nint64<\/code><\/td>\n5<\/code><\/td>\n<\/tr>\n
      EMPTY_EMERGENCY<\/strong><\/td>\nEmergencies<\/code><\/td>\n[NONE, NONE, NONE, NONE]<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Software Model Operators<\/h4>\n

      CALL GRAPH<\/strong><\/p>\n

      The tree of the model operators is shown in the call diagram below, the operator<\/p>\n

      “TopIntersection” is the root operator.<\/p>\n

      1. TrafficLight
      \n1.1 TopIntersection
      \n1.2 BasicBlocks<\/p>\n

      1.2.1 Counter
      \n1.2.2 EdgeDetector<\/p>\n

      1.3 INOUT_Handler<\/p>\n

      1.3.1 InputRegulator
      \n1.3.2 OutputHandler
      \n1.3.3 StateToRGB<\/p>\n

      1.4 Emergency_Handler<\/p>\n

      1.4.1 DetectEmergencies
      \n1.4.2 EmergencyVehicleDetector
      \n1.4.3 WhichLane<\/p>\n

      1.5 EmergenciesList_Handler<\/p>\n

      1.5.1 AddToListEmergencies
      \n1.5.2 AttendNextEmergency
      \n1.5.3 DeleteFromListEmergencies
      \n1.5.4 EmergencyListHandler
      \n1.5.5 EmergecyStateCalculator<\/p>\n

      1.6 TrafficLights_Handler<\/p>\n

      1.6.1 SM_TrafficLightState
      \n1.6.2 TrafficLightHandler<\/p>\n

      1.7 Intersection_Controller<\/p>\n

      1.7.1 IntersectionController
      \n1.7.2 SM_TrafficState<\/p>\n

      TOP INTERSECTION OPERATOR<\/strong><\/p>\n

      This operator is the interface of the system, in other words, it contains its inputs and outputs, which have been already explained earlier.<\/p>\n

      <\/p>\n

      INTERSECTION CONTROLLER OPERATOR<\/strong><\/p>\n

      This module connects the system’s principal operators, its main function is to integrate the different<\/p>\n

      modules to ensure that they work together effectively.<\/p>\n

      DetectEmergencies <\/em>receives the outside sensors and delivers the flags that denote when and from which lane an emergency vehicle has been detected. EmergenciesListHandler <\/em>updates the list of emergencies unattended whenever an emergency vehicle has been detected entering or exiting the intersection.<\/p>\n

      SM_TrafficState <\/em>and TrafficLightsHandler <\/em>work in a symbiotic, reciprocating way. The first one is a state machine that receives the current state of the traffic lights and sends the signals in charge of changing them, the second one receives these signals and acts correspondingly, sending back the current state of the traffic lights. These states are also sent outside of the system by OutputHandler<\/em>.<\/p>\n


      \n
      \n
      \n<\/p>\n

      SM_TRAFFIC STATE OPERATOR<\/strong><\/p>\n

      All traffic lights need a signal to know when to change from red to green or green to red, so this module controls when these signals are activated, this module is necessary to synchronize all the lights and make sure that each change is executed correctly.<\/p>\n

      This module has a state machine with 4 main states LightLane1<\/em>, LightLane2<\/em>, LightLane3 <\/em>and LightLane4<\/em>, a transition state Emergency<\/em>_Lane <\/em>and a state that sets every light to red in special cases.<\/p>\n

      Every main state represents one of the four traffic lights, inside of every state, its own signal to go to green is activated and the signals of the other traffic lights are deactivated, also the signals to go to red of every traffic light is deactivated, this is for be prepared to activate these signals in other states.<\/p>\n

      The normal behavior of the system is a cyclic clockwise order, this means that every traffic light has a turn to be green and only changes to the next traffic light when the current traffic light has just changed to red.<\/p>\n

      When an emergency is detected, the system uses the transition state, this state is a connection between all states and set every light to red before entering to any other state, and similar to this transition state, every main state has a state that sets their own light to red, and continues only when all the lights are red.<\/p>\n

      This module has an array that contains the list of emergencies and a signal that indicates when a new emergency has been detected.<\/p>\n

      This module has an output that indicates the current state of each traffic light, it can be RED, YELLOW or GREEN.<\/p>\n

      <\/p>\n

      TRAFFIC LIGHT HANDLER OPERATOR<\/strong><\/p>\n

      This module controls the inputs and outputs of the state machine of each traffic light, it has all the inputs that every traffic light needs, the signal goGreen <\/em>to set the green light, the signal goRed <\/em>to set the red light and the emergencyState <\/em>signal that indicates if there is a current emergency in the system.<\/p>\n

      Also, it has every state of all the traffic lights as a output and a signal that indicates if a traffic light green time limit has elapsed to delete an emergency in that case by the output deleteEmergency<\/em>.<\/p>\n

      <\/p>\n

      STATE MACHINE TRAFFIC LIGHT OPERATOR<\/strong><\/p>\n

      This module controls the state of one traffic light, it contains a state machine with red, yellow and green states. The initial and main state is the Red state, it only goes to green state when it is indicated with the goGreen <\/em>input signal, it stays in that state for a period of time set by the current state of the system using the emergencyState <\/em>input, if there is an emergency, the time in green will be longer, if there is more than one emergency, the time in green returns to normal, the green state can be interrupted by the input signal goRed<\/em>, is important to specify that before set the traffic light to red, it is set to yellow first. The traffic light is going to turn red again after a period set by the constant YELLOW<\/em>_LIGHT<\/em>_DEF<\/em>. Also, this module can send a signal when the green time has done using the emergencyGreenDone <\/em>output.<\/p>\n

      <\/p>\n

      EMERGENCY STATE CALCULATOR OPERATOR<\/strong><\/p>\n

      This module performs the task of determining the state of the system, the system can be in three states, NORMAL<\/em>, SINGLE<\/em>_EMERGENCY <\/em>and MULTIPLE<\/em>_EMERGENCIES<\/em>, this is especially useful for determining the green light time period at any time.<\/p>\n

      The module has the list of emergencies as an input, if the firs element is empty, the current state is NORMAL, if the first element is not empty, the current state is SINGLE_EMERGENCY, and if the first and second element are not empty, the current state is MULTIPLE_EMERGENCIES.<\/p>\n

      <\/p>\n

      ATTEND NEXT EMERGENCY OPERATOR<\/strong><\/p>\n

      This module has the function of signaling when the system must focus on the next emergency to be attended. This flag can be raised either when there were no emergencies and one has just appeared, or when there are multiple emergencies, and one has already been handled, leaving room for the system to focus on the next one.<\/p>\n

      The module receives the list of emergencies, analyses the current and last number of emergencies in the system and sets a flag to true <\/em>when one of the cases already mentioned happens.<\/p>\n

      <\/p>\n

      EMERGENCY LIST HANDLER OPERATOR<\/strong><\/p>\n

      This module has the function to manipulate the system’s list of emergencies, adding or erasing one as received signals command it. It receives the boolean inputs emergencySignal<\/em>, mustEraseEmergency <\/em>and emergencyDoneSignal. <\/em>If the first one has a true <\/em>value, the module will enable AddToListEmergencies <\/em>and add the value of emergencyLane <\/em>at the end of the List. If mustEraseEmergency <\/em>or emergencyDoneSignal <\/em>are true, the module will enable DeleteFromListEmergencies allowing the list to erase its first element and roll the other ones.<\/p>\n


      \n<\/p>\n

      DELETE FROM LIST EMERGENCIES OPERATOR<\/strong><\/p>\n

      This module, whenever it is enabled, has the function to delete the first emergency from the emergencies list. It receives the list and takes only its last three elements, adding a new one with the value of NONE <\/em>at the end of it. Simulating the behavior of a FIFO list.<\/p>\n

      <\/p>\n

      ADD TO LIST EMERGENCIES OPERATOR<\/strong><\/p>\n

      This module has the function of registering the next emergency that is detected, it will save the line in which the emergency occurs knowing where it was saved in order of how the emergencies are arriving.<\/p>\n

      It imitates a FIFO list behavior so the system can always access the first element to attend the next emergency or check if there are any emergencies at the moment.<\/p>\n

      This module has the current list of emergencies as an input and a data type<\/p>\n

      emergencyLane<\/em>, that indicates the line where the emergency was detected.<\/p>\n

      The module has an array output that indicates the new list of emergencies with the last emergency detected added.<\/p>\n


      \n
      \n<\/p>\n

      DETECT EMERGENCIES OPERATOR<\/strong><\/p>\n

      This module uses the EmergencyVehicleDetector <\/em>block to constantly monitor all sensors, and when a signal is detected from some of them, an emergencySignal <\/em>or emergencyDoneSignal <\/em>is sent to warn that an emergency was detected, also the module sends on which line it was detected a vehicle on the sensor before the traffic light using the emergencyLane <\/em>output.<\/p>\n


      \n<\/p>\n

      EMERGENCY VEHICLE DETECTOR OPERATOR<\/strong><\/p>\n

      This module has four inputs that represents four sensors, the input of every sensor is modulated to have a boolean response instead a voltage level using the inputRegulator <\/em>block, if there is any change detected, the module sends an output signal Alert and a data indicating the lane in which the emergency was detected.<\/p>\n

      <\/p>\n

      WHICH LANE OPERATOR<\/strong><\/p>\n

      This module receives four boolean signals and sends a data type LaneNumber <\/em>to indicate which of the four signals is activated.<\/p>\n

      <\/p>\n

      INPUT REGULATOR OPERATOR<\/strong><\/p>\n

      This module receives a data that represents a voltage level and if the input is less than the constant SENSOR_MIN<\/em>, the output is false by the other hand if the input is bigger or equal than the constant, the output is true, so the module can set a range of detection for each sensor.<\/p>\n

      STATE TO RGB OPERATOR<\/strong><\/p>\n

      The entire system has an independent state for each traffic light, so this block translates these states to its respective boolean value, because each traffic light needs three boolean values for the three lights red, yellow and green.<\/p>\n

      <\/p>\n

      OUTPUT HANDLER OPERATOR<\/strong><\/p>\n

      This module has the function to use four instances of StateToRGB<\/em>, one for each Traffic Light, to convert the system type LighState <\/em>to three booleans that indicate the whether the green, red and yellow lights of each Traffic Light must be on or off.<\/p>\n


      \n<\/p>\n

      COUNTER OPERATOR<\/strong><\/p>\n

      This operator is a counter used to wait for the time required for a traffic light to stay on green light and yellow light.<\/p>\n

      It has a Limit input where you enter the cycles to count, a reset input where you enter when you want to restart the counter and an output with the result of the count.<\/p>\n

      <\/p>\n

      EDGE DETECTOR OPERATOR<\/strong><\/p>\n

      This operator detects a rising edge on an input signal, resulting in a signal that lasts only one clock cycle, and is used for various system processes such as vehicle detection.<\/p>\n

      <\/p>\n

      Verification<\/h3>\n

      A critical part of the project development is to do the verification (testing and coverage) of the software. The following are two examples of the tests that were created to verify the system’s correct behavior.<\/p>\n

      <\/p>\n

      \n
      #<\/span>\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/<\/span>\r\n# Test Case Reference :<\/span>\r\n# TL_TEST_IB_06<\/span>\r\n#Test case Objectives :<\/span>\r\n# Verify the system is able to detect emergency only once even if the emergency vehicle Stays<\/span>\r\n#  on the sensor.<\/span>\r\n#Covered Requirements :<\/span>\r\n# TL_SEB_03<\/span>\r\n#Test Case Acceptance Criteria :<\/span>\r\n# check the green light of a lane when sensorBeforeLane is 5.0 and it shall be green only the<\/span>\r\n#  specified time.<\/span>\r\n#Test case Description :<\/span>\r\nSSM::<\/span>set TopIntersection\/<\/span>sensorBeforeLane4 5.0<\/span>\r\nSSM::<\/span>cycle 15<\/span>\r\nSSM::<\/span>check TopIntersection\/<\/span>greenLightLane4 true<\/span> sustain=<\/span>1<\/span>\r\nSSM::<\/span>set TopIntersection\/<\/span>sensorBeforeLane4 0.0<\/span>\r\nSSM::<\/span>cycle 15<\/span>\r\n#--------------------------------------------------------<\/span>\r\n<\/pre>\n<\/div>\n
      <\/p>\n
      \n
      #<\/span>\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/<\/span>\r\n# Test Case Reference:<\/span>\r\n# TL_TEST_IB_01<\/span>\r\n#Test Case Objectives :<\/span>\r\n# Verify that when the system is booted, the four traffic lights are in red.<\/span>\r\n#Covered Requirements :<\/span>\r\n# TL_SB_01<\/span>\r\n#Test Case Acceptance Criteria :<\/span>\r\n# Check the four lights redLightLane1, redLightLane2, redLightLane3 and redLightLane4, these<\/span>\r\n#   signals shall be true.<\/span>\r\n# Test Case Description :<\/span>\r\nSSM::<\/span>check TopIntersection\/<\/span>redLightLane1   true<\/span>\r\nSSM::<\/span>check TopIntersection\/<\/span>redLightLane2   true<\/span>\r\nSSM::<\/span>check TopIntersection\/<\/span>redLightLane3   true<\/span>\r\nSSM::<\/span>check TopIntersection\/<\/span>redLightLane4   true<\/span>\r\nSSM::<\/span>cycle 5<\/span>\r\n#--------------------------------------------------------<\/span>\r\n<\/pre>\n<\/div>\n
      Once all the tests corresponding to the software requirements have been done, it is mandatory to execute them to know if the model of software fulfills its expected functions. After passing the tests, making the model coverage is the next step.<\/p>\n
      As can be seen in the next images, the software model passed all the tests, and the tests have a coverage of 100%<\/p>\n

      \n
      \n<\/p>\n
      Implementation<\/h3>\n
      Implementation can take two different forms, whether via simulation or via physical application.<\/p>\n
      The first one can be executed with a control panel built in the tool SCADE Rapid Prototyper. The simulation shows the four Traffic Lights of the intersection and their behavior both under normal and urgent circumstances. The operator can use the switch at the right of the panel to emulate the presence of an incoming emergency vehicle by putting one of the Before levers <\/em>in an ON state. Similarly, the operator can simulate the exit of an emergency vehicle by putting one of the After <\/em>levers in an ON state.<\/p>\n
      <\/p>\n
      There are some scenarios implemented in simulation using the panel to show some functionalities, the scenarios that are shown below are tests shown later in the article.<\/p>\n
      Scenario 1:<\/p>\n
      Test ID: TL_TEST_SEB_03<\/strong><\/p>\n
      When an emergency is detected, the system shall set the current green light into a red light and set green the traffic light of the corresponding lane of the emergency.<\/p>\n
      <\/p>\n
      After 15 cycles is set green light of the lane 4:<\/p>\n
      <\/p>\n
      Test ID: TL_TEST_IB_01<\/strong><\/p>\n
      When the system starts, all traffic lights shall be red.<\/p>\n
      <\/p>\n
      Test ID: TL_TEST_MET_01<\/strong><\/p>\n
      When two or more emergencies are detected, the system shall attend these emergencies in order they arrive.<\/p>\n
      <\/p>\n
      After 10 cycles is set green light of the lane 3:<\/p>\n
      <\/p>\n
      After 10 cycles is set green light of the lane 1:<\/p>\n
      <\/p>\n
      The second kind of demonstration is the physical implementation. This one entails the use of different components, that will be listed below:<\/p>\n
        \n
      • Arduino Mega 2560.<\/li>\n
      • 4 mini-Traffic Light GYR modules.<\/li>\n
      • 8 receiver phototransistors.<\/li>\n
      • 4 infrared diodes.<\/li>\n
      • 4 battery holders type AA.<\/li>\n
      • A Model of a four-way street.<\/li>\n<\/ul>\n
        In the next images, the physical implementation can be seen:<\/p>\n

        \n<\/p>\n
        Results<\/h3>\n
        The intelligent traffic light system demonstrated its capability to enhance emergency vehicle response times in urban settings. By utilizing transmitters and receivers to detect emergency vehicles in specific lanes, the system dynamically adjusted traffic light timings, prioritizing green light extensions for lanes with detected emergencies.<\/p>\n
        This adaptive approach significantly improved the efficiency of emergency vehicle passage through intersections, potentially leading to faster response times and enhanced safety outcomes. The project highlighted the feasibility and advantages of integrating intelligent traffic management systems in urban environments, aiming to establish a new standard in urban mobility and safety by effectively balancing emergency vehicle prioritization with maintaining efficient traffic flow.<\/p>\n
        Feedback summary about MBD & SCADE<\/h3>\n
        MBD (Model-Based Design) and SCADE are powerful tools for developing embedded systems. They streamline the design process by allowing for detailed modeling and simulation before physical prototyping. This approach helps catch potential issues early and improves overall system reliability. The structured nature of MBD and the capabilities of SCADE have made project development more efficient and collaborative, especially in complex applications.<\/p>\n
        SCADE, particularly, offers specialized tools and environments specifically designed for safety-critical applications, such as aerospace, automotive, and industrial control systems. Its graphical modeling capabilities and automatic code generation features not only streamline the design process but also ensure compliance with safety standards and regulations.<\/p>\n
        About the authors<\/h3>\n\n\n\n\n
        \n
        <\/p>\n<\/td>\n
        		Patricio Emiliano Morales Diaz Patricio Emiliano Morales Diaz, graduated as a technologist in software development from Centro de Ense\u00f1anza T\u00e9cnica Industrial (CETI), Mexico in 2022. He is currently studying engineering in robotics at the Centro Universitario de Ciencias Exactas e Ingenier\u00edas (CUCEI). His interests include software development and programming, studies in embedded systems and the application of emerging technologies in innovative projects.<\/td>\n<\/tr>\n
        \n
        <\/p>\n<\/td>\n
        		Mariana Corona Aldana received the title of technologist in software development from Centro de Ense\u00f1anza Tecnica Industrial (CETI), M\u00e9xico, in 2022. She is currently studying to get a degree in Robotics from Centro Universitario de Ciencias Exactas e Ingenier\u00edas (CUCEI). Her interests include development of both software and embedded software.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"template":"","class_list":["post-183424","topic","type-topic","status-publish","hentry","topic-tag-cinvestav","topic-tag-guest-article","topic-tag-scade","topic-tag-scade-rapid-prototyper","topic-tag-scade-suite","topic-tag-scade-test","topic-tag-student"],"aioseo_notices":[],"acf":[],"custom_fields":[{"0":{"_edit_lock":["1743783672:1769"],"_edit_last":["1769"],"filter_by_optics_product":["Lumerical"],"_filter_by_optics_product":["field_64fb192ba3121"],"application_name":[""],"_application_name":["field_64a80903c8e15"],"family":[""],"_family":["field_64a809229a857"],"siebel_km_number":[""],"_siebel_km_number":["field_63ecbffce60db"],"salesforce_km_number":[""],"_salesforce_km_number":["field_63ecc018e60dc"],"km_published_date":[""],"_km_published_date":["field_64c77704499dd"],"product_version":[""],"_product_version":["field_64c776cb4fd2e"],"_bbp_forum_id":["27825"],"_bbp_topic_id":["196481"],"_bbp_author_ip":["194.98.52.82"],"_bbp_last_reply_id":["0"],"_bbp_last_active_id":["183426"],"_bbp_last_active_time":["2024-09-06 14:23:46"],"_bbp_reply_count":["0"],"_bbp_reply_count_hidden":["0"],"_bbp_voice_count":["0"],"_yoast_wpseo_content_score":["30"],"_yoast_wpseo_estimated-reading-time-minutes":["26"],"_btv_view_count":["1415"],"_bbp_likes_count":["5"],"_aioseo_title":[null],"_aioseo_description":[null],"_aioseo_keywords":["a:0:{}"],"_aioseo_og_title":[null],"_aioseo_og_description":[null],"_aioseo_og_article_section":[""],"_aioseo_og_article_tags":["a:0:{}"],"_aioseo_twitter_title":[null],"_aioseo_twitter_description":[null]},"test":"solution"}],"_links":{"self":[{"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/topics\/183424","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/topics"}],"about":[{"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":7,"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/topics\/183424\/revisions"}],"predecessor-version":[{"id":196481,"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/topics\/183424\/revisions\/196481"}],"wp:attachment":[{"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/media?parent=183424"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}