Quoted from PinMario:This time it works fine with a Raspberry Pi3 A+ but with a Pi0 (v1.3) i'm getting an error on the display PIC and the display's shows rubbish. The same Pi0 works fine in a LiSY35 with the same image.
It 'comes and goes' with the latest Linux kernel update, and I though I had solved it 
Need to check, what game did you used for testing, a System80B?
Quoted from bontango:It 'comes and goes' with the latest Linux kernel update, and I though I had solved it
Need to check, what game did you used for testing, a System80B?
Tested on a Bountyhunter (80B)
I tested with a Pi0 (v1.3) and a Pi0W (v1.1) no problems with the display on Bountyhunter for me
However I only started a game and let the attract mode run, when does the display error pops up?
What you can try is to set the I2C bus with Pi0 to the ame settings as for Pi3.
For that you need to edit config.txt in the root folder of the SD card. ( you may want to save a copy before editing)
Scroll to the bottom and delete the '[pi3]' line and the last 5 lines
Your last 5 lines in config.txt should now look like this:
# disable bluetooth on PI3 and PI3+, this will enable hardware driver for serial again
#set baudrate fix to 200KHz (bug in PI3?)
dtparam=i2c_arm=on,i2c_arm_baudrate=200000
dtoverlay=pi3-disable-bt
Quoted from bontango:I tested with a Pi0 (v1.3) and a Pi0W (v1.1) no problems with the display on Bountyhunter for me
However I only started a game and let the attract mode run, when does the display error pops up?
What you can try is to set the I2C bus with Pi0 to the ame settings as for Pi3.
For that you need to edit config.txt in the root folder of the SD card. ( you may want to save a copy before editing)
Scroll to the bottom and delete the '[pi3]' line and the last 5 lines
Your last 5 lines in config.txt should now look like this:
# disable bluetooth on PI3 and PI3+, this will enable hardware driver for serial again
#set baudrate fix to 200KHz (bug in PI3?)
dtparam=i2c_arm=on,i2c_arm_baudrate=200000
dtoverlay=pi3-disable-bt
Tried your suggestion, but now it is worse, the game won't even start, and the Pi and error LED's are blinking. The same image still works fine in a Pi3A.
Can I find an older image to use with the Pi0's, my older Lisy with Pi0 is running fine ( but it isn't not at home so i cannot copy the sd).
interisting, would like to know which version runs for you, do you know?
You can try version http://www.flipperkeller.de/lisy/LISY_Version_5_27-23.zip which is still available on the server
Edit: you may also try LISY Fast!
http://www.flipperkeller.de/lisy/LISY_Version_5_26-17_FAST.zip
It appears nothing is working, is there a way to diagnose this? PI3A+ always working, Pi0 always trouble with the display PIC in the LISY80. They work on the Lisy35 so ????
Going to buy a bunch of Pi3A+ boards. 
Hello, I was wondering if anyone knows the status for GOSOF or alternate Sys80 Sound solutions? I thought there was an older board as well at one point?
Just thinking of options, as I need to source a working sys80 sound board for a star race, and figured this route might be fun to try.
All of the GOSOF boards state jic not available, but I was wondering if there is any source for this, or what perhaps needs to be done and if there is anyway to help get something working here, testing, or development etc.
Thank you-
Quoted from PinMario:It appears nothing is working, is there a way to diagnose this? PI3A+ always working, Pi0 always trouble with the display PIC in the LISY80. They work on the Lisy35 so ????
Is the Error LED on?
Can you make a debug log?
As said, working for me .. so maybe something on your PCB?
I would double check all components around the I2C bus ( e.g. orientation and value of R4 )
Quoted from koji:I thought there was an older board as well at one point?
Yes, there was a board based on "Altera CycloneII EP2C5T144"
Looks like there will no FPGA available at JLC in the near future, so I will put this version back on lisy.dev this weekend
Quoted from PinMario:It appears nothing is working, is there a way to diagnose this? PI3A+ always working, Pi0 always trouble with the display PIC in the LISY80. They work on the Lisy35 so ????
Going to buy a bunch of Pi3A+ boards.
Do you have a Pi0 or Pi0 wireless? Also have you tried a different Pi0 in case the Pi0 is bad?
Quoted from bontango:Yes, there was a board based on "Altera CycloneII EP2C5T144"
Looks like there will no FPGA available at JLC in the near future, so I will put this version back on lisy.dev this weekend
Wow.. shame about the FPGA. But appreciate this thiank you.
Quoted from Robotworkshop:ust curious if you ever had an opportunity to take a look at the Bally tester code for the lamp section? Trying to find out if something is wrong on my build or if something needed to be tweaked in the firmware. When using the lamp test there were only a handful of lamps lit compared to using a real Bally or Stern MPU.
Also, besides a timed mode that there is now having a more manual mode where the forward and back single step and turn on/off a lamp or fire a solenoid. Some may find that a useful feature.
Just checked it in my Elektra and the lamptest worked for me.
I have created v0.4 of the Bally Tester, it may can help to identify where the problem is.
changes with v0.4:
The lamptest now do switch ON/OFF the lamps one by one rather then switching all lamps at the same time
the time for each lamp can be adusted from 0.1 to 0.9 seconds.
By selecting 0.0sec for the time it will go to 'manual mode', you can move the lamp by the 'Left' and 'Right' button
I have put the hex file on my dropbox
https://www.dropbox.com/s/5oksu7s1hnoe8q1/Bally_Tester_v04.hex?dl=0
Quoted from bontango:Just checked it in my Elektra and the lamptest worked for me.
I have created v0.4 of the Bally Tester, it may can help to identify where the problem is.
changes with v0.4:
The lamptest now do switch ON/OFF the lamps one by one rather then switching all lamps at the same time
the time for each lamp can be adusted from 0.1 to 0.9 seconds.
By selecting 0.0sec for the time it will go to 'manual mode', you can move the lamp by the 'Left' and 'Right' button
I have put the hex file on my dropbox
https://www.dropbox.com/s/5oksu7s1hnoe8q1/Bally_Tester_v04.hex?dl=0
The updates sound awesome! Will download it and give it a try. Thank you for enhancing the code. I think it will help a lot with troubleshooting.
bontango I recently sold my Mr and Mrs Pacman machine and gave the new owner a spare LISY-35 board with it. He thought the LISY-35 board is awesome and loved the web interface. He is going to try some custom programming. Just wanted to share that a lot of people appreciate what you do and sharing it with the world. Thanks for that!
Quoted from bontango:Is the Error LED on?
Can you make a debug log?
As said, working for me .. so maybe something on your PCB?
I would double check all components around the I2C bus ( e.g. orientation and value of R4 )
Yes, the error LED is on together with the LiSY80 LED.
If there is a fault on the PCB, how come the Pi3A+ is working perfect?
here is the debug text:
LISY basic DEBUG activ
[141.675366][0.000073] LISY DEBUG timer set
[141.676131][0.000765] Info: udp switch reader server for debug mode succesfully started
[141.676424][0.000293] LISY Hardware init start
[142.279018][0.602594] Software Display PIC has version 6.0
Info: LISY80 Hardware: Revision 320 ; HW ID is 2
[143.182887][0.903869] Software Coil PIC has version 5.2
[143.484226][0.301339] K3 Coil PIC returns 3
[145.002365][1.518139] Software Switch PIC has version 4.1
[145.002836][0.000471] LISY option: Freeplay
[145.003112][0.000276] LISY option: debug
LISY80: Throttle value is 1000
LISY80: we are emulating Game No:40 bountyh
info: trying to parse: /usr/local/share/xpinmame/xpinmamerc
info: trying to parse: /root/.xpinmame/xpinmamerc
info: trying to parse: /usr/local/share/xpinmame/xpinmame-vid_lisyrc
info: trying to parse: /root/.xpinmame/xpinmame-vid_lisyrc
info: trying to parse: /usr/local/share/xpinmame/rc/bountyhrc
info: trying to parse: /root/.xpinmame/rc/bountyhrc
LISY80_SIG_HANDLER: SIGUSR1 catched
This is LISY (Lisy80) by bontango, Version 527 39
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[145.489279][0.486167] ERROR: lisy80_write_byte_pic(Display Pic): repeat
for byte:86
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[149.497042][4.007763] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:86
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[150.499260][1.002218] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:86
[150.500023][0.000763] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:86
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
Info: checking for Coil min pulse time extension config
LISY80: opening /boot/lisy/lisy80/coils/040_lisy80_coils.csv failed Info: no coil opts file; or error occured, min pulse time extension disabled
loading rom 0: prom1.cpu
done
[151.745532][1.245509] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:85
mpudips return: 01000000 for switch:0
[151.794929][0.049397] LISY80: DIP switch settings according to /boot/lisy/lisy80/dips/default_lisy80_dips.csv
mpudips return: 11000001 for switch
[151.797025][0.002096] LISY80: DIP switch settings according to /boot/lisy/lisy80/dips/default_lisy80_dips.csv
mpudips return: 11011011 for switch:2
[151.797970][0.000945] LISY80: DIP switch settings according to /boot/lisy/lisy80/dips/default_lisy80_dips.csv
mpudips return: 11111111 for switch:3
[151.798222][0.000252] LISY80: DIP switch settings according to /boot/lisy/lisy80/dips/default_lisy80_dips.csv
[151.805632][0.007410] NVRAM delayed write initiated by GAME OVER Relay
[151.839757][0.034125] NVRAM delayed write initiated by GAME OVER Relay
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[151.864837][0.025080] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:87
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[155.922333][4.057496] NVRAM write DONE
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[156.532665][0.610332] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:87
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[156.558519][0.025854] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.193787][0.635268] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[157.194679][0.000892] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.218025][0.023346] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[157.218722][0.000697] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[157.219395][0.000673] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.241367][0.021972] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[157.242090][0.000723] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.264397][0.022307] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.287221][0.022824] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[157.287936][0.000715] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[157.288610][0.000674] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.334339][0.045729] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[157.335032][0.000693] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.358165][0.023133] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[157.358852][0.000687] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.418193][0.059341] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.441492][0.023299] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.509688][0.068196] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[157.555032][0.045344] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[157.555716][0.000684] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[159.873971][2.318255] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[159.910611][0.036640] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[159.956232][0.045621] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.001314][0.045082] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.023379][0.022065] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.048298][0.024919] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[160.048988][0.000690] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[160.049658][0.000670] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[160.050354][0.000696] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
[160.051039][0.000685] ERROR: lisy80_write_byte_pic(Display Pic): repeat:5 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.073421][0.022382] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.154567][0.081146] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.177454][0.022887] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[160.178153][0.000699] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.200195][0.022042] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[160.200901][0.000706] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[160.201575][0.000674] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[160.202236][0.000661] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.271881][0.069645] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[160.399285][0.127404] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[162.715232][2.315947] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[162.758883][0.043651] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[162.759364][0.000481] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[162.759830][0.000466] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[162.760296][0.000466] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[162.785198][0.024902] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[162.785679][0.000481] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[162.786146][0.000467] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[162.786613][0.000467] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
[162.787082][0.000469] ERROR: lisy80_write_byte_pic(Display Pic): repeat:5 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[162.844992][0.057910] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[162.845471][0.000479] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[162.911269][0.065798] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[162.911753][0.000484] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[162.912218][0.000465] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[162.958788][0.046570] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[163.003142][0.044354] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[163.003622][0.000480] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[163.129102][0.125480] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[163.129579][0.000477] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[163.153673][0.024094] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[163.154136][0.000463] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[163.154589][0.000453] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[165.424970][2.270381] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[165.425444][0.000474] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[165.425911][0.000467] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[165.426376][0.000465] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
[165.426838][0.000462] ERROR: lisy80_write_byte_pic(Display Pic): repeat:5 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[165.491631][0.064793] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[165.492106][0.000475] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[165.492568][0.000462] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[165.493035][0.000467] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
[165.493495][0.000460] ERROR: lisy80_write_byte_pic(Display Pic): repeat:5 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[165.494017][0.000522] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte
[165.494482][0.000465] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[165.577525][0.083043] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[165.578007][0.000482] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[165.665896][0.087889] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[165.666399][0.000503] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[165.666865][0.000466] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[165.667331][0.000466] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[165.712717][0.045386] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[165.713197][0.000480] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[165.713661][0.000464] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[165.795399][0.081738] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[165.795879][0.000480] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[165.907366][0.111487] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.176923][2.269557] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.220289][0.043366] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.281756][0.061467] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[168.282236][0.000480] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.325883][0.043647] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.348402][0.022519] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[168.348878][0.000476] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.392698][0.043820] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[168.393176][0.000478] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.442252][0.049076] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.476719][0.034467] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[168.477191][0.000472] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[168.477650][0.000459] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[168.478102][0.000452] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
[168.478550][0.000448] ERROR: lisy80_write_byte_pic(Display Pic): repeat:5 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.479053][0.000503] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.523090][0.044037] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[168.523570][0.000480] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[168.666240][0.142670] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[168.666716][0.000476] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[175.497819][6.831103] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:87
[175.498299][0.000480] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:87
[175.498767][0.000468] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:87
[175.499228][0.000461] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:87
[175.499689][0.000461] ERROR: lisy80_write_byte_pic(Display Pic): repeat:5 for byte:87
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[175.522489][0.022800] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:87
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[176.178920][0.656431] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[176.179396][0.000476] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
[176.179864][0.000468] ERROR: lisy80_write_byte_pic(Display Pic): repeat:3 for byte:4
[176.180325][0.000461] ERROR: lisy80_write_byte_pic(Display Pic): repeat:4 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[176.271558][0.091233] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[176.322679][0.051121] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[176.323159][0.000480] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[176.352192][0.029033] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[176.352670][0.000478] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[176.376943][0.024273] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
LISY80_SYS_ERROR:6 >Failed to write to the I2C bus display pic (121:Remote I/O error)
[176.421090][0.044147] ERROR: lisy80_write_byte_pic(Display Pic): repeat for byte:4
[176.421808][0.000718] ERROR: lisy80_write_byte_pic(Display Pic): repeat:2 for byte:4
From the log it is a problem with the I2C bus
Quoted from PinMario:If there is a fault on the PCB, how come the Pi3A+ is working perfect?
The PI3 may have another I2C bus termination, did you check R4?
As discussed due to unavailibility of FPGA chips at JLCPCB GOSOF80 'DIP' version is back!
https://lisy.dev/gosof.html
I need to work on the software ( backporting from Gosof ) and will add also System1 in the next version.
Quoted from bontango:From the log it is a problem with the I2C bus
The PI3 may have another I2C bus termination, did you check R4?
The PI3 may have another I2C bus termination, did you check R4?
Yes, it"s a RP 5 pins and 3k3, but in your pfd of the board assembly it says it's a SIL 5-4 3K3, the ones i use are 5X-1-332LF. This looks the same part to me.
Just as a test, I replaced the RP with 4 standard 3k3 resistors soldered with a common connection, still the same problem. 
Update: after changing some settings in the config.txt file, I got the Pi 0 working 
Mainly commenting parts I don't think I need and added 'i2c_arm_baudrate=200000' , don't know what did the trick, but I leave that to the pro's 
Here's my current config:
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
# uncomment for composite PAL
#sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on,i2c_arm_baudrate=200000
#dtparam=i2s=on
#dtparam=spi=on
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
#dtparam=audio=on
# enable serial console
enable_uart=1
# Disable rainbow image at boot
disable_splash=1
# use mmap option (for mono output)
dtoverlay=i2s-mmap
# and load the driver for YOUR soundcard
# by uncommenting the driver
# LISY use hifiberry by default
#
# this is for the Waveshare wm8960soundcard
# dtoverlay=wm8960-soundcard
# this is for the justboom soundcard
# dtoverlay=justboom-dac
# for hifiberry and compatible ones ( e.g Speaker PHAT )load this one
#dtoverlay=hifiberry-dac
# Set the bootloader delay to 0 seconds. The default is 1s if not specified.
boot_delay=0
#Gadget driver , PI-Zero(W) only! With PI3 Ethernet will not work anymore
#need to be disabled for APC
#[pi0]
#dtoverlay=dwc2
Quoted from PinMario:Update: after changing some settings in the config.txt file, I got the Pi 0 working
Mainly commenting parts I don't think I need and added 'i2c_arm_baudrate=200000'
Great that it is working now
I will keep the setting in the config file until other users reporting similar problems
I'm building up a Lisy1 board for Charlies Angels and if the slowest boat from China ever arrives with my resistor inline packs I can finish it.
For the roms I have come across two versions of the charlies.zip file;
One contains the files - 425.cpu, u4_ce.bin and u5_cf.bin
the other just has - 425.cpu
Which version do I place on the sd card? Thanks.
Quoted from SYS6:One contains the files - 425.cpu, u4_ce.bin and u5_cf.bin
that's the correct one
Quoted from bontango:Yes, there was a board based on "Altera CycloneII EP2C5T144"
Looks like there will no FPGA available at JLC in the near future, so I will put this version back on lisy.dev this weekend
Thank you for putting the old version back up.
For sound, I was wondering what the status is of this board as a replacement on a Star Race? I need to get some lisy1 anyway, so wasn't sure if it is ready for this as a drop-in, or if there are still issues to work out for early sys80?
Thank you
Quoted from bontango:Yes, there was a board based on "Altera CycloneII EP2C5T144"
Looks like there will no FPGA available at JLC in the near future, so I will put this version back on lisy.dev this weekend
It seems there is no .poc available for any of the boards mentioned here : https://lisy.dev/gosof.html
There is a speech.zip containing wav files only.
I assume we cannot use the DIP version of Gosof without the corresponding .poc file ?
I need to search my archive for the programs ( pof files ), almost all are OK, but I need to include some improvements made with the FPGA version.
All games listed ( except System1 which will be supported in next HW version) should be running with this board.
Only difference is that because of the smaller memory I can only include two games per pof file.
So the plan is to create five program versions ( Sys1, MA55, MA216, MA309 & MA490 ) and read the roms from SD.
Not sure when I will have time for Sys1 extension and these five program versions but if you order PCBs now and need a pof for Star Race
before this 'universal' program versions are ready, I can produce a 'Star race only' version for you.
Quoted from bontango:I need to search my archive for the programs ( pof files ), almost all are OK, but I need to include some improvements made with the FPGA version.
All games listed ( except System1 which will be supported in next HW version) should be running with this board.
Only difference is that because of the smaller memory I can only include two games per pof file.
So the plan is to create five program versions ( Sys1, MA55, MA216, MA309 & MA490 ) and read the roms from SD.
Not sure when I will have time for Sys1 extension and these five program versions but if you order PCBs now and need a pof for Star Race
before this 'universal' program versions are ready, I can produce a 'Star race only' version for you.
That would be wonderful. Very much appreciated thank you.
Due to unavailability of FPGA chips I'm thinking of to replace the current used FPGA board "EP2C5T144" with the "Waveshare CoreEP4CE6".
The Waveshare is a bit more expensive ( around 25..30€ compared to 15€ for the EP2" ) but has more memory, newer technology and
the quality of the EP4 boards seams to be better then the EP2 ones. ( many users reporting failed EP2 boards to me)
In addition the program code would be compatible to the current Gosof 'SMD version', so once
the FPGA chips are back in stock the code could be reused.
Feedback welcome, please let me know what you think!
pasted_image (resized).pngpasted_image (resized).pngQuoted from bontango:Note: I made a small mistake with the text on the backside of my Bally displays v1.3, it should be corrected now with v1.31
see pictures below, for 1.3 double check position of 'key', which need to be at position 14
thanks to Parnell for the hint[quoted image][quoted image]
My display boards came in! They look fantastic, happy with the quality from jlc.
I did however just realize the caps in ordered for C5 on the display are non polarized. And the silk screen shows a potential polarize direction. Will this be an issue?
Now it’s just waiting for the led segments to show up
These are the caps
https://www.mouser.com/ProductDetail/cornell-dubilier/107bpa016m/?qs=3tP%252bN51vMXcmVaYjLpsFVA%3D%3D&countrycode=US¤cycode=USD
Quoted from northvibe:I did however just realize the caps in ordered for C5 on the display are non polarized. And the silk screen shows a potential polarize direction. Will this be an issue?
YES, it will be an issue! In worst case they will explode ( no kidding ). You have to go with the polarized version!
Quoted from bontango:YES, it will be an issue! In worst case they will explode ( no kidding ). You have to go with the polarized version!
Ok, thank you. I’ll order different ones. Dang, should of read more before ordering
Quoted from bontango:I need to search my archive for the programs ( pof files ), almost all are OK, but I need to include some improvements made with the FPGA version.
All games listed ( except System1 which will be supported in next HW version) should be running with this board.
Only difference is that because of the smaller memory I can only include two games per pof file.
So the plan is to create five program versions ( Sys1, MA55, MA216, MA309 & MA490 ) and read the roms from SD.
Not sure when I will have time for Sys1 extension and these five program versions but if you order PCBs now and need a pof for Star Race
before this 'universal' program versions are ready, I can produce a 'Star race only' version for you.
Hmm.. sorry if you started this already.. I think I might hold off for a bit and continue trying to get the audio to be close enough with the single lisy80 and phat.
It seems close, I was wondering if there is any part in the guide which goes over sampling rates, or if everything is pretty much supported? I was curious as it seems like there is a very small delay on the sound when a switch is engaged etc. I could not find anything about this. I figure I can test with some of the panthera samples to see if it is just my samples.
Also, I was wondering if anyone had done much testing with the pinmame sound emulation option (using phat sound + test dip switch), this enables pinmame sound emulation to the game.. I found my sound here seems distorted? just curious if this works well for anyone at the moment.
Thank you-!
Hi @bontango,
I was wondering if you had any other ideas for my sound volume issue.
For internal volume jumpered, I read the resistance going from the small pot, to pin15 on the Pi header, and found that I could vary the resistance as expected when the pot is adjusted.. yet no matter what is adjusted the volume is way too loud.
This is the debug log from before:
This is LISY (Lisy80) by bontango, Version 527 01
Simple mixer control 'PCM',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 255
Front Left: 180 [71%]
Front Right: 180 [71%]
So it is as if it is not reading that value I presume. so I was wondering if there is any chance it is with my software configuration somewhere?
Thank you-
-Koji
Quoted from koji:So it is as if it is not reading that value I presume. so I was wondering if there is any chance it is with my software configuration somewhere?
Do the percentage in the log change when you change the position of the pot?
Quoted from bontango:Do the percentage in the log change when you change the position of the pot?
No, it seems to be stuck at 71%, regardless of having the pot all the way up or down.. I thought maybe my pot or resistor was off, but seeing it change on my meter at that pin15 to the Pi board made me think that perhaps something else is interfering with the ability to change the volume.
Thank you-
Do you have network access to your LISY? LISY_control or better direct ssh access would be good for troubleshooting ...
Quoted from bontango:thats the one I used before (out of stock at JLCPCB), in the new BOM I'm using this one:
https://lcsc.com/product-detail/Variable-Resistors_BOURNS-3314J-1-203E_C55069.html/?href=jlc-SMT
they will work both
Just got these, soldered it on, and the display works great! Hecccck yeah! 
Hi,
Really I'm interested by this topic.
Indeed, I got GTBs and Ballys from end of 70's to mid 80's with obso to manage. Not talking about the famous SC01, sounds cards may be a prob to repair the time passing by, not talking about CPUs. I got a look on the LISY site and I'm sure this is a real great thing. But I'm only a nerd and this is not easy not having a step by step manual to assemble, connect and configure.
Of course you would tell me, everything is in, and I'm sure you are right saying it... But you have to be wise and well connected to guess how to do it properly.
Remember I'm a nerd. Of course I have already translated a lot of documents on repairing/restoring/maintening (in French for Clay's and Pinwiki) to help my Pin community but I'm not an electronician.
I'm sure the Lisy initiative is a solution for everybody. On the other hand, it's a very long time I turned to DIY do do things (Masonry, tiling, plumbery, electricity and so on... And for my bobbies, PC maintenance, soldering, woodworking...). So I'm convinced this is the real way to do things.
I'm not talking german, so flippermarked is not for me but I can easily manage english. I have already exchanged with some smart people in France wishing to go LISY and I would like to go for and be part of it.
Please let me know if I can be of any help, but a guide for dummy for me would be a must. Maybe more by MP or by email?
BR
Eric
Quoted from emsrph:Anyone have one 1.3 version of the 6 digit to sell? Thx.
Maybe shouldn’t limit myself to the latest hw version…it’s just a resistor change in the latest upgrade?
Quoted from bontango:Do you have network access to your LISY? LISY_control or better direct ssh access would be good for troubleshooting ...
Thank you, I have not tried remotely connecting, but I will do so, and am familiar with SSH.
Please let me know what sort of troubleshooting commands you might try?
Thank you-
Quoted from koji:Please let me know what sort of troubleshooting commands you might try?
There is a small program "poti_step" in /home/pi/lisy/src/lisy/testprogs
With that you can test the function of the pot on the bench.
JLC was out of stock on C5 for the gottlieb 7 digit displays - what voltage do I need to order for this so I can install it manually once I receive the boards?
Also, are the schematics available for the displays? I could have probably looked at those to figure this out too.
Thanks for letting me know
C5 is in the 5Volt section, so anything >= 5Volt and with the same case is fine.
I will change the BOM for C5 to this part #C99833 and add the schematics ASAP.
I’ve built a few of the LISY 35 boards and they seem to work really well. The only part that is giving me trouble is the optional phat sound add-on. Just thought it would be cool to experiment with that and try some alternative sounds.
For testing I was using LISY control. I have a phat daughter card installed with the sound section populated and the jumper near it set to int. I also have dip switches 2, 6, and 8 on. There is a sound bar plugged into the audio jack of the phat sound module. When I am in LISY control I can see it reads the value of the volume pot ok since I see it change if I move it and refresh the page.
Tried to have it play some text to speech but not getting any output.
Are there any additional jumpers to set on the LISY 35 board or do I need to manually edit some of the config files in order for that section to work?
This is what I get:
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0]
Subdevices: 0/1
Subdevice #0: subdevice #0
error: no sound opts file; sound init failed
info: sound init done
info: Volume set to 36 percent
When I try to use the txt to speech I get nothing. In order to get any sounds like this do I need to create a configuration file on the SD card? Are there some default sounds for each of the games or do all the sounds need to be added later?
Quoted from Robotworkshop:In order to get any sounds like this do I need to create a configuration file on the SD card? Are there some default sounds for each of the games or do all the sounds need to be added later?
Yes, a config file is needed. For some games I have added sounds provided by other users,
but for the majority of the games you need to add them yourself.
Take a look at chapter 13.5 of the user manual, should all be there
Thank you. I'll try to make a config file. I thought that was only needed for the actual game sounds and something else wrong when it didn't talk at startup or when I tried to enter text in the txt to speech part of LISY config.
In a future update it may help to add and extra button to just test the default hardware to make it play a test sound or test text string just to confirm the hardware is ok. I think it would be help since if that doesn't work that can be addressed first instead of not knowing if it is a hardware issue or a typo in the config file.
my led segment displays arrived! For some reason kiss is blowing f4 fuse, but I'll get the displays built and test!
Quoted from northvibe:my led segment displays arrived! For some reason kiss is blowing f4 fuse, but I'll get the displays built and test!
Holy moly, I had rebuilt the flippers and didn’t adjust the switch to open/close with the flipper… ok fixed.
Displays are in! I was building these at night and word of warning double check before you solder, I soldered the header pins on the wrong side and removing wirh a solder sucker was a bear, broke a few traces on one and had to ask Ralf for some help to figure out schematics. Jumped the 3 lines and it’s all up! These are great! Having jpc build most the parts on is awesome! The black silk screen is nice. Can’t say enough! Also being able to dim the leds and enable/disable dots on the 7segments
1730854F-7AFC-4A12-B29F-F047903678A8 (resized).jpeg81A2AD36-33EF-48C3-ACA5-C7B902713002 (resized).jpeg8BDABDE4-9936-4986-8AD2-BFC30E8B3FFA (resized).jpegD6967571-CC24-49A9-B28F-1B2833CD2D74 (resized).jpegWanna join the discussion? Please sign in to reply to this topic.
Great to see you're enjoying Pinside! Did you know Pinside is able to run without any 3rd-party banners or ads, thanks to the support from our visitors? Please consider a donation to Pinside and get anext to your username to show for it! Or better yet, subscribe to Pinside+!
This page was printed from https://pinside.com/pinball/forum/topic/diy-lisy-a-replacement-mpu-for-gottlieb-bally-amp-stern/page/12 and we tried optimising it for printing. Some page elements may have been deliberately hidden.
Scan the QR code on the left to jump to the URL this document was printed from.
Surrey, BC
Sydney
Stavanger
Marseille