(Topic ID: 179619)

Rebuilding sound for DataEast & WPC using a pi

By steve45

5 years ago


Topic Heartbeat

Topic Stats

  • 1,864 posts
  • 106 Pinsiders participating
  • Latest reply 10 hours ago by Robotworkshop
  • Topic is favorited by 137 Pinsiders

You

Linked Games

Topic Gallery

View topic image gallery

tilt2_5d (resized).jpg
tilt2_6a (resized).jpg
TL-board (resized).jpg
tiltaudiopic1 (resized).PNG
pasted_image (resized).png
rom (resized).png
pasted_image2 (resized).png
pasted_image (resized).png
raspilog.pdf (PDF preview)
20220102232634-Sebinouse-FD802F28-3EEC-4661-9A38-5A35D35F80E4 (resized).jpeg
20220102224622-Sebinouse-28F808E6-D074-48AA-BDCC-C0BFA18607DB (resized).jpeg
image (resized).jpg
image (resized).jpg
DD979586-D242-46E9-8FFF-D6711145A834 (resized).jpeg
screen (resized).png
C5A11AC0-78A6-45DF-8737-C3E1E046DEDE (resized).jpeg

There are 1,864 posts in this topic. You are on page 37 of 38.
#1801 4 months ago
Quoted from Robotworkshop:

Supposedly if the AV board is dead you can use a WPC DMD driver board and then a separate sound card like the Pinsound or Tilt Audio.

WRONG!
well ... let's say rather that it is not exactly TRUE
But this need some technical explanations...

Indeed, many people think that the WPC-95 (A-20516) Audio Video board can be replaced with a separate video board from WPC-89 / WPC-S (A-14039) and an independent audio board (like Tilt Audio, or Pinsound).
Granted, it works in some cases. But not always! Why?

➤ Simply because it's not exactly equivalent to an original WPC-95 AV board.

Let us not forget either the serial interface (which is independent of the ASIC), which is lost if one replaces an AV card by other boards. Granted, this was only used on the "NBA Fastbreak" and "Phantom Haus", and isn't really something essential, except if you want to play NBA in network, or connect the serial printer.

Remember that, no one has ever seen the ASIC datasheet used on WPC-95 AV boards and it is only "assumed", or "presumed" to be identical to the discrete components previously used on WPC-89 / WPC-S board. However, this assumption is a mistake , because Williams made some improvements by creating this ASIC, with features that are not found on previous WPC-89/WPC-S boards.

Really ? YES.

A simple example: if you look at the diagram of the DMD WPC / WPC-S video board (A-14039 or A-14039.1) you will see that this board will never be able to manage DOT displays of more than 32 lines. Indeed, the comparator (U21 - 74HC588) receives only 5 address lines and on the other hand, the hardware generation (U23A / B / C + U6C / D) of the synchro signal (ROW_DATA) also only uses 5 bits.

However, there is a WPC-95 machine with a display of more than 32 lines: the "Phantom Haus", which has a 128x64 DMD - in other words, 64 lines!

So how can this work?

⬥ I disassembled the part of the ROMs concerning display management and the obvious: the registers in the ASIC are more than 5 bits, since sometimes a value greater than 32 is written in them. Without going into too much detail, let's say the bottom line is that the ASIC registers on the WPC-95 AV board are a bit different from those implemented on the WPC-89 / WPC-S video board.
Moral: The video section of a WPC-95 is well designed differently from that of a WPC-S, although at first glance it looks similar.

⬥ I had already made this observation by analyzing the ROMs of certain pinball machines, produced both in WPC-S and in WPC-95. Because there are indeed some VERY particular models in the WPC-S and WPC-95:
- the "Demolition Man", which is a WPC-89, but which also served as a prototype for the WPC-S
- the "Jackbot", which is a WPC-S, and which served as a prototype for the WPC-95
- the "Phantom Haus", which is a WPC-95 with very specific hardware and a larger resolution display.
- the "Congo", originally produced in WPC-95, but which was then offered as a conversion kit for WPC-S (keeping the WPC-S boards)

