Technical Update: DM02 (500W) Firmware Optimization

[Atak_Snajpera]

Please allow me to downgrade my firmware to older version. I would like to verify that my problem with cadence sensor is or not related to new firmware. Unfortunately your programmers intentionally decided to block any firmware downgrades.

 

[to7motor@SZ]

Instead of going to such great lengths to limit the DM02, why not just provide the 500w core in a DM01 housing? This would allow a higher power with plenty of heat management and with the larger housing, you have room for increasing the efficiency.

Or ideally create a housing that is midway between the dm01 and dm02. this way the q-factor is as close to that of the dm02 - which is almost perfect.

If you think about it, most people will use the DM01/750 to 1000w for mountain climbing (as well as road). If the DM01 to ground clearance is good enough for mountain bikers than a DM01 chassis hosting a 500w for regular road use is perfectly fine.

For many of us, the focus is on power (not for speed but to lessen load on body especially when going on uphill roads) and reliability.

Dear customer,

Thanks for following up. You’ve raised some very practical points, especially regarding the ground clearance and the idea of "over-building" the 500W unit.

To be direct, putting the 500W core in the DM01 housing would indeed make it a "tank" in terms of heat management. You’re right; it would be virtually indestructible under road use.

But here is why we took the path of optimizing RPM and Firmware instead of just using a larger housing:

The Efficiency Myth: A larger housing doesn't actually increase the internal efficiency of the motor core, it only helps dissipate the heat that's already been lost. The real efficiency gain comes from the electromagnetic design and the gear ratio. By lowering the RPM, we keep the motor in its peak efficiency zone (74.3%) during those steep climbs you mentioned. This prevents the heat from being generated in the first place, rather than just trying to cool it down later with a bigger shell.

Q-Factor & Biomechanics: If a motor is too wide, the biomechanics of the rider's knees are compromised, regardless of how cool the motor runs.

We hear you on wanting to "lessen the load on the body." That’s precisely why we re-calibrated it for torque. It gives you that "uphill push" without needing a bulky chassis that adds unnecessary weight to a road-oriented build.

We really appreciate this kind of back-and-forth. It’s exactly what helps us refine our next generation of motor platforms.

Toseven Support Team

 

[to7motor@SZ]

Please allow me to downgrade my firmware to older version. I would like to verify that my problem with cadence sensor is or not related to new firmware. Unfortunately your programmers intentionally decided to block any firmware downgrades.

Dear Mr. Snajpera,

Thank you for your message.

We would like to clarify that our team has not intentionally blocked firmware downgrades. The users always welcome to reinstall a previous version if needed.

But please note that each firmware update is released to improve motor performance and the overall riding experience. We generally recommend keeping the latest version installed to benefit from these optimizations.

If you'd prefer to go back to the older firmware to test the cadence sensor, that's completely fine. Should you require any assistance from us, please feel free to reach out.

Toseven Support Team

 

[Atak_Snajpera]

Dear Mr. Snajpera,

Thank you for your message.

We would like to clarify that our team has not intentionally blocked firmware downgrades. The users always welcome to reinstall a previous version if needed.

But please note that each firmware update is released to improve motor performance and the overall riding experience. We generally recommend keeping the latest version installed to benefit from these optimizations.

If you'd prefer to go back to the older firmware to test the cadence sensor, that's completely fine. Should you require any assistance from us, please feel free to reach out.

Toseven Support Team

Are you sure about that? https://static.wikitide.net/tosevenwiki/5/5f/Picture171.png

 

[Mateuszbytom]

Hi, I have a question: will there ever be an update to the toseven dm01 1000w T24 v1 display? Specifically, I'm referring to the introduction of a 250w legal mode via key combinations? Does this mainly apply to roadside checks by the police?

 

[Atak_Snajpera]

Things next firmware should fix:

