9 replies to this topic

[mb944]

Hi there!

I'm currently working on an exciting new midi project: A PINBALL(see photos)

I haven't a clue with Pic programming so I'm only using the Mios hardware as an IO inteface between a VISUAL BASIC application and the pinball hardware.

The pic is loaded with the default midi128 firmware.

Here's the pogress so far:

DAY ONE:
built a DIN and connected all 38 triggers to it, ran the ball through them, Visual basic registered all the NOTE ON messages.
that made my day!  ;)

DAY TWO:
Made a Dout vectorboard and connected 25 Leds to It, programmed a simple sequence of consecutive lights:
YES YES YES  ;D that had me dancing
Ok, not much talent envolved here but its my first DOUT and It worked first go!

unfortunately, when I took a closer look at sequencing, it noticed that the leds are being a bit random:
Sometimes they come on, sometimes they just flicker on then stay off
Sometimes when I light 10 leds, the 11th simply cuts off the 10 others

Maybe I need to change the software config?
My visual basic app handles midi in 3 decimals  (MESSAGE; DATA1; DATA2)

I've therefore been using the folowing code the light a led:

144; 64; 1; (meaning NOTE ON; PIN 64; velocity 1)
as i said, it will come on, But not allways first time, and if I loop the message,
It will eventually turn off again, back on, flicker etc.

Is there another decimal value other than 144 that would work better? does it toggle by default?

I thought that My visual basic software might be unaccurate, but I have already used it in other situations
and it worked flawlessly Millisecond precise.

i know something needs changing in the software anyway because at the moment,
the din pin trigger their respective Dout pins, and i only wont them to send midi out.

This project is definitley great fun, But I dont want to ruin it because of unaccurate Dout,
especialy the next step being 25v solenoid coils on relays. I can't afford to burn them out because of a "sticky" pin >:(



By the way, I'm supplying 9VDC at 500 mA to the core, could this be the problem?


Thanks in advance for your interest in my project and for any advice with configuring the software.
Best regards,
Alex



above: playfield before

above: playfield after (still needs touching up, plastics and decals)

above: See the midibox? ;D

above: nice rotating element

above: theres that core!

[smashtv]

Ahhhh!  Having flashbacks........  ;)

[TK.]

Hi mb944,

what a fancy project!

I just have tested MIDIO128 on my MIDIbox SEQ and noticed exactly the same behaviour. This shocked me a little, because I don't remember that this problem occured during the implementation of the last changes. After some debugging I finally found out that in app_defines.inc the "MB_STAT_FETCH_DIN_REQ" flag is assigned to the same bit like "MB_STAT_DISPLAY_UPDATE_REQ" (a totally unexpected error) and this causes the flickering.

So, when you change this flag to 1 and recompile the code, it will work.

It will also work when you set the "DEFAULT_FORWARD_IO" option to 0 in main.asm (you have to do this anyhow), thats possibly the reason why there were no complaints about this error in the past, because most people don't use the forwarding option, this is only for testing the DINs/DOUTs

Ok, and I found out why I never saw this problem: it was one of the last changes which I've tested on my MIDIbox LC which has a graphical display. Since characters are printed out slower than on a common LCD, the possibility that the wrong bit assignment affects the DOUT is much lower

Best Regards, Thorsten.

[moebius]

I think saw something, that was resembling a cow flyin'

Was it like a 3rd unknow bug around MIOS / ported APPS..

Now TK,

Would you mind being nominated for a SynthDIY Soddy? And to not break the rules, what would you consider as your favourite MB release for the Year 2004?

Bye, Moebius

[TK.]

Would you mind being nominated for a SynthDIY Soddy?

*grin* just compare the number of code lines against the number of bugs ;-)

The only thing which makes me worry each time is that now we will notice an increased number of postings where people assume software bugs before they start to check their hardware. From my experience it will take 3-4 months until MIOS applications have reached the known confidence level again ;-)

And to not break the rules, what would you consider as your favourite MB release for the Year 2004?

There are too much favourite MBs in the different categories, but last year no MIDIbox reached the originality of PulseBox16 (for the guys who don't remember the best design ever, here the design: http://homepage.ntlw...on/pb16--ad.jpg and here what the press said: http://homepage.ntlw...midibox_mag.jpg)

Best Regards, Thorsten.

[TK.]

Just gone through the synth-diy mailings, now it's clear what you mean with "SynthDIY Soddy" - I mixed it with "shoddy" ;-)

Best Regards, Thorsten.

[mb944]

thanks for the info Tk!
I'll get activeperl downloaded and recompile

best regards,
Alex

[mb944]

Hey Tk!
Dont want you to think I was doubting the quality of your app!! Trust, me i have tried loads of leds before asking  ;)
obviously, i was convinced it was a hardware problem at first!

You told me to change the flag in the app_defines.inc file, but he zip I downloaded contains app_defines.h
Should I rename this extension?
Thanks in avance, and cheer up, your work is the best in my opinion,
All my friends are hooked on midiboxing, its a crazy thing!

best regards,
Alex

[TK.]

Thanks

app_defines.h is the right name, don't rename it, otherwise you are not able to build the project anymore

Best Regards, Thorsten.

[airmailed]

this is from the pd-announce list.. it is not me..  the address of the creator is at the bottom of the post
----------------------------------------------------------------


Hi all,

Tomorrow, there will be the first public showing of my pinball machine
project.

venue : Tent, CBK (visual arts center for Rotterdam)
adress: Witte de Withstraat 50
Rotterdam, Netherlands
time : 20:30 starting time
http://www.tentplaza.nl is their official site,
warning: this is a very artistic flash site (and not up to date)
taking over
your entire screen.
The presentation is part of an evening with various Berlin Artists, and
a
beerstube with bratwurst.

ABOUT:
A slightly modified and repainted pinball machine (a 1992 DataEast) is
hooked
up to a computer running linux, effectively replacing the soundcard of
the
pinball machine.

In this first presentation, the sounds are generated by csound and the
composition controlled by pd interpreting the many codes it receives
from the
pinball machine in sometimes surprising ways.
A play costs a Euro, and for that price you get your very own
interactive
concert of contemporary electronic music and a chance to win another
round,
or to enter your initials or to play the fabulous multiball mode.


FUTURE:
I would like to invite other composers to write pieces for pinball
machine.
Stay tuned for further announcements about this.

ciao

gerard

--
electronic & acoustic musics-- http://www.xs4all.nl/~gml