For the latter, there are ROM versions that work just as well on a WPC-S CPU board as they do on a WPC-95 CPU board!
This is surprising, because the hardware (driver, audio, video) is obviously not the same at all.
When the CPU starts up, the video board registers are interrogated. The answer being different between a video board WPC-S A-14039 and an AV WPC-95 A-20516, it is thus possible to determine whether the pinball machine is a WPC-S or a WPC-95.
It goes without saying that this kind of functionality can never be integrated on an alternative audio card, since it is the video part of the ASIC which is used to make the identification.

It is not possible either, to use an AV board to keep the video part and to put another audio board next to it. Because the audio and video sections of ASIC are inseparable and cannot be deactivated. Connecting a second audio board, while leaving the AV board in place, will lead to conflicts (exchanges with the CPU being bi-directional).

And for those who haven't had the courage to read these technical explanations, let's summarize:
There are cases, where for a WPC-95, installing an alternative audio board (TiltAudio, Pinsound ...) does not work.

Having said that, TiltAudio is still a great project

#1802 4 months ago
Quoted from noflip95:

WRONG!
well ... let's say rather that it is not exactly TRUE
But this need some technical explanations...
Indeed, many people think that the WPC-95 (A-20516) Audio Video board can be replaced with a separate video board from WPC-89 / WPC-S (A-14039) and an independent audio board (like Tilt Audio, or Pinsound).
Granted, it works in some cases. But not always! Why?
➤ Simply because it's not exactly equivalent to an original WPC-95 AV board.
Let us not forget either the serial interface (which is independent of the ASIC), which is lost if one replaces an AV card by other boards. Granted, this was only used on the "NBA Fastbreak" and "Phantom Haus", and isn't really something essential, except if you want to play NBA in network, or connect the serial printer.

Excellent notes about the details on the AV board and it would be best to just keep it but if the board dies they aren't as easy to get as other boards so just mentioned one option that I read about. I never said it was a combination that was meant to work in all cases but according to this thread:

https://pinside.com/pinball/forum/topic/williams-wpc95-audio-visual-board

quite a few people that had dead WPC AV boards swapped out with the combination of the older DMD and one of the replacement sound boards with good results. So if you have a dead AV board it is certainly an option to try. Even if everything doesn't work it is probably better than nothing working.

That is a good point about the network play and serial printer but many people just have a single machine and I don't think I have ever seen the serial printer option or know of anyone that used it so that one I don't think would affect anyone.

#1803 4 months ago
Quoted from steve45:

TRACE level logfile is not really helpful in this case. It actually only tells about loading sounds and of course all startup params, but so far there is nothing obvious wrong. It has especially not a single line from the interrupt handler, that tells about a command byte received from the game ...

just an update. TiltAudio Board 3.7 tried in two DE Star Trek, a DE GnR, and a DE Lethal Weapon. Same results. No sound to game but sounds play fine via WebUI.

#1804 4 months ago
Quoted from ptolemy:

just an update. TiltAudio Board 3.7 tried in two DE Star Trek, a DE GnR, and a DE Lethal Weapon. Same results. No sound to game but sounds play fine via WebUI.

I actually can hardly believe it, but I will do some regression testing on my LW3 with latest hard- and software. Br Steve

#1805 4 months ago

Finally got around to hooking my tilt audio up. Didn't see the raspisound.ini in the data/sound folder after flashing the image, so I ignored it.

I have pinwoofer amp and speakers. When I turn on the machine I hear "whistling" is that a ground issue?

I did hear the license number start to go but could understand it through the whistling. Thinking ground issue or raspisound.ini issue or both? Thanks

#1806 4 months ago
Quoted from ViperJelly:

I did hear the license number start to go but could understand it through the whistling. Thinking ground issue or raspisound.ini issue or both? Thanks

I'm not familiar with your setup (pinwoofer amp and speakers) but I can say that the ini file should not matter. no file is no problem for a fresh start, as anything has smart defaults. The amps on the TILT!Audio board are digital class-d amps based on a PAM8610 chip, so the outputs should not short anywhere to ground but instead directly drive the speaker coils for backbox left and right and cab speaker