1) There is noticeable lag before motor activates. This gets progressively worse with higher FILTER value (TorqueSensor -> Filter option). For more natural and smoother riding experience I've increased default filter value from 1 to 5. Unfortunately this has negative consequences like mentioned above. Motor should start giving assist immediately when force on pedal is detected. Currently with Filter = 5 delay is around 2 seconds. Way too long!

2) Lag on display when it comes to POWER WATT value. Instead of showing real current WATT value we have that artificial smoothing. Motor is already off but value on display is still counting down instead of showing immediately real value (zero in this case). Before changing gear I like to verify that power is less than 100W. With Toseven's T154 display this is not very useful method because it takes many seconds before real value shows up on display. I didn't have that issue on my CYC STEALTH. The lag was no more than 0.5s. On toseven lag is around 8s! Again. Way too high!

3) Last line of pixels on T154 displays is not correctly refreshed

Here is video demonstrating above issues

Here is video showing how power values should change without that extra 8 second delay

 

[Serpent]

Dear ToSeven, i've purchased a DM02 48V 500W some months ago, i was glad about power and feeling.
I've tried some configurations but the major issue was alwais the same, floating voltage on torque sensor.
As the motor gets hot, the resting voltage for the torque sensor rises as well, so instead of 0.6 - 0.7V at rest, you may see anything up to 1.2V or more and the motor keeps pushing also without pedaling (may be dangerous in some conditions) or happends it keeps pushing with 0 load and slow spinning of pedals.

I read the latest firmware of Febrary '26 should solve this issue and i tried it. The update was succesfully installed but the new firmware doesn't do absolutly nothing about that issue, the problem is still the same.

Is there some feature to activate? Must be updated also the display (T24)?

Please, solve this issue, that's the only one issue it has...

It's frustrating switching on and off every temperature changing.

Thanks for reading.

 

[Atak_Snajpera]

Dear ToSeven, i've purchased a DM02 48V 500W some months ago, i was glad about power and feeling.
I've tried some configurations but the major issue was alwais the same, floating voltage on torque sensor.
As the motor gets hot, the resting voltage for the torque sensor rises as well, so instead of 0.6 - 0.7V at rest, you may see anything up to 1.2V or more and the motor keeps pushing also without pedaling (may be dangerous in some conditions) or happends it keeps pushing with 0 load and slow spinning of pedals.

I read the latest firmware of Febrary '26 should solve this issue and i tried it. The update was succesfully installed but the new firmware doesn't do absolutly nothing about that issue, the problem is still the same.

Is there some feature to activate? Must be updated also the display (T24)?

Please, solve this issue, that's the only one issue it has...

It's frustrating switching on and off every temperature changing.

Thanks for reading.

They are working on it

Reviewing torque signal processing and filtering
Evaluating offset stability under temperature changes
Optimizing control logic for better low-torque recognition
They are also looking at reducing the drag after exceeding the speed cutoff as well as the lag before the motor reengages when it drops back below it.

 

[Atak_Snajpera]

Here are more suggestions for T154 display to make it perfect

1) Restore last used assist level and information at the bottom screen after power on



2) For energy consumption use more suitable Wh (Watt-hour) instead of Ah. Amp-hour is not very useful for tracking energy consumption in system where voltage is constantly changing (due to voltage sag and normal discharging).




My eggrider display could also show Wh for energy consumption


3) Bar on left which represents electric power should be automatically scaled according to real power limit set in ECO,CITY,SPORT profile. Currently it is fixed at 1000W.
Bar on right should only represent HUMAN POWER (Torque * Cadence). Currently it is a weird combination of human power + electric power. Not very useful.



4) Ambient temperature is shifted by ~15C versus real temperature



5) Bug Motor RPM does not show 0 RPM when motor switches off

 

[to7motor@SZ]

Here are more suggestions for T154 display to make it perfect

1) Restore last used assist level and information at the bottom screen after power on

View attachment 386709

2) For energy consumption use more suitable Wh (Watt-hour) instead of Ah. Amp-hour is not very useful for tracking energy consumption in system where voltage is constantly changing (due to voltage sag and normal discharging).


