fatal python error (pygame parachute) segmentation fault

[Applefamily]

I have two things I need help with
1) one is what the subject stated "fatal python error (pygame parachute) segmentation fault"
2) two is I'm experiencing some times when my call back is called it executed twice.

I'm new and a NOOB with python, I'm comfortable in VBA, and consider myself a great with Rockwell PLC's and Motion Control.(My back grown)

This project is a 10 meter and 40 meter dash timer and my first project since receiving my Pi. The operator will start the countdown and race the clock to the 40 meter line capturing the 10 meter time as well. At both intervals there is a laser pointer focused on a photo resister. This resister is connected to a Schmitt trigger Op amp then to GPIO pins. There are a few LED connected to GPIO as well just to give me some insight to where the program is.
With my python code I'm been struggling to not break some of the "rules of code" global tags to be my first crime so be gentle this is my first time.

With number one I think it might me because my main program and callback both use common sub def's. "draw_time()" could this be? should I research a mutex function in python? Is that what could be triggering the error and shutting down the program. You will see in may parts of the program I use try: This is because much of the development I have been using a windows pc because it easier for me to search the web for samples and walk through different tutorials. I then can test functions of the program. When testing this way I have no troubles this is why I think there is a possibility both threads are trying to use this sub and crashing.
What I'm trying to do is update the timer for current time and do a final update when the laser is tripped. Maybe I should redesign the screen with a running time and update the T1 and T2 clocks with what ever is in the T1 or T2 register each scan or if T1,T2 >0.

The other problem I have seen discussed too. I have not resolved this and am looking for some input here as well. Maybe there is a better way.

Your guidance is welcomed.

[Applefamily]

I have tested a few of my ideas with removing the "draw_time()" call in my callback and adding

Code: Select all

if T1>0:
draw_time(SCREEN,1,T1)

if T2>0:
draw_time(SCREEN,2,T2)

to my main program.

I also tested the suggestion from the other post on double callback exicutes by only having one callback for both inputs and filtering what channel triggered the callback.

No joy on either problem. Think I’m going to try and use a powered USB hub. Currently using a keyboard, wireless mouse, and thumb drive. In addition to the 3 LED outputs, two op-amps, and LED’s tied to the Op-amp outputs for feed back to what is the current state. All these devices draw power from the Pi.

[Applefamily]

I think the mutex is the fix. I'm still testing