#1807 4 months ago
Quoted from steve45:

I actually can hardly believe it, but I will do some regression testing on my LW3 with latest hard- and software. Br Steve

I have a version 3.0 board being shipped from BrewNinja so I will test that once it arrives.

I am baffled as well. Three different Tilt Audio boards in four different DE machines and I can't get any of them to work

Hoping it is a simple issue on my part. It will be interesting to see what your regression testing determines.

#1808 4 months ago

I took the latest update too and lost sound on my Data East Jurassic Park. I thought for awhile it was a corrupted sd card but it wasnt.

#1809 4 months ago

Did some tests today, but still not really more insights?!? On my LW3 it works like a charm:


I tried 1.39 firmware and 1.38rc6 no difference. Board rev is 3.5 (1st gen with stm subboard), unfortunately I don't have a 3.7 at hand for testing, but the differences between the boards are minor (only Charlies changes adding an additional WPC95) connector.

Quoted from waynestatemac:

I took the latest update too

For error reports please be precise, so it is easier to track issues. Latest board? -> what revision. Latest firmware -> which version

#1810 4 months ago

Just to prevent "but what about ..." the 3.7 board revision works also as expected:

So from my side, I don't see where the issue should be. Could only recommend the usual:
- check all soldering (also the 4 extra pins of the black pill, as they are needed! )
- check connections from IDC connector to the resistor network and from there to the black pill.
- check connections from black pill to the pi

What should be connected can be looked up in the schematics https://oshwlab.com/steve45/tiltaudio-3-6

With latest firmware you could also make the black pill led flash, when data arrives.

pasted_image (resized).png

That's basically all I can contribute for now. Hard to debug from remote.
If the black pill is detected and initialised correctly, you should see the version in the webUI (and logfile)
pasted_image2 (resized).png

#1811 4 months ago

Maybe check the orientation of the ribbon cable ?

#1812 4 months ago

Took out the Tilt card and put back an original sound card in my TAF.
Now the flippers flip at the end of the round and the sounds are in sync with the end of ball bonus counts again.
Probably out of scope for the Tilt card, but there seems to be some kind of communication between the sound card and the MPU missing.
Would be interesting to know if other games used this ?

#1813 4 months ago
Quoted from ptolemy:

I have a version 3.0 board being shipped from BrewNinja so I will test that once it arrives.
I am baffled as well. Three different Tilt Audio boards in four different DE machines and I can't get any of them to work
Hoping it is a simple issue on my part. It will be interesting to see what your regression testing determines.

Sidenote, which Pi are you using in your TA boards?

#1814 4 months ago
Quoted from steve45:

Just to prevent "but what about ..." the 3.7 board revision works also as expected:
So from my side, I don't see where the issue should be. Could only recommend the usual:
- check all soldering (also the 4 extra pins of the black pill, as they are needed! )
- check connections from IDC connector to the resistor network and from there to the black pill.
- check connections from black pill to the pi
What should be connected can be looked up in the schematics https://oshwlab.com/steve45/tiltaudio-3-6
With latest firmware you could also make the black pill led flash, when data arrives.
[quoted image]
That's basically all I can contribute for now. Hard to debug from remote.
If the black pill is detected and initialised correctly, you should see the version in the webUI (and logfile)
[quoted image]

I'm running Board rev 3.7 with 1.38 Firmware although I also tested it with 1.37 Firmware too. I am running a Raspberry Pi 3 Model B+

I used my DMM and checked continuity from the DE connector to the resistor network and the Pi.

Can you clarify that its possible for the board to work in the WPC machines but not the DE machines? Are there specific components I should focus on with regards to confirming continuity for DE?

#1815 4 months ago
Quoted from lucky1:

Maybe check the orientation of the ribbon cable ?

I've tried swapping the orientation of the ribbon cable to no avail. Honestly though I've tried so many different combinations of cables, machines, boards, etc.. I'm just hoping it is a bad solder connection or a reversed component, etc..

#1816 4 months ago
Quoted from ptolemy:

Can you clarify that its possible for the board to work in the WPC machines but not the DE machines? Are there specific components I should focus on with regards to confirming continuity for DE?

