Originally posted by karter16
View Post
Experienced a bit of tunnel vision with base16 thing yesterday, but now that I think about it, the behavior as a whole of this feature is not at all what I expected. This is meant to be implemented as a "X m/ft remaining until next turn" thing, so I would have expected the cluster to scale the data in the incoming command by 10 (or maybe even 100), to save on message length. Not entirely sure in what situation "turn left in 3m" would be useful...
Also, the fact that it does the weird base16 thing and maxes out at uint8 means that it only displays up to 165. Again, when would numbers that small be useful?
I did have to code the cluster with NCS to have it react to the commands, so maybe there's some scaling option I missed that I can use to my advantage. Ooor maybe there's some flags hidden in the upper bits. We'll see.
Originally posted by rtrules
View Post
Originally posted by rtrules
View Post
I do have a scan of the cabin air filter housing, but I did not recreate that piece in CAD. I used the scan as a reference to base the design of my modified filter housing on.
Here's the scan if you want to use it for anything: https://cad.onshape.com/documents/7e...fe3bf8e81c64d2
(link should take you directly to it, but if it doesn't, it's "E46 Cabin Air Filter Housing" inside the "References" folder)
Originally posted by George Hill
View Post
Originally posted by Keith_MN
View Post
Originally posted by oceansize
View Post



Leave a comment: