RegisterSearchFAQMemberlistUsergroupsLog in
Reply to topic Page 6 of 6
Goto page Previous  1, 2, 3, 4, 5, 6
Raspberry Pi support - enables a hard-wired, dedicated dash
Author Message
Reply with quote
Post  
Which thing are you seeing exactly? Is it working properly with the official RPi display?


_________________
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 screen success 
I am building a display with a SunFounder 10.1" capacitive touch screen. On the initial install, the touch screen was not responsive.

I found Joe D's comments about the settings for this screen and made his changes for config.ini and am happy to report that the touch screen is now responding. Thanks to Joe D. for his info on this screen and you guys for this really nice option.

Now to get rid of the touch circle, and make sure the screen saver never kicks on and then to build a case.

Pete

View user's profile Send private message
Reply with quote
Post  
Awesome. Thanks for the update!


_________________
Brent Picasso
Founder, Autosport Labs
Facebook | Twitter
View user's profile Send private message Send e-mail
Reply with quote
Post RPI UPS FOLLOW-UP 
Just thought id follow up on my Rpi under voltage issues while cranking the starter. I purchased the UPS PICO 450 stack plus hat, which allows a 12v power feed and automatic switching to back up battery. I ordered it from MODMYPI overseas, and didn't know if you contact them in advance they can swap the stock 450mah battery for one of the larger ones (customs issue). so I got a 3cell series 18650 batt holder and three 3300mah e-cig batteries to work as the battery backup supply (ttl 9900mah). the PICO requires a little soldering, but not to terrible. after install it works very well. what's really nice is you can simply turn the batt master off and after 60seconds the PICO initiates a safe PI shutdown. then shuts itself off. when the car is running on 12v it will also charge the back up batteries. what I don't like is you cant see the status led's to tell if everything is functioning.

I also since found you can get the PICO in the US at http://www.sfo-takumi.com/shop/

View user's profile Send private message
Reply with quote
Post Re: RPI UPS FOLLOW-UP 
PS14 wrote:
Just thought id follow up on my Rpi under voltage issues while cranking the starter. I purchased the UPS PICO 450 stack plus hat, which allows a 12v power feed and automatic switching to back up battery. I ordered it from MODMYPI overseas, and didn't know if you contact them in advance they can swap the stock 450mah battery for one of the larger ones (customs issue). so I got a 3cell series 18650 batt holder and three 3300mah e-cig batteries to work as the battery backup supply (ttl 9900mah). the PICO requires a little soldering, but not to terrible. after install it works very well. what's really nice is you can simply turn the batt master off and after 60seconds the PICO initiates a safe PI shutdown. then shuts itself off. when the car is running on 12v it will also charge the back up batteries. what I don't like is you cant see the status led's to tell if everything is functioning.

I also since found you can get the PICO in the US at http://www.sfo-takumi.com/shop/


With this setup, is there a way to disable the 60 second safety shutdown?

View user's profile Send private message
Reply with quote
Post  
yes, from the manual:
On Battery Powering Running Time when cable power loses or not exist. After that time a File Safe Shut Down Procedure will be executed and System will be shut downed without restart. Battery power will be disconnected. System is in sleep mode (LPR) and RTC is running. If Raspberry Pi cable power returns again system will be start automatically. If during the sleep mode (LPR) the F button will be pressed for longer time than 2 seconds (with battery or cable powering) Raspberry Pi will re-start again. Value of 0xff (255) disable this timer, and system will be running on battery powering until battery discharge to 3.4V for LP battery and 2.8V fro LF Battery type. Factory default value is 70 seconds Each number stands for 1 minute of Battery Running. Default Value is 0, and the highest Value is 0xFE. If user will enter i.e. 2, the Battery Running time will be 60 seconds + 2 x 60 seconds = 180 seconds. After that time system will be shutdown. If user after that will press again F button system will restart and run for 180 seconds again and then shutdown. Read: Anytime, Return actual fssd_timeout value Write: 0x00 Ė 0xFF Any change on this register will cause immediate writing of the new value to the PIco EEPROM

https://drive.google.com/file/d/1GT3Q0WAXriDvFNevW2MRNGomZwrixBxI/view

View user's profile Send private message
Reply with quote
Post RaceCapture autostart on RPi? 
I am trying to get the auto start of RaceCapture to work, but to not restart automatically if I close it.
I did the recommended setting in rc.local of

Code:
 /opt/racecapture/boot_racecapture.sh pi