All the new board 3.5+ are using common components for DE and WPC. In fact the only hardware difference between DE and WPC is a different interrupt input for the stm sub processor. Everything else is the same.

Also the ISR is very similar, the DE version simply skips the address decoding & filtering as there is no address for data east.

So short answer is: the board should work the same on DE and WPC, except there is an issue with one of the interrupt wires (or address wires for WPC).

Br Steve

#1817 4 months ago
Quoted from Zigzagzag:

Now the flippers flip at the end of the round and the sounds are in sync with the end of ball bonus counts again.
Probably out of scope for the Tilt card, but there seems to be some kind of communication between the sound card and the MPU missing.

That's an interesting one. You raised that concern earlier and I would agree that the syncing could depend on some sound board communication back to the MPU. Not so easy the debug and discover though. I will see how much time I can invest in this topic, because it is very specific I guess.

#1818 4 months ago
Quoted from steve45:

That's an interesting one. You raised that concern earlier and I would agree that the syncing could depend on some sound board communication back to the MPU. Not so easy the debug and discover though. I will see how much time I can invest in this topic, because it is very specific I guess.

Yeah, it would have been interesting to know which games had this kind of bidirectional communication.
So far I have only noticed this on TAF of the games I have placed a Tilt audio card in.

Let me know if there´s anything I can do to assist.

#1819 4 months ago
Quoted from steve45:

All the new board 3.5+ are using common components for DE and WPC. In fact the only hardware difference between DE and WPC is a different interrupt input for the stm sub processor. Everything else is the same.
Also the ISR is very similar, the DE version simply skips the address decoding & filtering as there is no address for data east.
So short answer is: the board should work the same on DE and WPC, except there is an issue with one of the interrupt wires (or address wires for WPC).
Br Steve

I've verified connectivity from the DE 20 pin IDC connector to the resistor network, from the resistor network to the STM, and from the STM to the Pi. All test fine for connectivity. I was really hoping for a cold solder joint but doesn't appear to be the case.

My friend has a LW3 that we tested in but can you confirm what version of Game ROM you are running in your LW3 so I can be 100% sure our configuration matches yours for testing.

Can you also confirm orientation of the ribbon cable from the main board to the Tilt Audio board. I am aligning the cable with the red stripe on pin one of the game board to pin one of the Tilt Audio DE 20 pin IDC connector.

#1820 4 months ago
Quoted from ptolemy:

I've verified connectivity from the DE 20 pin IDC connector to the resistor network, from the resistor network to the STM

Did you also verify connectivity from the DE IDC connector to the STM through the resistor network. You should have 47Ohms on each line except D0 (Pin15 on IDC) which has 1k+47Ohms to A0 of the STM. The most important Pin for DE is from Pin13 of the IDC to C15 of the STM which is strobe.

#1821 4 months ago
Quoted from lucky1:

Did you also verify connectivity from the DE IDC connector to the STM through the resistor network. You should have 47Ohms on each line except D0 (Pin15 on IDC) which has 1k+47Ohms to A0 of the STM. The most important Pin for DE is from Pin13 of the IDC to C15 of the STM which is strobe.

I will check and report back.

#1822 4 months ago
Quoted from lucky1:

Did you also verify connectivity from the DE IDC connector to the STM through the resistor network. You should have 47Ohms on each line except D0 (Pin15 on IDC) which has 1k+47Ohms to A0 of the STM. The most important Pin for DE is from Pin13 of the IDC to C15 of the STM which is strobe.

I measured the data lines from the IDC connector to the STM and all were within tolerance (47.2, 47.2, 47.4, etc.. ohms). You state that D0 is pin 15 on the IDC connector however on my 3.7 board D0 is on pin 3 of the IDC connector.

Measuring from this pin 3 on the IDC to A0 on the STM I get 1.03K Ohms.

Pin 13 of the IDC to pin C15 of the STM reads 47.3 Ohms

#1823 4 months ago

Any plans for Williams System11 A/B support?

#1824 4 months ago
Quoted from ptolemy:

You state that D0 is pin 15

Sorry, you are right. It is pin 15 on WPC

#1825 4 months ago
Quoted from lucky1:

Sorry, you are right. It is pin 15 on WPC

Is 1.03K an acceptable reading?

I'm baffled as to what the issue could be.

#1826 4 months ago
Quoted from ptolemy:

My friend has a LW3 that we tested in but can you confirm what version of Game ROM you are running in your LW3 so I can be 100% sure our configuration matches yours for testing.

The latest rom 2.08 rom (resized).png

Quoted from ptolemy:

Can you also confirm orientation of the ribbon cable from the main board to the Tilt Audio board. I am aligning the cable with the red stripe on pin one of the game board to pin one of the Tilt Audio DE 20 pin IDC connector.

Of course the ribbon cable orientation is correct in my setting otherwise you would not get any byte from the MPU. That's clear by just looking at the pinout.

You can also see the ribbon cable orientation in the video

the red wire with the board in "portrait orientation" is the bottom wire and the cable is connected "from the right". There is always this notch on the IDC connectors that need to match on board and cable.
Unfortunately the old pinball games connector, don't have these real elevated "thing" that really prohibits wrong orientation, but you can still see it. You can also see the "pin 1" marker.
pasted_image (resized).png

#1827 4 months ago
Quoted from ptolemy:

Is 1.03K an acceptable reading?

Yes !

#1828 4 months ago
Quoted from steve45:

The latest rom 2.08 [quoted image]

Of course the ribbon cable orientation is correct in my setting otherwise you would not get any byte from the MPU. That's clear by just looking at the pinout.
You can also see the ribbon cable orientation in the video the red wire with the board in "portrait orientation" is the bottom wire and the cable is connected "from the right". There is always this notch on the IDC connectors that need to match on board and cable.
Unfortunately the old pinball games connector, don't have these real elevated "thing" that really prohibits wrong orientation, but you can still see it. You can also see the "pin 1" marker.
[quoted image]

thanks. I will confirm the ROM version and test again.

#1829 4 months ago
Quoted from steve45:

Just to prevent "but what about ..." the 3.7 board revision works also as expected:
So from my side, I don't see where the issue should be. Could only recommend the usual:
- check all soldering (also the 4 extra pins of the black pill, as they are needed! )
- check connections from IDC connector to the resistor network and from there to the black pill.
- check connections from black pill to the pi
What should be connected can be looked up in the schematics https://oshwlab.com/steve45/tiltaudio-3-6
With latest firmware you could also make the black pill led flash, when data arrives.
[quoted image]
That's basically all I can contribute for now. Hard to debug from remote.
If the black pill is detected and initialised correctly, you should see the version in the webUI (and logfile)
[quoted image]

Just a quick update. Tilt Audio board 3.7, Pi Firmware 1.39, MCU Firmware .2, Raspberry 3 Model B+

received Version 3.0 board from BrewNinja and it did not resolve the issue. Same behavior as 3.7 Board. All sounds play fine via web interface, just no game sounds. Yes I made sure the jumper was set to DE.

Swapped in my original 3.7 Board and upgraded to 1.39 figuring I have nothing to lose. No change. All sounds play fine via web interface, just no game sounds.

Went into web interface and confirmed MCU was detected and the version numbers were correct (1.39 and .2) See attached image. Tested the blink function on test screen and it successfully blinks the blue led on the STM.

Selected MCU LED Test when data present and as expected the LED did not blink.

These tests were done on my DE Star Trek. I will test more on my friends LW3 in a few days once I confirm ROM version, etc.. Maybe there is something unique about Star Trek....

tiltaudiopic1 (resized).PNG
#1830 4 months ago
Quoted from steve45:

The latest rom 2.08 [quoted image]

Of course the ribbon cable orientation is correct in my setting otherwise you would not get any byte from the MPU. That's clear by just looking at the pinout.
You can also see the ribbon cable orientation in the video the red wire with the board in "portrait orientation" is the bottom wire and the cable is connected "from the right". There is always this notch on the IDC connectors that need to match on board and cable.
Unfortunately the old pinball games connector, don't have these real elevated "thing" that really prohibits wrong orientation, but you can still see it. You can also see the "pin 1" marker.
[quoted image]