View attachment 386710

My eggrider display could also show Wh for energy consumption
View attachment 386713

3) Bar on left which represents electric power should be automatically scaled according to real power limit set in ECO,CITY,SPORT profile. Currently it is fixed at 1000W.
Bar on right should only represent HUMAN POWER (Torque * Cadence). Currently it is a weird combination of human power + electric power. Not very useful.

View attachment 386711

4) Ambient temperature is shifted by ~15C versus real temperature

View attachment 386712

5) Bug Motor RPM does not show 0 RPM when motor switches off

Dear Customer,

Thanks for your detailed feedback. We really appreciate the time you put into this.

Here's what our factory can actually do, and what needs more work.

1) Restore the last used assist level after power-on

Makes sense. We can do this on the software side pretty easily (needs persistent storage). We're looking at making it an optional setting, not forced. We need to ensure it complies with regional safety standards (like EN15194) before rolling it out globally.

Because in some regions, starting at low assist is preferred for safety and compliance.

2) Use Wh instead of Ah for energy display

You're right, Wh is more accurate, especially under variable voltage.

So, doing this correctly requires stable, calibrated real-time sampling of voltage and current, plus reliable integration over time. Our take is simple: no data is better than wrong data. Until we can guarantee high-precision integration, we prefer to stick with reliable raw metrics. It's on the radar, but not a short-term change.

3) Power bar scaling and human power display

Two separate things:

Motor power bar scaling — Agreed.
A fixed scale (e.g. 1000W) is misleading when profiles have different limits. We're reviewing how to make the bar reflect actual output per mode.

Human power display — Tougher.
Real-time human power calculation depends on precise torque sensor calibration, cadence sync, and filtering. Done wrong, it's just misleading. Right now, our focus is on making assist behavior stable and predictable — not adding derived numbers that might be inaccurate.

4) Ambient temperature offset (~+15°C)

Thanks for bring this to our attention. That kind of deviation is not normal, does it stay constant after a cold start, or does it increase during long climbs? Knowing this will help us pinpoint if it's an NTC placement issue or an internal heat-soak problem. We're actively looking into it.

Our Summary

Current priorities:

System stability
Sensor accuracy
Predictable assist behavior

Some of your suggestions (assist memory, better power visualization) fit well, we're evaluating them. Others (Wh metrics, human power) need more validation before we commit.

Thanks again and if you have more real-world riding observations, we'd love to hear them at any time.

Toseven Support Team

 

[to7motor@SZ]

Hi, I have a question: will there ever be an update to the toseven dm01 1000w T24 v1 display? Specifically, I'm referring to the introduction of a 250w legal mode via key combinations? Does this mainly apply to roadside checks by the police?

Dear Customer,

Thanks for reaching out. Here's where our factory stands on this.

1. Regulatory side
We would like to clarify that our factory has to keep TOSEVEN products legal for sale in the EU, AU, and other markets, which means following EN15194. Regulators see a hidden power switch via a key combo as a compliance bypass. That puts both us and the rider at risk. So we can't do it.

2. If you require a 250W-legal motor
Please note that DM01 1000W is a high-performance system. For regions with strict 250W limits, we strongly recommend the DM02 series, it's designed, labeled, and certified for the 250W/EN15194 category.

Currently, we don't have a one-key stealth mode, but the T24 display and controller software do allow deep parameter customization. You can manually set current and speed limits to match local laws via the programming interface. That gives you a permanent compliant setup, not a temporary toggle.

We have to prioritize product legality and rider safety. Hope that makes sense.

Thanks for your time and understanding.

Toseven Support Team

 

[to7motor@SZ]

Dear ToSeven, i've purchased a DM02 48V 500W some months ago, i was glad about power and feeling.
I've tried some configurations but the major issue was alwais the same, floating voltage on torque sensor.
As the motor gets hot, the resting voltage for the torque sensor rises as well, so instead of 0.6 - 0.7V at rest, you may see anything up to 1.2V or more and the motor keeps pushing also without pedaling (may be dangerous in some conditions) or happends it keeps pushing with 0 load and slow spinning of pedals.

