Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

$BTC Outlook — Full orderflow breakdown. 🧠 In this video: -Range analysis break -TPO + single prints -Footprint aggression -Stacked imbalance continuation play -Liquidations map -Net positioning across exchanges

joel_sabugal's profile picture

JoelXBT

7,958 subscribers

95,907 Aufrufe • vor 5 Monaten •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Footprint & Market Profile (TPO) | Complete Guide a video 📹 Timestamps: 0:47 - chart setup & exo intro 1:50 - tick size 2:47 - converting BTC to USD 3:37 - aggregated footprint 5:14 - footprint order types 7:20 - understanding volume & delta 11:22 - cluster & text types 15:22 - intra-bar components 17:26 - footprint bar statistics 19:21 - open interest (aggregated) 20:37 - using the footprint IMPORTANT 26:02 - net longs/net shorts 26:42 - tsize - note 27:11 - stacked imbalances 29:56 - other neat exo features 30:48 - liquidations 31:57 - basics of TPO 34:58 - TPO vs volume profile 36:45 - POC discrepancies 39:48 - poor highs/lows 44:06 - single prints/gaps 46:03 - HTF TPO settings 48:26 - initial balance 49:55 - custom tpo splits 51:41 - merging sessions & volume vs. time 52:48 - session filtering 54:11 - market profile statistics
56:26

Footprint & Market Profile (TPO) | Complete Guide a video 📹 Timestamps: 0:47 - chart setup & exo intro 1:50 - tick size 2:47 - converting BTC to USD 3:37 - aggregated footprint 5:14 - footprint order types 7:20 - understanding volume & delta 11:22 - cluster & text types 15:22 - intra-bar components 17:26 - footprint bar statistics 19:21 - open interest (aggregated) 20:37 - using the footprint IMPORTANT 26:02 - net longs/net shorts 26:42 - tsize - note 27:11 - stacked imbalances 29:56 - other neat exo features 30:48 - liquidations 31:57 - basics of TPO 34:58 - TPO vs volume profile 36:45 - POC discrepancies 39:48 - poor highs/lows 44:06 - single prints/gaps 46:03 - HTF TPO settings 48:26 - initial balance 49:55 - custom tpo splits 51:41 - merging sessions & volume vs. time 52:48 - session filtering 54:11 - market profile statistics

Luckshury

62,461 Aufrufe • vor 1 Jahr

This ONE Adjustment Makes Your Safeties Play 10x Better in #Madden27. 🧠 Two simple Coaching Adjustments can make them much better against both the pass AND run: 1️⃣ Safety Depth → 9 2️⃣ Safety Width → Pinch Why it works: ✅ Better positioning against Seam routes ✅ Faster reactions against the run ✅ Helps close down interior running lanes before they develop This is one of the easiest adjustments to make and can be left on for virtually the entire game. 🎥 Full breakdown in the video. 📌 Bookmark this & follow Swolosimo for more Madden 27 tips!
0:30

This ONE Adjustment Makes Your Safeties Play 10x Better in #Madden27. 🧠 Two simple Coaching Adjustments can make them much better against both the pass AND run: 1️⃣ Safety Depth → 9 2️⃣ Safety Width → Pinch Why it works: ✅ Better positioning against Seam routes ✅ Faster reactions against the run ✅ Helps close down interior running lanes before they develop This is one of the easiest adjustments to make and can be left on for virtually the entire game. 🎥 Full breakdown in the video. 📌 Bookmark this & follow Swolosimo for more Madden 27 tips!

Swolosimo

10,291 Aufrufe • vor 1 Monat

🇿🇦🇪🇹 Ethiopian Mafia & Money Laundering‼️​ In this video we break down ​Hawala & Money Laundering: ▪️How funds bypass standard banking channels to move across borders. ▪️How organized groups leverage their network to set market rates. ▪️The role that undocumented or falsified spaza registrations play in securing access to these financial pipelines. ​ WATCH the full breakdown to understand how these underground networks operate and their impact on the formal economy. ​ #Ethiopia #southafrica #Immigration #hawala
3:20

🇿🇦🇪🇹 Ethiopian Mafia & Money Laundering‼️​ In this video we break down ​Hawala & Money Laundering: ▪️How funds bypass standard banking channels to move across borders. ▪️How organized groups leverage their network to set market rates. ▪️The role that undocumented or falsified spaza registrations play in securing access to these financial pipelines. ​ WATCH the full breakdown to understand how these underground networks operate and their impact on the formal economy. ​ #Ethiopia #southafrica #Immigration #hawala

I ❤️ Cape Town ~ I Stand with Russia🇷🇺 MAGA

26,160 Aufrufe • vor 2 Monaten

THIS IS F**KING DANGEROUS I GAVE CLAUDE ACCESS TO OPTIONS FLOW, ORDER BOOK DATA, AND GAMMA WALLS — AND IT STARTED CALLING LEVELS BETTER THAN I DO not a chart with two moving averages. not a “buy the dip” alert. this is a full institutional desk compressed into one AI session here’s what’s on the screen right now: → GEXRadar pulling Gamma Exposure across 44 strikes in real time → Delta Exposure flipping between bars and candles showing where dealer hedging shifts → Major Walls: call wall at $700 with +276M, put wall at $691 with -97M → Hedging Pressure gauge sitting at 48/100 — neutral, dealer flow balanced → Net Drift tracking $19.93B in calls against $32.39B in puts — put dominated → IV Surface Analysis rotating in 3D showing where volatility is mispriced by strike and expiry → MotiveWave footprint printing every bid and ask at every price level, tick by tick → DOM ladder on MNQ futures with live bid/ask stacking — 29,103.75 ask, 29,103.50 bid Claude reads all of it not the chart — the structure underneath the chart gamma exposure tells it where dealers are forced to buy or sell. delta exposure tells it which direction the hedging pressure is building. the wall map tells it where price stalls. the footprint tells it whether the move is real volume or just air entry: 1 contract MNQ at 29,054.75 TP set: 29,178.25 P&L climbs → +$64 → +$146 → +$167 the trade wasn’t a guess. the call wall at $700 held, hedging pressure was neutral, gamma flip sat at $698, and the footprint confirmed buyers absorbing every offer at the 29,050 level Claude saw the wall. saw the flow. saw the absorption. and said: this is the entry tested this setup with $100 starting capital — ended the session at $3,153 that’s not leverage doing the work. that’s an AI reading options structure, order flow, and gamma positioning simultaneously — something no human can do across 44 strikes in real time you’re still drawing trendlines Claude is reading the market’s skeleton save this — the full setup and session walkthrough is in the article below ↓
0:34

THIS IS F**KING DANGEROUS I GAVE CLAUDE ACCESS TO OPTIONS FLOW, ORDER BOOK DATA, AND GAMMA WALLS — AND IT STARTED CALLING LEVELS BETTER THAN I DO not a chart with two moving averages. not a “buy the dip” alert. this is a full institutional desk compressed into one AI session here’s what’s on the screen right now: → GEXRadar pulling Gamma Exposure across 44 strikes in real time → Delta Exposure flipping between bars and candles showing where dealer hedging shifts → Major Walls: call wall at $700 with +276M, put wall at $691 with -97M → Hedging Pressure gauge sitting at 48/100 — neutral, dealer flow balanced → Net Drift tracking $19.93B in calls against $32.39B in puts — put dominated → IV Surface Analysis rotating in 3D showing where volatility is mispriced by strike and expiry → MotiveWave footprint printing every bid and ask at every price level, tick by tick → DOM ladder on MNQ futures with live bid/ask stacking — 29,103.75 ask, 29,103.50 bid Claude reads all of it not the chart — the structure underneath the chart gamma exposure tells it where dealers are forced to buy or sell. delta exposure tells it which direction the hedging pressure is building. the wall map tells it where price stalls. the footprint tells it whether the move is real volume or just air entry: 1 contract MNQ at 29,054.75 TP set: 29,178.25 P&L climbs → +$64 → +$146 → +$167 the trade wasn’t a guess. the call wall at $700 held, hedging pressure was neutral, gamma flip sat at $698, and the footprint confirmed buyers absorbing every offer at the 29,050 level Claude saw the wall. saw the flow. saw the absorption. and said: this is the entry tested this setup with $100 starting capital — ended the session at $3,153 that’s not leverage doing the work. that’s an AI reading options structure, order flow, and gamma positioning simultaneously — something no human can do across 44 strikes in real time you’re still drawing trendlines Claude is reading the market’s skeleton save this — the full setup and session walkthrough is in the article below ↓

INSIDER

173,271 Aufrufe • vor 7 Tagen

HOLY SH*T CLAUDE FILLED A LIMIT AT 29,088.00, EXACT PRICE, EXACT SECOND. CANCELLED THE STOP 0.4 SECONDS LATER. PLACED THE NEXT LIMIT 3 TICKS ABOVE. GOT FILLED AGAIN. +$4,225 STACKED BEFORE THE CANDLE CLOSED. not suggesting trades. not highlighting zones. placing actual orders. filling them. cancelling the ones that don't hit. and moving to the next setup here's what's on screen right now: left side — NQ futures (NQM26) on two timeframes. 1-minute and 30-minute charts running side by side. price at 29,238. multiple limit orders stacked across the chart: → green limit at +$1,869.00 — active → green limit at +$4,225.00 — active → green limit at +$8,335.00 — active → red stop at -$8,765.00 — risk defined → red stop at -$5,785.00 — tighter risk on a separate entry every order has a calculated target and a calculated stop. nothing is open-ended. nothing is "let it run and hope" bottom left — order confirmations updating live: "Order Filled: +1 MNQ Limit at 29,088.00" "Order Cancelled: +1 MNQ Stop Market at 29,075.75" Claude filled the limit. saw the stop was no longer needed. cancelled it. moved on top right — Gamma Exposure heatmap by strike. key gamma strike highlighted at 29,000. the chart shows where dealer positioning creates support and resistance — not where a line was drawn, where actual options hedging forces the market to react bottom right — MotiveWave footprint on MESM6 Range(20) with DOM. bid/ask delta visible at every price level. volume profile stacking on the right. the footprint confirms whether the move into Claude's limit was real buying or just air Claude cross-references the gamma strike map with the footprint. enters at levels where dealer hedging aligns with real order flow. sets mechanical targets. sets mechanical stops. fills, cancels, adjusts — all without a human touching the keyboard a properly configured strategy like this can generate up to $2,000 per day starting from as little as $100 — Claude isn't making one big bet, it's stacking precise micro entries at levels where the options market and the order book agree you're watching charts and thinking about entries Claude already placed five, filled two, cancelled one, and is scanning for the next save this — full strategy breakdown in the article below ↓
0:20

HOLY SH*T CLAUDE FILLED A LIMIT AT 29,088.00, EXACT PRICE, EXACT SECOND. CANCELLED THE STOP 0.4 SECONDS LATER. PLACED THE NEXT LIMIT 3 TICKS ABOVE. GOT FILLED AGAIN. +$4,225 STACKED BEFORE THE CANDLE CLOSED. not suggesting trades. not highlighting zones. placing actual orders. filling them. cancelling the ones that don't hit. and moving to the next setup here's what's on screen right now: left side — NQ futures (NQM26) on two timeframes. 1-minute and 30-minute charts running side by side. price at 29,238. multiple limit orders stacked across the chart: → green limit at +$1,869.00 — active → green limit at +$4,225.00 — active → green limit at +$8,335.00 — active → red stop at -$8,765.00 — risk defined → red stop at -$5,785.00 — tighter risk on a separate entry every order has a calculated target and a calculated stop. nothing is open-ended. nothing is "let it run and hope" bottom left — order confirmations updating live: "Order Filled: +1 MNQ Limit at 29,088.00" "Order Cancelled: +1 MNQ Stop Market at 29,075.75" Claude filled the limit. saw the stop was no longer needed. cancelled it. moved on top right — Gamma Exposure heatmap by strike. key gamma strike highlighted at 29,000. the chart shows where dealer positioning creates support and resistance — not where a line was drawn, where actual options hedging forces the market to react bottom right — MotiveWave footprint on MESM6 Range(20) with DOM. bid/ask delta visible at every price level. volume profile stacking on the right. the footprint confirms whether the move into Claude's limit was real buying or just air Claude cross-references the gamma strike map with the footprint. enters at levels where dealer hedging aligns with real order flow. sets mechanical targets. sets mechanical stops. fills, cancels, adjusts — all without a human touching the keyboard a properly configured strategy like this can generate up to $2,000 per day starting from as little as $100 — Claude isn't making one big bet, it's stacking precise micro entries at levels where the options market and the order book agree you're watching charts and thinking about entries Claude already placed five, filled two, cancelled one, and is scanning for the next save this — full strategy breakdown in the article below ↓

INSIDER

26,945 Aufrufe • vor 2 Tagen

