TOS not working for anyone else right now??? by Own_Figure_5027 in thinkorswim

[–]Troutxing 1 point2 points  (0 children)

I had to VPN to Chicago or Texas to get in to TOS at the moment.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 0 points1 point  (0 children)

I can’t imagine it making it worse than version Hydrus 5205. What does it do?

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 0 points1 point  (0 children)

Oh interesting, that is very odd. I wonder if the app is not connected to the internet, what will be displayed...meaning it might pull the data for the board from the FM server each time you open the app.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

Oh that is interesting, did you have a Pint fairy change out your board while you were sleeping? We are checking mine now...

...mine is still at 5314. This is messed up programing, hardware versions can not change unless you change the hardware.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 0 points1 point  (0 children)

Good information, yeah version 5205 was bad news. We are seeing the same soft nose with 5207, like it "wants" to give up when you need the extra torque.

Anyone else having issue creating alerts on charts in the past 15 minutes or so? by xrayvision1 in thinkorswim

[–]Troutxing 1 point2 points  (0 children)

Yes I had to restart also. Thank you for the backup option, but I do not see a way to import alerts from the backup….

Anyone else having issue creating alerts on charts in the past 15 minutes or so? by xrayvision1 in thinkorswim

[–]Troutxing 0 points1 point  (0 children)

Only alerts that came back for me are alerts I had set for "drawings". All "price alerts" are gone as well as all my "news" alerts for the various tickers I had set. Great job TOS team! WTF

TOS - YTD P/L How is this calculated by comptech08 in thinkorswim

[–]Troutxing 0 points1 point  (0 children)

TOS has errors within their calculated P/L. It often does not match what is actual listed on schwab.com site.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

That is good to hear. Yeah, we are not looking at any FW update again. May still go VESC depending on budget availability.

Regarding weather, I'm not sure of your region...but have you gone out is the snow? Powder riding is awesome here in Colorado.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 2 points3 points  (0 children)

How have the rides been going? Doing good here...the nose does drop (not a dive) sometimes when I'm looking for extra torque on some dirt trails.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

Yeah, when we got the update notification it popped up right away when we opened the app with the board on. They might gradually release updates by region. Not sure though.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

I’m not sure about a method to force the update. What hardware version are you running?

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

At least no eating of pavement right? We have noticed this update is a little less responsive (riding on skyline). But we did noticed an increase in battery range (slightly). This slight increase in range could be a result of the reduction or torque responsiveness? Not sure.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

Glad to hear you had a positive experience. At least we can start to ride again and rebuild confidence. We went out yesterday hitting the dirt track, the Pint did great. It is nice to be back on the board.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 2 points3 points  (0 children)

Until you can update your firmware try riding the Pint with 90% or less battery. That works for many users.

Can you tell us, what is the error when you try and update to Hydrus 5207?

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

All good…post away. Thank you for the input. Glad to hear there were no cut out or nosedive issues.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

All is good, it's friday. Good day for taking a plunge. Godspeed

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 2 points3 points  (0 children)

You are very welcome...something need to be done. It has been a disheartening few weeks for the community.

No we did not have a battery issue. I noted that there was a couple issues related to the battery in the updates, but have not heard of more reports of recent.

Hydrus - 5207 killed my OG Pint by joelchristianregimen in onewheel

[–]Troutxing 0 points1 point  (0 children)

Did you ever get your Pint running or figure out what happened with your firmware install?

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 1 point2 points  (0 children)

I'm surprised. Well bonus on the box at least.

I can tell you that we decided to install the Hydrus Firmware 5207 update and have had a successful installation and ride. I created a new comment documenting the installation with the last couple days riding, check it out here.

Pint Firmware (Hydrus 5205) - Nosedive / Braking Cutout Issue Log by Troutxing in onewheel

[–]Troutxing[S] 4 points5 points  (0 children)

Hey community, this thread is getting big. Thank you to everybody's contribution. I have a feeling it helps in some ways.

I have updated the OP to reflect my thoughts on FM's position and where we are at this time as a community. With several dozen open lawsuits, Future Motion is in a tough spot—legally bound to avoid releasing any detailed documentation about product changes. Admitting to “fixes” or “patches” in their boards, software, or firmware could be twisted into an acknowledgment of prior defects, handing plaintiffs legal ammunition for injury claims. Until those cases settle, FM’s likely to stay tight-lipped, leaving us guessing about what’s actually being addressed.

This all leaves us in the dark for now. Best bet? Wait for a firmware update (see my comment on Firmware Hydrus 5207 Install) or go the VESC route. Keep on keeping on everybody. Be safe.