I read the latest firmware of Febrary '26 should solve this issue and i tried it. The update was succesfully installed but the new firmware doesn't do absolutly nothing about that issue, the problem is still the same.

Is there some feature to activate? Must be updated also the display (T24)?

Please, solve this issue, that's the only one issue it has...

It's frustrating switching on and off every temperature changing.

Thanks for reading.

Dear Customer,

Thanks for your detailed feedback. We truly appreciate the data you provided regarding the voltage rise (from 0.7V to 1.2V) under heat.

After a thorough review with our technical team, we have identified that the issue is primarily related to the analog signal processing circuit on the early-version controller, rather than the sensor itself or the firmware.

While the February firmware optimized the software filtering logic, it cannot physically counteract the hardware-level thermal drift when it exceeds a certain threshold (like the 1.2V you experienced).

Since the drift is hardware-related, we kindly recommend the following adjustment on your T24 display to ensure safety:

Increase the Start Torque/Voltage threshold: Please try setting the starting threshold slightly above your maximum drift voltage (e.g., set it to 1.3V).

We have since upgraded the controller hardware in our latest production batches with better thermal stability and interference shielding, which effectively eliminates this drift.

Please provide us with the QR, and we will do our best to support you.


Toseven Support Team

 

[Atak_Snajpera]

2) Use Wh instead of Ah for energy display

You're right, Wh is more accurate, especially under variable voltage.

So, doing this correctly requires stable, calibrated real-time sampling of voltage and current, plus reliable integration over time. Our take is simple: no data is better than wrong data. Until we can guarantee high-precision integration, we prefer to stick with reliable raw metrics. It's on the radar, but not a short-term change.

Your firmware is already able to show power in watt so adding Wh calculation is just a matter of adding time component.
It is a simple math.

All you need to add is sampling rate let's say every 1 second. Formula would look like this in pseudo code

repeat
     W = V * A; // Watts = Volts * Amps
     Wh = Wh + W * (1/3600); // 3600 seconds in 1 hour
     Sleep(1000); // wait for 1s
until Terminated;

Human power display — Tougher.
Real-time human power calculation depends on precise torque sensor calibration, cadence sync, and filtering. Done wrong, it's just misleading. Right now, our focus is on making assist behavior stable and predictable — not adding derived numbers that might be inaccurate.

I'm not asking about fancy human power value in watts! Just a simple graphic representation of human input (torque sensor voltage * cadence). Basically it should show how much effort is put in pedaling by human. Nothing more and nothing less.

Pseudo code

TorqueVoltageRange = TorqueVoltageMaxValue - TorqueVoltageMinValue; // for example 3.0V - 0.7V = 2.3V
TorqueCurrentVoltageNormalized = TorqueCurrentVoltage - TorqueVoltageMinValue; // for example 1.7V - 0.7V = 1.0V
NormalizedTorqueValue = TorqueCurrentVoltageNormalized / TorqueVoltageRange; // 1.0 / 2.3 = 0.43

NormalizedCadenceRPM = CurrentCadenceRPM / MaxCadenceRPM; // for example 90 rpm / 100 rpm

HumanInputNormalized = NormalizedTorqueValue * NormalizedCadenceRPM; // for example 0.43 * 0.9 = 0.39 (39% of max bar size)

Once you have that value (0.39) you can easily translate that to pixels for bar size. Easy peasy!

4) Ambient temperature offset (~+15°C)

Thanks for bring this to our attention. That kind of deviation is not normal, does it stay constant after a cold start, or does it increase during long climbs? Knowing this will help us pinpoint if it's an NTC placement issue or an internal heat-soak problem. We're actively looking into it.