I noticed you have the audio configuration set to "sndrpi..." however there are multiple options in the audio configuration settings.

What should I have it set to for DataEast? Could it be as simple as the wrong audio configuration set?

#1831 4 months ago
Quoted from ptolemy:

Just a quick update. Tilt Audio board 3.7, Pi Firmware 1.39, MCU Firmware .2, Raspberry 3 Model B+
received Version 3.0 board from BrewNinja and it did not resolve the issue. Same behavior as 3.7 Board. All sounds play fine via web interface, just no game sounds. Yes I made sure the jumper was set to DE.
Swapped in my original 3.7 Board and upgraded to 1.39 figuring I have nothing to lose. No change. All sounds play fine via web interface, just no game sounds.
Went into web interface and confirmed MCU was detected and the version numbers were correct (1.39 and .2) See attached image. Tested the blink function on test screen and it successfully blinks the blue led on the STM.
Selected MCU LED Test when data present and as expected the LED did not blink.
These tests were done on my DE Star Trek. I will test more on my friends LW3 in a few days once I confirm ROM version, etc.. Maybe there is something unique about Star Trek....[quoted image]

Have you tried disabling LUA ?
There have been issues when this has been enabled.
Perhaps running it without a license is worth a try ?

#1832 4 months ago
Quoted from Zigzagzag:

Have you tried disabling LUA ?
There have been issues when this has been enabled.
Perhaps running it without a license is worth a try ?

I'm quite sure that this is unrelated. Lua scripting is only involved, when sound playback is triggered AND you define a start or stop command along with that sound. but in this case the sound gets not even triggered (only manually in the webUI).

#1833 4 months ago
Quoted from ptolemy:

What should I have it set to for DataEast? Could it be as simple as the wrong audio configuration set?

That is unrelated to the game type. It is only about the audio device the Pi is using to generate sound. And as you have sound (triggered from the web UI), this is not the problem.

#1834 4 months ago
Quoted from Sgrsgr:

Any plans for Williams System11 A/B support?

I did some experiments on my Whirlwind, but there is a challenge in SYS11 A/B: parts of the sound is created by the CPU and not on the sound board. So there are two options to deal with it:
1. replace only parts of the sound and mix the CPU generate sound to the TILT!Audio board sound. That kind of works with the aux in plug available on board revs 3.5 and newer.
2. pickup the sound commands that the main CPU send to the "on board sound board", by hooking on one of the PIA chips on the CPU board.

Solution 1 works in lab condition, but i never applied it to a real game.
Solution 2 also should work, but I never really took the time to try it out.

So bottom line the answer is: there are ideas, but not really plans.

#1835 4 months ago
Quoted from steve45:

I'm quite sure that this is unrelated. Lua scripting is only involved, when sound playback is triggered AND you define a start or stop command along with that sound. but in this case the sound gets not even triggered (only manually in the webUI).

Still stumped. Just for the heck of it I put in a Raspberry Pi Zero 2 W that I had and get the same result. sounds play fine via web interface, no data is indicated from the main board to the Tilt Audio i.e. when STM set to blink on data the LED remains off..

As previously indicated the Version 3.0 board also does not work which was built by BrewNinja so this should eliminate any potential soldering issues on the boards I assembled. I don't believe there are issues on my boards as they work fine in my WPC and I also checked every DE pin from the IDC to the resistor network to the STM to the Pi as well as took Ohm readings.

Prior to switching my Raspberry Pi 3 Model B+ with the Raspberry Pi Zero 2 W tonight the only constant was the Raspberry Pi as I swapped it onto multiple boards to test. Could there be something with the Raspberry Pi image on the SD Card that would prevent it from working in DE but work fine in WPC?

I know it is a long shot but I am about to ship my board to Steve for testing in his LW

#1836 4 months ago
Quoted from steve45:

