delay()<\/code> freezing the button.<\/p>\nBefore you begin<\/h2>\nParts<\/h3>\n
\n\n\nPart<\/th>\n Siratek product<\/th>\n Its own tutorial<\/th>\n<\/tr>\n<\/thead>\n \n\nArduino Uno<\/td>\n 2219<\/td>\n Getting Started with Arduino Uno<\/em><\/td>\n<\/tr>\n\nLED traffic light module<\/td>\n 49920<\/td>\n LED Traffic Light Module<\/em><\/td>\n<\/tr>\n\nTactile push button<\/td>\n 49488<\/td>\n Read a Push Button<\/em><\/td>\n<\/tr>\n\nPassive buzzer<\/td>\n 8051<\/td>\n Play Tones with a Passive Buzzer<\/em><\/td>\n<\/tr>\n\nBreadboard and jumper wires<\/td>\n <\/td>\n Using a Breadboard<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nBuild each of those three on its own first if you have not. This page assumes all three work separately, and the first stage below checks that assumption rather than trusting it.<\/p>\n
What this project is really teaching<\/h3>\n
A crossing is a state machine<\/strong>. At any moment it is in exactly one of a handful of states, and each state knows what comes next and when.<\/p>\nThat sounds grand for a set of lights. It matters because the obvious approach does not work:<\/p>\n
\/\/ The obvious version, which cannot work.\nif (buttonPressed()) {\n digitalWrite(green, LOW);\n digitalWrite(amber, HIGH);\n delay(3000); \/\/ the button is ignored for three seconds\n digitalWrite(amber, LOW);\n digitalWrite(red, HIGH);\n delay(8000); \/\/ and for eight more\n \/\/ ...\n}<\/code><\/pre>\nDuring those eleven seconds the sketch is blind. It cannot beep in a pattern, cannot watch the button, cannot do anything. Real crossings do all of that at once.<\/p>\n
The state machine solves it with no cleverness: a variable says which state we are in, a timestamp says when we entered it, and loop()<\/code> asks each pass whether it is time to move on. It is the millis()<\/code> pattern from Timing Without delay()<\/em>, applied to a sequence rather than one LED.<\/p>\nHow it works<\/h2>\n
Five states, and the rules between them:<\/p>\n
\n\n\nState<\/th>\n Lights<\/th>\n What ends it<\/th>\n<\/tr>\n<\/thead>\n \n\nTRAFFIC_GREEN<\/code><\/td>\nGreen<\/td>\n A button press, and<\/strong> at least 5 s since the last crossing<\/td>\n<\/tr>\n\nTRAFFIC_AMBER<\/code><\/td>\nAmber<\/td>\n 3 seconds<\/td>\n<\/tr>\n \nPEDESTRIAN_CROSS<\/code><\/td>\nRed<\/td>\n 8 seconds, with the buzzer beeping<\/td>\n<\/tr>\n \nPEDESTRIAN_CLEAR<\/code><\/td>\nRed, buzzer faster<\/td>\n 4 seconds<\/td>\n<\/tr>\n \nTRAFFIC_RETURN<\/code><\/td>\nAmber<\/td>\n 2 seconds, then back to green<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTwo design decisions are worth naming, because they are the difference between a toy and something that behaves properly.<\/p>\n
The minimum green time.<\/strong> Without it, holding the button down cycles the crossing continuously and traffic never moves. Five seconds of guaranteed green after a crossing finishes is what a real installation does, and it is one comparison in the code.<\/p>\nThe press is remembered, not acted on.<\/strong> Pressing during the red phase does not queue a second crossing. The request is recorded, and it is cleared when the crossing begins.<\/p>\n![\"The](\"http:\/\/siratek.net\/wp-content\/uploads\/2026\/11\/pedestrian-crossing-states.svg\")
The minimum green time is what stops a held button blocking traffic for ever.<\/figcaption><\/figure>\nBuild it in stages<\/h2>\n
Each stage ends with something you can see. Do not move on until you have seen it.<\/p>\n
Stage 1: prove the three parts<\/h3>\n
Wire all three and run this. It does nothing clever; it proves the wiring before any logic exists.<\/p>\n
\/\/ Siratek: stage 1. Each part, one at a time.\n\nconst int redPin = 8;\nconst int amberPin = 9;\nconst int greenPin = 10;\nconst int buttonPin = 2;\nconst int buzzerPin = 11;\n\nvoid setup() {\n pinMode(redPin, OUTPUT);\n pinMode(amberPin, OUTPUT);\n pinMode(greenPin, OUTPUT);\n pinMode(buzzerPin, OUTPUT);\n pinMode(buttonPin, INPUT_PULLUP);\n\n Serial.begin(9600);\n Serial.println(\"Siratek: red, amber, green, beep, then the button.\");\n\n int pins[] = {redPin, amberPin, greenPin};\n for (int i = 0; i < 3; i++) {\n digitalWrite(pins[i], HIGH);\n delay(600);\n digitalWrite(pins[i], LOW);\n }\n\n tone(buzzerPin, 1000, 300);\n}\n\nvoid loop() {\n Serial.println(digitalRead(buttonPin) == LOW ? \"pressed\" : \"up\");\n delay(300);\n}<\/code><\/pre>\nEach light in turn, one beep, then the button state printed. If any of those is wrong, fix it now: it will be far harder to find once there is a state machine on top.<\/p>\n
Stage 2: the sequence, without the button<\/h3>\n
Replace loop()<\/code> with a sequence that runs on a timer, so you can watch the timings and adjust them before the button complicates things.<\/p>\n\/\/ Siratek: stage 2. The sequence, triggered every 15 seconds.\n\nenum State { TRAFFIC_GREEN, TRAFFIC_AMBER, PEDESTRIAN_CROSS, PEDESTRIAN_CLEAR, TRAFFIC_RETURN };\n\nState state = TRAFFIC_GREEN;\nunsigned long stateSince = 0;\n\nvoid enter(State next) {\n state = next;\n stateSince = millis();\n\n digitalWrite(redPin, state == PEDESTRIAN_CROSS || state == PEDESTRIAN_CLEAR);\n digitalWrite(amberPin, state == TRAFFIC_AMBER || state == TRAFFIC_RETURN);\n digitalWrite(greenPin, state == TRAFFIC_GREEN);\n}\n\nunsigned long elapsed() {\n return millis() - stateSince;\n}\n\nvoid loop() {\n switch (state) {\n case TRAFFIC_GREEN:\n if (elapsed() >= 15000) enter(TRAFFIC_AMBER);\n break;\n case TRAFFIC_AMBER:\n if (elapsed() >= 3000) enter(PEDESTRIAN_CROSS);\n break;\n case PEDESTRIAN_CROSS:\n if (elapsed() >= 8000) enter(PEDESTRIAN_CLEAR);\n break;\n case PEDESTRIAN_CLEAR:\n if (elapsed() >= 4000) enter(TRAFFIC_RETURN);\n break;\n case TRAFFIC_RETURN:\n if (elapsed() >= 2000) enter(TRAFFIC_GREEN);\n break;\n }\n}<\/code><\/pre>\nWatch a full cycle. Adjust the numbers until the rhythm feels right. Notice that enter()<\/code> sets all three lights from the state, so no state can accidentally leave a light on: that is worth more than it looks.<\/p>\nStage 3: the button and the buzzer<\/h3>\n
Now add the request, the minimum green time, and the beeping. That is the complete sketch below.<\/p>\n
The complete sketch<\/h2>\n\/\/ Siratek: a pedestrian crossing.\n\/\/ Traffic runs on green until someone asks to cross.\n\nconst int redPin = 8;\nconst int amberPin = 9;\nconst int greenPin = 10;\nconst int buttonPin = 2;\nconst int buzzerPin = 11;\n\n\/\/ Timings, in milliseconds. Adjust to taste.\nconst unsigned long AMBER_TIME = 3000;\nconst unsigned long CROSS_TIME = 8000;\nconst unsigned long CLEAR_TIME = 4000;\nconst unsigned long RETURN_TIME = 2000;\nconst unsigned long MINIMUM_GREEN = 5000; \/\/ traffic gets at least this long\n\n\/\/ Beep rates: slow while crossing, urgent while clearing.\nconst unsigned long CROSS_BEEP = 700;\nconst unsigned long CLEAR_BEEP = 220;\n\nenum State { TRAFFIC_GREEN, TRAFFIC_AMBER, PEDESTRIAN_CROSS, PEDESTRIAN_CLEAR, TRAFFIC_RETURN };\n\nState state = TRAFFIC_GREEN;\nunsigned long stateSince = 0;\n\nbool requested = false;\n\n\/\/ Button debouncing, as in Making a Button Behave.\nint lastReading = HIGH;\nunsigned long lastChange = 0;\nconst unsigned long DEBOUNCE = 40;\n\nunsigned long lastBeep = 0;\n\nvoid enter(State next) {\n state = next;\n stateSince = millis();\n\n digitalWrite(redPin, state == PEDESTRIAN_CROSS || state == PEDESTRIAN_CLEAR);\n digitalWrite(amberPin, state == TRAFFIC_AMBER || state == TRAFFIC_RETURN);\n digitalWrite(greenPin, state == TRAFFIC_GREEN);\n\n noTone(buzzerPin);\n\n Serial.print(\"state: \");\n switch (state) {\n case TRAFFIC_GREEN: Serial.println(\"traffic green\"); break;\n case TRAFFIC_AMBER: Serial.println(\"amber\"); break;\n case PEDESTRIAN_CROSS: Serial.println(\"cross\"); break;\n case PEDESTRIAN_CLEAR: Serial.println(\"clearing\"); break;\n case TRAFFIC_RETURN: Serial.println(\"returning\"); break;\n }\n}\n\nunsigned long elapsed() {\n return millis() - stateSince;\n}\n\nvoid readButton() {\n int reading = digitalRead(buttonPin);\n\n if (reading != lastReading) {\n lastChange = millis();\n lastReading = reading;\n return;\n }\n\n \/\/ Act on a settled press, once.\n if (millis() - lastChange > DEBOUNCE && reading == LOW && !requested) {\n requested = true;\n Serial.println(\" request noted\");\n }\n}\n\nvoid beepEvery(unsigned long interval) {\n if (millis() - lastBeep >= interval) {\n lastBeep = millis();\n tone(buzzerPin, 1800, 80);\n }\n}\n\nvoid setup() {\n pinMode(redPin, OUTPUT);\n pinMode(amberPin, OUTPUT);\n pinMode(greenPin, OUTPUT);\n pinMode(buzzerPin, OUTPUT);\n pinMode(buttonPin, INPUT_PULLUP);\n\n Serial.begin(9600);\n Serial.println(\"Siratek: pedestrian crossing.\");\n\n enter(TRAFFIC_GREEN);\n}\n\nvoid loop() {\n readButton(); \/\/ every pass, whatever state we are in\n\n switch (state) {\n case TRAFFIC_GREEN:\n \/\/ Honour the request, but not before traffic has had its minimum.\n if (requested && elapsed() >= MINIMUM_GREEN) {\n enter(TRAFFIC_AMBER);\n }\n break;\n\n case TRAFFIC_AMBER:\n if (elapsed() >= AMBER_TIME) {\n requested = false; \/\/ the request has been granted\n enter(PEDESTRIAN_CROSS);\n }\n break;\n\n case PEDESTRIAN_CROSS:\n beepEvery(CROSS_BEEP);\n if (elapsed() >= CROSS_TIME) {\n enter(PEDESTRIAN_CLEAR);\n }\n break;\n\n case PEDESTRIAN_CLEAR:\n beepEvery(CLEAR_BEEP);\n if (elapsed() >= CLEAR_TIME) {\n enter(TRAFFIC_RETURN);\n }\n break;\n\n case TRAFFIC_RETURN:\n if (elapsed() >= RETURN_TIME) {\n enter(TRAFFIC_GREEN);\n }\n break;\n }\n}<\/code><\/pre>\nWhy readButton()<\/code> is called first, every pass<\/h3>\nBecause the button must work in every state, not only on green. Pressing during the crossing should be noticed and simply have no effect, rather than being missed entirely.<\/p>\n
That is also why the request is cleared when the crossing starts<\/strong>, not when the button is read. A press during the amber phase is part of the crossing already under way; a press during the crossing itself sets the flag again and will be honoured next time.<\/p>\nWhy tone()<\/code> and not digitalWrite()<\/code><\/h3>\nA passive buzzer needs a changing signal, and tone()<\/code> with a duration is non-blocking: it starts the note and returns immediately. beepEvery()<\/code> therefore costs nothing in the loop.<\/p>\nRemember that tone()<\/code> uses Timer2, so PWM on pins 3 and 11 is unavailable<\/strong>. Pin 11 is the buzzer here, which is fine, but it is why the lights are on 8, 9 and 10.<\/p>\nTesting it<\/h2>\n
Work through these deliberately. Each one checks a decision rather than the wiring.<\/p>\n
\n\n\nTry this<\/th>\n It should<\/th>\n<\/tr>\n<\/thead>\n \n\nLeave it alone<\/td>\n Stay on green indefinitely<\/td>\n<\/tr>\n \nPress once<\/td>\n Amber, then red with beeping, then back to green<\/td>\n<\/tr>\n \nPress, then press again during red<\/td>\n Nothing extra; one crossing<\/td>\n<\/tr>\n \nPress immediately after a crossing ends<\/td>\n Wait for the minimum green, then go<\/td>\n<\/tr>\n \nHold the button down<\/td>\n One crossing per minimum-green period, not continuous<\/td>\n<\/tr>\n \nPress during amber<\/td>\n No effect; the crossing is already starting<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nThe fifth is the one that catches a careless implementation, and the one a real crossing has to get right.<\/p>\n
Making it yours<\/h2>\n\n- A waiting light.<\/strong> A fourth LED lit from the moment the request is noted until the crossing begins. That is what tells a person their press registered, and it is one
digitalWrite()<\/code> in readButton()<\/code> and one in enter()<\/code>.<\/li>\n- A night mode.<\/strong> Add an LDR, and after dark make the amber flash rather than running the full sequence. Measuring Light with an LDR<\/em> has the threshold work.<\/li>\n
- Two directions.<\/strong> A second light module for the other road, red when the first is green. The state machine barely changes;
enter()<\/code> sets six pins instead of three.<\/li>\n- A countdown.<\/strong> A 7-segment display showing the seconds left to cross. Driving a 4-Digit 7-Segment Display<\/em> covers the multiplexing, and the number comes from
CROSS_TIME - elapsed()<\/code>.<\/li>\n<\/ul>\nTroubleshooting<\/h2>\n
\n\n\nSymptom<\/th>\n Likely cause<\/th>\n Check or fix<\/th>\n<\/tr>\n<\/thead>\n \n\nA light stays on in the wrong state<\/td>\n Set outside enter()<\/code><\/td>\nAll three are set there, from the state<\/td>\n<\/tr>\n \nButton does nothing<\/td>\n Not INPUT_PULLUP<\/code>, or wrong pin<\/td>\nStage 1 checks this<\/td>\n<\/tr>\n \nOne press causes several crossings<\/td>\n Not debounced, or the flag not cleared<\/td>\n Clear requested<\/code> when the crossing starts<\/td>\n<\/tr>\n\nHolding the button blocks traffic<\/td>\n No minimum green<\/td>\n That comparison is the fix<\/td>\n<\/tr>\n \nBuzzer silent<\/td>\n Active buzzer, not passive<\/td>\n tone()<\/code> needs a passive one<\/td>\n<\/tr>\n\nBuzzer sounds but an LED stopped dimming<\/td>\n tone()<\/code> has taken Timer2<\/td>\nPins 3 and 11 lose PWM<\/td>\n<\/tr>\n \nBeeping is irregular<\/td>\n delay()<\/code> crept back in<\/td>\nNothing in loop()<\/code> may block<\/td>\n<\/tr>\n\nSequence drifts over hours<\/td>\n Comparing millis()<\/code> wrongly<\/td>\nAlways subtract, as elapsed()<\/code> does<\/td>\n<\/tr>\n\nLights dim<\/td>\n All three on at once, or no resistors<\/td>\n The module has its own; check the module tutorial<\/td>\n<\/tr>\n \nWorks, then stops after seven weeks<\/td>\n millis()<\/code> rollover<\/td>\nSubtraction survives it; comparison does not<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nSources and attribution<\/h2>\n
All text, wiring guidance and code in this project are original Siratek work.<\/p>\n
\n- The component behaviour is as described in LED Traffic Light Module<\/em>, Read a Push Button<\/em> and Play Tones with a Passive Buzzer<\/em>, including the module\u2019s onboard current-limiting resistors and the
tone()<\/code> timer conflict.<\/li>\n<\/ul>\nThe state machine and the timings here are a teaching arrangement, not a specification for a real road crossing, which is a regulated installation with requirements this project does not attempt to meet. No third-party tutorial text, diagrams, photographs or code has been reproduced here.<\/p>\n
<\/p>\n<\/body>","protected":false},"excerpt":{"rendered":"
A working pedestrian crossing. The traffic light sits on green. Press the button and nothing happens for a moment, then amber, then red, a beep while the crossing is clear, and back to green after a sensible pause.<\/p>\n","protected":false},"featured_media":0,"template":"","siratek_tutorial_level":[],"class_list":["post-52309","siratek_tutorial","type-siratek_tutorial","status-publish","hentry"],"yoast_head":"\n
Project, a Pedestrian Crossing - siratek<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Project, a Pedestrian Crossing - siratek\" \/>\n<meta property=\"og:description\" content=\"A working pedestrian crossing. The traffic light sits on green. Press the button and nothing happens for a moment, then amber, then red, a beep while the crossing is clear, and back to green after a sensible pause.\" \/>\n<meta property=\"og:url\" content=\"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/\" \/>\n<meta property=\"og:site_name\" content=\"siratek\" \/>\n<meta property=\"og:image\" content=\"http:\/\/siratek.net\/wp-content\/uploads\/2026\/11\/pedestrian-crossing-states.svg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/pedestrian-crossing\\\/\",\"url\":\"http:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/pedestrian-crossing\\\/\",\"name\":\"Project, a Pedestrian Crossing - siratek\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/siratek.net\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/pedestrian-crossing\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/pedestrian-crossing\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/siratek.net\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/pedestrian-crossing-states.svg\",\"datePublished\":\"2026-11-01T10:50:55+00:00\",\"breadcrumb\":{\"@id\":\"http:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/pedestrian-crossing\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/pedestrian-crossing\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/pedestrian-crossing\\\/#primaryimage\",\"url\":\"https:\\\/\\\/siratek.net\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/pedestrian-crossing-states.svg\",\"contentUrl\":\"https:\\\/\\\/siratek.net\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/pedestrian-crossing-states.svg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/pedestrian-crossing\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/siratek.net\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Tutorials\",\"item\":\"https:\\\/\\\/siratek.net\\\/index.php\\\/tutorials\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Project, a Pedestrian Crossing\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/siratek.net\\\/#website\",\"url\":\"https:\\\/\\\/siratek.net\\\/\",\"name\":\"siratek\",\"description\":\"Your Best Electronic Retail Shop\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/siratek.net\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Project, a Pedestrian Crossing - siratek","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/","og_locale":"en_US","og_type":"article","og_title":"Project, a Pedestrian Crossing - siratek","og_description":"A working pedestrian crossing. The traffic light sits on green. Press the button and nothing happens for a moment, then amber, then red, a beep while the crossing is clear, and back to green after a sensible pause.","og_url":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/","og_site_name":"siratek","og_image":[{"url":"http:\/\/siratek.net\/wp-content\/uploads\/2026\/11\/pedestrian-crossing-states.svg","type":"","width":"","height":""}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/","url":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/","name":"Project, a Pedestrian Crossing - siratek","isPartOf":{"@id":"https:\/\/siratek.net\/#website"},"primaryImageOfPage":{"@id":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/#primaryimage"},"image":{"@id":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/#primaryimage"},"thumbnailUrl":"http:\/\/siratek.net\/wp-content\/uploads\/2026\/11\/pedestrian-crossing-states.svg","datePublished":"2026-11-01T10:50:55+00:00","breadcrumb":{"@id":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/#primaryimage","url":"https:\/\/siratek.net\/wp-content\/uploads\/2026\/11\/pedestrian-crossing-states.svg","contentUrl":"https:\/\/siratek.net\/wp-content\/uploads\/2026\/11\/pedestrian-crossing-states.svg"},{"@type":"BreadcrumbList","@id":"http:\/\/siratek.net\/index.php\/tutorials\/pedestrian-crossing\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/siratek.net\/"},{"@type":"ListItem","position":2,"name":"Tutorials","item":"https:\/\/siratek.net\/index.php\/tutorials\/"},{"@type":"ListItem","position":3,"name":"Project, a Pedestrian Crossing"}]},{"@type":"WebSite","@id":"https:\/\/siratek.net\/#website","url":"https:\/\/siratek.net\/","name":"siratek","description":"Your Best Electronic Retail Shop","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/siratek.net\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"}]}},"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/siratek.net\/index.php\/wp-json\/wp\/v2\/siratek_tutorial\/52309","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/siratek.net\/index.php\/wp-json\/wp\/v2\/siratek_tutorial"}],"about":[{"href":"https:\/\/siratek.net\/index.php\/wp-json\/wp\/v2\/types\/siratek_tutorial"}],"version-history":[{"count":0,"href":"https:\/\/siratek.net\/index.php\/wp-json\/wp\/v2\/siratek_tutorial\/52309\/revisions"}],"wp:attachment":[{"href":"https:\/\/siratek.net\/index.php\/wp-json\/wp\/v2\/media?parent=52309"}],"wp:term":[{"taxonomy":"siratek_tutorial_level","embeddable":true,"href":"https:\/\/siratek.net\/index.php\/wp-json\/wp\/v2\/siratek_tutorial_level?post=52309"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}