After POWER ON temperature goes up and then stabilizes. After stabilization, error is at about +15C/+16C.
Keep in mind that I'm talking about temperature sensor in T154 DISPLAY. Temp sensor in controller itself is working correctly.

 

[to7motor@SZ]

Dear Customer,

We really appreciate the detailed feedback. Seriously impressive stuff.

Your firmware is already able to show power in watt so adding Wh calculation is just a matter of adding time component.
It is a simple math.

All you need to add is sampling rate let's say every 1 second. Formula would look like this in pseudo code

repeat
     W = V * A; // Watts = Volts * Amps
     Wh = Wh + W * (1/3600); // 3600 seconds in 1 hour
     Sleep(1000); // wait for 1s
until Terminated;

I'm not asking about fancy human power value in watts! Just a simple graphic representation of human input (torque sensor voltage * cadence). Basically it should show how much effort is put in pedaling by human. Nothing more and nothing less.

Pseudo code

TorqueVoltageRange = TorqueVoltageMaxValue - TorqueVoltageMinValue; // for example 3.0V - 0.7V = 2.3V
TorqueCurrentVoltageNormalized = TorqueCurrentVoltage - TorqueVoltageMinValue; // for example 1.7V - 0.7V = 1.0V
NormalizedTorqueValue = TorqueCurrentVoltageNormalized / TorqueVoltageRange; // 1.0 / 2.3 = 0.43

NormalizedCadenceRPM = CurrentCadenceRPM / MaxCadenceRPM; // for example 90 rpm / 100 rpm

HumanInputNormalized = NormalizedTorqueValue * NormalizedCadenceRPM; // for example 0.43 * 0.9 = 0.39 (39% of max bar size)

Once you have that value (0.39) you can easily translate that to pixels for bar size. Easy peasy!





After POWER ON temperature goes up and then stabilizes. After stabilization, error is at about +15C/+16C.
Keep in mind that I'm talking about temperature sensor in T154 DISPLAY. Temp sensor in controller itself is working correctly.

Dear Customer,

We really appreciate the detailed feedback. Seriously impressive stuff.

We looked at your logic with our technical team. Here's our response:

- On Wh calculation:
You're right, the math is easy. The real issue is data persistence; writing to flash too often kills it over time, but writing too rarely risks losing data on a sudden BMS cutoff.

But your feedback pushed us to prioritize a better caching algorithm. We are considering testing saving Wh on system-off signals or specific voltage drops now.

- On the human power graphic:
Your normalized torque * cadence idea is solid. Much smarter than showing a jumpy raw Watt value. We love the pixel-bar approach. We'll discuss the posibility to add this to the next major T154/T24 firmware update.

- On the temperature offset (+15°C):
Your video with the Sigma doesn't lie. It's heat-soak; the MCU and backlight heat get trapped inside the casing. Can't move the sensor on existing units, but we're working on a software compensation curve that subtracts the predicted internal heat based on warm-up rate after power-on.

Thanks for pushing us to be better. We are now integrating these logic tweaks into our development sprint. We plan to release an updated firmware build as soon as it clears basic safety stability tests, and we would value your help in beta-testing these new features.

Stay tuned, and we’ll reach out once the build is ready for your input.

Toseven Support Team

 

[Atak_Snajpera]

1) Hide Motor Temperature section. Toseven motors do not have temperature sensors in motor core so this section is only a source of confusion for new owners. Some customers may assume that their motor has a faulty temperature sensor.

2) Replace nonfunctional sections on MOTOR page with something more useful
a) Transfer ratio replace with efficiency (Wh/km). Consumed Wh divided by number of km done when motor was ON
b) Motor Constant replace with Average Input Power (Wh/Timer). Consumed Wh divided by time when motor was ON

 

[dobanion]

After a thorough review with our technical team, we have identified that the issue is primarily related to the analog signal processing circuit on the early-version controller, rather than the sensor itself or the firmware.

While the February firmware optimized the software filtering logic, it cannot physically counteract the hardware-level thermal drift when it exceeds a certain threshold (like the 1.2V you experienced).

