Thanks for your suggestions.
The screen is plugged on to the GPIO header and has a small HDMI connector for video, so I assume the video is through the HDMI and the touchscreen control is through the GPIO header.

If I manually replace the 'GPIO 25' entries for Vol+, Vol-, Random, Skip, Left, and Right in fruitbox.btn, fruitbox will start (no duplication error), but the touchscreen does not respond.

Interestingly, if I assign only one button to GPIO 25 in fruitbox.btn file, to avoid the duplication error, then reboot, that function will work when I touch the screen anywhere. It's like the touchscreen is working as one giant button.

Thanks for your suggestions.
The screen is plugged on to the GPIO header and has a small HDMI connector for video, so I assume the video is through the HDMI and the touchscreen control is through the GPIO header.

If I manually replace the 'GPIO 25' entries for Vol+, Vol-, Random, Skip, Left, and Right in fruitbox.btn, fruitbox will start (no duplication error), but the touchscreen does not respond.

Interestingly, if I assign only one button to GPIO 25 in fruitbox.btn file, to avoid the duplication error, then reboot, that function will work when I touch the screen anywhere. It's like the touchscreen is working as one giant button.

Thanks again
Colin

Hi Colin,

Have you by any chance tried using evtest to see what your touch screen is doing? I was having trouble getting mine set up until I found out that mine had two different underlying ELO devices. Once I started using the right one, things worked. I was in the same boat. Mine worked with the PI desktop but not Fruitbox until I took the time to investigate further with evtest.

it's obviously doing something, not sure what though. lol.
Could it be a driver issue? I used the one on the CD that came with the touchscreen, but the instructions pointed me to a url with a driver that had a different filename....
Anyway, thanks!

it's obviously doing something, not sure what though. lol.
Could it be a driver issue? I used the one on the CD that came with the touchscreen, but the instructions pointed me to a url with a driver that had a different filename....
Anyway, thanks!

Looks like it's passing the necessary information. Touch event, x and y coordinates. It was just a thought. You could try the other driver, but since it's working on the desktop that's probably not the issue.

One other question, are you running fruitbox using sudo? Sudo fruitbox ... ... I also had to do this to get my screen working...

Steve
I greatly appreciate the help you've offered. You've given me some confidence already and hopefully it isn't just a dumb mistake on my part, or something that I've missed reading in the forum.
Thanks again
Colin

I think only Mike can help here. It may be due to the order of device polling. If an action of a GPIO pin is detected first, is Touch no longer checked for this action? Unfortunately, I only have displays that give touch signals via USB.

I assume these are min and max x,y coordinates for the button touch areas, but when I run evtest the smallest values I can generate in the top left corner of my screen are around 150,400, and the bottom right comes in about 3800,3800. That being said, It appeared to me that if fruitbox was running the touchscreen with these button coordinates they would be all up in the upper left corner of the screen, so I poked around with my stylus in that corner, and was able to find all of the functions by poking various areas in that corner. So, it appears the touchscreen is working, but the min/max values for the button areas need to be configured to work with my screen.

Seems like progress to me

I will read up on remapping the min/max button x,y coordinates in the user guide.

I assume these are min and max x,y coordinates for the button touch areas, but when I run evtest the smallest values I can generate in the top left corner of my screen are around 150,400, and the bottom right comes in about 3800,3800. That being said, It appeared to me that if fruitbox was running the touchscreen with these button coordinates they would be all up in the upper left corner of the screen, so I poked around with my stylus in that corner, and was able to find all of the functions by poking various areas in that corner. So, it appears the touchscreen is working, but the min/max values for the button areas need to be configured to work with my screen.

Seems like progress to me

I will read up on remapping the min/max button x,y coordinates in the user guide.

Thanks everyone,
I will report my success or failure.
Colin

Hi Colin,

The [touch areas] define the rectangular regions for the buttons (top left x, top left y, width, height).

It seems that the touchscreen you are using has a higher resolution touch co-ordinate system than the display resolution. This is one of the scenarios Jurgen and I debugged a while ago, and fruitbox should support this no problem. Under normal conditions, you need to use the --calibrate-touch command line option in conjunction with --config-buttons option, and fruitbox will write the correct values of TouchMin and TouchMax values in the fruitbox.btn file. However, in your case touch is being confused with GPIO 25 so this won't work. You can however bypass the touch calibration by putting the following two lines in the fruitbox.btn file to see if it helps...