Just to prevent "but what about ..." the 3.7 board revision works also as expected:
So from my side, I don't see where the issue should be. Could only recommend the usual:
- check all soldering (also the 4 extra pins of the black pill, as they are needed! )
- check connections from IDC connector to the resistor network and from there to the black pill.
- check connections from black pill to the pi
What should be connected can be looked up in the schematics https://oshwlab.com/steve45/tiltaudio-3-6
With latest firmware you could also make the black pill led flash, when data arrives.
[quoted image]
That's basically all I can contribute for now. Hard to debug from remote.
If the black pill is detected and initialised correctly, you should see the version in the webUI (and logfile)
[quoted image]

looks like your board is only populated with the DE components. Have you tested with a fully populated board as well? all my boards are fully populated with the DE and WPC components. it also looks like you are powering the board externally. I understand that it shouldn't matter, just looking for a direct comparison of what I am testing.

Also I noticed in the configuration section of the webui that there are two Data East selections. One with an Asterisk and (*) and one without. is this relevant? Why they difference?

#1837 4 months ago
Quoted from ptolemy:

looks like your board is only populated with the DE components. Have you tested with a fully populated board as well?

No. But I think we should not overuse this "is it really, really exactly the same" thing, because WPC differs only in power supply and different connectors. Also the external power supply should not matter, was just an easier test setup.

The next thing I'm going to test is related to the game code. There is no difference in the schematics when I rechecked the manuals of LW3 and StarTrek so maybe it is something in the code.

As I don't have a StarTrek I will run my LW3 CPU with StarTrek game code and see what happens ... In the Williams WPC world this type of tests are meaningful as you can easily test startup behaviour of differnt games this way.

#1838 4 months ago
Quoted from ptolemy:

confirm what version of Game ROM you are running in your LW3

What version of game rom do you have in your Star Trek?

#1839 4 months ago
Quoted from steve45:

What version of game rom do you have in your Star Trek?

2.01

#1840 4 months ago

Progress! I finally made it over to my friend's house who has a collection of DE Games. I took along my Version 3.0 and 3.7 boards as well as my Raspberry Pi 3 Model B+ and my Raspberry Pi Zero 2 W.

Tested my boards in his DE GnR, his WWF, and his Star Trek. My boards worked fine in his GnR and WWF however they did not work in his Star Trek. Basically in the Star Trek I am getting the same thing as my Star Trek. Sounds work fine in Web UI but not for game play.

I have taken his TiltAudio board and brought it back to my house to troubleshoot on the bench for issues. The board boots fine however the MCU is not detected. I will check it and report back any finds. Hoping for a bad solder joint but might be the STM itself.

Unfortunately the only DE game I have is Star Trek hence my limited ability to test DE compatibility until I went to my friend's house.

I suspect that DE Star Trek must use a combination of CPU sound and Sound Card Sound and this is causing some problems with Tilt Audio.

so in summary - I've gotten TiltAudio to work in other DE games - just not the one game I own - DE Star Trek.

#1841 4 months ago

I'm still on it, but it is really suspicious. Yesterday I had the chance to test on a data east Checkpoint. A very similar data east, according to pinwiki hardware should be exactly the same. MPU / Sound even the half size dmd is the same in this machine.
Despite to the fact that I have not prepared a matching sound pack for the machine, everything worked well. Just as expected.

I will change the game rom in my DE LW3 to star trek and try with star trek code .. but honestly I don't expect much.

We also tested on a batman forever that had so much problem with power supply that both the stm and the raspberry pi was repeatedly rebooting. But that was maybe specific for that machine. And one could easily spot it, because the red led on the stm was not even constantly on but flickering.

#1842 3 months ago
Quoted from steve45:

I'm still on it, but it is really suspicious. Yesterday I had the chance to test on a data east Checkpoint. A very similar data east, according to pinwiki hardware should be exactly the same. MPU / Sound even the half size dmd is the same in this machine.
Despite to the fact that I have not prepared a matching sound pack for the machine, everything worked well. Just as expected.
I will change the game rom in my DE LW3 to star trek and try with star trek code .. but honestly I don't expect much.
We also tested on a batman forever that had so much problem with power supply that both the stm and the raspberry pi was repeatedly rebooting. But that was maybe specific for that machine. And one could easily spot it, because the red led on the stm was not even constantly on but flickering.

