Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Thread

Re: [analogue-sequencer] Re: case and midi

Re: [analogue-sequencer] Re: case and midi

2004-07-22 by Colin f

> but i still get no signal @ midi out
> is there any self test function on the p3?
> the midi clock is turned on!

The midi out pin 4 is connected to the 5v supply via a 220R resistor.
Pin 2 is 0v direct. Pin 5 connects to the serial output pin on the CPU via
another 220R resistor.
With 'mclk' set to 'on', you should see regular pulses at the midi output
pin 5. The midi output is designed to drive an LED (inside an opto-isolator)
so you can connect an LED between pin 4 and 5 to test it (anode to pin 4).
With the tempo turned up high, the clock bytes should be enough to light the
LED dimly.
If you don't see pulses there, check on the CPU pin itself - it's pin 11.
You can probably use an LED to test the CPU pin too. If you see pulses at
the CPU pin, but not the output, check the 220R resistor, the output socket
and the tracks and solder joints between. Check your ribbon cable is crimped
into the IDC plug correctly too.
If you don't see anything at the CPU output pin, remove the resistor to make
sure it isn't being pulled high or low by a short somewhere. If you see
nothing at the CPU pin with nothing else connected to it, the output could
be fried. If you return the CPU to me, I'll test it and send you a
replacement.

Cheers,
Colin f



________________________________________________
Message sent using UebiMiau 2.7.2

Re: [analogue-sequencer] Re: case and midi

2004-07-22 by MAG

thanks for the tips, i gonna test it after work! 
(bad work, can't concetrate, want to fix my p3....) 

Colin f <colin@colinfraser.com> wrote:
> but i still get no signal @ midi out
> is there any self test function on the p3?
> the midi clock is turned on!

The midi out pin 4 is connected to the 5v supply via a 220R resistor.
Pin 2 is 0v direct. Pin 5 connects to the serial output pin on the CPU via
another 220R resistor.
With 'mclk' set to 'on', you should see regular pulses at the midi output
pin 5. The midi output is designed to drive an LED (inside an opto-isolator)
so you can connect an LED between pin 4 and 5 to test it (anode to pin 4).
With the tempo turned up high, the clock bytes should be enough to light the
LED dimly.
If you don't see pulses there, check on the CPU pin itself - it's pin 11.
You can probably use an LED to test the CPU pin too. If you see pulses at
the CPU pin, but not the output, check the 220R resistor, the output socket
and the tracks and solder joints between. Check your ribbon cable is crimped
into the IDC plug correctly too.
If you don't see anything at the CPU output pin, remove the resistor to make
sure it isn't being pulled high or low by a short somewhere. If you see
nothing at the CPU pin with nothing else connected to it, the output could
be fried. If you return the CPU to me, I'll test it and send you a
replacement.

Cheers,
Colin f



________________________________________________
Message sent using UebiMiau 2.7.2





Yahoo! Groups Links






		
---------------------------------
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.

[Non-text portions of this message have been removed]

Re: [analogue-sequencer] Re: case and midi

2004-07-22 by MAG

hi
i've tested everything like you described, it seems to work.
but after i connected it to the midiox and pushed play, 
i didn't get any message (also ^not when connected to a unitor8+logic audio)
 
its confusing 'coz when i put a led into the plug and turn
the tempo knop it gets brighter and darker.
 
the plaroty the resistor everything seems to work correct, but still
no midi data....
 
do i have to configure something other in the p3, 
how can i check if there is a problem with the software?
 


Colin f <colin@colinfraser.com> wrote:
> but i still get no signal @ midi out
> is there any self test function on the p3?
> the midi clock is turned on!

The midi out pin 4 is connected to the 5v supply via a 220R resistor.
Pin 2 is 0v direct. Pin 5 connects to the serial output pin on the CPU via
another 220R resistor.
With 'mclk' set to 'on', you should see regular pulses at the midi output
pin 5. The midi output is designed to drive an LED (inside an opto-isolator)
so you can connect an LED between pin 4 and 5 to test it (anode to pin 4).
With the tempo turned up high, the clock bytes should be enough to light the
LED dimly.
If you don't see pulses there, check on the CPU pin itself - it's pin 11.
You can probably use an LED to test the CPU pin too. If you see pulses at
the CPU pin, but not the output, check the 220R resistor, the output socket
and the tracks and solder joints between. Check your ribbon cable is crimped
into the IDC plug correctly too.
If you don't see anything at the CPU output pin, remove the resistor to make
sure it isn't being pulled high or low by a short somewhere. If you see
nothing at the CPU pin with nothing else connected to it, the output could
be fried. If you return the CPU to me, I'll test it and send you a
replacement.

Cheers,
Colin f



________________________________________________
Message sent using UebiMiau 2.7.2





Yahoo! Groups Links






		
---------------------------------
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!

[Non-text portions of this message have been removed]

RE: [analogue-sequencer] Re: case and midi

2004-07-22 by Colin f

> i've tested everything like you described, it seems to work.
> but after i connected it to the midiox and pushed play, 
> i didn't get any message (also ^not when connected to a unitor8+logic
audio)

Have you got system realtime filtering on ? Can you see the midi clock
bytes ?

> its confusing 'coz when i put a led into the plug and turn
> the tempo knop it gets brighter and darker.
>  
> the plaroty the resistor everything seems to work correct, but still
> no midi data....
>  
> do i have to configure something other in the p3, 
> how can i check if there is a problem with the software?

The easiest way to generate midi data is to press the 'tune' softkey
with some tracks active - regardless of whether you've entered any
pattern data, that will send some note ons.

Cheers,
Colin f

RE: [analogue-sequencer] Re: case and midi

2004-07-23 by MAG

i cant see the midi clock bytes. i did the tune thing but still no midi bytes.
so i connected a korg drum machine to midi input, selected the menu for
midi thru 'any' , connected the output to my computer but still nothing.
i doesn't even eat a midi clock from an external instrument.
 
system realtime filtering?
 
confusing is that there seems to be data sent thru the midi port (led test),
but possibly not midi data. i showed the circuit to a friend, he was lookin if everthing
is soldered right and he told me that everthing should work from the hardware site.
 
is it because there are some chips faster than wanted?
could it be the programm on CPU.
any more tips?
 
:-) :-( :-) :-(

Colin f <colin@colinfraser.com> wrote:
> i've tested everything like you described, it seems to work.
> but after i connected it to the midiox and pushed play, 
> i didn't get any message (also ^not when connected to a unitor8+logic
audio)

Have you got system realtime filtering on ? Can you see the midi clock
bytes ?

> its confusing 'coz when i put a led into the plug and turn
> the tempo knop it gets brighter and darker.
> 
> the plaroty the resistor everything seems to work correct, but still
> no midi data....
> 
> do i have to configure something other in the p3, 
> how can i check if there is a problem with the software?

The easiest way to generate midi data is to press the 'tune' softkey
with some tracks active - regardless of whether you've entered any
pattern data, that will send some note ons.

Cheers,
Colin f








Yahoo! Groups Links






		
---------------------------------
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!

[Non-text portions of this message have been removed]

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.