Hello, I joined this forum just to respond to this specifically. I have had the ToSeven DM02 for a little over a year now. During this time, I have had horrible issues with the torque sensor. #1 problem, it drifts over time and eventually, the power level will drop suddenly, then within a few more minutes of riding, it will drop to zero. If I go to check the reading on the T24 display for the voltage from the torque sensor, it will read 0.0V at this point. Sometimes a long power off and cool off (10+ minutes) will result in a fix, and the torque sensor will read 0.7V after restart.

Second problem was surging of power when NOT pedaling, which is very distressing, and this will happen almost anytime that the torque sensor is functioning. I will note, I installed the latest firmware, which reduced the surging, but has done nothing for the power dropout problem.

I suspect my problem is as described, the "analog signal processing circuit" in the controller. Would a new controller with freshly installed firmware likely fix my problem? Currently, I gave up on torque sensing and am using the unit in PAS mode only.

 

[Serpent]

Dear Customer,

Thanks for your detailed feedback. We truly appreciate the data you provided regarding the voltage rise (from 0.7V to 1.2V) under heat.

After a thorough review with our technical team, we have identified that the issue is primarily related to the analog signal processing circuit on the early-version controller, rather than the sensor itself or the firmware.

While the February firmware optimized the software filtering logic, it cannot physically counteract the hardware-level thermal drift when it exceeds a certain threshold (like the 1.2V you experienced).

Since the drift is hardware-related, we kindly recommend the following adjustment on your T24 display to ensure safety:

Increase the Start Torque/Voltage threshold: Please try setting the starting threshold slightly above your maximum drift voltage (e.g., set it to 1.3V).

We have since upgraded the controller hardware in our latest production batches with better thermal stability and interference shielding, which effectively eliminates this drift.

Please provide us with the QR, and we will do our best to support you.


Toseven Support Team

Attached the qr code, is there a way to fix it? I can change every part needed if you send me. I think there's a 1 year warranty, right?

Today i had a trip where i tried a lot of setup... the new firmware is absolutely worse tha previous!!! Also setting the zero voltage to 1.5v the motor start pushing only spinning pedals with no torque appling and it displays to be at 0.9v... if the settings works it should not going to happen! There's no setting to have a working torque sensor.
With previous firmware that settings were working. Also the setting 'mode' where you can choose 'sensitive' and 'safe' seems not working, with previous firmware there was a big difference between this two settings.


with the latest firmware the torque sensor works very bad and it's impossible to manage it!
With next update give the possibility to DOWNGRADE because it seems the beta tester are we final users.

Thank you

 

[to7motor@SZ]

Attached the qr code, is there a way to fix it? I can change every part needed if you send me. I think there's a 1 year warranty, right?

Today i had a trip where i tried a lot of setup... the new firmware is absolutely worse tha previous!!! Also setting the zero voltage to 1.5v the motor start pushing only spinning pedals with no torque appling and it displays to be at 0.9v... if the settings works it should not going to happen! There's no setting to have a working torque sensor.
With previous firmware that settings were working. Also the setting 'mode' where you can choose 'sensitive' and 'safe' seems not working, with previous firmware there was a big difference between this two settings.


with the latest firmware the torque sensor works very bad and it's impossible to manage it!
With next update give the possibility to DOWNGRADE because it seems the beta tester are we final users.

Thank you

Dear Customer,

Thanks for the extra testing and the detailed feedback.

We completely understand your frustration with the latest firmware behavior. Our technical team is going for further investigation.

At this point, we don't want you to keep tweaking settings or power cycling the system just to work around the issue. We want to make this right for you.

Could you please confirm your shipping details below?

Full name
Full address
Phone number

Once confirmed, we'll get the replacement parts sent out to you. And please send us your purchase invoice.

Thanks for putting in the time and effort to test and document all of this.

Toseven Support Team

 

[to7motor@SZ]

