Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added new static port information for TechnicLargeLinearMotor #197

Merged

Conversation

mennolodder
Copy link
Contributor

This is the last issue to fix #193

@tthiery
Copy link
Member

tthiery commented Jan 15, 2024

Hi @mennolodder

for this I need some time.

  • I need to see how my unpatched motors/hubs react and [ ] maybe even update my motor/hub.
  • The XLarge motors are basically twins to the Large ones so I expect the same behavior there.
  • I have to check whether the old hub has a software version different from yours, which would allow us to hold two different static port infos.

Give me a day or two

@tthiery
Copy link
Member

tthiery commented Feb 11, 2024

So I re-run discovery on my xlarge and linear motors. Unfortunately, both are still reporting as 0.0.0.1000. So the new (yours) and old (mine) output is not distinguishable.

@tthiery
Copy link
Member

tthiery commented Feb 11, 2024

So the change in your PR is compatible with the unpatched motor (which is good, then we can merge it without harm).

The hex-code contain two details

  • The self-description raw range is changed from -360 to +360 to -179 to +180 which reflects also the real values we get (so they fixed the description to the actual behavior).
  • The removed the "CALIB" mode ... which is probably a calibration mode during production or development of the motors (something like a final qualification test for the motors)

@tthiery
Copy link
Member

tthiery commented Feb 11, 2024

I was able to use the Technical Control+ App to trigger a firmware update on my technic hub. Which allowed me to add the XLarge motor as well.

@tthiery
Copy link
Member

tthiery commented Feb 11, 2024

Had to fix the Robot Inventor TechnicMediumAngularMotorGrey as well (tons of updates there). The sensors (distance and color) still worked. Unfortunately, this leaves TechnicLargeAngularMotorGrey hanging in the air (I do not have this one).

@rickjansen-dev I think you originally contributed this motor any chance you can update your firmware (e.g. via Technic Control+ app) and provide us updated hex-dumps and pretty prints?

@tthiery tthiery self-requested a review February 11, 2024 20:23
@tthiery tthiery added the bug Something isn't working label Feb 11, 2024
@tthiery tthiery added this to the v5.0 (breaking) milestone Feb 11, 2024
@tthiery tthiery added enhancement New feature or request area-device-motor and removed bug Something isn't working labels Feb 11, 2024
@tthiery
Copy link
Member

tthiery commented Feb 11, 2024

@mennolodder Thanks for your work and patience here. I was a bit under stress work-wise and unfortunately could not have a look earlier.

Unfortunately, the change was indeed a bit worse than expected. But I think both your fixes, the discovery disablement and this one will improve this product a lot. I would love to give @rickjansen-dev some days to respond. My goal is that at the end of the week to release v5.0.

@mennolodder
Copy link
Contributor Author

Sweet, no problem. Glad I could help

@tthiery tthiery merged commit d35a200 into sharpbrick:master Feb 28, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-device-motor enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

poweredup device list hangs
2 participants