Yeah it has me stumped as well. Not sure if I mentioned this but one thing I noticed that is unique to Star Trek is as soon as you power the machine up with the original DE sound board it says "Scotty here!" and then the display shows and the game goes through its startup. The fact this happens before the game boots led me to believe maybe it was coming from the CPU versus the sound board.

At least I've been able to eliminate the core TiltAudio hardware as being a problem and narrowed it down to DE Star Trek. The fact that the board works in other DE games but two different DE Star Trek machines exhibit the same behavior is pretty interesting.

Let me know what you find when you test with the Star Trek ROM.

#1843 3 months ago
Quoted from steve45:

I'm still on it, but it is really suspicious. Yesterday I had the chance to test on a data east Checkpoint. A very similar data east, according to pinwiki hardware should be exactly the same. MPU / Sound even the half size dmd is the same in this machine.
Despite to the fact that I have not prepared a matching sound pack for the machine, everything worked well. Just as expected.
I will change the game rom in my DE LW3 to star trek and try with star trek code .. but honestly I don't expect much.
We also tested on a batman forever that had so much problem with power supply that both the stm and the raspberry pi was repeatedly rebooting. But that was maybe specific for that machine. And one could easily spot it, because the red led on the stm was not even constantly on but flickering.

one other thought. is it possible that the Trek_201 Alt sound pack file is corrupted in some way?

This is the file I am using https://mega.nz/file/bmJyQKqZ#HcN8ee3HhQq4f7zVTYaEFGgSjNJtgdtuVpjwSGjEyS0

#1844 3 months ago
Quoted from ptolemy:

up with the original DE sound board it says "Scotty here!" and then the display shows and the game goes through its startup. The fact this happens before the game boots led me to believe maybe it was coming from the CPU versus the sound board.

No that is actually coming from the sound card that has game specific roms and therefore also game specific startup sound. You will here that startup sound even if you remove the ribbon cable.

#1845 3 months ago
Quoted from ptolemy:

is it possible that the Trek_201 Alt sound pack file is corrupted in some way?

what do you mean by that? I quickly checked the distribution of the IDs and these looked quite normal for a data east.

#1846 3 months ago
Quoted from steve45:

what do you mean by that? I quickly checked the distribution of the IDs and these looked quite normal for a data east.

just offering ideas. as Star Trek seems to be the only DE game I can't get to work I was just trying to identify differences.

1 week later
#1847 3 months ago

steve45 just checking in to see if you have any more ideas regarding the DE Star Trek and TiltAudio

1 week later
#1848 3 months ago

I am having this same issue with my LW3.

Tilt 3.7 board
Version 1.39
Pi 3 A+ (the only one I could get)
Game ROM 2.0

Sound output from machine through web UI, no sound out when in gameplay. Data cable red on one both sides.

I threw the board into my RAB with the same settings and works just fine.

Sounds like it might be an early data east game compatibility issue?

#1849 3 months ago
Quoted from SpaceCadet88:

Sounds like it might be an early data east game compatibility issue?

can you give some more details e.g. rom version, MPU board rev or board number? I just did a test on my LW3 mentioned a few posts above and there was no problem. Would be really nice if someone could provide a logic analyser recording from a NOT working game.
(sorry game rom version is given already = 2.0, my test was done with 2.08 and it works)

#1850 3 months ago

Another thing you could try: flash a different debug version of the MCU firmware. Since 1.39 there is an extra flashing possibility for the MCU firmware. This could be used to flash one or more testing versions with a different timing. I can prepare something tomorrow, maybe this helps to shed some light on the problem.

Promoted items from the Pinside Marketplace
$ 18.95
$ 93.00
Lighting - Interactive
ArcadeMade
$ 49.00
Playfield - Toys/Add-ons
Lermods
$ 85.00
Cabinet - Other
Pinball Haus
$ 65.00
Playfield - Toys/Add-ons
G-Money Mods
From: $ 27.00
Boards
KAHR.US Circuits
There are 1,864 posts in this topic. You are on page 37 of 38.

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!