Regarding your initial problem (Touch registering as GPIO 25), maybe Jurgen was correct; fruitbox does indeed check for GPIO events before touch events so could be getting confused by your particular touchscreen. I can try swapping the detection around in the software and put a debug version of fruitbox on GitHub for you to try. Are you using Stretch or Jessie?

The buttons are now close to where they should be and all seem to work in the vicinty of their functions. 3800 was just a guess though, so I'll experiment with those values.

I am running Stretch btw

Hi Colin,

The [touch areas] define the rectangular regions for the buttons (top left x, top left y, width, height).

It seems that the touchscreen you are using has a higher resolution touch co-ordinate system than the display resolution. This is one of the scenarios Jurgen and I debugged a while ago, and fruitbox should support this no problem. Under normal conditions, you need to use the --calibrate-touch command line option in conjunction with --config-buttons option, and fruitbox will write the correct values of TouchMin and TouchMax values in the fruitbox.btn file. However, in your case touch is being confused with GPIO 25 so this won't work. You can however bypass the touch calibration by putting the following two lines in the fruitbox.btn file to see if it helps...
Code: Select all

TouchMin = 0 0
TouchMax = 3800 3800
Regarding your initial problem (Touch registering as GPIO 25), maybe Jurgen was correct; fruitbox does indeed check for GPIO events before touch events so could be getting confused by your particular touchscreen. I can try swapping the detection around in the software and put a debug version of fruitbox on GitHub for you to try. Are you using Stretch or Jessie?

Hey Mike.
Thank you for looking into this.
I created a new install to test the debug version, following the directions you provided.
I still get '* GPIO 25 *' messages when I touch the screen when running
sudo ./fruitbox-1.12-debug-colin-1 --config-buttons --calibrate-touch.

evtest also indicates min and max values through its report (looking at a previous post it appears to be min 0,0; max 4095, 4095).

Mike

Hi Mike,

just so we do not misunderstand. Min / Max 0 - 4095 are the limits of touch resolution. But I think, fruitbox needs the values ​​that are reported at a touch in the corners, so that this can be synchronized with the physical resolution of the display? On my display with deviating touch resolution in fruitbox.btn is min always greater 0 (500 for example) and max always much smaller than e.g. 4095.

Automatically run fruitbox on power up
--------------------------------------
To run fruitbox automatically on power up, add the following
lines to ~/.bashrc :
cd <directory where fruitbox is installed>
sudo ./fruitbox --cfg <your cfg file>

evtest also indicates min and max values through its report (looking at a previous post it appears to be min 0,0; max 4095, 4095).

Mike

Hi Mike, Jurgen.
I 'm running with your suggestions, with a manually created fruitbox.btn specifying TouchMin at 0 0 and TouchMax at 3950 4100. I experimented with different values for TouchMax and these values seemed to correspond with the button placement about the best. All buttons are now working, and I'm ready to install my Pi with this amazing program into my juke. Thank you so much you two, as well as Steve, for your hard work on this project and for your assistance and kindness to me.
Colin

evtest also indicates min and max values through its report (looking at a previous post it appears to be min 0,0; max 4095, 4095).

Mike

Hi Mike,

just so we do not misunderstand. Min / Max 0 - 4095 are the limits of touch resolution. But I think, fruitbox needs the values ​​that are reported at a touch in the corners, so that this can be synchronized with the physical resolution of the display? On my display with deviating touch resolution in fruitbox.btn is min always greater 0 (500 for example) and max always much smaller than e.g. 4095.

Cheers
Jürgen

ok, just so nobody gets confused:
In my last post, I exaggerated a bit as far as the offset was concerned.
My current display has a resolution of 1280 x 800.
Touch resolution is 0 0, 2047 2047.

Is it possible to create a button who can delete the file fruitbox.db ?

The idea would be to run Fruitbox and the action of one button 'DeleteDB' will delete the file before power off.

this is usefull pour those who use a USB memory stick and want modify their MP3 list.

Cheers.

JoggyBnoob.

Hi,

Not directly, but you could use one of the new FLAG buttons, to write a mesage to a file (using a [status] Output). Then you'll need an external script which reads the said file for the message and then deletes the database file.