📺 $TSLA $500 NEXT OR REVERSAL FIRST? Please ❤️like and share with fellow Tesla traders/investors Tesla ($TSLA#Tesla is sitting right at a critical resistance zone after a strong run: $442.26 to $444.99 (channel top). This is not just any level. This is a decision zone that determines whether #TSLA: – Breaks into a new leg higher (bullish continuation) – Or rejects and rotates lower (range or pullback) * So, the entire bullish thesis hinges on the weekly close above $444.99. If confirmed: – Short-term target (2–3 weeks): ~$498.83 (prior December high) – Medium-term target (2–3 months): ~$541.33 This move could extend through June–July and into Q3. An additional early signal would be a close above $452.34 on Thursday. It would suggest strong momentum and imply a likely continuation into Friday, with an immediate upside projection of ~$474.07 the next day. If the price breaks above the resistance, it likely accelerates quickly—this becomes a momentum trade. * If #TSLA fails to hold above resistance, the tone flips. A key rejection signal is a weekly close below $442.26. Then, the stock likely enters a range ($347 → $442) or a pullback phase, with a possible consolidation lasting 2-3 months. Downside levels: – First support: $426.50. Break below → early weakness signal – Next target: $409.03 – Intermediate level: $387.07 – Deeper downside: $340 s – $350 s Failure at resistance = no trend, just chop or pullback. This is where overbought conditions unwind. * Right now (in resistance zone), take profits on longs and consider short setups if rejection confirms. Aggressive long entry only if $452.34 breaks/holds (early signal) OR a weekly close above $444.99 (confirmation). Early bearish positioning if $TSLA closes below $426.50 – signals potential rotation lower into June. * So, the entire setup comes down to one concept: acceptance vs. rejection at resistance. – Acceptance above ~$445 → trend continuation → momentum higher – Rejection below ~$442 → range/pullback → time correction No guessing tops. No predicting narratives. Just reacting to price behavior at key levels. * Watch the full Trading Plan for May 14, 2026 in this short video🔽
2:59

📺 $TSLA $500 NEXT OR REVERSAL FIRST? Please ❤️like and share with fellow Tesla traders/investors Tesla ($TSLA#Tesla is sitting right at a critical resistance zone after a strong run: $442.26 to $444.99 (channel top). This is not just any level. This is a decision zone that determines whether #TSLA: – Breaks into a new leg higher (bullish continuation) – Or rejects and rotates lower (range or pullback) * So, the entire bullish thesis hinges on the weekly close above $444.99. If confirmed: – Short-term target (2–3 weeks): ~$498.83 (prior December high) – Medium-term target (2–3 months): ~$541.33 This move could extend through June–July and into Q3. An additional early signal would be a close above $452.34 on Thursday. It would suggest strong momentum and imply a likely continuation into Friday, with an immediate upside projection of ~$474.07 the next day. If the price breaks above the resistance, it likely accelerates quickly—this becomes a momentum trade. * If #TSLA fails to hold above resistance, the tone flips. A key rejection signal is a weekly close below $442.26. Then, the stock likely enters a range ($347 → $442) or a pullback phase, with a possible consolidation lasting 2-3 months. Downside levels: – First support: $426.50. Break below → early weakness signal – Next target: $409.03 – Intermediate level: $387.07 – Deeper downside: $340 s – $350 s Failure at resistance = no trend, just chop or pullback. This is where overbought conditions unwind. * Right now (in resistance zone), take profits on longs and consider short setups if rejection confirms. Aggressive long entry only if $452.34 breaks/holds (early signal) OR a weekly close above $444.99 (confirmation). Early bearish positioning if $TSLA closes below $426.50 – signals potential rotation lower into June. * So, the entire setup comes down to one concept: acceptance vs. rejection at resistance. – Acceptance above ~$445 → trend continuation → momentum higher – Rejection below ~$442 → range/pullback → time correction No guessing tops. No predicting narratives. Just reacting to price behavior at key levels. * Watch the full Trading Plan for May 14, 2026 in this short video🔽

Wicked Stocks

22,667 Aufrufe • vor 4 Monaten

TradingView can't replay the order book. It can't even rewind. Today, we are releasing Market Replay. In the clip, we replayed yesterday's CPI print release tick by tick. They replay the chart. We replay the market. It allows you to jump back in time and replay every candle, every order book tick, every liquidation, exactly as it happened. Pick any moment from years back. Scrub it like a video. What you will see is exactly what a live trader saw at that second. Here's what's inside: • The full order book, replayed. Rebuilt second by second at tick resolution: walls stacking, getting pulled, getting swept. • A real scrubber. Drag anywhere, both directions, instantly. Pause, step, or play at ten speeds from 0.25x to 30x. • Honest playback. Speed changes how fast you watch, never what happened. • Live data is gated out during replay. Replay is the only thing painting the chart. • 71 indicators replay in sync: CVD, open interest, funding, liquidations, footprint, volume delta, TPO, session profiles, VWAP, long/short ratios, ETF flows, dominance. • Your own scripts replay too, including ones built on orderbook and orderflow data. • Watch candles form: a 4h candle builds update by update, and at tick resolution second by second, with the book moving behind it. • Depth and liquidity readouts show the book as it stood at that moment, not now. • Years of candle and indicator history. Jump with the calendar or click any candle. Add an indicator mid-replay and it joins the timeline.
0:43

TradingView can't replay the order book. It can't even rewind. Today, we are releasing Market Replay. In the clip, we replayed yesterday's CPI print release tick by tick. They replay the chart. We replay the market. It allows you to jump back in time and replay every candle, every order book tick, every liquidation, exactly as it happened. Pick any moment from years back. Scrub it like a video. What you will see is exactly what a live trader saw at that second. Here's what's inside: • The full order book, replayed. Rebuilt second by second at tick resolution: walls stacking, getting pulled, getting swept. • A real scrubber. Drag anywhere, both directions, instantly. Pause, step, or play at ten speeds from 0.25x to 30x. • Honest playback. Speed changes how fast you watch, never what happened. • Live data is gated out during replay. Replay is the only thing painting the chart. • 71 indicators replay in sync: CVD, open interest, funding, liquidations, footprint, volume delta, TPO, session profiles, VWAP, long/short ratios, ETF flows, dominance. • Your own scripts replay too, including ones built on orderbook and orderflow data. • Watch candles form: a 4h candle builds update by update, and at tick resolution second by second, with the book moving behind it. • Depth and liquidity readouts show the book as it stood at that moment, not now. • Years of candle and indicator history. Jump with the calendar or click any candle. Add an indicator mid-replay and it joins the timeline.

OpenMarket

12,945 Aufrufe • vor 2 Monaten

DL Stunting is still one of the best ways to get INSTANT pressure in Madden 26 🔥🧠 Some of the best players in the world are STILL using the same stunts we fell in love with early in the cycle. Where to run stunts: • Any Nickel Single Mug formation Almost every playbook has a version of it. How to set them up: • In the play call menu, hold the play button, scroll to the stunt, release • Or after the call, press Left on the D-pad → RB → select your stunt Best stunt in the game: • Texas 4 Man After selecting it, spread your defensive line In most cases, you get immediate pressure through one of the interior gaps. With the QB juke burst removed, rollouts are far less of a risk now. If they still try to roll out: • Switch to Texas 2 Man off the left + contain You keep solid pressure while shutting the rollout down. If they start picking it up: • That usually means advanced protection • Stop calling the stunt, crash down and contain You will often get a DT in free. If you know they are in empty: • Dial up an Exit Stunt This frees a DE through the B-gap. 🎥 Full breakdown in the video! Bookmark this and follow Swolosimo for more Madden tips!
1:00

DL Stunting is still one of the best ways to get INSTANT pressure in Madden 26 🔥🧠 Some of the best players in the world are STILL using the same stunts we fell in love with early in the cycle. Where to run stunts: • Any Nickel Single Mug formation Almost every playbook has a version of it. How to set them up: • In the play call menu, hold the play button, scroll to the stunt, release • Or after the call, press Left on the D-pad → RB → select your stunt Best stunt in the game: • Texas 4 Man After selecting it, spread your defensive line In most cases, you get immediate pressure through one of the interior gaps. With the QB juke burst removed, rollouts are far less of a risk now. If they still try to roll out: • Switch to Texas 2 Man off the left + contain You keep solid pressure while shutting the rollout down. If they start picking it up: • That usually means advanced protection • Stop calling the stunt, crash down and contain You will often get a DT in free. If you know they are in empty: • Dial up an Exit Stunt This frees a DE through the B-gap. 🎥 Full breakdown in the video! Bookmark this and follow Swolosimo for more Madden tips!

Swolosimo

12,103 Aufrufe • vor 7 Monaten

THIS IS INSANE — AN ANTHROPIC ENGINEER BUILT A CLAUDE CODE BOT THAT READS INSTITUTIONAL OPTIONS FLOW IN REAL TIME AND TURNED $200 INTO $14,300 TRADING ALONGSIDE THE BIGGEST ORDERS ON THE TAPE the bot doesn't predict. it stalks it reads thousands of institutional options orders streaming through SpotGamma — scores every block by size, direction, and how it historically moves price — then trades only when the heaviest hands on the tape are moving here's what's running on screen right now: → GEX Surface Analysis — 3D gamma exposure map rotating in real time, strike $8,168, GEX at 1.36B → MotiveWave footprint — ESU6 Range(20) with cumulative delta crashing to -9,500. every bid and ask printed at every level → SpotGamma Live Flow — institutional tape streaming tick by tick: SPX, QQQ, NVDA, AAPL, META, MSTR, NDX. strike, volume, premium — all live → GEXRadar — QQQ at $720.09, Hedging Pressure 53/100, Major Walls mapped, bullish flow → MNQU6 on mobile — Nasdaq 100 M1, bid 29,589 ask 29,591, TP set, P&L at +$109.50 when an institution drops $40K on SPX 7,740 calls or $28,639 on NDX puts — Claude sees it before FinTwit even screenshots it the bot makes only 10 trades per day not 50. not 100. ten. because Claude Code learned the edge isn't frequency — it's selectivity. large institutional block orders only and it exits early. before the institutions unwind. the same flow analysis that finds the entry also maps when large players historically take profit — the bot exits ahead of the crowd $200 in. $14,300 out. built by an engineer who used Claude Code to do what no dashboard can — read every institutional options order in real time and trade only when the biggest ones align you're watching one chart this bot is reading every block order on the tape to find the 10 setups that matter today save this — full setup breakdown below ↓
0:40

THIS IS INSANE — AN ANTHROPIC ENGINEER BUILT A CLAUDE CODE BOT THAT READS INSTITUTIONAL OPTIONS FLOW IN REAL TIME AND TURNED $200 INTO $14,300 TRADING ALONGSIDE THE BIGGEST ORDERS ON THE TAPE the bot doesn't predict. it stalks it reads thousands of institutional options orders streaming through SpotGamma — scores every block by size, direction, and how it historically moves price — then trades only when the heaviest hands on the tape are moving here's what's running on screen right now: → GEX Surface Analysis — 3D gamma exposure map rotating in real time, strike $8,168, GEX at 1.36B → MotiveWave footprint — ESU6 Range(20) with cumulative delta crashing to -9,500. every bid and ask printed at every level → SpotGamma Live Flow — institutional tape streaming tick by tick: SPX, QQQ, NVDA, AAPL, META, MSTR, NDX. strike, volume, premium — all live → GEXRadar — QQQ at $720.09, Hedging Pressure 53/100, Major Walls mapped, bullish flow → MNQU6 on mobile — Nasdaq 100 M1, bid 29,589 ask 29,591, TP set, P&L at +$109.50 when an institution drops $40K on SPX 7,740 calls or $28,639 on NDX puts — Claude sees it before FinTwit even screenshots it the bot makes only 10 trades per day not 50. not 100. ten. because Claude Code learned the edge isn't frequency — it's selectivity. large institutional block orders only and it exits early. before the institutions unwind. the same flow analysis that finds the entry also maps when large players historically take profit — the bot exits ahead of the crowd $200 in. $14,300 out. built by an engineer who used Claude Code to do what no dashboard can — read every institutional options order in real time and trade only when the biggest ones align you're watching one chart this bot is reading every block order on the tape to find the 10 setups that matter today save this — full setup breakdown below ↓

INSIDER

132,383 Aufrufe • vor 4 Tagen

Hear me out: Dijonai Carrington should be suspended for the season, since she knew exactly what she was doing - any basketball player worth their salt knows you NEVER headhunt or "bridge" another defenseless player. This wasn’t just a hard foul or "physical basketball." Carrington’s arm came across Sophie Cunningham’s head and neck while she was airborne and completely vulnerable on a fast-break layup. That kind of contact can instantly cause a neck/head injury, concussion, or permanent spinal cord damage upon impact. One wrong angle or landing and a player may never walk the same again. People who have never played basketball may only see the highlight-reel aggression or the "We support Sophie", but the reality is that unprotected hits to the head and neck at full speed are life-altering risks every single time they happen. This is the kind of play that forces a clear conversation about physicality thresholds in the WNBA, or any league claiming it emphasizes and cares about player safety.
0:28

Hear me out: Dijonai Carrington should be suspended for the season, since she knew exactly what she was doing - any basketball player worth their salt knows you NEVER headhunt or "bridge" another defenseless player. This wasn’t just a hard foul or "physical basketball." Carrington’s arm came across Sophie Cunningham’s head and neck while she was airborne and completely vulnerable on a fast-break layup. That kind of contact can instantly cause a neck/head injury, concussion, or permanent spinal cord damage upon impact. One wrong angle or landing and a player may never walk the same again. People who have never played basketball may only see the highlight-reel aggression or the "We support Sophie", but the reality is that unprotected hits to the head and neck at full speed are life-altering risks every single time they happen. This is the kind of play that forces a clear conversation about physicality thresholds in the WNBA, or any league claiming it emphasizes and cares about player safety.

Time4SumAxShun

12,661 Aufrufe • vor 1 Monat

I spent my Sunday mapping the setups that matter most this shortened week. Tech is still leading this market. Software earnings may decide what happens next. $QCOM is setting up above 242. $ASTS continues to show momentum in the space trade. $ZS software earnings could shift the tone for the entire group. Here’s the watchlist and recording: $SPX: Healthy week overall. Reclaimed the 9-day and pushed back above 7500 before fading into Friday’s close. Trend remains intact. A higher low here could set up another breakout attempt above 7500. $QQQ: Still rangebound between roughly 695 and ATHs near 722. Tech leadership remains intact, but there’s a mild double top warning if momentum stalls. $IWM: Constructive range near highs. 270 double bottom held perfectly. Not bearish at all. Still one of the cleaner consolidation setups if rates cooperate. $BTC #BTC: No trade for now. Sitting below major moving averages. Needs 84–85K reclaim before momentum becomes interesting again. $SMH: New ATH Friday despite $NVDA weakness. Semiconductor rotation remains alive. Above 583 opens the door toward 600. $AAPL: Extremely strong. Multiple new highs. 303 is first warning. 300 is must-hold. As long as buyers defend breakout levels, trend remains intact. $MSFT: Harder trade, but very large cup-and-handle structure. Above 530 opens 542. Bigger breakout potential if momentum follows. $AMZN: One of the better big tech setups. Friday was a clean backtest of breakout trendline. Above 270 gets interesting quickly. $GOOGL: Looking tired. 380 reclaim could trigger failed breakdown reversal. Otherwise, not much here. $TSLA: Interesting setup. 420 and 435 are the key levels. Above 435 opens gap-fill toward 442. $NVDA: Weak post-earnings reaction. Pulling back into prior breakout zone around 215–217 and the 20-day. Needs to hold that area. $AMD: New ATH Friday but failed to hold the move. Above 470 could re-ignite momentum. $AVGO: Large range consolidation. Harder trade for now. $NVTS: One of the cleaner semiconductor momentum setups. One-time framing higher. Above 30 keeps continuation alive. $DELL: Fantastic structure. 298 opens 300. Above 300 could accelerate. $QCOM: One of the cleaner setups this week. 242 breakout opens 248–250. $RGTI: Quantum momentum remains alive. Above 27 opens 30+. $QBTS: Similar quantum continuation setup. $AXTI: One of the strongest photonics names right now. Clear leadership. $AAOI: Laggard vs AXTI but above 193 opens 200. $LITE: Looking constructive. 1000 reclaim could trigger momentum. SWKS: Quiet semiconductor strength. Above 83.50 opens 92, then potentially 100. LUNR: One of the stronger space setups. Above 38.30 opens continuation. $RKLB: Failed breakout Friday. Above 140 becomes interesting again. $ASTS: Strong recovery. Hold 100, break 108, and momentum could continue toward ATHs. $SMTC: Big Friday move but messy close. Harder setup. $ZS: Big software earnings this week. Important for group sentiment. $CRWD: Extremely strong. New ATH continuation setup. $PANW: Beautiful one-time framing higher. Momentum remains intact. $NET: Laggard, but could benefit if software earnings surprise positively. $DDOG: Monster move. Gap never backtested. Momentum remains very strong. $SNOW: Earnings this week. Worth watching. ON: Quiet strength. $FSLR: Solar remains hot. Above 260 opens 300 potential. $ENPH: Vertical momentum move. Needs continuation. $ARM: Monster breakout from prior balance. Hold 300 and continuation remains alive. $MRVL: Grinding higher. 200 is the key breakout. NOW: Holding 100 well. Trump positioning narrative still in play. $LLY: Strong above 1000. 1070 breakout could open ATH move. $INTC: Looks ready. Above 123 could trigger fresh highs. LRCX: Strong breakout. Holding above 300 keeps dip-buy thesis alive. $GS: Strong breakout and leadership among banks. $JPM: Reclaiming key moving averages. MS: New ATHs. Very strong bank setup. $IBM: Needs reclaim above 260. $MU: Ugly Friday reversal. Harder trade for now. $SNDK: Better than MU. Above 1530 gets interesting. $WDC: Looking constructive. Above 490 could move toward 500. $COST: Big move but sold off. Harder setup. WMT: Ugly post-earnings reaction. TGT: Holding gains better. Above 128 becomes interesting. If you like this, then ❤️ it! sm
26:26

I spent my Sunday mapping the setups that matter most this shortened week. Tech is still leading this market. Software earnings may decide what happens next. $QCOM is setting up above 242. $ASTS continues to show momentum in the space trade. $ZS software earnings could shift the tone for the entire group. Here’s the watchlist and recording: $SPX: Healthy week overall. Reclaimed the 9-day and pushed back above 7500 before fading into Friday’s close. Trend remains intact. A higher low here could set up another breakout attempt above 7500. $QQQ: Still rangebound between roughly 695 and ATHs near 722. Tech leadership remains intact, but there’s a mild double top warning if momentum stalls. $IWM: Constructive range near highs. 270 double bottom held perfectly. Not bearish at all. Still one of the cleaner consolidation setups if rates cooperate. $BTC #BTC: No trade for now. Sitting below major moving averages. Needs 84–85K reclaim before momentum becomes interesting again. $SMH: New ATH Friday despite $NVDA weakness. Semiconductor rotation remains alive. Above 583 opens the door toward 600. $AAPL: Extremely strong. Multiple new highs. 303 is first warning. 300 is must-hold. As long as buyers defend breakout levels, trend remains intact. $MSFT: Harder trade, but very large cup-and-handle structure. Above 530 opens 542. Bigger breakout potential if momentum follows. $AMZN: One of the better big tech setups. Friday was a clean backtest of breakout trendline. Above 270 gets interesting quickly. $GOOGL: Looking tired. 380 reclaim could trigger failed breakdown reversal. Otherwise, not much here. $TSLA: Interesting setup. 420 and 435 are the key levels. Above 435 opens gap-fill toward 442. $NVDA: Weak post-earnings reaction. Pulling back into prior breakout zone around 215–217 and the 20-day. Needs to hold that area. $AMD: New ATH Friday but failed to hold the move. Above 470 could re-ignite momentum. $AVGO: Large range consolidation. Harder trade for now. $NVTS: One of the cleaner semiconductor momentum setups. One-time framing higher. Above 30 keeps continuation alive. $DELL: Fantastic structure. 298 opens 300. Above 300 could accelerate. $QCOM: One of the cleaner setups this week. 242 breakout opens 248–250. $RGTI: Quantum momentum remains alive. Above 27 opens 30+. $QBTS: Similar quantum continuation setup. $AXTI: One of the strongest photonics names right now. Clear leadership. $AAOI: Laggard vs AXTI but above 193 opens 200. $LITE: Looking constructive. 1000 reclaim could trigger momentum. SWKS: Quiet semiconductor strength. Above 83.50 opens 92, then potentially 100. LUNR: One of the stronger space setups. Above 38.30 opens continuation. $RKLB: Failed breakout Friday. Above 140 becomes interesting again. $ASTS: Strong recovery. Hold 100, break 108, and momentum could continue toward ATHs. $SMTC: Big Friday move but messy close. Harder setup. $ZS: Big software earnings this week. Important for group sentiment. $CRWD: Extremely strong. New ATH continuation setup. $PANW: Beautiful one-time framing higher. Momentum remains intact. $NET: Laggard, but could benefit if software earnings surprise positively. $DDOG: Monster move. Gap never backtested. Momentum remains very strong. $SNOW: Earnings this week. Worth watching. ON: Quiet strength. $FSLR: Solar remains hot. Above 260 opens 300 potential. $ENPH: Vertical momentum move. Needs continuation. $ARM: Monster breakout from prior balance. Hold 300 and continuation remains alive. $MRVL: Grinding higher. 200 is the key breakout. NOW: Holding 100 well. Trump positioning narrative still in play. $LLY: Strong above 1000. 1070 breakout could open ATH move. $INTC: Looks ready. Above 123 could trigger fresh highs. LRCX: Strong breakout. Holding above 300 keeps dip-buy thesis alive. $GS: Strong breakout and leadership among banks. $JPM: Reclaiming key moving averages. MS: New ATHs. Very strong bank setup. $IBM: Needs reclaim above 260. $MU: Ugly Friday reversal. Harder trade for now. $SNDK: Better than MU. Above 1530 gets interesting. $WDC: Looking constructive. Above 490 could move toward 500. $COST: Big move but sold off. Harder setup. WMT: Ugly post-earnings reaction. TGT: Holding gains better. Above 128 becomes interesting. If you like this, then ❤️ it! sm

spacemonkey

86,996 Aufrufe • vor 3 Monaten

I spent 2 hours of my Saturday reviewing hundreds of charts. These are the setups that stood out and what you should focus on this week. Software and healthcare are starting to catch a bid. Semiconductors are showing fatigue. The next rotation may already be underway. 📼 Video attached (8m 25s) $SNOW is breaking higher from a strong earnings base. $PANW is reclaiming 300 and looks ready for continuation. $LLY continues to show exceptional relative strength. Here’s the watchlist and recording: $SPX: Still trapped in a range. 7338 remains the key support. Holding it keeps the higher-low thesis intact. Below 7236 opens downside toward 7150. Above 7500 would be a strong signal that the pullback is complete. $QQQ: Showing relative weakness versus SPX. Holding the 50-day moving average for now, but a break below 700 could open a move toward 685. $IWM: One of the strongest indices right now. Watching 300 closely. A breakout could trigger a move into all-time highs and potentially much higher. $SMH: Starting to roll over. Unable to hold the 9-day moving average. Below 600 could open a larger pullback toward 550. $IGV: One of the most interesting charts in the market. Software finally caught a strong bid on Friday after weeks of selling. Watching for continuation. $AAPL: Strong relative strength Friday. Above 286 could trigger a gap-fill toward 293. Above 302 would be very bullish. $MSFT: Potential swing low forming. Failed breakdown at yearly lows and a strong reversal Friday. Needs 376-380 reclaimed before confidence returns. $GOOGL: Nice bounce but still lacking a clear setup. Watching for follow-through from Friday’s strength. $AMZN: Still fighting with the 200-day moving average. Worth monitoring if the rotation into mega caps continues. $NFLX: One of the stronger recoveries. Holding 70 and reclaiming 75 could trigger a failed-breakdown move back toward highs. $NVDA: Still weak. Watching 109 and the 200-day moving average. A break there could lead to another leg lower. $TSLA: Remains difficult. Needs a move back above 400 before becoming interesting. Bigger level remains 418 near the 200-day moving average. $FCEL: Huge momentum. Watching a break above 25-26 for continuation. $MRNA: Healthcare remains strong. Watching above 68 for continuation. $NOW: Attempting to bottom. Watching for a reclaim of the 50-day moving average. $SNOW: One of the better software charts. Holding the earnings gap and breaking trend. Watching 248-250. $DDOG: Strong software setup. Holding its earnings gap and building a higher low. Watching 242. $BROS: Breaking a major daily trendline. Watching above 72 for continuation toward 80+. $CROX: Strong relative strength. Watching 130 for continuation. $LLY: One of the strongest charts in healthcare. Watching continuation above 1200 or a pullback into support. $UBER: Excellent recovery. Reclaimed the 50-day moving average. Watching 76.5-77. $XYZ: Strong close near range highs. Above 78 could open a move toward 82-85. $NET: Software leadership candidate. Watching above 240. $HUT: Strong setup. Watching a breakout above 127-130. $OKTA: Similar setup to SNOW and DDOG. Watching 125 for continuation. $OSCR: Healthcare continues to lead. Above 30 could open a move toward 37 and all-time highs. $XLV: One of the strongest sectors in the market. Healthcare continues to attract capital. $PANW: One of my favorite charts. Holding 300 and reclaiming 305-306 could trigger a major move. $CRWD: Looking constructive. Holding 700 is key. Watching 704-705. $ABNB: Watching the important 148-150 area. $SN: Strong trend. Watching 145-146 for continuation. $SPCX: Holding the 150 area. No trade for now unless it breaks below 148 or reclaims momentum higher. $MU: Pulling back after a huge run. Watching 1000 and 1100. $QCOM: Looking tired. A break below 186 could open further downside. $SNDK: Needs to hold 2000. Below that, 1850 becomes the next major area. Overall theme: Money appears to be rotating out of semiconductors and AI leaders. Software is finally showing signs of life. Healthcare continues to outperform. The best opportunities may no longer be where they’ve been for the last few months. SNOW, PANW, LLY, DDOG, CRWD, and FCEL are some of my favorite charts going into next week. If you like this, please like it ❤️
8:24

I spent 2 hours of my Saturday reviewing hundreds of charts. These are the setups that stood out and what you should focus on this week. Software and healthcare are starting to catch a bid. Semiconductors are showing fatigue. The next rotation may already be underway. 📼 Video attached (8m 25s) $SNOW is breaking higher from a strong earnings base. $PANW is reclaiming 300 and looks ready for continuation. $LLY continues to show exceptional relative strength. Here’s the watchlist and recording: $SPX: Still trapped in a range. 7338 remains the key support. Holding it keeps the higher-low thesis intact. Below 7236 opens downside toward 7150. Above 7500 would be a strong signal that the pullback is complete. $QQQ: Showing relative weakness versus SPX. Holding the 50-day moving average for now, but a break below 700 could open a move toward 685. $IWM: One of the strongest indices right now. Watching 300 closely. A breakout could trigger a move into all-time highs and potentially much higher. $SMH: Starting to roll over. Unable to hold the 9-day moving average. Below 600 could open a larger pullback toward 550. $IGV: One of the most interesting charts in the market. Software finally caught a strong bid on Friday after weeks of selling. Watching for continuation. $AAPL: Strong relative strength Friday. Above 286 could trigger a gap-fill toward 293. Above 302 would be very bullish. $MSFT: Potential swing low forming. Failed breakdown at yearly lows and a strong reversal Friday. Needs 376-380 reclaimed before confidence returns. $GOOGL: Nice bounce but still lacking a clear setup. Watching for follow-through from Friday’s strength. $AMZN: Still fighting with the 200-day moving average. Worth monitoring if the rotation into mega caps continues. $NFLX: One of the stronger recoveries. Holding 70 and reclaiming 75 could trigger a failed-breakdown move back toward highs. $NVDA: Still weak. Watching 109 and the 200-day moving average. A break there could lead to another leg lower. $TSLA: Remains difficult. Needs a move back above 400 before becoming interesting. Bigger level remains 418 near the 200-day moving average. $FCEL: Huge momentum. Watching a break above 25-26 for continuation. $MRNA: Healthcare remains strong. Watching above 68 for continuation. $NOW: Attempting to bottom. Watching for a reclaim of the 50-day moving average. $SNOW: One of the better software charts. Holding the earnings gap and breaking trend. Watching 248-250. $DDOG: Strong software setup. Holding its earnings gap and building a higher low. Watching 242. $BROS: Breaking a major daily trendline. Watching above 72 for continuation toward 80+. $CROX: Strong relative strength. Watching 130 for continuation. $LLY: One of the strongest charts in healthcare. Watching continuation above 1200 or a pullback into support. $UBER: Excellent recovery. Reclaimed the 50-day moving average. Watching 76.5-77. $XYZ: Strong close near range highs. Above 78 could open a move toward 82-85. $NET: Software leadership candidate. Watching above 240. $HUT: Strong setup. Watching a breakout above 127-130. $OKTA: Similar setup to SNOW and DDOG. Watching 125 for continuation. $OSCR: Healthcare continues to lead. Above 30 could open a move toward 37 and all-time highs. $XLV: One of the strongest sectors in the market. Healthcare continues to attract capital. $PANW: One of my favorite charts. Holding 300 and reclaiming 305-306 could trigger a major move. $CRWD: Looking constructive. Holding 700 is key. Watching 704-705. $ABNB: Watching the important 148-150 area. $SN: Strong trend. Watching 145-146 for continuation. $SPCX: Holding the 150 area. No trade for now unless it breaks below 148 or reclaims momentum higher. $MU: Pulling back after a huge run. Watching 1000 and 1100. $QCOM: Looking tired. A break below 186 could open further downside. $SNDK: Needs to hold 2000. Below that, 1850 becomes the next major area. Overall theme: Money appears to be rotating out of semiconductors and AI leaders. Software is finally showing signs of life. Healthcare continues to outperform. The best opportunities may no longer be where they’ve been for the last few months. SNOW, PANW, LLY, DDOG, CRWD, and FCEL are some of my favorite charts going into next week. If you like this, please like it ❤️

spacemonkey

56,205 Aufrufe • vor 2 Monaten

THIS GUY IS USING GTA 6 TO MAKE $10,000 A MONTH ON THE GAME'S LAUNCH. Not after the game launches. Before it launches. That is the whole play. The creator’s bet is simple: GTA 6 is already a search engine before anyone can play it. Trailers. Scenes. Map theories. Car theories. Release rumors. Money glitch theories. Tiny details people want explained. In the video, he says GTA 6 is projected to make $1B on day one and $7.6B in its first two months. His move is to stand in front of that demand early. The workflow he shows: 1. Take a GTA 6 trailer, scene, rumor, or news angle 2. Ask ChatGPT for a scene-by-scene breakdown 3. Turn that breakdown into YouTube Shorts ideas 4. Paste it into Viewmaxx io for video generation, scriptwriting, and AI voiceover 5. Add captions so the clip still works when people are scrolling fast, muted, or half watching 6. Repeat across every micro-question people search before launch The money claim is the bait. He points to YouTube Shorts paying roughly $2K - $5K per million views, but that is not a guaranteed income plan. RPM depends on niche, country, retention, ad demand, monetization status, and whether the content is original enough to pass platform rules. AI voice + captions + GTA clips is not a business by itself. The useful part is the arbitrage: find a giant upcoming event, break it into small questions, use AI to ship faster than normal editors, and attach each post to demand that already exists. GTA 6 is the example. The reusable model is event-driven Shorts before the event peaks.
0:56

THIS GUY IS USING GTA 6 TO MAKE $10,000 A MONTH ON THE GAME'S LAUNCH. Not after the game launches. Before it launches. That is the whole play. The creator’s bet is simple: GTA 6 is already a search engine before anyone can play it. Trailers. Scenes. Map theories. Car theories. Release rumors. Money glitch theories. Tiny details people want explained. In the video, he says GTA 6 is projected to make $1B on day one and $7.6B in its first two months. His move is to stand in front of that demand early. The workflow he shows: 1. Take a GTA 6 trailer, scene, rumor, or news angle 2. Ask ChatGPT for a scene-by-scene breakdown 3. Turn that breakdown into YouTube Shorts ideas 4. Paste it into Viewmaxx io for video generation, scriptwriting, and AI voiceover 5. Add captions so the clip still works when people are scrolling fast, muted, or half watching 6. Repeat across every micro-question people search before launch The money claim is the bait. He points to YouTube Shorts paying roughly $2K - $5K per million views, but that is not a guaranteed income plan. RPM depends on niche, country, retention, ad demand, monetization status, and whether the content is original enough to pass platform rules. AI voice + captions + GTA clips is not a business by itself. The useful part is the arbitrage: find a giant upcoming event, break it into small questions, use AI to ship faster than normal editors, and attach each post to demand that already exists. GTA 6 is the example. The reusable model is event-driven Shorts before the event peaks.

kocer

11,134 Aufrufe • vor 2 Monaten

An Anthropic intern watched me make $38 in three minutes at Equator Coffee I was on Market Street. Laptop open. BTC 5-minute markets cycling on screen. A green fill popped. She was behind me in line. Anthropic badge on her lanyard. "Wait. Is that Claude running trades" I told her. Claude Code. Four repos. $25 a month. She sat down across from me without asking. "I'm on the evals team. We benchmark Claude's reasoning on stuff way simpler than this. You're letting it run a full execution loop with real money" I showed her the first repo. 86 million trades. Claude finds which wallets consistently win. Reverse-engineers their timing. Copies their exits. "So you're not writing trading rules. Claude is finding them on its own from the data" Exactly. It watches Binance and Coinbase diverge from Chainlink. When both exchanges move $50+ the same way and Chainlink lags - it enters. 94% follow-through. Another trade closed on screen. +$41. "How often does it trade" About 55 times a day. Out of 400+ windows. Kills 85%. Only enters when order book imbalance confirms the price signal. Three commands. 500+ markets. Claude scores them in 20 minutes. She watched the screen for a while. My setup: Claude API - $20/mo VPS - $5/mo Everything else - free 30 days. 1,847 trades. 71% win rate. +$14,200. Copytrade here: She leaned back. "We spend all day testing what Claude can do in theory. You just showed me what it does in practice" I published the full breakdown that night. She DM'd me the next morning. "My team lead read your article. He wants to know if you'll consult for us" I told him to read it again. Everything's in there. Too late to gatekeep.
0:20

An Anthropic intern watched me make $38 in three minutes at Equator Coffee I was on Market Street. Laptop open. BTC 5-minute markets cycling on screen. A green fill popped. She was behind me in line. Anthropic badge on her lanyard. "Wait. Is that Claude running trades" I told her. Claude Code. Four repos. $25 a month. She sat down across from me without asking. "I'm on the evals team. We benchmark Claude's reasoning on stuff way simpler than this. You're letting it run a full execution loop with real money" I showed her the first repo. 86 million trades. Claude finds which wallets consistently win. Reverse-engineers their timing. Copies their exits. "So you're not writing trading rules. Claude is finding them on its own from the data" Exactly. It watches Binance and Coinbase diverge from Chainlink. When both exchanges move $50+ the same way and Chainlink lags - it enters. 94% follow-through. Another trade closed on screen. +$41. "How often does it trade" About 55 times a day. Out of 400+ windows. Kills 85%. Only enters when order book imbalance confirms the price signal. Three commands. 500+ markets. Claude scores them in 20 minutes. She watched the screen for a while. My setup: Claude API - $20/mo VPS - $5/mo Everything else - free 30 days. 1,847 trades. 71% win rate. +$14,200. Copytrade here: She leaned back. "We spend all day testing what Claude can do in theory. You just showed me what it does in practice" I published the full breakdown that night. She DM'd me the next morning. "My team lead read your article. He wants to know if you'll consult for us" I told him to read it again. Everything's in there. Too late to gatekeep.

Lunar

68,685 Aufrufe • vor 4 Monaten

$TSLA ABOVE $361.59 – BUY SIGNAL IN PLAY Please ❤️like and 🔁share with fellow Tesla traders/investors #Tesla successfully tested the $338.27 long-term channel bottom (1-year structure) after the earlier breakdown below ~$432. #TSLA had a strong bounce, which confirms this level as major support (for now). The downside objective is now complete, and the bias has shifted from bearish to cautiously bullish. * As long as $TSLA holds above $338.27, the strategy is to stay long/bullish. Target: $432.90 (major structure), extension: $440–$450+ into May–July. Stock may chop sideways in a wide range (roughly $330s → $430s) through Q3. It's likely volatile, range-bound accumulation before higher. If $TSLA closes below $338.27 by ~1% (≈ $334.87), that triggers a new 3–5 month sell signal down to ~$224.55. * Key pivot right now is $361.59. This is the decision level for the next few days. If #TSLA closes above $361.59 at the end of the week, it triggers a 3–5 day buy signal with $386.93 (short-term resistance) target. If that breaks, a move toward $432.90 by late May is expected. If $TSLA fails below $361.59, expect a pullback to $338.27. We could possibly see a choppy move in the upper $330s and the “Wedge formation” over the next few weeks. * So, for short-term traders, take profits near $386.93 (2–3 week target). For position traders, stay long above $338. For aggressive traders, trade the $361 pivot break (up or down). * Watch the full $TSLA Trading Plan for Apr 15, 2026 in this short video🔽
2:52

$TSLA ABOVE $361.59 – BUY SIGNAL IN PLAY Please ❤️like and 🔁share with fellow Tesla traders/investors #Tesla successfully tested the $338.27 long-term channel bottom (1-year structure) after the earlier breakdown below ~$432. #TSLA had a strong bounce, which confirms this level as major support (for now). The downside objective is now complete, and the bias has shifted from bearish to cautiously bullish. * As long as $TSLA holds above $338.27, the strategy is to stay long/bullish. Target: $432.90 (major structure), extension: $440–$450+ into May–July. Stock may chop sideways in a wide range (roughly $330s → $430s) through Q3. It's likely volatile, range-bound accumulation before higher. If $TSLA closes below $338.27 by ~1% (≈ $334.87), that triggers a new 3–5 month sell signal down to ~$224.55. * Key pivot right now is $361.59. This is the decision level for the next few days. If #TSLA closes above $361.59 at the end of the week, it triggers a 3–5 day buy signal with $386.93 (short-term resistance) target. If that breaks, a move toward $432.90 by late May is expected. If $TSLA fails below $361.59, expect a pullback to $338.27. We could possibly see a choppy move in the upper $330s and the “Wedge formation” over the next few weeks. * So, for short-term traders, take profits near $386.93 (2–3 week target). For position traders, stay long above $338. For aggressive traders, trade the $361 pivot break (up or down). * Watch the full $TSLA Trading Plan for Apr 15, 2026 in this short video🔽

Wicked Stocks

23,490 Aufrufe • vor 5 Monaten

The semiconductor memory cycle has a timing problem. Sell-side consensus models for the DRAM supply-demand inflection largely ignore yield ramp realities, HBM wafer diversion, and the structural lag between capacity announcements and actual bit output. The gap between when the street expects the turn and when it actually arrives is where the trade lives. That timing gap is precisely what this Play quantifies. It models five supply-demand variables across SK Hynix, Samsung, and Micron — producing a probability distribution for when DRAM transitions from shortage to oversupply, not a single date. Here's what the Play covers: Inflection Probability Timeline The model produces a quarter-by-quarter cumulative probability curve for when supply-demand balance tips. Rather than anchoring on one date, it shows the full distribution — helping investors identify where consensus positioning diverges from modeled likelihood. Supplier Capacity Tracker Each of the three major DRAM producers carries different expansion timelines, yield curves, and long-term agreement lock ratios. SK Hynix leads on yield and speed; Samsung carries the largest absolute capacity delta but with slower ramp; Micron's Idaho fab represents a significant future supply addition. The Play tracks each supplier's effective supply contribution quarter by quarter. Scenario Analysis Four distinct scenarios — ranging from aggressive capacity ramp to prolonged supply tightness — allow investors to stress-test positioning under materially different industry conditions. Each scenario adjusts multiple variables simultaneously to capture how correlated shifts in demand and supply interact. Sensitivity Tornado Ten independent variables are ranked by their impact on inflection timing. Initial days-of-inventory dominates the total swing. HBM bit demand growth and wafer diversion ratio follow. The tornado chart makes clear which assumptions to monitor — and which are noise. DRAM Memory Inflection is now live on FUNDA for all subscribers.
0:23

The semiconductor memory cycle has a timing problem. Sell-side consensus models for the DRAM supply-demand inflection largely ignore yield ramp realities, HBM wafer diversion, and the structural lag between capacity announcements and actual bit output. The gap between when the street expects the turn and when it actually arrives is where the trade lives. That timing gap is precisely what this Play quantifies. It models five supply-demand variables across SK Hynix, Samsung, and Micron — producing a probability distribution for when DRAM transitions from shortage to oversupply, not a single date. Here's what the Play covers: Inflection Probability Timeline The model produces a quarter-by-quarter cumulative probability curve for when supply-demand balance tips. Rather than anchoring on one date, it shows the full distribution — helping investors identify where consensus positioning diverges from modeled likelihood. Supplier Capacity Tracker Each of the three major DRAM producers carries different expansion timelines, yield curves, and long-term agreement lock ratios. SK Hynix leads on yield and speed; Samsung carries the largest absolute capacity delta but with slower ramp; Micron's Idaho fab represents a significant future supply addition. The Play tracks each supplier's effective supply contribution quarter by quarter. Scenario Analysis Four distinct scenarios — ranging from aggressive capacity ramp to prolonged supply tightness — allow investors to stress-test positioning under materially different industry conditions. Each scenario adjusts multiple variables simultaneously to capture how correlated shifts in demand and supply interact. Sensitivity Tornado Ten independent variables are ranked by their impact on inflection timing. Initial days-of-inventory dominates the total swing. HBM bit demand growth and wafer diversion ratio follow. The tornado chart makes clear which assumptions to monitor — and which are noise. DRAM Memory Inflection is now live on FUNDA for all subscribers.

FUNDA

13,076 Aufrufe • vor 3 Monaten

i'm looking for feedback, thank you here's the full definition of my schematic: import { mkdirSync, writeFileSync } from "node:fs" import path from "node:path" import { defineCircuit, definePart, exportKiCadNetlist, instantiate, net, pin, } from "../../../tools/circuitd/src" const ch32v203f8u6 = definePart({ id: "CH32V203F8U6", kicadSymbol: "tinybee:CH32V203F8U6", footprint: "tinybee:QFN-20_L3.0-W3.0-P0.40-BL-EP1.7", defaultValue: "CH32V203F8U6", datasheet: " description: "144 MHz RISC-V MCU with ADCs, op-amps, advanced timers, and SWD", fields: { "LCSC Part": "C7570477", }, designNotes: [ "Power this MCU from a 3.3 V rail only; do not allow the VDD pin to see more than 3.6 V.", "Place a 100 nF decoupler immediately next to VDD and the QFN ground return, and keep that loop as short as possible.", "Put a small series resistor between PA0 and any off-board throttle or one-wire configuration signal so the MCU pin is not directly exposed at the connector.", "Keep PA13 and PA14 easy to probe and free of hard loads so SWD still works during bring-up and recovery.", "Keep PA8, PA9, PA10, PA7, PB0, and PB1 on the three phase-drive nets, and keep PA6/BKI free for a future fault or protection input.", "If you follow the openwch RISC-V ESC zero-cross scheme, tie PA3 and PA4 back into PA2 externally and reserve PA2 for that shared interrupt net.", "Route back-EMF and op-amp related pins away from phase copper, gate-drive loops, and other fast-switching nodes.", ], pins: { "PA0/WKUP/ADC0": "1", "PA1/ADC1": "2", "PA2/ADC2/OP2O0": "3", "PA3/ADC3/OP1O0": "4", "PA4/ADC4/OP2O1": "5", "PA5/ADC5/OP2N1": "6", "PA7/ADC7/OP2P1/CH1N": "7", "PB0/ADC8/OP1P1/CH2N": "8", "PB1/ADC9/OP1O1/CH3N": "9", "PB10/OP2N0": "10", "PB11/OP1N0": "11", "PB14/OP2P0": "12", "PB15/OP1P0": "13", "PA8/CH1": "14", "PA9/CH2": "15", "PA13/SWD/PA12/UDP": "16", "PA14/SWC/PA11/UDM": "17", "PA10/CH3": "18", VDD: "19", "PA6/ADC6/OP1N1/BKI": "20", GND: "21", }, }) const tlv75533pdqnt = definePart({ id: "TLV75533PDQNT", kicadSymbol: "Regulator_Linear:TLV75533PDBV", footprint: "tinybee:Texas_X2SON-4_1x1mm_P0.65mm", defaultValue: "TLV75533PDQNT", datasheet: " description: "500mA low-dropout fixed 3.3V regulator in 1x1mm X2SON-4", designNotes: [ "Treat +BATT as a 1S Li-ion or LiPo rail only; this regulator has a 5.5 V maximum input rating, so 2S or higher is out of bounds for this graph.", "Place at least 1 uF ceramic directly at IN and at least 1 uF ceramic directly at OUT; do not push those capacitors away from the package.", "Check regulator heating with (VIN - 3.3 V) * load current and add copper area if the dissipation is not comfortably safe.", "Add local input bulk when the battery lead is long or inductive so the LDO input does not absorb line spikes by itself.", "Keep EN tied to a known state at all times; if startup control matters later, break it out deliberately instead of bodging it in.", "The X2SON thermal pad is internally tied to GND; flood it into the local ground copper and do not leave the center pad floating.", ], pins: { OUT: "1", GND: "2", EN: "3", IN: "4", THERMAL_PAD: "5", }, }) const controlHeader = definePart({ id: "CTRL_IN_HEADER_1X01", kicadSymbol: "Connector_Generic:Conn_01x01", footprint: "tinybee:CTRL_PAD_1x01_Micro", defaultValue: "CTRL_IN", description: "1-pin control input wire pad for throttle signal", designNotes: [ "Use this only for the control signal.", "Ground reference is expected to be shared elsewhere in the system when this pad is in use.", "Battery power comes in through the dedicated battery wire holes, not through this control pad.", "PA0 on the CH32 is not a true FT input; treat this header as a 3.3 V logic input unless you deliberately add a real level-conditioning stage.", ], pins: { PIN1: "1", }, }) const motorHeader = definePart({ id: "MOTOR_OUT_HEADER_1X03", kicadSymbol: "Connector_Generic:Conn_01x03", footprint: "tinybee:MOTOR_PADS_1x03_Micro", defaultValue: "MOTOR_OUT", description: "3-pin motor phase wire pad group", designNotes: [ "This is the board edge interface for the three motor phases.", "Use direct wire holes here rather than a bulky 2.54 mm header footprint.", ], pins: { PIN1: "1", PIN2: "2", PIN3: "3", }, }) const programmingHeader = definePart({ id: "PROG_HEADER_1X04", kicadSymbol: "Connector_Generic:Conn_01x04", footprint: "tinybee:PROG_PADS_1x04_Micro", defaultValue: "PROG", description: "4-pin fine-pitch SWD programming header", designNotes: [ "Break out SWDIO, SWCLK, GND, and 3.3 V so the CH32 can be flashed and recovered without bodge wires.", "Keep this header free of extra loading and avoid reusing the SWD pins elsewhere until firmware bring-up is stable.", "Treat the 3.3 V pin here as target reference unless you deliberately design reverse-current-safe back-powering through the regulator path.", ], pins: { PIN1: "1", PIN2: "2", PIN3: "3", PIN4: "4", }, }) const batteryHeader = definePart({ id: "BATT_IN_HEADER_1X02", kicadSymbol: "Connector_Generic:Conn_01x02", footprint: "tinybee:BATT_PADS_1x02_Micro", defaultValue: "BATT_IN", description: "2-pin battery wire pad pair", designNotes: [ "Use this dedicated pair for battery positive and battery negative input.", "Keep the battery loop tight to the bulk capacitors and half-bridge supply entry.", ], pins: { PIN1: "1", PIN2: "2", }, }) const complementaryHalfBridge = definePart({ id: "PMCPB5530X_115", kicadSymbol: "tinybee:PMCPB5530X,115", footprint: "tinybee:DFN2020-6_L2.0-W2.0-P0.65-BL", defaultValue: "PMCPB5530X,115", datasheet: " description: "20 V complementary N/P MOSFET half-bridge in DFN2020-6", fields: { "LCSC Part": "C552747", }, designNotes: [ "Use this complementary half-bridge only on a 1S Li-ion or LiPo rail; do not reuse the direct P-gate pull-down topology above the 1S battery range.", "With +BATT limited to the 1S range, the direct P-gate pull-down swing stays inside the device gate limits and gives usable drive headroom.", "Drive the low-side N-FET gates directly from the 3.3 V timer outputs only in this 1S design; rework the stage before raising the battery voltage.", "Do not skimp on local +BATT bypass; keep real ceramic bulk plus a high-frequency bypass capacitor tight to the half-bridge supply loop.", "Pour the duplicated drain pads into real copper for current and heat spreading; do not neck them down right at the package.", "Keep each gate loop short, tight, and referenced to its own source return to reduce ringing and false turn-on.", "Assume the board copper sets the real current limit; check temperature rise on the actual ESC geometry, not only the datasheet headline current.", ], pins: { LOW_SIDE_SOURCE: "1", LOW_SIDE_GATE: "2", HIGH_SIDE_DRAIN: ["3", "8"], HIGH_SIDE_SOURCE: "4", HIGH_SIDE_GATE: "5", LOW_SIDE_DRAIN: ["6", "7"], }, }) const highSidePullDownBjt = definePart({ id: "BC847BLP_7", kicadSymbol: "Transistor_BJT:Q_NPN_BEC", footprint: "Package_TO_SOT_SMD:SOT-883", defaultValue: "BC847BLP-7", datasheet: " description: "45 V, 100 mA NPN small-signal transistor in SOT-883", designNotes: [ "Use this device only as the helper pull-down for the high-side P-gate nets; do not put motor or supply current through it as a power path element.", "In this topology, keep emitter at GND, collector on the P-gate net, and drive the base through a resistor from the MCU.", "Give the base a defined pulldown so the PMOS high side stays off while the MCU is in reset or high-impedance.", "With a 470R P-gate pull-up on a 1S rail, this transistor sinks about 9 mA at full turn-on, which is still well inside the BC847BLP-7's capability.", "Check the B-E-C pin order against the footprint before layout release; small BJTs are easy to rotate or mirror by accident.", ], pins: { BASE: "1", EMITTER: "2", COLLECTOR: "3", }, }) const yageoRc0201Datasheet = " const kemetMlccDatasheet = " const defineYageoRc0201 = (mpn: string, value: string) => definePart({ id: mpn, kicadSymbol: "Device:R", footprint: "Resistor_SMD:R_0201_0603Metric", defaultValue: value, datasheet: yageoRc0201Datasheet, description: `Yageo ${mpn} 0201 1% thick-film resistor`, fields: { Manufacturer: "Yageo", MPN: mpn, Tolerance: "1%", Power: "0.05W", }, designNotes: [ "This BOM is locked to an exact Yageo RC0201FR-07 1% resistor, not a generic 0201 placeholder.", "Keep the 1% series on the back-EMF divider path so thresholds stay predictable across temperature.", "Re-check pulse and dissipation stress if the battery domain or gate network changes.", ], pins: { A: "1", B: "2", }, }) const defineYageoRc0402 = (mpn: string, value: string) => definePart({ id: mpn, kicadSymbol: "Device:R", footprint: "Resistor_SMD:R_0402_1005Metric", defaultValue: value, datasheet: " description: `Yageo ${mpn} 0402 1% thick-film resistor`, fields: { Manufacturer: "Yageo", MPN: mpn, Tolerance: "1%", Power: "0.063W", }, designNotes: [ "Use 0402 here where the resistor sees non-trivial continuous dissipation on the switching rail.", "Do not silently shrink these positions back to 0201 without re-checking power and temperature margin.", ], pins: { A: "1", B: "2", }, }) const defineKemetMlcc = ({ mpn, value, footprint, description, voltage, dielectric, designNotes, }: { mpn: string value: string footprint: string description: string voltage: string dielectric: string designNotes: readonly string[] }) => definePart({ id: mpn, kicadSymbol: "Device:C", footprint, defaultValue: value, datasheet: kemetMlccDatasheet, description, fields: { Manufacturer: "KEMET", MPN: mpn, Dielectric: dielectric, "Rated Voltage": voltage, }, designNotes, pins: { POS: "1", NEG: "2", }, }) const resistor30r = defineYageoRc0201("RC0201FR-0730RL", "30R") const resistor470r0402 = defineYageoRc0402("RC0402FR-07470RL", "470R") const resistor1k = defineYageoRc0201("RC0201FR-071KL", "1k") const resistor10k = defineYageoRc0201("RC0201FR-0710KL", "10k") const resistor100k = defineYageoRc0201("RC0201FR-07100KL", "100k") const resistor12k = defineYageoRc0201("RC0201FR-0712KL", "12k") const resistor15k = defineYageoRc0201("RC0201FR-0715KL", "15k") const resistor33k = defineYageoRc0201("RC0201FR-0733KL", "33k") const swdVrefIsolationDiode = definePart({ id: "RB751CS40,315", kicadSymbol: "Device:D_Schottky", footprint: "tinybee:D_SOD-882", defaultValue: "RB751CS40,315", datasheet: " description: "40 V small-signal Schottky diode in SOD-882 for isolated SWD Vref sensing", designNotes: [ "This diode lets the programming header sense the target 3.3 V rail without back-powering the TLV755 when an external tool drives Vref.", "Place it close to the programming pads, and keep the +3V3 cathode side on the board rail with the isolated anode side only on the header Vref pin.", ], pins: { K: "1", A: "2", }, }) const capacitor100nF0402 = defineKemetMlcc({ mpn: "C0402C104K4RACTU", value: "100nF", footprint: "Capacitor_SMD:C_0402_1005Metric", description: "KEMET 100nF 16V X7R MLCC, 0402", voltage: "16V", dielectric: "X7R", designNotes: [ "This exact 16 V X7R part is locked for the 100 nF bypass positions in this 1S design.", "Use it for local high-frequency bypass on +BATT or V3.3; do not silently substitute a lower-voltage or poor-stability dielectric.", ], }) const capacitor100nF0201 = defineKemetMlcc({ mpn: "C0201C104K9PACTU", value: "100nF", footprint: "Capacitor_SMD:C_0201_0603Metric", description: "KEMET 100nF 6.3V X5R MLCC, 0201", voltage: "6.3V", dielectric: "X5R", designNotes: [ "Use this only for local low-voltage decoupling like the CH32 VDD bypass.", "Do not silently reuse this 0201 part on the battery rail; keep the battery-facing 100 nF positions on the 16 V 0402 part.", ], }) const capacitor1uF0402 = defineKemetMlcc({ mpn: "C0402C105K8PAC7411", value: "1uF", footprint: "Capacitor_SMD:C_0402_1005Metric", description: "KEMET 1uF 10V X5R MLCC, 0402", voltage: "10V", dielectric: "X5R", designNotes: [ "This exact 10 V X5R part is the TLV755 output capacitor and satisfies the regulator's 1 uF ceramic requirement.", "A 0402 body is acceptable here, but this is still a regulator output part, not a battery-domain bypass; do not shrink it further without checking bias derating and stability.", ], }) const capacitor22uF0805 = defineKemetMlcc({ mpn: "C0805C226M8PACTU", value: "22uF", footprint: "Capacitor_SMD:C_0805_2012Metric", description: "KEMET 22uF 10V X5R MLCC, 0805", voltage: "10V", dielectric: "X5R", designNotes: [ "This exact 10 V X5R 0805 part is the 1S battery-side bulk capacitor.", "Keep this input bulk capacitor in 0805 or larger; do not shrink it back to 0603 without re-checking effective capacitance at 1S bias.", ], }) const C1 = instantiate(capacitor1uF0402, "C1") const C2 = instantiate(capacitor100nF0201, "C2") const C3 = instantiate(capacitor100nF0402, "C3") const C4 = instantiate(capacitor22uF0805, "C4") const C5 = instantiate(capacitor100nF0201, "C5") const C6 = instantiate(capacitor22uF0805, "C6") const Q1 = instantiate(complementaryHalfBridge, "Q1") const Q2 = instantiate(complementaryHalfBridge, "Q2") const Q3 = instantiate(complementaryHalfBridge, "Q3") const Q4 = instantiate(highSidePullDownBjt, "Q4") const Q5 = instantiate(highSidePullDownBjt, "Q5") const Q6 = instantiate(highSidePullDownBjt, "Q6") const J_CTRL = instantiate(controlHeader, "J_CTRL") const J_BATT = instantiate(batteryHeader, "J_BATT") const J_MOTOR = instantiate(motorHeader, "J_MOTOR") const TP_PROG = instantiate(programmingHeader, "TP_PROG") const D1 = instantiate(swdVrefIsolationDiode, "D1") const R1 = instantiate(resistor30r, "R1") const R2 = instantiate(resistor1k, "R2") const R3 = instantiate(resistor10k, "R3") const R4 = instantiate(resistor470r0402, "R4") const R5 = instantiate(resistor30r, "R5") const R6 = instantiate(resistor1k, "R6") const R7 = instantiate(resistor10k, "R7") const R8 = instantiate(resistor470r0402, "R8") const R9 = instantiate(resistor30r, "R9") const R10 = instantiate(resistor1k, "R10") const R11 = instantiate(resistor10k, "R11") const R12 = instantiate(resistor470r0402, "R12") const R13 = instantiate(resistor15k, "R13") const R14 = instantiate(resistor33k, "R14") const R15 = instantiate(resistor100k, "R15") const R16 = instantiate(resistor15k, "R16") const R17 = instantiate(resistor33k, "R17") const R18 = instantiate(resistor100k, "R18") const R19 = instantiate(resistor15k, "R19") const R20 = instantiate(resistor33k, "R20") const R21 = instantiate(resistor100k, "R21") const R22 = instantiate(resistor100k, "R22") const R23 = instantiate(resistor100k, "R23") const R24 = instantiate(resistor100k, "R24") const R25 = instantiate(resistor12k, "R25") const R26 = instantiate(resistor33k, "R26") const R27 = instantiate(resistor1k, "R27") const U1 = instantiate(tlv75533pdqnt, "U1") const U2 = instantiate(ch32v203f8u6, "U2") const tinybeeEscChannel = defineCircuit({ name: "tinybee-esc-channel", source: "projects/tinybee/circuitd/tinybee-esc-channel.ts", description: "1S CH32-based tinybee ESC channel aligned to the openwch RISC-V_ESC V203 pinout", parts: [ C1, C2, C3, C4, C5, C6, D1, J_BATT, J_CTRL, J_MOTOR, Q1, Q2, Q3, Q4, Q5, Q6, R1, R2, R3, R4, R5, R6, R7, R8, R9, R10, R11, R12, R13, R14, R15, R16, R17, R18, R19, R20, R21, R22, R23, R24, R25, R26, R27, TP_PROG, U1, U2, ], nets: [ net( "+BATTERY", pin(J_BATT, "PIN1"), pin(C3, "POS"), pin(C4, "POS"), pin(C6, "POS"), pin(Q1, "HIGH_SIDE_SOURCE"), pin(Q2, "HIGH_SIDE_SOURCE"), pin(Q3, "HIGH_SIDE_SOURCE"), pin(R4, "B"), pin(R8, "B"), pin(R12, "B"), pin(R25, "B"), pin(U1, "IN"), pin(U1, "EN"), ), net("/ADC_VOLTAGE_SENSE", pin(C5, "POS"), pin(R25, "A"), pin(R26, "B"), pin(U2, "PA1/ADC1")), net("/A_HIGH_COMMAND", pin(R2, "B"), pin(U2, "PA10/CH3")), net("/A_LOW_COMMAND", pin(R1, "B"), pin(U2, "PB1/ADC9/OP1O1/CH3N")), net("/A_HIGH_CONTROL", pin(Q4, "BASE"), pin(R2, "A"), pin(R3, "B")), net("/A_LOW_GATE", pin(Q1, "LOW_SIDE_GATE"), pin(R1, "A"), pin(R22, "B")), net("/A_P_GATE", pin(Q1, "HIGH_SIDE_GATE"), pin(Q4, "COLLECTOR"), pin(R4, "A")), net("/A_BACK_EMF", pin(R13, "A"), pin(R14, "B"), pin(R15, "A"), pin(U2, "PA5/ADC5/OP2N1")), net("/B_BACK_EMF", pin(R16, "A"), pin(R17, "B"), pin(R18, "A"), pin(U2, "PB10/OP2N0")), net("/C_BACK_EMF", pin(R19, "A"), pin(R20, "B"), pin(R21, "A"), pin(U2, "PB11/OP1N0")), net("/BACK_EMF_COMMON", pin(R15, "B"), pin(R18, "B"), pin(R21, "B"), pin(U2, "PB14/OP2P0"), pin(U2, "PB15/OP1P0")), net("/B_HIGH_COMMAND", pin(R6, "B"), pin(U2, "PA9/CH2")), net("/B_LOW_COMMAND", pin(R5, "B"), pin(U2, "PB0/ADC8/OP1P1/CH2N")), net("/B_HIGH_CONTROL", pin(Q5, "BASE"), pin(R6, "A"), pin(R7, "B")), net("/B_LOW_GATE", pin(Q3, "LOW_SIDE_GATE"), pin(R5, "A"), pin(R23, "B")), net("/B_P_GATE", pin(Q3, "HIGH_SIDE_GATE"), pin(Q5, "COLLECTOR"), pin(R8, "A")), net("/C_HIGH_COMMAND", pin(R10, "B"), pin(U2, "PA8/CH1")), net("/C_LOW_COMMAND", pin(R9, "B"), pin(U2, "PA7/ADC7/OP2P1/CH1N")), net("/C_HIGH_CONTROL", pin(Q6, "BASE"), pin(R10, "A"), pin(R11, "B")), net("/C_LOW_GATE", pin(Q2, "LOW_SIDE_GATE"), pin(R9, "A"), pin(R24, "B")), net("/C_P_GATE", pin(Q2, "HIGH_SIDE_GATE"), pin(Q6, "COLLECTOR"), pin(R12, "A")), net("/PWM_INPUT", pin(J_CTRL, "PIN1"), pin(R27, "A")), net("/PWM_INPUT_MCU", pin(R27, "B"), pin(U2, "PA0/WKUP/ADC0")), net("/OPA_ZERO_CROSS_INTERRUPT", pin(U2, "PA2/ADC2/OP2O0"), pin(U2, "PA3/ADC3/OP1O0"), pin(U2, "PA4/ADC4/OP2O1")), net("/PHASE_A", pin(J_MOTOR, "PIN1"), pin(Q1, "HIGH_SIDE_DRAIN"), pin(Q1, "LOW_SIDE_DRAIN"), pin(R13, "B")), net("/PHASE_B", pin(J_MOTOR, "PIN2"), pin(Q3, "HIGH_SIDE_DRAIN"), pin(Q3, "LOW_SIDE_DRAIN"), pin(R16, "B")), net("/PHASE_C", pin(J_MOTOR, "PIN3"), pin(Q2, "HIGH_SIDE_DRAIN"), pin(Q2, "LOW_SIDE_DRAIN"), pin(R19, "B")), net("/SWD_CLOCK", pin(TP_PROG, "PIN1"), pin(U2, "PA14/SWC/PA11/UDM")), net("/SWD_DATA", pin(TP_PROG, "PIN2"), pin(U2, "PA13/SWD/PA12/UDP")), net("/SWD_VREF", pin(D1, "A"), pin(TP_PROG, "PIN4")), net( "GND", pin(J_BATT, "PIN2"), pin(C1, "NEG"), pin(C2, "NEG"), pin(C3, "NEG"), pin(C4, "NEG"), pin(C6, "NEG"), pin(Q1, "LOW_SIDE_SOURCE"), pin(Q2, "LOW_SIDE_SOURCE"), pin(Q3, "LOW_SIDE_SOURCE"), pin(Q4, "EMITTER"), pin(Q5, "EMITTER"), pin(Q6, "EMITTER"), pin(R3, "A"), pin(R7, "A"), pin(R11, "A"), pin(R14, "A"), pin(R17, "A"), pin(R20, "A"), pin(R22, "A"), pin(R23, "A"), pin(R24, "A"), pin(R26, "A"), pin(C5, "NEG"), pin(TP_PROG, "PIN3"), pin(U1, "GND"), pin(U1, "THERMAL_PAD"), pin(U2, "GND"), ), net("+3V3", pin(C1, "POS"), pin(C2, "POS"), pin(D1, "K"), pin(U1, "OUT"), pin(U2, "VDD")), net("unconnected-(U2-PA6{slash}ADC6{slash}OP1N1{slash}BKI-Pad20)", pin(U2, "PA6/ADC6/OP1N1/BKI")), ], }) const outputPath = path.resolve(__dirname, "generated", " const main = () => { mkdirSync(path.dirname(outputPath), { recursive: true }) writeFileSync(outputPath, exportKiCadNetlist(tinybeeEscChannel), "utf8") process.stdout.write(`${outputPath}\n`) } if (import.meta.main) { main() } export { tinybeeEscChannel } export default tinybeeEscChannel
0:30

i'm looking for feedback, thank you here's the full definition of my schematic: import { mkdirSync, writeFileSync } from "node:fs" import path from "node:path" import { defineCircuit, definePart, exportKiCadNetlist, instantiate, net, pin, } from "../../../tools/circuitd/src" const ch32v203f8u6 = definePart({ id: "CH32V203F8U6", kicadSymbol: "tinybee:CH32V203F8U6", footprint: "tinybee:QFN-20_L3.0-W3.0-P0.40-BL-EP1.7", defaultValue: "CH32V203F8U6", datasheet: " description: "144 MHz RISC-V MCU with ADCs, op-amps, advanced timers, and SWD", fields: { "LCSC Part": "C7570477", }, designNotes: [ "Power this MCU from a 3.3 V rail only; do not allow the VDD pin to see more than 3.6 V.", "Place a 100 nF decoupler immediately next to VDD and the QFN ground return, and keep that loop as short as possible.", "Put a small series resistor between PA0 and any off-board throttle or one-wire configuration signal so the MCU pin is not directly exposed at the connector.", "Keep PA13 and PA14 easy to probe and free of hard loads so SWD still works during bring-up and recovery.", "Keep PA8, PA9, PA10, PA7, PB0, and PB1 on the three phase-drive nets, and keep PA6/BKI free for a future fault or protection input.", "If you follow the openwch RISC-V ESC zero-cross scheme, tie PA3 and PA4 back into PA2 externally and reserve PA2 for that shared interrupt net.", "Route back-EMF and op-amp related pins away from phase copper, gate-drive loops, and other fast-switching nodes.", ], pins: { "PA0/WKUP/ADC0": "1", "PA1/ADC1": "2", "PA2/ADC2/OP2O0": "3", "PA3/ADC3/OP1O0": "4", "PA4/ADC4/OP2O1": "5", "PA5/ADC5/OP2N1": "6", "PA7/ADC7/OP2P1/CH1N": "7", "PB0/ADC8/OP1P1/CH2N": "8", "PB1/ADC9/OP1O1/CH3N": "9", "PB10/OP2N0": "10", "PB11/OP1N0": "11", "PB14/OP2P0": "12", "PB15/OP1P0": "13", "PA8/CH1": "14", "PA9/CH2": "15", "PA13/SWD/PA12/UDP": "16", "PA14/SWC/PA11/UDM": "17", "PA10/CH3": "18", VDD: "19", "PA6/ADC6/OP1N1/BKI": "20", GND: "21", }, }) const tlv75533pdqnt = definePart({ id: "TLV75533PDQNT", kicadSymbol: "Regulator_Linear:TLV75533PDBV", footprint: "tinybee:Texas_X2SON-4_1x1mm_P0.65mm", defaultValue: "TLV75533PDQNT", datasheet: " description: "500mA low-dropout fixed 3.3V regulator in 1x1mm X2SON-4", designNotes: [ "Treat +BATT as a 1S Li-ion or LiPo rail only; this regulator has a 5.5 V maximum input rating, so 2S or higher is out of bounds for this graph.", "Place at least 1 uF ceramic directly at IN and at least 1 uF ceramic directly at OUT; do not push those capacitors away from the package.", "Check regulator heating with (VIN - 3.3 V) * load current and add copper area if the dissipation is not comfortably safe.", "Add local input bulk when the battery lead is long or inductive so the LDO input does not absorb line spikes by itself.", "Keep EN tied to a known state at all times; if startup control matters later, break it out deliberately instead of bodging it in.", "The X2SON thermal pad is internally tied to GND; flood it into the local ground copper and do not leave the center pad floating.", ], pins: { OUT: "1", GND: "2", EN: "3", IN: "4", THERMAL_PAD: "5", }, }) const controlHeader = definePart({ id: "CTRL_IN_HEADER_1X01", kicadSymbol: "Connector_Generic:Conn_01x01", footprint: "tinybee:CTRL_PAD_1x01_Micro", defaultValue: "CTRL_IN", description: "1-pin control input wire pad for throttle signal", designNotes: [ "Use this only for the control signal.", "Ground reference is expected to be shared elsewhere in the system when this pad is in use.", "Battery power comes in through the dedicated battery wire holes, not through this control pad.", "PA0 on the CH32 is not a true FT input; treat this header as a 3.3 V logic input unless you deliberately add a real level-conditioning stage.", ], pins: { PIN1: "1", }, }) const motorHeader = definePart({ id: "MOTOR_OUT_HEADER_1X03", kicadSymbol: "Connector_Generic:Conn_01x03", footprint: "tinybee:MOTOR_PADS_1x03_Micro", defaultValue: "MOTOR_OUT", description: "3-pin motor phase wire pad group", designNotes: [ "This is the board edge interface for the three motor phases.", "Use direct wire holes here rather than a bulky 2.54 mm header footprint.", ], pins: { PIN1: "1", PIN2: "2", PIN3: "3", }, }) const programmingHeader = definePart({ id: "PROG_HEADER_1X04", kicadSymbol: "Connector_Generic:Conn_01x04", footprint: "tinybee:PROG_PADS_1x04_Micro", defaultValue: "PROG", description: "4-pin fine-pitch SWD programming header", designNotes: [ "Break out SWDIO, SWCLK, GND, and 3.3 V so the CH32 can be flashed and recovered without bodge wires.", "Keep this header free of extra loading and avoid reusing the SWD pins elsewhere until firmware bring-up is stable.", "Treat the 3.3 V pin here as target reference unless you deliberately design reverse-current-safe back-powering through the regulator path.", ], pins: { PIN1: "1", PIN2: "2", PIN3: "3", PIN4: "4", }, }) const batteryHeader = definePart({ id: "BATT_IN_HEADER_1X02", kicadSymbol: "Connector_Generic:Conn_01x02", footprint: "tinybee:BATT_PADS_1x02_Micro", defaultValue: "BATT_IN", description: "2-pin battery wire pad pair", designNotes: [ "Use this dedicated pair for battery positive and battery negative input.", "Keep the battery loop tight to the bulk capacitors and half-bridge supply entry.", ], pins: { PIN1: "1", PIN2: "2", }, }) const complementaryHalfBridge = definePart({ id: "PMCPB5530X_115", kicadSymbol: "tinybee:PMCPB5530X,115", footprint: "tinybee:DFN2020-6_L2.0-W2.0-P0.65-BL", defaultValue: "PMCPB5530X,115", datasheet: " description: "20 V complementary N/P MOSFET half-bridge in DFN2020-6", fields: { "LCSC Part": "C552747", }, designNotes: [ "Use this complementary half-bridge only on a 1S Li-ion or LiPo rail; do not reuse the direct P-gate pull-down topology above the 1S battery range.", "With +BATT limited to the 1S range, the direct P-gate pull-down swing stays inside the device gate limits and gives usable drive headroom.", "Drive the low-side N-FET gates directly from the 3.3 V timer outputs only in this 1S design; rework the stage before raising the battery voltage.", "Do not skimp on local +BATT bypass; keep real ceramic bulk plus a high-frequency bypass capacitor tight to the half-bridge supply loop.", "Pour the duplicated drain pads into real copper for current and heat spreading; do not neck them down right at the package.", "Keep each gate loop short, tight, and referenced to its own source return to reduce ringing and false turn-on.", "Assume the board copper sets the real current limit; check temperature rise on the actual ESC geometry, not only the datasheet headline current.", ], pins: { LOW_SIDE_SOURCE: "1", LOW_SIDE_GATE: "2", HIGH_SIDE_DRAIN: ["3", "8"], HIGH_SIDE_SOURCE: "4", HIGH_SIDE_GATE: "5", LOW_SIDE_DRAIN: ["6", "7"], }, }) const highSidePullDownBjt = definePart({ id: "BC847BLP_7", kicadSymbol: "Transistor_BJT:Q_NPN_BEC", footprint: "Package_TO_SOT_SMD:SOT-883", defaultValue: "BC847BLP-7", datasheet: " description: "45 V, 100 mA NPN small-signal transistor in SOT-883", designNotes: [ "Use this device only as the helper pull-down for the high-side P-gate nets; do not put motor or supply current through it as a power path element.", "In this topology, keep emitter at GND, collector on the P-gate net, and drive the base through a resistor from the MCU.", "Give the base a defined pulldown so the PMOS high side stays off while the MCU is in reset or high-impedance.", "With a 470R P-gate pull-up on a 1S rail, this transistor sinks about 9 mA at full turn-on, which is still well inside the BC847BLP-7's capability.", "Check the B-E-C pin order against the footprint before layout release; small BJTs are easy to rotate or mirror by accident.", ], pins: { BASE: "1", EMITTER: "2", COLLECTOR: "3", }, }) const yageoRc0201Datasheet = " const kemetMlccDatasheet = " const defineYageoRc0201 = (mpn: string, value: string) => definePart({ id: mpn, kicadSymbol: "Device:R", footprint: "Resistor_SMD:R_0201_0603Metric", defaultValue: value, datasheet: yageoRc0201Datasheet, description: `Yageo ${mpn} 0201 1% thick-film resistor`, fields: { Manufacturer: "Yageo", MPN: mpn, Tolerance: "1%", Power: "0.05W", }, designNotes: [ "This BOM is locked to an exact Yageo RC0201FR-07 1% resistor, not a generic 0201 placeholder.", "Keep the 1% series on the back-EMF divider path so thresholds stay predictable across temperature.", "Re-check pulse and dissipation stress if the battery domain or gate network changes.", ], pins: { A: "1", B: "2", }, }) const defineYageoRc0402 = (mpn: string, value: string) => definePart({ id: mpn, kicadSymbol: "Device:R", footprint: "Resistor_SMD:R_0402_1005Metric", defaultValue: value, datasheet: " description: `Yageo ${mpn} 0402 1% thick-film resistor`, fields: { Manufacturer: "Yageo", MPN: mpn, Tolerance: "1%", Power: "0.063W", }, designNotes: [ "Use 0402 here where the resistor sees non-trivial continuous dissipation on the switching rail.", "Do not silently shrink these positions back to 0201 without re-checking power and temperature margin.", ], pins: { A: "1", B: "2", }, }) const defineKemetMlcc = ({ mpn, value, footprint, description, voltage, dielectric, designNotes, }: { mpn: string value: string footprint: string description: string voltage: string dielectric: string designNotes: readonly string[] }) => definePart({ id: mpn, kicadSymbol: "Device:C", footprint, defaultValue: value, datasheet: kemetMlccDatasheet, description, fields: { Manufacturer: "KEMET", MPN: mpn, Dielectric: dielectric, "Rated Voltage": voltage, }, designNotes, pins: { POS: "1", NEG: "2", }, }) const resistor30r = defineYageoRc0201("RC0201FR-0730RL", "30R") const resistor470r0402 = defineYageoRc0402("RC0402FR-07470RL", "470R") const resistor1k = defineYageoRc0201("RC0201FR-071KL", "1k") const resistor10k = defineYageoRc0201("RC0201FR-0710KL", "10k") const resistor100k = defineYageoRc0201("RC0201FR-07100KL", "100k") const resistor12k = defineYageoRc0201("RC0201FR-0712KL", "12k") const resistor15k = defineYageoRc0201("RC0201FR-0715KL", "15k") const resistor33k = defineYageoRc0201("RC0201FR-0733KL", "33k") const swdVrefIsolationDiode = definePart({ id: "RB751CS40,315", kicadSymbol: "Device:D_Schottky", footprint: "tinybee:D_SOD-882", defaultValue: "RB751CS40,315", datasheet: " description: "40 V small-signal Schottky diode in SOD-882 for isolated SWD Vref sensing", designNotes: [ "This diode lets the programming header sense the target 3.3 V rail without back-powering the TLV755 when an external tool drives Vref.", "Place it close to the programming pads, and keep the +3V3 cathode side on the board rail with the isolated anode side only on the header Vref pin.", ], pins: { K: "1", A: "2", }, }) const capacitor100nF0402 = defineKemetMlcc({ mpn: "C0402C104K4RACTU", value: "100nF", footprint: "Capacitor_SMD:C_0402_1005Metric", description: "KEMET 100nF 16V X7R MLCC, 0402", voltage: "16V", dielectric: "X7R", designNotes: [ "This exact 16 V X7R part is locked for the 100 nF bypass positions in this 1S design.", "Use it for local high-frequency bypass on +BATT or V3.3; do not silently substitute a lower-voltage or poor-stability dielectric.", ], }) const capacitor100nF0201 = defineKemetMlcc({ mpn: "C0201C104K9PACTU", value: "100nF", footprint: "Capacitor_SMD:C_0201_0603Metric", description: "KEMET 100nF 6.3V X5R MLCC, 0201", voltage: "6.3V", dielectric: "X5R", designNotes: [ "Use this only for local low-voltage decoupling like the CH32 VDD bypass.", "Do not silently reuse this 0201 part on the battery rail; keep the battery-facing 100 nF positions on the 16 V 0402 part.", ], }) const capacitor1uF0402 = defineKemetMlcc({ mpn: "C0402C105K8PAC7411", value: "1uF", footprint: "Capacitor_SMD:C_0402_1005Metric", description: "KEMET 1uF 10V X5R MLCC, 0402", voltage: "10V", dielectric: "X5R", designNotes: [ "This exact 10 V X5R part is the TLV755 output capacitor and satisfies the regulator's 1 uF ceramic requirement.", "A 0402 body is acceptable here, but this is still a regulator output part, not a battery-domain bypass; do not shrink it further without checking bias derating and stability.", ], }) const capacitor22uF0805 = defineKemetMlcc({ mpn: "C0805C226M8PACTU", value: "22uF", footprint: "Capacitor_SMD:C_0805_2012Metric", description: "KEMET 22uF 10V X5R MLCC, 0805", voltage: "10V", dielectric: "X5R", designNotes: [ "This exact 10 V X5R 0805 part is the 1S battery-side bulk capacitor.", "Keep this input bulk capacitor in 0805 or larger; do not shrink it back to 0603 without re-checking effective capacitance at 1S bias.", ], }) const C1 = instantiate(capacitor1uF0402, "C1") const C2 = instantiate(capacitor100nF0201, "C2") const C3 = instantiate(capacitor100nF0402, "C3") const C4 = instantiate(capacitor22uF0805, "C4") const C5 = instantiate(capacitor100nF0201, "C5") const C6 = instantiate(capacitor22uF0805, "C6") const Q1 = instantiate(complementaryHalfBridge, "Q1") const Q2 = instantiate(complementaryHalfBridge, "Q2") const Q3 = instantiate(complementaryHalfBridge, "Q3") const Q4 = instantiate(highSidePullDownBjt, "Q4") const Q5 = instantiate(highSidePullDownBjt, "Q5") const Q6 = instantiate(highSidePullDownBjt, "Q6") const J_CTRL = instantiate(controlHeader, "J_CTRL") const J_BATT = instantiate(batteryHeader, "J_BATT") const J_MOTOR = instantiate(motorHeader, "J_MOTOR") const TP_PROG = instantiate(programmingHeader, "TP_PROG") const D1 = instantiate(swdVrefIsolationDiode, "D1") const R1 = instantiate(resistor30r, "R1") const R2 = instantiate(resistor1k, "R2") const R3 = instantiate(resistor10k, "R3") const R4 = instantiate(resistor470r0402, "R4") const R5 = instantiate(resistor30r, "R5") const R6 = instantiate(resistor1k, "R6") const R7 = instantiate(resistor10k, "R7") const R8 = instantiate(resistor470r0402, "R8") const R9 = instantiate(resistor30r, "R9") const R10 = instantiate(resistor1k, "R10") const R11 = instantiate(resistor10k, "R11") const R12 = instantiate(resistor470r0402, "R12") const R13 = instantiate(resistor15k, "R13") const R14 = instantiate(resistor33k, "R14") const R15 = instantiate(resistor100k, "R15") const R16 = instantiate(resistor15k, "R16") const R17 = instantiate(resistor33k, "R17") const R18 = instantiate(resistor100k, "R18") const R19 = instantiate(resistor15k, "R19") const R20 = instantiate(resistor33k, "R20") const R21 = instantiate(resistor100k, "R21") const R22 = instantiate(resistor100k, "R22") const R23 = instantiate(resistor100k, "R23") const R24 = instantiate(resistor100k, "R24") const R25 = instantiate(resistor12k, "R25") const R26 = instantiate(resistor33k, "R26") const R27 = instantiate(resistor1k, "R27") const U1 = instantiate(tlv75533pdqnt, "U1") const U2 = instantiate(ch32v203f8u6, "U2") const tinybeeEscChannel = defineCircuit({ name: "tinybee-esc-channel", source: "projects/tinybee/circuitd/tinybee-esc-channel.ts", description: "1S CH32-based tinybee ESC channel aligned to the openwch RISC-V_ESC V203 pinout", parts: [ C1, C2, C3, C4, C5, C6, D1, J_BATT, J_CTRL, J_MOTOR, Q1, Q2, Q3, Q4, Q5, Q6, R1, R2, R3, R4, R5, R6, R7, R8, R9, R10, R11, R12, R13, R14, R15, R16, R17, R18, R19, R20, R21, R22, R23, R24, R25, R26, R27, TP_PROG, U1, U2, ], nets: [ net( "+BATTERY", pin(J_BATT, "PIN1"), pin(C3, "POS"), pin(C4, "POS"), pin(C6, "POS"), pin(Q1, "HIGH_SIDE_SOURCE"), pin(Q2, "HIGH_SIDE_SOURCE"), pin(Q3, "HIGH_SIDE_SOURCE"), pin(R4, "B"), pin(R8, "B"), pin(R12, "B"), pin(R25, "B"), pin(U1, "IN"), pin(U1, "EN"), ), net("/ADC_VOLTAGE_SENSE", pin(C5, "POS"), pin(R25, "A"), pin(R26, "B"), pin(U2, "PA1/ADC1")), net("/A_HIGH_COMMAND", pin(R2, "B"), pin(U2, "PA10/CH3")), net("/A_LOW_COMMAND", pin(R1, "B"), pin(U2, "PB1/ADC9/OP1O1/CH3N")), net("/A_HIGH_CONTROL", pin(Q4, "BASE"), pin(R2, "A"), pin(R3, "B")), net("/A_LOW_GATE", pin(Q1, "LOW_SIDE_GATE"), pin(R1, "A"), pin(R22, "B")), net("/A_P_GATE", pin(Q1, "HIGH_SIDE_GATE"), pin(Q4, "COLLECTOR"), pin(R4, "A")), net("/A_BACK_EMF", pin(R13, "A"), pin(R14, "B"), pin(R15, "A"), pin(U2, "PA5/ADC5/OP2N1")), net("/B_BACK_EMF", pin(R16, "A"), pin(R17, "B"), pin(R18, "A"), pin(U2, "PB10/OP2N0")), net("/C_BACK_EMF", pin(R19, "A"), pin(R20, "B"), pin(R21, "A"), pin(U2, "PB11/OP1N0")), net("/BACK_EMF_COMMON", pin(R15, "B"), pin(R18, "B"), pin(R21, "B"), pin(U2, "PB14/OP2P0"), pin(U2, "PB15/OP1P0")), net("/B_HIGH_COMMAND", pin(R6, "B"), pin(U2, "PA9/CH2")), net("/B_LOW_COMMAND", pin(R5, "B"), pin(U2, "PB0/ADC8/OP1P1/CH2N")), net("/B_HIGH_CONTROL", pin(Q5, "BASE"), pin(R6, "A"), pin(R7, "B")), net("/B_LOW_GATE", pin(Q3, "LOW_SIDE_GATE"), pin(R5, "A"), pin(R23, "B")), net("/B_P_GATE", pin(Q3, "HIGH_SIDE_GATE"), pin(Q5, "COLLECTOR"), pin(R8, "A")), net("/C_HIGH_COMMAND", pin(R10, "B"), pin(U2, "PA8/CH1")), net("/C_LOW_COMMAND", pin(R9, "B"), pin(U2, "PA7/ADC7/OP2P1/CH1N")), net("/C_HIGH_CONTROL", pin(Q6, "BASE"), pin(R10, "A"), pin(R11, "B")), net("/C_LOW_GATE", pin(Q2, "LOW_SIDE_GATE"), pin(R9, "A"), pin(R24, "B")), net("/C_P_GATE", pin(Q2, "HIGH_SIDE_GATE"), pin(Q6, "COLLECTOR"), pin(R12, "A")), net("/PWM_INPUT", pin(J_CTRL, "PIN1"), pin(R27, "A")), net("/PWM_INPUT_MCU", pin(R27, "B"), pin(U2, "PA0/WKUP/ADC0")), net("/OPA_ZERO_CROSS_INTERRUPT", pin(U2, "PA2/ADC2/OP2O0"), pin(U2, "PA3/ADC3/OP1O0"), pin(U2, "PA4/ADC4/OP2O1")), net("/PHASE_A", pin(J_MOTOR, "PIN1"), pin(Q1, "HIGH_SIDE_DRAIN"), pin(Q1, "LOW_SIDE_DRAIN"), pin(R13, "B")), net("/PHASE_B", pin(J_MOTOR, "PIN2"), pin(Q3, "HIGH_SIDE_DRAIN"), pin(Q3, "LOW_SIDE_DRAIN"), pin(R16, "B")), net("/PHASE_C", pin(J_MOTOR, "PIN3"), pin(Q2, "HIGH_SIDE_DRAIN"), pin(Q2, "LOW_SIDE_DRAIN"), pin(R19, "B")), net("/SWD_CLOCK", pin(TP_PROG, "PIN1"), pin(U2, "PA14/SWC/PA11/UDM")), net("/SWD_DATA", pin(TP_PROG, "PIN2"), pin(U2, "PA13/SWD/PA12/UDP")), net("/SWD_VREF", pin(D1, "A"), pin(TP_PROG, "PIN4")), net( "GND", pin(J_BATT, "PIN2"), pin(C1, "NEG"), pin(C2, "NEG"), pin(C3, "NEG"), pin(C4, "NEG"), pin(C6, "NEG"), pin(Q1, "LOW_SIDE_SOURCE"), pin(Q2, "LOW_SIDE_SOURCE"), pin(Q3, "LOW_SIDE_SOURCE"), pin(Q4, "EMITTER"), pin(Q5, "EMITTER"), pin(Q6, "EMITTER"), pin(R3, "A"), pin(R7, "A"), pin(R11, "A"), pin(R14, "A"), pin(R17, "A"), pin(R20, "A"), pin(R22, "A"), pin(R23, "A"), pin(R24, "A"), pin(R26, "A"), pin(C5, "NEG"), pin(TP_PROG, "PIN3"), pin(U1, "GND"), pin(U1, "THERMAL_PAD"), pin(U2, "GND"), ), net("+3V3", pin(C1, "POS"), pin(C2, "POS"), pin(D1, "K"), pin(U1, "OUT"), pin(U2, "VDD")), net("unconnected-(U2-PA6{slash}ADC6{slash}OP1N1{slash}BKI-Pad20)", pin(U2, "PA6/ADC6/OP1N1/BKI")), ], }) const outputPath = path.resolve(__dirname, "generated", " const main = () => { mkdirSync(path.dirname(outputPath), { recursive: true }) writeFileSync(outputPath, exportKiCadNetlist(tinybeeEscChannel), "utf8") process.stdout.write(`${outputPath}\n`) } if (import.meta.main) { main() } export { tinybeeEscChannel } export default tinybeeEscChannel

kache

25,459 Aufrufe • vor 6 Monaten

Heads up #Battlefield1 fans 😎 WW1 mobile shooter "Weltkrieg 1: Firestorm" @weltkrieg1fs is now recruting people for their upcoming April playtest on Android devices via Google Play. You can sing up here 👇 🔹️ Factions: United Kingdom vs German Empire. 🔹️ Map: Somme 🔹️ Game Mode: TDM (6v6) 🔹️ Units: Assault, Heavy, Medic and Sniper. 🔹️ Flamethrower and Grenadier. 🔹️ Battle Points System 🔹️ AI soldiers. Key features and future plans: 🔹️ No pay-to-win elements. 🔹️ There will be new playtests in May and June, including this summer beta. 🔹️ The beta is planned to launch first in Indonesia, the Philippines and Thailand — with more regions added over time. 🔹️ iOS testing will follow after the beta phase. 🔹️ It's being developed by a small team (3 people). 🔹️ Tanks (including the British Mark V and the German A7V), artillery (Morser M10), infantry battle...they're looking to add armored cars and planes in future updates - aircraft will appear as atmospheric elements only. 🔹️ Ultimate Conquest (10v10) includes tanks and artillery. 🔹️ Destruction System: You can knock down trees, break through barbed wire and clear various obstacles. According to devs, buildings are static and can’t be destroyed to keep performance stable across all devices. 🔹️ Controller support is planned for future updates. It will come after the beta. 🔹️ Players will be able to choose the game mode, but not the map — locations will be selected randomly. 🔹️ They’re planning a No HUD gameplay mode in future updates. 🔹️ Single-player modes and a full campaign are planned for stages after the beta. 🔹️ They're aiming for 60fps as the sweet spot for most players. 🔹️ The second multiplayer map Passchendaele "is all about chaos" — rain pouring down while fire still burns from recent shelling. The map also features gas effects which are currently used for visual atmosphere only - but gas will also impact gameplay in the future. 🔹️ Background music is on their radar.
0:36

Heads up #Battlefield1 fans 😎 WW1 mobile shooter "Weltkrieg 1: Firestorm" @weltkrieg1fs is now recruting people for their upcoming April playtest on Android devices via Google Play. You can sing up here 👇 🔹️ Factions: United Kingdom vs German Empire. 🔹️ Map: Somme 🔹️ Game Mode: TDM (6v6) 🔹️ Units: Assault, Heavy, Medic and Sniper. 🔹️ Flamethrower and Grenadier. 🔹️ Battle Points System 🔹️ AI soldiers. Key features and future plans: 🔹️ No pay-to-win elements. 🔹️ There will be new playtests in May and June, including this summer beta. 🔹️ The beta is planned to launch first in Indonesia, the Philippines and Thailand — with more regions added over time. 🔹️ iOS testing will follow after the beta phase. 🔹️ It's being developed by a small team (3 people). 🔹️ Tanks (including the British Mark V and the German A7V), artillery (Morser M10), infantry battle...they're looking to add armored cars and planes in future updates - aircraft will appear as atmospheric elements only. 🔹️ Ultimate Conquest (10v10) includes tanks and artillery. 🔹️ Destruction System: You can knock down trees, break through barbed wire and clear various obstacles. According to devs, buildings are static and can’t be destroyed to keep performance stable across all devices. 🔹️ Controller support is planned for future updates. It will come after the beta. 🔹️ Players will be able to choose the game mode, but not the map — locations will be selected randomly. 🔹️ They’re planning a No HUD gameplay mode in future updates. 🔹️ Single-player modes and a full campaign are planned for stages after the beta. 🔹️ They're aiming for 60fps as the sweet spot for most players. 🔹️ The second multiplayer map Passchendaele "is all about chaos" — rain pouring down while fire still burns from recent shelling. The map also features gas effects which are currently used for visual atmosphere only - but gas will also impact gameplay in the future. 🔹️ Background music is on their radar.

Battlefield Bulletin

14,461 Aufrufe • vor 1 Jahr

#SterliteTech #STL #Q1FY27 #OpticalFibre New video: I went through Sterlite Technologies' Q1 FY27 numbers end to end — and this is one of the more interesting prints I've covered this quarter. The headline: revenue of Rs 1,910 Cr, EBITDA margin of 20.8% — the highest in nearly 20 quarters — after two brutal years (FY24-FY25) of losses through a global telecom-capex down-cycle. Management didn't just deliver, they raised guidance live on the call: full-year EBITDA margin guidance went from 20% to 23%, and Data-Centre + Enterprise revenue mix guidance went from 30% to 50% — a target Q1 alone already printed 39% against. Behind that is a genuinely structural shift, not just a good quarter. STL signed a $1.11 billion multi-year Product Award Letter from a hyperscaler spanning FY27-FY29, on top of the balance sheet completely flipping — net debt of Rs 1,128 Cr as recently as Q4 FY26 is now net cash of Rs 483 Cr after a Rs 1,500 Cr QIP, with a CRISIL outlook upgrade and an ICRA upgrade to AA following. Order book stands at Rs 18,618 Cr, up 2.4x QoQ — and management said something worth sitting with: they're now "picking and choosing" orders based on capacity, not chasing demand. That's a different company than it was a year ago. I also cover what management didn't say. A confirmed US$101.25 million verdict against a US subsidiary in an ongoing litigation wasn't mentioned once on the call — by management or any of the ten analysts on the line. The company explicitly won't guide revenue in rupee terms, only margin and mix, which matters because the revenue number driving most valuation models (including mine) is an independent estimate, not something management has put their own credibility behind. And gross margins stayed flat despite an improving product mix — management pointed to Germanium, Helium and Polyethylene cost pressure, and gave the same non-specific answer to four different analysts asking about it. Full breakdown, numbers, and both sides of the case in the video. Disclaimer: Not investment advice. Independent research, not SEBI-registered. Please DYOR.
19:54

#SterliteTech #STL #Q1FY27 #OpticalFibre New video: I went through Sterlite Technologies' Q1 FY27 numbers end to end — and this is one of the more interesting prints I've covered this quarter. The headline: revenue of Rs 1,910 Cr, EBITDA margin of 20.8% — the highest in nearly 20 quarters — after two brutal years (FY24-FY25) of losses through a global telecom-capex down-cycle. Management didn't just deliver, they raised guidance live on the call: full-year EBITDA margin guidance went from 20% to 23%, and Data-Centre + Enterprise revenue mix guidance went from 30% to 50% — a target Q1 alone already printed 39% against. Behind that is a genuinely structural shift, not just a good quarter. STL signed a $1.11 billion multi-year Product Award Letter from a hyperscaler spanning FY27-FY29, on top of the balance sheet completely flipping — net debt of Rs 1,128 Cr as recently as Q4 FY26 is now net cash of Rs 483 Cr after a Rs 1,500 Cr QIP, with a CRISIL outlook upgrade and an ICRA upgrade to AA following. Order book stands at Rs 18,618 Cr, up 2.4x QoQ — and management said something worth sitting with: they're now "picking and choosing" orders based on capacity, not chasing demand. That's a different company than it was a year ago. I also cover what management didn't say. A confirmed US$101.25 million verdict against a US subsidiary in an ongoing litigation wasn't mentioned once on the call — by management or any of the ten analysts on the line. The company explicitly won't guide revenue in rupee terms, only margin and mix, which matters because the revenue number driving most valuation models (including mine) is an independent estimate, not something management has put their own credibility behind. And gross margins stayed flat despite an improving product mix — management pointed to Germanium, Helium and Polyethylene cost pressure, and gave the same non-specific answer to four different analysts asking about it. Full breakdown, numbers, and both sides of the case in the video. Disclaimer: Not investment advice. Independent research, not SEBI-registered. Please DYOR.

Avishkar Nagrath

15,412 Aufrufe • vor 1 Monat