and it starts racecapture, but if I close racecapture another is started automatically.

I am not using the watchdog setting. Why it is doing this? Is there any way to prevent it?
What does the pi parameter do? I don't see that referenced in the script.

If I comment out the
Code:
if [[$WATCHDOG -ne 1 ]]; then
and fi lines in run_racecapture, racecapture does not auto restart so something about that test is not working properly.

Thanks
Pete



Last edited by ppressle on Mon Sep 17, 2018 2:35 am; edited 1 time in total
View user's profile Send private message
Reply with quote
Post  
Dont know why it does it, but you can type (while racecapture is running) "killall 9 run_racecapture.sh -w 1", then exit racecapture, and when you get the terminal the text should be entered so just press enter. you made need to exit racecapture twice (then just use the up arrow to see last line entered (the killall command) and press enter. that will stop the script untill the next reboot. i usually hashtag out the line in rc.local if i'm doing some pi software work. and remove it when i'm done updating or whatever. Dave

View user's profile Send private message
Reply with quote
Post RPi connectivity to mifi 
A quick note for RPi users, not RaceCapture specific, but which might be helpful.

The RPi connects to my Verizon mifi ONLY in 5 GHz. So if you set the mifi to use 5 GHz instead of the 2.4GHz you might have better luck.

Worked for me.
Pete

View user's profile Send private message
Reply with quote
Post Re: Inverting HID mouse input? 
mikesmith wrote:
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...


Finally got back to this; seems to be a Kivy bug. Adding ",invert_y=0' to the hidinput options fixes it. (Yes, that's a zero, not a 1).

View user's profile Send private message
Reply with quote
Post  
I tried this app this weekend - Iím using the B+ raspberry pi, genuine 7Ē raspberry pi screen, and have installed per instructions, etc the latest stable release. I have tried the beta too but same result..
I have the screen attached by the display ribbon cable, and the 4 header cables for 12v, gnd and the two other inputs

The problem Iím having is similar to on the first page of this thread - the app loads fine but is completely unresponsive to everything except the escape button on a USB keyboard, which only works once to get from the initial set up screen to the main menu.

The touch screen works perfectly when not using the RaceCapture app, so Iím a bit stuck - Iím not mega computer savvy but can follow instructions. Iíve rotated my screen, have WiFi set up, etc so everything is how Iíd want it, just need to get the touch screen working correctly

The resolution on page 1 seems to be to install the older version of the app (1.10.? ) but this seems an odd thing to do as others have presumably got this working?
If anyone has any pointers or things I can try Iíd appreciate it - Iíve tried 3 or 4 completely fresh installs using beta and stable versions but always the same issue..

Should also add I donít think I have a power issue - itís being run from a pair of 2A usb power ports in the house. I tried doing this a couple of ways but no difference so think power wise Iím fine

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

What Pi distribution are you currently running? We have a number of people reporting success with the current beta.

Once you know the touchscreen driver is loaded per the instructions provided by the RPi official display, you can launch the racecapture app directly, instead of the wrapper shell script, You can inspect the command line output of the app to see if it complains about a mouse driver.


_________________
Brent Picasso
Founder, Autosport Labs
Facebook | Twitter
View user's profile Send private message Send e-mail
Reply with quote
Post  
brentp wrote:
Hi,

What Pi distribution are you currently running? We have a number of people reporting success with the current beta.


Your latest as of right now - 1.13.1
Should I try 1.14.4 instead?

Quote:
Once you know the touchscreen driver is loaded per the instructions provided by the RPi official display, you can launch the racecapture app directly, instead of the wrapper shell script, You can inspect the command line output of the app to see if it complains about a mouse driver.


I donít understand much of that - when you say launch directly do you mean from typing /opt/racecapture/run_racecapture.sh
at the command line? Or by using the auto launch thing.. I tried the auto launch but it meant because it was unresponsive I had to basically unplug it to get out then I couldnít do anything because I was stuck in the auto launch mode and I couldnít exit the app once it started

How do I inspect the command line output? I canít escape the app once it starts - I can hit ESC on a usb keyboard to go from the setup wizard launch screen to the main menu but after that itís completely unresponsive to key presses or any touch.. isthere a way to log it and go back in after a power off to see whatís going on?

View user's profile Send private message
Display posts from previous:
Reply to topic Page 6 of 6
Goto page Previous  1, 2, 3, 4, 5, 6
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