You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Being pretty new to Pis and linux in general, and driving a 2013 Honda Fit which has bluetooth, but the bluetooth ONLY works for calls..... Crankshaft is VERY appealing
That being said, the screen I have was a nightmare to get working. For the most part it was plug and play, UI scaling went OK (Screen reports out 1080p when it isn't, but that was a really easy fix, just a config thing I set manually). Touch was even registering right away.... but wasn't calibrated. So a touch on the screen would click in some wild place of course
Screen is a KeiDei 3.5". It seems like a rebranded waveshare (however none of the "drivers" actually work). With where it is in my car, 7" would absolutely not work, 5" is pushing it. 3.5 was great, same size as the pi, mounted next to my gauge cluster
-Hooked up a mouse and keyboard to the Pi to navigate Crankshaft and do some basic trouble shooting
-Once I learned what PuTTY was, I tried the X-Server touch calibration thing. Installed just fine, but would not start running the code. Followed many step by step, just said it "Couldn't connect to X-Server"
-Eventually I found a single thread about this keidei screen, and with my luck, someone posted a calibration file they were using. However I had no clue how to get the Pi to actually read it
-Thankfully someone had a tutorial about a totally different screen, and showed how to navigate and type in the text values. I typed in what the other person had posted, and bam working screen
Now to repeat that, I'd rather not heh. That was too many hours
That being said, is there a reason there's no native tool in Crankshaft to write a calibration file?
It would be nice to just have a button in Crankshaft settings that takes you through the simple 9-point targets and makes a simple calibration layer. Hook up a mouse and navigate, or maybe use a simple single line command to start the process. Thoughts?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Being pretty new to Pis and linux in general, and driving a 2013 Honda Fit which has bluetooth, but the bluetooth ONLY works for calls..... Crankshaft is VERY appealing
That being said, the screen I have was a nightmare to get working. For the most part it was plug and play, UI scaling went OK (Screen reports out 1080p when it isn't, but that was a really easy fix, just a config thing I set manually). Touch was even registering right away.... but wasn't calibrated. So a touch on the screen would click in some wild place of course
Screen is a KeiDei 3.5". It seems like a rebranded waveshare (however none of the "drivers" actually work). With where it is in my car, 7" would absolutely not work, 5" is pushing it. 3.5 was great, same size as the pi, mounted next to my gauge cluster
-Hooked up a mouse and keyboard to the Pi to navigate Crankshaft and do some basic trouble shooting
-Once I learned what PuTTY was, I tried the X-Server touch calibration thing. Installed just fine, but would not start running the code. Followed many step by step, just said it "Couldn't connect to X-Server"
-Eventually I found a single thread about this keidei screen, and with my luck, someone posted a calibration file they were using. However I had no clue how to get the Pi to actually read it
-Thankfully someone had a tutorial about a totally different screen, and showed how to navigate and type in the text values. I typed in what the other person had posted, and bam working screen
Now to repeat that, I'd rather not heh. That was too many hours
That being said, is there a reason there's no native tool in Crankshaft to write a calibration file?
It would be nice to just have a button in Crankshaft settings that takes you through the simple 9-point targets and makes a simple calibration layer. Hook up a mouse and navigate, or maybe use a simple single line command to start the process. Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions