RegisterSearchFAQMemberlistUsergroupsLog in
Reply to topic Page 4 of 4
Goto page Previous  1, 2, 3, 4
Raspberry Pi support - enables a hard-wired, dedicated dash
Author Message
Reply with quote
Post  
psfp wrote:
mikesmith wrote:
psfp wrote:
It was really simple (after I figured it out, of course Laughing )

I just added a "cursor = 1" row in Kivy's config.ini file


In which section? I've tried all of the obvious places, but I don't see "cursor = 1" mentioned in any of the relevant Kivy documentation (did you mean show_cursor?)


In modules section:


(to access this file you must type sudo nano /home/pi/.kivy/config.ini in command line)


Thanks - since one logs in as 'pi' the 'sudo' prefix isn't required.

Sadly, as Brent notes, things fall over pretty quickly when clicking around. Hopefully it's a bit more solid with the keybindings (I'm aiming to use the GPIO keyboard emulator to get some hard buttons).

View user's profile Send private message
Reply with quote
Post PI3 Screen wont work without mouse plugged in 
need some help from you PI guys. I have a PI3 running stretch lite. ive installed the GPIO buttons according to THokes82 instructions. only difference i used pins 36-40. ive been working on it with the mouse and keyboard hooked up. works perfectly untill i unplug the mouse, then touchscreen fails to work,GPIO buttons work. plug mouse back in, reboot, GPIO buttons work fine, touchscreen works fine. so i would assume it is readdressing the /dev/events?

FYI, im not using the official screen.

it also now seems to take several seconds to connect to my MK2, is see a bunch of time outs in the log. but id like to address the mouse issue first. thanks dave

View user's profile Send private message
Reply with quote
Post  
I was able to figure out the /dev/events addressing problem. fix was changing the config.ini input to "device_%(name)s = probesysfs,provider=hidinput". thanks google!

I do have a question with the rc.local script. when I add the script for the automatic startup, works good (RPI boots into RCP in less than 20 seconds). but when I exit the RCP app to get back to the terminal, it just reloads the app after a few seconds. not enuff time to kill the app process. is this normal? I would think the start up script is only called on startup.

View user's profile Send private message
Reply with quote
Post  
PS14 wrote:
I was able to figure out the /dev/events addressing problem. fix was changing the config.ini input to "device_%(name)s = probesysfs,provider=hidinput". thanks google!

I do have a question with the rc.local script. when I add the script for the automatic startup, works good (RPI boots into RCP in less than 20 seconds). but when I exit the RCP app to get back to the terminal, it just reloads the app after a few seconds. not enuff time to kill the app process. is this normal? I would think the start up script is only called on startup.


I don't have my Pi handy, but check to see which run level executes rc.local. I think it should be started in the RC3 level, but not positive.

View user's profile Send private message
Reply with quote
Post  
mikesmith wrote:

Sadly, as Brent notes, things fall over pretty quickly when clicking around. Hopefully it's a bit more solid with the keybindings (I'm aiming to use the GPIO keyboard emulator to get some hard buttons).


Just to update - things are looking much better with the 1.12 build.

You can still make it very sad with keybindings (S or A from the main screen in particular), but I got a Pi 3 in the meantime and the snappy level is also much improved.

View user's profile Send private message
Reply with quote
Post  
Thanks for testing it! Glad the downloadable 1.12.0 package is working well for you.


_________________
Brent Picasso
Founder, Autosport Labs
Facebook | Twitter
View user's profile Send private message Send e-mail
Reply with quote
Post SunFounder 10.1" capacitive touch 
I've been playing around with the SunFounder 10.1" capacitive touch screen this weekend and am pleased to report I have it working with the RaceCapture app on the Pi. I ended up doing it similar to PS14's way with the Waveshare resistive touch.

I edited /opt/racecapture/run_racecapture.sh and commented out everything involved with "check for ar1100 resistive touch" and "check for ft5406 capacitive touch".

Edit /home/pi/.kivy/config.ini and add these lines from ft5406 config file to the top:

[input]
mouse = mouse
mtdev_%(name)s = probesysfs,provider=mtdev
hid_%(name)s = probesysfs,provider=hidinput
%(name)s = probesysfs,provider=hidinput

[modules]
cursor=1

Everything seems to be working as needed. Just figured I'd give more info for another working touch screen.

View user's profile Send private message
Reply with quote
Post No Data 
I got my PI3 running with the standard 7" screen this morning in about 45 minutes the benefit of 20+ years of Linux experience. However RC app doesn't seem to be getting any data - the setup shows it's connected to USB but when I swipe to the "Raw Channels" screen I get "Waiting on Data" and occasionally in the top right of he RC app I get "Searching for /dev/ttyACMO"

Anyone know what the issue may be?

View user's profile Send private message
Reply with quote
Post  
Hi,

What happens when you check dmesg and you plug RCP into USB? do you see any messages about /dev/ttyACM0 or similar?

If you do, try launching minicom, pointed to the device reported by dmesg. Are you able to see the console?

Also, What RCP hardware and firmware version are you running?


_________________
Brent Picasso
Founder, Autosport Labs
Facebook | Twitter
View user's profile Send private message Send e-mail
Reply with quote
Post  
Hi Brent, a got it to work, I didn't do anything however. After about 4 or 5 minutes it connected and was solid. Not sure why it takes so long for the Pi to read the Race Capture.

View user's profile Send private message
Reply with quote
Post Inverting HID mouse input? 
I've upgraded(?) to a Waveshare 10" cap-touch LCD which emulates a HID mouse. Everything seems to "just work" with the default Kivy config... except that the mouse Y direction is inverted.

I found out how to invert touchscreen X/Y axes, but so far have had no joy talking Kivy into inverting the mouse (and honestly, why should it? this should 'just work')

Any thoughts on a Linux or Kivy-level config that will let me flip the Y axis? It's a bit of a brain teaser but otherwise seems to work very well...

View user's profile Send private message
Display posts from previous:
Reply to topic Page 4 of 4
Goto page Previous  1, 2, 3, 4
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum