(Topic ID: 253917)

DIY: 'LISY', a replacement MPU for Gottlieb, Bally & Stern

By bontango

2 years ago


Topic Heartbeat

Topic Stats

  • 983 posts
  • 68 Pinsiders participating
  • Latest reply 2 hours ago by Robotworkshop
  • Topic is favorited by 83 Pinsiders

You

Linked Games

No games have been linked to this topic.

    Topic Gallery

    View topic image gallery

    Kissd.png
    IMG_6220 (resized).jpg
    pasted_image (resized).png
    PXL_20220420_191415167.MP (resized).jpg
    lisy80_debug.pdf (PDF preview)
    lisy80_debug.pdf (PDF preview)
    20220325_170554 (resized).jpg
    20220325_170624 (resized).jpg
    20220318_014224 (1) (resized).jpg
    2022-03-04 13.44.28 (resized).jpg
    20220227_013431 (resized).jpg
    20220225_105202 (resized).jpg
    20220225_102434 (resized).jpg
    lisy_kit (resized).jpg
    pasted_image (resized).png
    pasted_image (resized).png

    There are 983 posts in this topic. You are on page 14 of 20.
    #651 9 months ago

    bontango In my Black hole I am missing the first 2 numbers in display 1, 3 and the lower level bonus display.
    I have swapped around the displays and all numbers work in the other positions.
    I have tried swapping around the associated ICs on the board and gone over the soldering again.
    Cables look ok, wiggling connectors (repinned) doesn't change anything.
    I am using a Gottfa80 board that was tested in Genesis and worked there.
    Is this a software bug or should I be looking at something else ?

    #652 9 months ago
    Quoted from Zigzagzag:

    Is this a software bug or should I be looking at something else ?

    Should be something with your hardware, I'm using GottFA (v1.0) with my Panthera which has the same type of displays, working fine.
    Your faulty displays have digits D1 .. D6 in common which are not used for your 80B Genesis.
    Didi you check/replace IC16 (74HC138N) and IC19 (74HCT240N) and the connector J3 pin 1&2 ?

    #653 9 months ago
    Quoted from bontango:

    Should be something with your hardware, I'm using GottFA (v1.0) with my Panthera which has the same type of displays, working fine.
    Your faulty displays have digits D1 .. D6 in common which are not used for your 80B Genesis.
    Didi you check/replace IC16 (74HC138N) and IC19 (74HCT240N) and the connector J3 pin 1&2 ?

    I suspected as much. Yes, I swapped the ICs with their neighbours. I guess it might be the connection on the FPGA itself.

    Easiest will probably be just to place this board in Genesis and put that board in BH

    #654 9 months ago
    Quoted from Zigzagzag:

    I guess it might be the connection on the FPGA itself.

    I don't think so, looking to the schematics four FPGA IOs feeding the digit strobes, if one of them
    are faulty it would affect other digits too. Sure that the edge connector is OK?
    GottFA PCB (as well as LISY) are a bit skinny compared to the original

    #655 9 months ago
    Quoted from bontango:

    I don't think so, looking to the schematics four FPGA IOs feeding the digit strobes, if one of them
    are faulty it would affect other digits too. Sure that the edge connector is OK?
    GottFA PCB (as well as LISY) are a bit skinny compared to the original

    Never sure, of course ... problem is, BH is 4 hours away, so a quick check is difficult. All displays worked on the original board, though.

    I will try to investigate further.

    #656 9 months ago
    Quoted from KenLayton:

    Ever thought about doing a LISY Bally 6803 system board?

    No, it is not on my list. I had a short look and saw that it uses the same technique as the combo boards
    in games like 'Grand Slam'. As this board is still causing problems with LISY and BallyFA I did not investigate further.

    #657 9 months ago
    Quoted from bontango:

    No, it is not on my list. I had a short look and saw that it uses the same technique as the combo boards
    in games like 'Grand Slam'. As this board is still causing problems with LISY and BallyFA I did not investigate further.

    Isn’t the Grand Slam MPU just an -35 MPU but with a diode in place of a resistor? I’ve had to make that mod to use a -35 in Grand Slam and Goldball. If the same mod is done to LISY then it should work in those games.

    #658 9 months ago
    Quoted from Robotworkshop:

    Isn’t the Grand Slam MPU just an -35 MPU but with a diode in place of a resistor?

    Yep, thats the change for the hardware and LISY and BallyFA have this diode already as it works for all games with the diode present.
    So far so good ...
    The 'problem' is how the lamps are controlled. Bally did use a tricky control circuit to lower the number of Thyristors (cost cutting)
    Each Thyristor is used to control TWO different lamps instead of one. ( A and B phase )
    For that it feeds the lamps with positive and negative power and spend a diode for each lamp.
    The zerocross signal is then interpretet by software on the falling AND raising edge, generating two interrupts
    for phase A and phase B instead of only one Interrupt on the falling edge for the 'older' games.

    And I still have problem with these two interrupts implementing in LISY and BallyFA

    #659 9 months ago
    Quoted from bontango:

    And I still have problem with these two interrupts implementing in LISY and BallyFA

    What exactly is going wrong with the current implementation?

    I haven't looked at the game code, but I presume (guesstimate):
    6821 is programmed for normal falling edge trigger which happens on the rising phase A.
    Phase A crosses zero upwards and rises causing an interrupt to trigger.
    Interrupt is serviced then 6821 is changed to sense a rising edge trigger (falling phase A).
    Phase A falls and generates an interrupt trigger about 0.3ms *before* it has crossed zero.
    Interrupt is taken but flagged to service phase B about 0.6ms later when phase B has become active.
    0.6ms later phase B lamps are refreshed and 6821 is reprogrammed back to normal falling edge trigger for next rising phase A.

    Or am I totally off base?

    #660 9 months ago

    Top Tip: when installing your LED blocks in the LISY 80 displays, do not install them upside down.

    Then the center segment becomes the dot and vice versa.

    Whoops.

    (sorry no pic.... I already desoldered it and flipped it over to the proper direction).

    #661 9 months ago
    Quoted from Quench:

    Or am I totally off base?

    There is also a difference in the feeding of the zero cross detection

    Details here on 'pinballinfo'
    https://www.pinballinfo.com/community/threads/bally-zero-crossing-detector-circuit.17196/
    "On GOLD BALL Pin 15 on J4 is no longer fed by the +43VDC from the solenoid circuit, but instead uses one of the 10VAC lines from the Switched Illumination. This is a totally un-rectified AC voltage"
    I pasted the two zero cross signals from the thread below, first i the 'normal' signal, and the second the signal with the combo board.

    It may becoming a bit 'off topic' here, but I can start a seperate thread on this topic,
    and would be happy if you could help me there .. ?!

    pasted_image (resized).pngpasted_image (resized).png
    #662 9 months ago
    Quoted from bontango:

    "On GOLD BALL Pin 15 on J4 is no longer fed by the +43VDC from the solenoid circuit, but instead uses one of the 10VAC lines from the Switched Illumination. This is a totally un-rectified AC voltage"

    My presumption in this regard was based on the Zero Crossing being AC, but I forgot it was only 10 volts. It means the trigger times I mentioned (0.3ms and 0.6ms) are too short and in reality need to be longer because of the slower rise/fall in 10 volts wave.

    See below wave snapshot showing the traditional relationship of the Zero Crossing detector output going into the 6821 against the 43VDC solenoid voltage. You can see the Z.C detector only changes state while the ripple is positive - actually it never "crosses zero" volts on traditional systems using DC.
    When the Zero Crossing detector input is AC, it cannot detect and change state while the input is negative voltage. So this is the reason I presume you need to alternate the edge direction detection on the 6821 CB1 input and then wait some time after phase A falls and triggers near zero and then goes negative voltage (where phase B is now positive).
    The Zero Crossing pulse length in the oscilloscope snapshot below is approximately 0.6ms (but again it's based on the steep rise/fall of 43 volts, not 10 volts).
    The diagram below it hopefully explains my theory. Does it sound reasonable?

    IMG_0052c.jpg
    DC_Ripple1.png

    #663 9 months ago
    Quoted from Quench:

    Does it sound reasonable?

    It does, thx. I will make some tests with my logic analyzer and compare waveforms
    of the CB1 input between the 43V rectified and the 10V unrectified input.
    In a second step I will record what happens with the interrupt line on BallyFA.
    Let you know ...

    #664 9 months ago

    Uhoh - I let the magic smoke(s) out....

    History.... got machine (jacks to open) and one original display not working, and one p2/p4 digit locked on. Rottendog replacement mpu, Gulf pinball PS. Get the locked digits going and got a replacement display from a pinsider, which initially worked ok. Went to keep shopping and the new display craps out, figure it was just its time, etc. - disconnect and keep going. Then, all displays out, gulf pinball display section smoked, no schematics available, not paying $80 for another. It was blowing fuse F3 as well.

    Go for the LISY design and the new PS/displays - had to repin a couple of the display harness connectors, visible sparking on the input voltage pin on 2x displays, so repinned both of those. Working fine up until a couple days ago, turned it on and display is incorrect on the credit display and other displays are really dim/off. It had blown F3 again.

    Disconnected all displays and PS, tested input voltage for displays 60vac ok, hooked up PS, test voltages, all ok. (+5 is 4.9 where it was 5.1 when I first installed PS, but likely not important). Reconnected only credit display, still has bad info on display but lit. (power off between all connect/disconnect of course) - I did do the 10ohm mod for the displays on the PS when I built it (I ordered enough parts to build 10 boards, still have 4-5 to build up) Hooked up the p1 display and smoked what I think is the power regulator, and the 10 ohm current limited resistor blew as well, and F3 blew again as well.

    I know it's never the transformer.... but do you think it could be the transformer? It doesn't blow F3 without anything hooked up to it, didn't blow it without the displays connected, but did blow (see pictures) when I hooked up the display. There was a big spark at the connector similar to what I noticed when the connector needed to be repinned.

    I do have one spare display board that I can move the LED digits over to but I'd like to nail this down if I can before hand so I don't just blow them all up. I did turn up the brightness on all the displays as they were too dim - possibly the current just isn't enough to run all the displays so caused an undue load?

    Any other thoughts?

    20210812_101353 (resized).jpg20210812_101417 (resized).jpg20210812_101427 (resized).jpg
    #665 9 months ago

    Ralf, finally got around to building a 35 board. I get random numbers on the displays. When hooked up to the hotspot lisy thinks it’s pink panther even tho S2 is set to on on rest off (eight all)

    All Roms are on the Sd for Bally none for gottlieb

    #666 9 months ago
    Quoted from slochar:

    I did turn up the brightness on all the displays as they were too dim - possibly the current just isn't enough to run all the displays so caused an undue load?

    Any other thoughts?

    with the '10Ohm mod' the brightness should be fine, even with all displays connected.

    From your pictures ( and the damage) it looks like you have a shortage somewhere.
    I would doublecheck the wiring to the displays, you never know what people have done before ...

    #667 9 months ago
    Quoted from hockeymutt:

    Ralf, finally got around to building a 35 board. I get random numbers on the displays. When hooked up to the hotspot lisy thinks it’s pink panther even tho S2 is set to on on rest off (eight all)

    All Roms are on the Sd for Bally none for gottlieb

    You said 'Pink Panther', so I guess you are talking about a LISY80, not about a LISY35?
    What random numbers do you get? If you have an 'old' LISY80 HW Version ( pre 6.0 ) you need
    to program the display PIC with another Software version!

    Due to Copyright the Gottlieb roms are NOT included in my Image.

    For the 'misinterpreted' S2 dip switch I would double check orientation of the diodes and the resistor arrays.

    #668 9 months ago

    That’s the funny part this is a lisy35 board,

    Quoted from bontango:

    You said 'Pink Panther', so I guess you are talking about a LISY80, not about a LISY35?
    What random numbers do you get? If you have an 'old' LISY80 HW Version ( pre 6.0 ) you need
    to program the display PIC with another Software version!
    Due to Copyright the Gottlieb roms are NOT included in my Image.
    For the 'misinterpreted' S2 dip switch I would double check orientation of the diodes and the resistor arrays.

    5F893EF8-256A-4315-B2BE-7C42F482DD4B (resized).png
    #669 9 months ago
    Quoted from hockeymutt:

    That’s the funny part this is a lisy35 board,

    The LISY Image can be used with all LISY variants, there is a HW detection when LISY starts which ask the display PIC for a HW ID.
    By placing a LISY80 display PIC in a LISY35 PCB LISY will assume to be conected to a LISY80.
    So I guess you programmed your LISY35 display PIC with a LISY80 hex file.
    Best to program the display PIC again

    #670 9 months ago

    bontango On the GottFA80 I remember there being some information about some 80B-games not being compatible with the older versions of the board due to memory limitations.
    This information seems to have disappeared.
    Could you tell me which games were affected by this as I have 3 "old" boards I could put to use ?

    #671 9 months ago

    ups, you are right, that information got lost when I went to version 4.x
    I added it again to the 'old' docs on the bottom of the page
    https://lisy.dev/gottfa80.html
    thanks for letting me know

    Note: due to memory limitations v1.0 of GottFA80 is not compatible with the 'late' 80B games ( Hot Shots, Big House, Bad Girls, Bonebusters and Night Moves ).

    #672 9 months ago
    Quoted from bontango:

    ups, you are right, that information got lost when I went to version 4.x
    I added it again to the 'old' docs on the bottom of the page
    https://lisy.dev/gottfa80.html
    thanks for letting me know
    Note: due to memory limitations v1.0 of GottFA80 is not compatible with the 'late' 80B games ( Hot Shots, Big House, Bad Girls, Bonebusters and Night Moves ).

    Thanks ! That explains why my Night moves locks up on game start, I suppose

    #673 9 months ago

    FYI: new Atari replacement displays on lisy.dev, have a look here
    https://pinside.com/pinball/forum/topic/diy-atari-gen1-replacement-displays-on-lisydev

    #674 9 months ago
    Quoted from Quench:

    The Zero Crossing pulse length in the oscilloscope snapshot below is approximately 0.6ms (but again it's based on the steep rise/fall of 43 volts, not 10 volts).

    Finally I found some time to do the tracings with my logic analyzer on a BallyFA

    with the 43Volt input I see a pulse length of around 0,74ms (picture1), with 10V AC the pulse length is about 1,76ms (picture2)
    however I did not saw zero cross interrupts at the cpu, only the display refresh interrupts.
    a third trace (picture3) showed that there is ONE ZC interrupt (falling edge) followed by a change of the pia control register to
    change the interrupt to rising edge around 5ms after that.

    So my current theory is that the pia6821 module has a bug with rising edge interrupts, need to investigate further
    I keep you posted

    pasted_image (resized).pngpasted_image (resized).pngpasted_image (resized).png
    #675 8 months ago

    I think I solved it, maybe someone can test the new BallyFA version as I have no pin with a comboboard?
    http://www.flipperkeller.de/lisy/BallyFA_114.pof
    ( I have a tester here in Germany, but could be different in US because of 60Hz power frequncy)

    Background: The Interrupt had trouble with the display refresh interrupt in my VHDL cpu code.
    I had to 'shift' the display refresh a bit, now it looks much better.
    What I see now ist two interrupts, one at the rising edge and one at the falling edge, HOWEVER looks
    like Bally change the transition setting after each zero cross and not in between (what I would have expected)

    So the lamp refresh (with 50Hz power frequency) with the comboboard is every 20ms, where it is every 10ms with he 'normal' board?
    I wonder if lamps tend to more flickering with the comboboard ... ?

    In the picture you see the rising edge int at 'A' and the falling edge int at 'B'

    pasted_image (resized).png
    #676 8 months ago
    Quoted from bontango:

    I think I solved it

    Great to hear!

    Quoted from bontango:

    Background: The Interrupt had trouble with the display refresh interrupt in my VHDL cpu code.
    I had to 'shift' the display refresh a bit, now it looks much better.

    BTW, the display interrupt generator runs at:
    Around 430Hz on Bally 7 digit display games
    Around 320Hz on Bally 6 digit display games and Stern MPU-100 games
    Around 400Hz on Stern MPU-200 games

    I think you are running the display interrupt generator at 400Hz based on your diagrams? Because your approach will be more precise there is the opportunity that its interrupt could happen at the same time in sync with a 100Hz zero crossing. I think it would be safer to run the display interrupt generator a little higher speed say 410Hz to minimise this occurrence.

    Quoted from bontango:

    HOWEVER looks like Bally change the transition setting after each zero cross and not in between (what I would have expected)

    I had a look at the code:
    - Zero Crossing interrupt occurs
    - Alternate a RAM phase flag (actually it's just bit zero of a free running counter)
    - Perform a delay around 1.10ms
    - If RAM phase flag is set, service the phase ØA lamps, else service phase ØB lamps
    - Perform all other Zero Crossing system services
    - Alternate the edge detection on the 6821 Zero Crossing CB1 input
    - Exit the Zero Crossing interrupt service routine

    Quoted from bontango:

    with 10V AC the pulse length is about 1,76ms (picture2)

    Looks around 1.3ms to me. Doesn't this seem too short to you considering the AC wave is 50% duty? With 20ms cycle (50Hz) I would expect the Zero Crossing Detector pulse to be around 12ms.
    It doesn't look like you are getting Zero Crossing interrupts occurring every transition, only every second transition which doesn't seem right like Zero Crossing is serviced at 50Hz, not 100Hz and the phases are serviced at 25Hz. This is likely happening because that Zero Crossing Detector pulse is too short considering the 1.10ms delay in the zero crossing service routine causing the edge detection not being reprogrammed in time for the next transition - see below.

    BallyFA_ZeroCrossing.png

    #677 8 months ago

    Thanks for the help got that sorted now having issues were I’m getting no lamps, and solenoids not working cross detector is always lit

    #678 8 months ago
    Quoted from hockeymutt:

    now having issues were I’m getting no lamps, and solenoids not working cross detector is always lit

    did you also reprogram the other PICs? They may have also the wrong code

    #679 8 months ago
    Quoted from Quench:

    BTW, the display interrupt generator runs at:
    Around 430Hz on Bally 7 digit display games
    Around 320Hz on Bally 6 digit display games and Stern MPU-100 games
    Around 400Hz on Stern MPU-200 games

    I think you are running the display interrupt generator at 400Hz based on your diagrams? Because your approach will be more precise there is the opportunity that its interrupt could happen at the same time in sync with a 100Hz zero crossing. I think it would be safer to run the display interrupt generator a little higher speed say 410Hz to minimise this occurrence.

    Thanks for the hint, I was not aware of different display interrupt timings. And yes, my internal generator runs at 400Hz.
    I had problems before when the display/zero cross interrupts occured at the same time but now I do 'restart/resync' the display
    timer with every zero cross interrupt to adapt to the power frequency which is not as exact as the internal timer.

    I commented my trace below, for me the logic should be OK, as at point:
    (1) the int does occur because the sense is set to falling edge
    (2) the int does occur because the CB1 interrupt is disabled
    (3) the int does occur because the sense is set to falling edge
    ...
    what do you think?

    pasted_image (resized).png
    #680 8 months ago
    Quoted from bontango:

    what do you think?

    Can you explain how you're generating the zero crossing detector signal?
    Is it controlled by the power signal coming from the rectifier board to the MPU board at J4 pin 15?
    Or is it a timer implemented in your hardware?

    An AC signal going into MPU J4 pin 15 will produce a zero crossing detector signal with a cycle time of 20ms (50Hz), but your snapshot shows the cycle time is 10ms.

    #681 8 months ago
    Quoted from bontango:

    I had problems before when the display/zero cross interrupts occured at the same time

    This occurs on factory MPU boards too that the interrupts will occur at the same time every now and then.

    #682 8 months ago
    Quoted from Quench:

    Can you explain how you're generating the zero crossing detector signal?
    Is it controlled by the power signal coming from the rectifier board to the MPU board at J4 pin 15?
    Or is it a timer implemented in your hardware?

    An AC signal going into MPU J4 pin 15 will produce a zero crossing detector signal with a cycle time of 20ms (50Hz), but your snapshot shows the cycle time is 10ms.

    I'm using exact the same circuit which is used on the Bally MPU, feeding an IO on my FPGA, where it goes to CB1 of U10 on the Bally MPU.
    But you are right, I HAD AN ERROR in my testcircuit on the bench, see picture below with a 12Volt AC signal on J4/Pin15
    Cycle time is now 20ms and the zero cross signal is MUCH longer (around 11ms) showing an interrupt on the rising AND on the falling edge.
    So this is finally the waveform I had expected .. see picture below

    HOWEVER: In case of the 'non comboboard' version the input on J4/Pin15 is a full rectified AC Signal, so there we have a cycle time of 10ms, correct?

    Does that mean that the lamp refresh with the comboboard is slower, and if this is the case, why do the lamps not flickering with the comboboard?

    Quoted from Quench:

    This occurs on factory MPU boards too that the interrupts will occur at the same time every now and then.

    Yes, but during my tests I noticed that the VDHL module I'm using for the 6800 emulation (cpu68.vhd) has problems with nested interrupts. So for my hardware emulation I needed to make sure that the Zero Cross & Display interrupts do not occur at the same time
    pasted_image (resized).png

    #683 8 months ago
    Quoted from bontango:

    So this is finally the waveform I had expected

    And that's exactly what I've been expected too! Well done.

    Quoted from bontango:

    HOWEVER: In case of the 'non comboboard' version the input on J4/Pin15 is a full rectified AC Signal, so there we have a cycle time of 10ms, correct?

    You mean full rectified DC signal? (not AC). If yes, then the cycle time is 10ms.

    Quoted from bontango:

    Does that mean that the lamp refresh with the comboboard is slower, and if this is the case, why do the lamps not flickering with the comboboard?

    Yes, games with the dual phase lamp setup will be refreshed at half speed on each phase. The AC voltage is higher to compensate for this and in terms of incandescent lamps that have long persistence, the higher voltage makes them stay on longer so the slower rate of refresh will not be noticeable or cause flicker.

    LEDs complicate matters since they have no persistence. 50Hz refresh will be enough to not produce flicker, the problem as we know is that with traditional single phase DC games the lamp refresh occurs early in the DC phase when there is not enough current draw from LEDs for the lamp driver boards SCRs to latch. The solution has been to add resistors across the LED circuits to increase the current draw that helps the SCRs latch. This still isn't perfect and I suspect flicker can still sometimes occur in part because of nested interrupts (display interrupts can interrupt the zero crossing service routine).

    Quoted from bontango:

    Yes, but during my tests I noticed that the VDHL module I'm using for the 6800 emulation (cpu68.vhd) has problems with nested interrupts.

    Why is this? The 6800 /IRQ input is level sensitive (not edge). The 6821 IRQ outputs are open drain and all tied together in an OR fashion meaning they could all request an interrupt at the same time. It is up to the game software (operating system) to prioritise IRQs and determine which IRQ source(s) is active.
    In other words, interrupts are prioritised and dealt with in software and nesting should only occur to one level based on their frequencies.

    Anyway, great work! and to get back to the original request, hopefully a Bally 6803 control board replacement will one day make it on your list

    #684 8 months ago

    Thanks for the help, built this board over the course of a month, over a 9 months ago. Grabbed the wrong resistor, didn’t have the 1.5m ohm but had 2m and it solved all my issues

    2 weeks later
    #685 8 months ago

    Does anyone have an extra LISY1 PCB? It looks like I could use one of them to revive a Buck Rogers. I think I have most of the parts to assemble it.

    #686 8 months ago

    Yes, I have two extras of the LISY 1 and 1 extra of the LISY 80 board.

    #687 8 months ago
    Quoted from KenLayton:

    Yes, I have two extras of the LISY 1 and 1 extra of the LISY 80 board.

    PM sent.

    1 week later
    #688 7 months ago
    Quoted from koji:

    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

    It took a little bit of time, but now the new Gosof80 software is ready.
    MA216 & MA390 soundboards supported at the moment, MA55 will be added next weekend at the latest.
    The goal is to create a'universal' program for the FPGA and have the Gottlieb rom files on a seperate micro SD card.

    https://lisy.dev/gosof.html

    Let me know what you think

    pasted_image (resized).png
    #689 7 months ago
    Quoted from bontango:

    It took a little bit of time, but now the new Gosof80 software is ready.
    MA216 & MA390 soundboards supported at the moment, MA55 will be added next weekend at the latest.
    The goal is to create a'universal' program for the FPGA and have the Gottlieb rom files on a seperate micro SD card.
    https://lisy.dev/gosof.html
    Let me know what you think
    [quoted image]

    That's amazing.. will make a lot of sys80 people happy I'm sure!

    #690 7 months ago

    Special awarded/no extra ball

    LISY80
    Chicago Cubs Triple Play (CCTP) 696
    LISY game number 041

    I finally got my System 80 board running. Everything seems to be working correctly expect from the extra ball. The game currently awards the special. I would prefer to have it reward an extra ball. There is not a dip.csv file for this game in the LISY files. I assume it is using the default file. The manual for CCTP shows that dip 22 controls whether the awards special or an extra ball. I examed several other dip files and they all had 22 as special/extra ball award. I thought I would clever and edit the default file by changing dip 22 from ON to OFF. Saved/exported as a CSV file and placed it in the LISY80 dip. When I reinstalled the SD card and powered up the machine it did not boot.

    I assumed that the csv file could be edited. Can it?
    Do you think perhaps the csv file was corrupted when I opened it? ( I did export from Numbers as an csv file).
    Anyone have ideas that I could try to so the awarded extra balls?

    Thanks,
    Phil

    #691 7 months ago

    Have you tried the LISY connect that let's you modify the virtual dip switches for that game?

    #692 7 months ago
    Quoted from BleacherBum:

    I thought I would clever and edit the default file by changing dip 22 from ON to OFF. Saved/exported as a CSV file and placed it in the LISY80 dip. When I reinstalled the SD card and powered up the machine it did not boot.

    Editing the default file should work, maybe you should use a text editor rather then Excel/CSV.
    But as Grangeomatic said. Once you have your LISY connected to your Network (or use the Host Mode)
    you can use LISY_Control via your webbrowser to create and edit the cfg file for your game.

    #693 7 months ago

    Thanks Bontango,

    I got the file edited in txt editor. Everything works great now. Thanks much.

    Somethings I am more technologically impaired than I care to admit. Still trying to get connected my webbrowers for future work.

    Phil

    1 week later
    #694 7 months ago

    Question about LISY support for Haunted House. It looks like it supports the original ROM and one patched for 7-digit displays.

    Is there support for any other alternate ROMs for Haunted House? Specifically the 669-3 and 669-4 and their variations to support the extra trap door sound or a game setup with a sound board modified for speech.

    https://www.flipprojets.fr/PromHH_EN.php

    If not those would be great additions to support. Would like to try a LISY80 on a Haunted House with speech but at the moment it doesn't seem to be supported.

    #695 7 months ago

    as long as it is supported by pinmame it 'should' work with LISY also.
    By default only the 'original' roms are defined in LISY as there are too many variants
    BUT, you can adjust your configuration yourself and give it a try
    see below example and pls. let me know if it worked for you

    Example for speech 669-4.cpu

    1)
    Check pinmame source code ( gts80games.c ) I'm using for LISY if it is supported
    You can find it on my github https://github.com/bontango/lisy-src-5.x/blob/master/src/wpc/gts80games.c
    For your Haunted House you will find on line 517 ff. the following:

    -------------------- SNIP ------------------------
    /*-------------------------------------------------------------------
    / Haunted House, since serial no. 5000 with added Speech and additional hardware Votrax MOD
    /-------------------------------------------------------------------*/
    INIT_S80(hh_4, dispNumeric2, SNDBRD_GTS80SS_VOTRAX)
    GTS80_1_ROMSTART ("669-4.cpu", CRC(8724cdf8) SHA1(9c8d7433ea14b8b50014deb7574c9d5043a794cc))
    GTS80SS22_ROMSTART("669-4-s1.snd", NO_DUMP, // unreleased by the Flipprojets guys so far
    "669-4-s2.snd", NO_DUMP)
    GTS80_ROMEND
    #define input_ports_hh_4 input_ports_hh
    CORE_CLONEDEFNV(hh_4,hh,"Haunted House (rev. 4 unofficial Votrax speech MOD)",1982,"Flipprojets",gl_mGTS80SS,0)

    -------------------- SNIP ------------------------

    The important informations here are:
    INIT_S80(hh_4, dispNumeric2, SNDBRD_GTS80SS_VOTRAX) -> "hh_4" need to be the name of the pinmame zip archive
    GTS80_1_ROMSTART ("669-4.cpu", CRC(872 ... -> 669-4.cpu need to be the name of the rom file in the zip archive AND it needs to match the CRC checksum
    GTS80SS22_ROMSTART("669-4-s1.snd", N ... -> name of soundrom in the zip file ( can be ignored for LISY80 )

    2)
    create a pinmame zip archive with name "hh_4.zip" and put your 669-4.cpu in it.
    copy your zip to folder \lisy\lisy80\roms on the LISY SD

    3)
    Edit "lisy80games.csv" on the SD card ( Folder: \lisy\lisy80\cfg )
    Use for example entry #38 (unused1) and change it according to the pasted image below
    ( you can just copy the 'hh' entry and change the first two columns)

    38 hh_4 SYS80 Haunted House 669 1000 Haunted House with speech

    alternativly you can use any entry between 1..39, entry #40 and above are for 80B games only!

    4)
    set 'game select' DIP bank to your choosen entry

    If all went well, LISY should boot your game and the green LED will be ON
    If not, take a look to the user manual how to create a debug file

    pasted_image (resized).png
    #696 7 months ago

    bontango Thank you for the explanation I think this will help others as well that may need to try alternative versions of code for games. That version to support Speech is a big one for many Haunted House owners. I'll try this on Haunted House and see how it goes.

    #697 7 months ago

    **EDIT: NEVERMIND I found it!***

    I ordered a batch of LEDs a while ago, in green and blue - but red, yellow and orange weren't available.

    Where does one go to find these LEDs - for the Bally display boards - these days?

    #698 7 months ago

     bontango Is there any way to test a GOSOF80 v.2.1 outside of the machine ?
    I have built one for my Black hole (MA216 version) - which is 5 hours away from here, so it would be nice to know if it works before I take the trip
    I guess I can't test it in my TX sector ?

    #699 7 months ago
    Quoted from Zigzagzag:

    I guess I can't test it in my TX sector ?

    not in a TX sector, the connector of the soundboard is different for 80B

    With 5 Volt you can check via jumpers and the 'input test' switch if it reacts ( e.g. activating the MP3 player for speech)
    For a full test you need 12 Volt and a speaker.
    I have added the schematics to my page so you can see where to connect 12Volt and speaker
    https://lisy.dev/media/files/gosof80_2_1_1_sch.pdf

    #700 7 months ago
    Quoted from bontango:

    not in a TX sector, the connector of the soundboard is different for 80B
    With 5 Volt you can check via jumpers and the 'input test' switch if it reacts ( e.g. activating the MP3 player for speech)
    For a full test you need 12 Volt and a speaker.
    I have added the schematics to my page so you can see where to connect 12Volt and speaker
    https://lisy.dev/media/files/gosof80_2_1_1_sch.pdf

    Awesome as always, thanks !

    There are 983 posts in this topic. You are on page 14 of 20.

    Reply

    Wanna join the discussion? Please sign in to reply to this topic.

    Hey there! Welcome to Pinside!

    Donate to Pinside

    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, become a Pinside+ member!