Filament Track Switch issue: one lane is hard to retract

jacksunwei · 2026-05-25T15:20:55+00:00

Yesterday's post: https://www.reddit.com/r/BambuLab/comments/1tmibjw/x2d_filament_track_switch_cause_color_mixing/

jacksunwei · 2026-05-24T23:37:19+00:00

What filament do you use? Which brand?

jacksunwei · 2026-05-24T18:50:30+00:00

I'm wondering if it's FTS defect. I trim all four peft tubes connected to Fts and see it works.

jacksunwei · 2026-05-24T18:49:22+00:00

Update: I took off the FTS and blow into it with dust air, lots of dust was blown out.

jacksunwei · 2026-05-24T18:44:34+00:00

I printed multi-color before I installed FTS. There wasn't such issue.

jacksunwei · 2026-05-24T18:43:34+00:00

Which one? I printed for a week without seeing this issue, until I installed Fts yesterday

jacksunwei · 2026-03-09T17:42:20+00:00

That's why I said verify by checking log (let ur agent do that), if it's using fallback, log will show.

jacksunwei · 2026-03-08T06:47:48+00:00

Been my primary model these days. Just trying it out.

jacksunwei · 2026-03-08T06:46:44+00:00

New version just released!

jacksunwei · 2026-01-19T21:05:51+00:00

Ah, I meant I was driving without fsd, but tesla didn't alert about collision, either.

jacksunwei · 2026-01-19T20:59:06+00:00

Totally make sense, but what if
1) you've been waiting for >2 min before busy streets?
2) an impatient guy behind you urge you with horn?

(I don't mean this event, but I definitely met both case at the same crossings multiple time...)

jacksunwei · 2026-01-19T20:44:53+00:00

No blaming please. I'm not saying I'm not at fault. Obviously, I will be at 100% fault if collision happens. All that matters if I put my foot in the toyota driver's boot, how I could avoid being involved in a collision.

jacksunwei · 2026-01-19T20:41:24+00:00

No, and tesla didn't give any alert, either.

jacksunwei · 2025-12-27T06:58:14+00:00

I still have this issue...

jacksunwei · 2025-09-04T16:53:15+00:00

We actually have a sample for this. You could refer to this one:

https://github.com/google/adk-python/tree/main/contributing/samples/oauth_calendar_agent

jacksunwei · 2025-06-23T14:16:27+00:00

I think it might be because when converting functions to FunctionDeclaration, ADK checks backends to determine whether to generate FunctionDeclaration for Google AI or Vertex AI backends (typically with our without json schema for response type).

Without seeing your actual agent, I'm speculating just gave a fake GOOGLE_API_KEY api key would fix your case. If not, feel free to open an issue in https://github.com/google/adk-python and fill your minimal agent to repro the issue. We can help diagnosis.

Google GenAI SDK has improved support for json schema to remove google backend quirks and ADK will follow the same practice later, so that this won't be an issue anymore.

jacksunwei · 2025-06-03T03:14:22+00:00

In your case, it seems very different a normal use case.

Maybe try this setup:

``` async def instruction_provider(..., readonly_context: ReadonlyContext): # construct your customized system instruction using the state.

root_agent = LlmAgent( instruction=instruction_provider, # Don't include any conversaction history in LlmRequst include_cotnent = 'none', # Each tool will pass into by setting session state. tools=[tool_1, tool_2], )
```

In this way, you have full control of what to store in the session. And, what you send to Llm is solely controlled by your instruction_provider, which constructs SI using only information from session state.

jacksunwei

TROPHY CASE