After a thorough review with our technical team, we have identified that the issue is primarily related to the analog signal processing circuit on the early-version controller, rather than the sensor itself or the firmware.

While the February firmware optimized the software filtering logic, it cannot physically counteract the hardware-level thermal drift when it exceeds a certain threshold (like the 1.2V you experienced).

Hello, I joined this forum just to respond to this specifically. I have had the ToSeven DM02 for a little over a year now. During this time, I have had horrible issues with the torque sensor. #1 problem, it drifts over time and eventually, the power level will drop suddenly, then within a few more minutes of riding, it will drop to zero. If I go to check the reading on the T24 display for the voltage from the torque sensor, it will read 0.0V at this point. Sometimes a long power off and cool off (10+ minutes) will result in a fix, and the torque sensor will read 0.7V after restart.

Second problem was surging of power when NOT pedaling, which is very distressing, and this will happen almost anytime that the torque sensor is functioning. I will note, I installed the latest firmware, which reduced the surging, but has done nothing for the power dropout problem.

I suspect my problem is as described, the "analog signal processing circuit" in the controller. Would a new controller with freshly installed firmware likely fix my problem? Currently, I gave up on torque sensing and am using the unit in PAS mode only.

Dear Customer,

Thanks for your detailed feedback and sharing your long-term experience using the DM02.

We understand your concerns about torque signal loss and unexpected assist behavior. Based on your description, this seems to be related to the torque sensing system and its signal stability under thermal conditions.

To better support your issue, please provide the following information to: support@to7motor.com:

Motor QR code
Purchase date/order information

After receiving the above information, we will arrange the next steps for support.

Thanks again for your patience and detailed technical feedback.

Toseven Support Team

 

[to7motor@SZ]

1) Hide Motor Temperature section. Toseven motors do not have temperature sensors in motor core so this section is only a source of confusion for new owners. Some customers may assume that their motor has a faulty temperature sensor.

2) Replace nonfunctional sections on MOTOR page with something more useful
a) Transfer ratio replace with efficiency (Wh/km). Consumed Wh divided by number of km done when motor was ON
b) Motor Constant replace with Average Input Power (Wh/Timer). Consumed Wh divided by time when motor was ON

Dear Mr. Snajpera,

Great to hear from you again. We remember your previous insights, and we want to be completely transparent about where we stand.

Following your last feedback, our technical team looked into a UI overhaul. We actually agree with your suggestions, but the challenge is that our current display hardware uses a pre-compiled chip from the supplier, so we're limited in what we can change right now.

The "Efficiency" calculations you proposed would also require a synchronized update to the controller's communication protocol to ensure data accuracy. As a factory, our primary focus has to stay on long-term stability and safety for all users.

We are already sourcing a more flexible, next-generation display for our 2027 product line.

Thanks for your persistence and for staying with us.

Toseven Support Team

 

[Atak_Snajpera]

Please post change log for 2026-05-14 firmware

 

[Atak_Snajpera]

We are already sourcing a more flexible, next-generation display for our 2027 product line.

I hope new generation displays will have similar size to T154 display. Personally I'm not a big fan of those big T24 displays.

 

[Serpent]

Dear Customer,

Thanks for the extra testing and the detailed feedback.

We completely understand your frustration with the latest firmware behavior. Our technical team is going for further investigation.

At this point, we don't want you to keep tweaking settings or power cycling the system just to work around the issue. We want to make this right for you.

Could you please confirm your shipping details below?

Full name
Full address
Phone number

Once confirmed, we'll get the replacement parts sent out to you. And please send us your purchase invoice.

Thanks for putting in the time and effort to test and document all of this.

Toseven Support Team

Just sent you a private message. Thank you

 

[Serpent]

Here you can see the issue, with that firmware appeared also that noise seems a frog

 

[Atak_Snajpera]

Torque sensor is showing incorrect value 1.7V. It should be ~0.7V. Did you have the same issue before installing new firmware (2026-05-26)?