jOrgan

A request.

I made a Hammond style organ. I'd like to be able to store the setting of a
continuous filter (drawbar) as a combination. I've also got some ideas about
how this feature might be useful also in classical style organs. I've made
organs with adjustable volume on each stop-- those settings could be
altered, adjusted, and saved.

Paul

Also-- is there a MIDI code for reverb?

On Mon, Jun 16, 2008 at 3:38 PM, Sven Meier <sven@...> wrote:

> Hi all,
>
> I've uploaded the first beta release of jOrgan 3.3.
>
> - Combination and Incrementer are now Switches.
> - I dropped the Sequence element, its functionality is now included in the
> Regulator element.
> - Changes of Regulators are now handled with improved performance.
>
> I updated the documentation on http://jorgan.sourceforge.net/disposition .
>
> Everything should work out of the box, your dispositions will automatically
> be converted.
> You'll have to download new versions of all Skins though.
>
> I'm not sure where we are heading with 3.3, but hopefully the changes will
> show us new possibilities for our SAMs solutions.
> Perhaps we might even see lighted-up pistons in the future ;).
>
> Have fun
>
> Sven
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>



-- 
__________________________________
Pastor Paul C. Stratman
St. Stephen's Ev. Lutheran Church (WELS)
Beaver Dam, Wisconsin
http://www.saintstephen.org
pastorstratman@...
pcstratman@...

NOW YOU'RE TALKING!!!

On Mon, Jun 16, 2008 at 3:38 PM, Sven Meier wrote:
<SNIP>

I'm not sure where we are heading with 3.3, but hopefully the changes will show us new possibilities for our SAMs solutions.

Perhaps we might even see lighted-up pistons in the future ;).

Have fun
<SNIP>

Hello Paul.

currently combinations can only capture the active state of switches. I 
agree that it would be nice, if  the value of continuous elements 
(regulators, continuous filters) could 'captured' too.

As always: I'm not sure when I'll be able to implement this though ;).

Regards

Sven

Paul Stratman schrieb:
> A request.
>
> I made a Hammond style organ. I'd like to be able to store the setting 
> of a continuous filter (drawbar) as a combination. I've also got some 
> ideas about how this feature might be useful also in classical style 
> organs. I've made organs with adjustable volume on each stop-- those 
> settings could be altered, adjusted, and saved.
>
> Paul
>
> Also-- is there a MIDI code for reverb?
>
> On Mon, Jun 16, 2008 at 3:38 PM, Sven Meier <sven@... 
> <mailto:sven@...>> wrote:
>
>     Hi all,
>
>     I've uploaded the first beta release of jOrgan 3.3.
>
>     - Combination and Incrementer are now Switches.
>     - I dropped the Sequence element, its functionality is now
>     included in the Regulator element.
>     - Changes of Regulators are now handled with improved performance.
>
>     I updated the documentation on
>     http://jorgan.sourceforge.net/disposition .
>
>     Everything should work out of the box, your dispositions will
>     automatically be converted.
>     You'll have to download new versions of all Skins though.
>
>     I'm not sure where we are heading with 3.3, but hopefully the
>     changes will show us new possibilities for our SAMs solutions.
>     Perhaps we might even see lighted-up pistons in the future ;).
>
>     Have fun
>
>     Sven
>
>
>     -------------------------------------------------------------------------
>     Check out the new SourceForge.net Marketplace.
>     It's the best place to buy or sell services for
>     just about anything Open Source.
>     http://sourceforge.net/services/buy/index.php
>     _______________________________________________
>     jOrgan-user mailing list
>     jOrgan-user@...
>     <mailto:jOrgan-user@...>
>     https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>
>
>
> -- 
> __________________________________
> Pastor Paul C. Stratman
> St. Stephen's Ev. Lutheran Church (WELS)
> Beaver Dam, Wisconsin
> http://www.saintstephen.org
> pastorstratman@... <mailto:pastorstratman@...>
> pcstratman@... <mailto:pcstratman@...>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

Hi all,

I've smashed two bugs in beta2, now downloadable from:

   http://sourceforge.net/project/showfiles.php?group_id=124803

Have fun

Sven

Sven Meier schrieb:
> Hi all,
>
> I've uploaded the first beta release of jOrgan 3.3.
>
> - Combination and Incrementer are now Switches.
> - I dropped the Sequence element, its functionality is now included in 
> the Regulator element.
> - Changes of Regulators are now handled with improved performance.
>
> I updated the documentation on 
> http://jorgan.sourceforge.net/disposition .
>
> Everything should work out of the box, your dispositions will 
> automatically be converted.
> You'll have to download new versions of all Skins though.
>
> I'm not sure where we are heading with 3.3, but hopefully the changes 
> will show us new possibilities for our SAMs solutions.
> Perhaps we might even see lighted-up pistons in the future ;).
>
> Have fun
>
> Sven
>
>

Has anyone yet figured out how to use jorgan to operate lighted pushbutton
SAMS????? My old combination action is getting complicated and overloaded.
It has about 2,000,188 physical wires (seems like).
Don Becker
-- 
View this message in context: http://n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p1556654.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Does anyone on the forum have multiple soundcards installed on a Windows 7 
system?   I am trying to install two X-Fi soundcards, an Xtreme Music
and a Titanium Pro and, so far, have had success with only one of the cards 
being installed and operative.  The correct drivers are installed for both, 
but
the Titanium Pro (which was functioning perfectly when alone)  "can not 
start"  when the Xtreme Music is installed.

Is there a workaround for this or is this an OS limitation for which there 
is none?

Thanks,
John Beach

Just to clarify: it is the "stops" you have "Lit" (not the pistons).

I believe jOrgan already sends out messages that Midi hardware like 
MidiBox MIDIO128 system DOUT cards would convert to an electronic signal 
to drive LED's, when a stop is active.
My understanding of the new "SAM's" extension is to put a "time-out" 
function on to it, so it doesn't burn out the magnetic coils of SAM's.
I think you want your stop LED's to stay on till the stop is no longer 
active, so would not want to set a time-out value.

I might be wrong, but this seems to me to be easy to achieve.

Regards
Rick

Don Becker wrote:
> Has anyone yet figured out how to use jorgan to operate lighted pushbutton
> SAMS????? My old combination action is getting complicated and overloaded.
> It has about 2,000,188 physical wires (seems like).
> Don Becker
>

Was this intended to read, "jOrgan 3.9 Beta 3"? or am I missing something?
-- 
View this message in context: http://n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p1556915.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

CDDu wrote
>Was this intended to read, "jOrgan 3.9 Beta 3"? or am I missing something?

Yes, you are.
Look at the date of the first post in this thread.

John Reimer
-- 
View this message in context: http://n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p1557844.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

I don't have LEDs. I have incandescent blubs that draw 50ma ea. I have a
pushbutton switch for "on"  and a pushbutton switch for "off".for each stop
(250  stops). It would be really nice at this point if I could use my jorgan
disposition for the combination action. Its getting pretty cumbersome with
all the wires and cables.
Thanks,
Don Becker
-- 
View this message in context: http://n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p1558074.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hi Don

What hardware do you use to convert your switches to Midi messages?
Do you have hardware that could read the Midi output from jOrgan and 
convert to transistor driven outputs?

The http://www.uCapps.de  MidiBox MIDIO128 system will cover all the hardware 
you would need to link to jOrgan to do what you are looking for at a 
very low cost.

Regards
Rick

Don Becker wrote:
> I don't have LEDs. I have incandescent blubs that draw 50ma ea. I have a
> pushbutton switch for "on"  and a pushbutton switch for "off".for each stop
> (250  stops). It would be really nice at this point if I could use my jorgan
> disposition for the combination action. Its getting pretty cumbersome with
> all the wires and cables.
> Thanks,
> Don Becker
>

Don, 
I'd love to hear more about your application.
I'm seeking to operate both SAMS and pipes,
and what your project entails may be a solution
to the problems I face. 

I'd love more details, off-list is probably best, since
most folks tell me what I seek is beyond the capabilities 
of j-Organ, but I will persist until I have pipes and SAMS
on the 260 organ and pipes and LED indicators above the
stoptabs and within the pistons for blind registrations
on the 216.  (just a few ranks of pipes, since most my
ranks are MIDIfied soundfonts)  H e l p!

PK
StentorVox.com



--- On Mon, 2/15/10, Don Becker <soniccr@...> wrote:

From: Don Becker <soniccr@...>
Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Monday, February 15, 2010, 1:30 PM

Has anyone yet figured out how to use jorgan to operate 
lighted pushbutton SAMS????? My old combination action 
is getting complicated and overloaded.
It has about 2,000,188 physical wires (seems like).
Don Becker

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
If discussion goes off-list I for one am keen to follow. I suspect
there are others. I'm a newcomer here but this discussion seems to fit
as well as a lot of the recent activity.<br>
<br>
I too have no hardware to make stops move of their own accord or lights
light. I'm investigating batteries, big capacitors, automotive relays,
etc., and keeping an eye on discussions like this that will shed light
on a mystery to me.<br>
<br>
I have this board<br>
&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-freetext" href="http://www.midi-hardware.com/litsw.html">http://www.midi-hardware.com/litsw.html</a><br>
which purports to be able to handle the lighting side, but I currently
have no lights to light with it (some new lighted pistons I hope are in
my near future). And its 3ma aren't going to activate my SAMs.<br>
<br>
Cheers,<br>
Matt<br>
<br>
<br>
Paul Kealy wrote:
<blockquote cite="mid:690892.44917.qm@..."
 type="cite">
  <table border="0" cellpadding="0" cellspacing="0">
    <tbody>
      <tr>
        <td
 style="font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit;"
 valign="top">Don, <br>
I'd love to hear more about your application.<br>
I'm seeking to operate both SAMS and pipes,<br>
and what your project entails may be a solution<br>
to the problems I face. <br>
        <br>
I'd love more details, off-list is probably best, since<br>
most folks tell me what I seek is beyond the capabilities <br>
of j-Organ, but I will persist until I have pipes and SAMS<br>
on the 260 organ and pipes and LED indicators above the<br>
stoptabs and within the pistons for blind registrations<br>
on the 216.&nbsp; (just a few ranks of pipes, since most my<br>
ranks are MIDIfied soundfonts)&nbsp; H e l p!<br>
        <br>
PK<br>
StentorVox.com<br>
        <br>
        <br>
        <br>
--- On <b>Mon, 2/15/10, Don Becker <i><a class="moz-txt-link-rfc2396E" href="mailto:soniccr@...>
wrote:<br>
        <br>
From: Don Becker <a class="moz-txt-link-rfc2396E" href="mailto:soniccr@...>
Subject: Re: [jOrgan-user] SAMS and lighted pistons<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:jorgan-user@...>
Date: Monday, February 15, 2010, 1:30 PM<br>
        <br>
Has anyone yet figured out how to use jorgan to operate <br>
lighted pushbutton SAMS????? My old combination action <br>
is getting complicated and overloaded.<br>
It has about 2,000,188 physical wires (seems like).<br>
Don Becker<br>
        <br>
        </td>
      </tr>
    </tbody>
  </table>
  <br>
  <pre wrap="">
<hr size="4" width="90%">
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/solaris-dev2dev">http://p.sf.net/sfu/solaris-dev2dev</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
jOrgan-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jOrgan-user@...>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/jorgan-user">https://lists.sourceforge.net/lists/listinfo/jorgan-user</a>
  </pre>
</blockquote>
</body>
</html>

Don,

In jOrgan, I would think you would be able to turn the lamps on and  
off with the "Activiated" and "Deactivated" messages coming from a  
stop.  You could do the same with "Activate" and "Deactivate" to make  
the stop respond to the two pushbuttons.  You could drive the lamps  
with any midi output system.  If you went the MIDIBox route, you  
would probably use the MIDIO128 project, as Rick said.  You could use  
ULN2803 or UDN2981 transistor arrays to drive the lamps.

-Trevor

On Feb 16, 2010, at 6:25 PM, Don Becker wrote:

>
> I don't have LEDs. I have incandescent blubs that draw 50ma ea. I  
> have a
> pushbutton switch for "on"  and a pushbutton switch for "off".for  
> each stop
> (250  stops). It would be really nice at this point if I could use  
> my jorgan
> disposition for the combination action. Its getting pretty  
> cumbersome with
> all the wires and cables.
> Thanks,
> Don Becker
> -- 
> View this message in context: http://n4.nabble.com/jOrgan-3-3-first- 
> beta-tp1001907p1558074.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------- 
> --------
> SOLARIS 10 is the OS for Data Centers - provides features such as  
> DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Paul,

I have both SAMs and pipes (swell shutters/percussions/traps too)  
operating through jOrgan.  Everything you're trying to do should be a  
piece of cake!

I haven't had time to try jOrgan's new SAMs feature yet, but I do  
have SAMs operating through a little app I threw together.  Here are  
a couple of videos showing some of the capabilities of jOrgan with a  
TPO.

http://www.youtube.com/watch?v=0eVfj6QGiUg
http://www.youtube.com/watch?v=lFnQUluP-d8

-Trevor

On Feb 16, 2010, at 10:31 PM, Paul Kealy wrote:

> Don,
> I'd love to hear more about your application.
> I'm seeking to operate both SAMS and pipes,
> and what your project entails may be a solution
> to the problems I face.
>
> I'd love more details, off-list is probably best, since
> most folks tell me what I seek is beyond the capabilities
> of j-Organ, but I will persist until I have pipes and SAMS
> on the 260 organ and pipes and LED indicators above the
> stoptabs and within the pistons for blind registrations
> on the 216.  (just a few ranks of pipes, since most my
> ranks are MIDIfied soundfonts)  H e l p!
>
> PK
> StentorVox.com
>
>
>
> --- On Mon, 2/15/10, Don Becker <soniccr@...> wrote:
>
> From: Don Becker <soniccr@...>
> Subject: Re: [jOrgan-user] SAMS and lighted pistons
> To: jorgan-user@...
> Date: Monday, February 15, 2010, 1:30 PM
>
> Has anyone yet figured out how to use jorgan to operate
> lighted pushbutton SAMS????? My old combination action
> is getting complicated and overloaded.
> It has about 2,000,188 physical wires (seems like).
> Don Becker
>
>
> ---------------------------------------------------------------------- 
> --------
> SOLARIS 10 is the OS for Data Centers - provides features such as  
> DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris- 
> dev2dev_______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Yes, please keep it on the list as I will be using jOrgan to also 
control a small pipe organ.

Thanks, Russ

--- On Tue, 2/16/10, Matt Pestle <matt.pestle@...> wrote:

> From: Matt Pestle <matt.pestle@...>
> Subject: Re: [jOrgan-user] SAMS and lighted pistons
> To: jorgan-user@...
> Date: Tuesday, February 16, 2010, 8:23 PM
> 
> 
> 
>   
>   
> 
>  
> If discussion goes off-list I for one am keen to follow. I
> suspect
> there are others. I'm a newcomer here but this
> discussion seems to fit
> as well as a lot of the recent activity.
> 
> 
> 
> I too have no hardware to make stops move of their own
> accord or lights
> light. I'm investigating batteries, big capacitors,
> automotive relays,
> etc., and keeping an eye on discussions like this that will
> shed light
> on a mystery to me.
> 
> 
> 
> I have this board
> 
>     http://www.midi-hardware.com/litsw.html
> 
> which purports to be able to handle the lighting side, but
> I currently
> have no lights to light with it (some new lighted pistons I
> hope are in
> my near future). And its 3ma aren't going to activate
> my SAMs.
> 
> 
> 
> Cheers,
> 
> Matt
> 
> 
> 
> 
> 
> Paul Kealy wrote:
> 
>   
>     
>       
>         Don, 
> 
> I'd love to hear more about your application.
> 
> I'm seeking to operate both SAMS and pipes,
> 
> and what your project entails may be a solution
> 
> to the problems I face. 
> 
>         
> 
> I'd love more details, off-list is probably best,
> since
> 
> most folks tell me what I seek is beyond the capabilities 
> 
> of j-Organ, but I will persist until I have pipes and SAMS
> 
> on the 260 organ and pipes and LED indicators above the
> 
> stoptabs and within the pistons for blind registrations
> 
> on the 216.  (just a few ranks of pipes, since most
> my
> 
> ranks are MIDIfied soundfonts)  H e l p!
> 
>         
> 
> PK
> 
> StentorVox.com
> 
>         
> 
>         
> 
>         
> 
> --- On Mon, 2/15/10, Don Becker <soniccr@...>
> wrote:
> 
>         
> 
> From: Don Becker <soniccr@...>
> 
> Subject: Re: [jOrgan-user] SAMS and lighted pistons
> 
> To: jorgan-user@...
> 
> Date: Monday, February 15, 2010, 1:30 PM
> 
>         
> 
> Has anyone yet figured out how to use jorgan to operate 
> 
> lighted pushbutton SAMS????? My old combination action 
> 
> is getting complicated and overloaded.
> 
> It has about 2,000,188 physical wires (seems like).
> 
> Don Becker
> 
>         
> 
>         
>       
>     
>   
>   
> 
>   
> 
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features
> such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris
> 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
>   
> 
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>   
> 
>  
> 
> 
> 
> -----Inline Attachment Follows-----
> 
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features
> such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris
> 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

Yes, I think all the discussion should stay on the list.  Now that Sven 
has incorporated the SAM's extension I think he will be keen have 
feedback from real applications communicating with consoles.

I don't think there should be any issue driving real pipes.  I think you 
could use the Generic Sound module to send Midi messages to uCapps 
MidiBox MIDIO128 cards and add current drivers as required to drive the 
solenoids.

Regards
Rick

RUSSELL P DOERING wrote:
> Yes, please keep it on the list as I will be using jOrgan to also 
> control a small pipe organ.
>
> Thanks, Russ
>
> --- On Tue, 2/16/10, Matt Pestle <matt.pestle@...> wrote:
>
>   
>> From: Matt Pestle <matt.pestle@...>
>> Subject: Re: [jOrgan-user] SAMS and lighted pistons
>> To: jorgan-user@...
>> Date: Tuesday, February 16, 2010, 8:23 PM
>>
>>
>>
>>   
>>   
>>
>>  
>> If discussion goes off-list I for one am keen to follow. I
>> suspect
>> there are others. I'm a newcomer here but this
>> discussion seems to fit
>> as well as a lot of the recent activity.
>>
>>
>>
>> I too have no hardware to make stops move of their own
>> accord or lights
>> light. I'm investigating batteries, big capacitors,
>> automotive relays,
>> etc., and keeping an eye on discussions like this that will
>> shed light
>> on a mystery to me.
>>
>>
>>
>> I have this board
>>
>>     http://www.midi-hardware.com/litsw.html
>>
>> which purports to be able to handle the lighting side, but
>> I currently
>> have no lights to light with it (some new lighted pistons I
>> hope are in
>> my near future). And its 3ma aren't going to activate
>> my SAMs.
>>
>>
>>
>> Cheers,
>>
>> Matt
>>
>>
>>
>>
>>
>> Paul Kealy wrote:
>>
>>   
>>     
>>       
>>         Don, 
>>
>> I'd love to hear more about your application.
>>
>> I'm seeking to operate both SAMS and pipes,
>>
>> and what your project entails may be a solution
>>
>> to the problems I face. 
>>
>>         
>>
>> I'd love more details, off-list is probably best,
>> since
>>
>> most folks tell me what I seek is beyond the capabilities 
>>
>> of j-Organ, but I will persist until I have pipes and SAMS
>>
>> on the 260 organ and pipes and LED indicators above the
>>
>> stoptabs and within the pistons for blind registrations
>>
>> on the 216.  (just a few ranks of pipes, since most
>> my
>>
>> ranks are MIDIfied soundfonts)  H e l p!
>>
>>         
>>
>> PK
>>
>> StentorVox.com
>>
>>         
>>
>>         
>>
>>         
>>
>> --- On Mon, 2/15/10, Don Becker <soniccr@...>
>> wrote:
>>
>>         
>>
>> From: Don Becker <soniccr@...>
>>
>> Subject: Re: [jOrgan-user] SAMS and lighted pistons
>>
>> To: jorgan-user@...
>>
>> Date: Monday, February 15, 2010, 1:30 PM
>>
>>         
>>
>> Has anyone yet figured out how to use jorgan to operate 
>>
>> lighted pushbutton SAMS????? My old combination action 
>>
>> is getting complicated and overloaded.
>>
>> It has about 2,000,188 physical wires (seems like).
>>
>> Don Becker
>>
>>         
>>
>>         
>>       
>>     
>>   
>>   
>>
>>   
>>
>> ------------------------------------------------------------------------------
>> SOLARIS 10 is the OS for Data Centers - provides features
>> such as DTrace,
>> Predictive Self Healing and Award Winning ZFS. Get Solaris
>> 10 NOW
>> http://p.sf.net/sfu/solaris-dev2dev
>>   
>>
>> _______________________________________________
>> jOrgan-user mailing list
>> jOrgan-user@...
>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>>   
>>
>>  
>>
>>
>>
>> -----Inline Attachment Follows-----
>>
>> ------------------------------------------------------------------------------
>> SOLARIS 10 is the OS for Data Centers - provides features
>> such as DTrace,
>> Predictive Self Healing and Award Winning ZFS. Get Solaris
>> 10 NOW
>> http://p.sf.net/sfu/solaris-dev2dev
>> -----Inline Attachment Follows-----
>>
>> _______________________________________________
>> jOrgan-user mailing list
>> jOrgan-user@...
>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>>
>>     
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>

Trevor,
Great news - can hardly wait to follow up on your applications.
More later!   :>)
PK
StentorVox

--- On Tue, 2/16/10, Trevor  <oddrocketboy> wrote:

<snip>
Paul,I
have both SAMs and pipes (swell shutters/percussions/traps too)

operating through jOrgan.  
Everything you're trying to do should be a
piece of cake!I haven't had time to try
jOrgan's new SAMs feature yet, 
but I do have SAMs operating through a
little app I threw together.  
Here are a couple of videos showing some
of the capabilities of 
jOrgan with a TPO.http://www.youtube.com/watch?v=0eVfj6QGiUghttp://www.youtube.com/watch?v=lFnQUluP-d8<snip>

Hi Paul, Matt, Trevor, Russell, Rick and Doug,
What a great response to my combo-action problem! My combo-action turns a
MIDI note on and off for each stop. It gets the MIDI signal from "Activate
and deactivate" from my disposition (its only half finished and is written
using jorgan 2.4, a much simpler jorgan version to work with, at least for
me). There are xstr drivers for a 5VDC lamp output for each stop also. BUT,
this combo-action (mfg by Sonic Creations in the 1990s, I was one of the
co-owners) is really big and cumbersome. I only have 64 stops working so far
and wiring the rest of it seems daunting. My organ is a good practice organ
even with its unfinishedness. It has 3 manuals, AGO pedals, I built it, it
has 8 jambs, space for 256 stopswitch sets, 64 lighted stops so far (but I
have all the hardware and jambs done except for some still to do assembly
work). I have only engraved (I have a Scott engraving set but each stop
takes 10-20 minutes to engrave) 64 stops so far. I'm using 4 Soundblaster
Live SB0220 (using Kx drivers) soundcards in a computer I built with an
Athlon X2 on a Gigabyte motherboard. I use 10 channels of sound + 2 reverb
channels (an old Peavey Ultraverb). I'd really like to use a convolution
reverb but haven't yet figured out vst hosts and how to use them. I do have
lots of magnet driver boards left over from years ago. They utilize UDN2982A
chips. I need to figure out how to use them to drive the lights. I'M OPEN TO
SUGGESTIONS and will also gladly give a helping hand to anyone who can use
my help.
There has never been a time when I have had everything working at once
(Anyone else have that experience??)
Don Becker   soniccr@...
-- 
View this message in context: http://n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p1559389.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Paul (and everyone else!),

I have my two latest disposition files available at the bottom of  
this page:

http://www.acmeorgan.com/trevordodd/player.html

Maybe someone can find them helpful?

I also made a better SAM demonstration video today.  That can be  
found here:

http://www.youtube.com/watch?v=28vcTuWDJw8

-Trevor


On Feb 17, 2010, at 9:28 AM, Paul Kealy wrote:

> Trevor,
> Great news - can hardly wait to follow up on your applications.
> More later!   :>)
> PK
> StentorVox
>
> --- On Tue, 2/16/10, Trevor  <oddrocketboy> wrote:
>
> <snip>
> Paul,
> I have both SAMs and pipes (swell shutters/percussions/traps too)
> operating through jOrgan.
> Everything you're trying to do should be a piece of cake!
> I haven't had time to try jOrgan's new SAMs feature yet,
> but I do have SAMs operating through a little app I threw together.
> Here are a couple of videos showing some of the capabilities of
> jOrgan with a TPO.
> http://www.youtube.com/watch?v=0eVfj6QGiUg
> http://www.youtube.com/watch?v=lFnQUluP-d8
> <snip>
>
>
> ---------------------------------------------------------------------- 
> --------
> SOLARIS 10 is the OS for Data Centers - provides features such as  
> DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris- 
> dev2dev_______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi Trevor

You have done a great job of that.  Thank you for sharing.

Regards
Rick

Trevor wrote:
> Paul (and everyone else!),
>
> I have my two latest disposition files available at the bottom of this 
> page:
>
> http://www.acmeorgan.com/trevordodd/player.html
>
> Maybe someone can find them helpful?
>
> I also made a better SAM demonstration video today.  That can be found 
> here:
>
> http://www.youtube.com/watch?v=28vcTuWDJw8
>
> -Trevor
>
>  
> On Feb 17, 2010, at 9:28 AM, Paul Kealy wrote:
>
>> Trevor,
>> Great news - can hardly wait to follow up on your applications.
>> More later!   :>)
>> PK
>> StentorVox
>>
>> --- On *Tue, 2/16/10, Trevor * <oddrocketboy> wrote:
>>
>> <snip>
>> Paul,
>> I have both SAMs and pipes (swell shutters/percussions/traps too)
>> operating through jOrgan. 
>> Everything you're trying to do should be a piece of cake!
>> I haven't had time to try jOrgan's new SAMs feature yet,
>> but I do have SAMs operating through a little app I threw together. 
>> Here are a couple of videos showing some of the capabilities of
>> jOrgan with a TPO.
>> http://www.youtube.com/watch?v=0eVfj6QGiUg
>> http://www.youtube.com/watch?v=lFnQUluP-d8
>> <snip>
>>
>>
>> ------------------------------------------------------------------------------
>> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>> http://p.sf.net/sfu/solaris-dev2dev_______________________________________________
>> jOrgan-user mailing list
>> jOrgan-user@... 
>> <mailto:jOrgan-user@...>
>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Download Intel&reg; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs 
> proactively, and fine-tune applications for parallel performance. 
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ------------------------------------------------------------------------
>
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Now that's just showing off!<br>
<br>
Yes, this is exactly the thing I have in my long term plan to be able
to do and I am well impressed.<br>
<br>
And while you're busy solving all of my
way-in-the-future-hard-problems, do you by any chance have a
disposition, or a little app you threw together, that implements
"programmable pistons" - whereby pushing and holding down say piston
"3", followed by pushing another piston (say the one marked "Prog"),
makes subsequent pushes of piston 3 return all SAMs to the position
they were in when you pressed "Prog"? Or is this functionality already
somewhere in jOrgan that I haven't yet discovered?<br>
<br>
Cheers<br>
<br>
<br>
Trevor wrote:
<blockquote cite="mid:4C6C12D5-71CD-47EC-98CE-4AE2FB311F45@..."
 type="cite">Paul (and everyone else!),
  <div><br>
  </div>
  <div>I have my two latest disposition files available at the bottom
of this page:</div>
  <div><br>
  </div>
  <div><a moz-do-not-send="true"
 href="http://www.acmeorgan.com/trevordodd/player.html">http://www.acmeorgan.com/trevordodd/player.html</a></div>
  <div><br>
  </div>
  <div>Maybe someone can find them helpful?</div>
  <div><br>
  </div>
  <div>I also made a better SAM demonstration video today. &nbsp;That can be
found here:</div>
  <div><br>
  </div>
  <div><a moz-do-not-send="true"
 href="http://www.youtube.com/watch?v=28vcTuWDJw8">http://www.youtube.com/watch?v=28vcTuWDJw8</a></div>
  <div><br>
  </div>
  <div>-Trevor</div>
  <div><br>
  </div>
  <div>&nbsp;</div>
  <div>
  <div>
  <div>On Feb 17, 2010, at 9:28 AM, Paul Kealy wrote:</div>
  <br class="Apple-interchange-newline">
  <blockquote type="cite">
    <table border="0" cellpadding="0" cellspacing="0">
      <tbody>
        <tr>
          <td
 style="font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit;"
 valign="top">Trevor,<br>
Great news - can hardly wait to follow up on your applications.<br>
More later!&nbsp;&nbsp; :&gt;)<br>
PK<br>
StentorVox<br>
          <br>
--- On <b>Tue, 2/16/10, Trevor&nbsp;</b> &lt;oddrocketboy&gt; wrote:<br>
          <br>
&lt;snip&gt;<br>
Paul,
          <div>I have both SAMs and pipes (swell
shutters/percussions/traps too) <br>
operating through jOrgan.&nbsp; <br>
Everything you're trying to do should be a piece of cake!</div>
          <div>I haven't had time to try jOrgan's new SAMs feature yet,
          <br>
but I do have SAMs operating through a little app I threw together.&nbsp; <br>
Here are a couple of videos showing some of the capabilities of <br>
jOrgan with a TPO.</div>
          <div><a moz-do-not-send="true" rel="nofollow" target="_blank"
 href="http://www.youtube.com/watch?v=0eVfj6QGiUg">http://www.youtube.com/watch?v=0eVfj6QGiUg</a></div>
          <div><a moz-do-not-send="true" rel="nofollow" target="_blank"
 href="http://www.youtube.com/watch?v=lFnQUluP-d8">http://www.youtube.com/watch?v=lFnQUluP-d8</a></div>
          <div>&lt;snip&gt;</div>
          <br>
          </td>
        </tr>
      </tbody>
    </table>
    <br>
    <div style="margin: 0px;">------------------------------------------------------------------------------</div>
    <div style="margin: 0px;">SOLARIS 10 is the OS for Data Centers -
provides features such as DTrace,</div>
    <div style="margin: 0px;">Predictive Self Healing and Award Winning
ZFS. Get Solaris 10 NOW</div>
    <div style="margin: 0px;"><a moz-do-not-send="true"
 href="http://p.sf.net/sfu/solaris-dev2dev_______________________________________________">http://p.sf.net/sfu/solaris-dev2dev_______________________________________________</a></div>
    <div style="margin: 0px;">jOrgan-user mailing list</div>
    <div style="margin: 0px;"><a moz-do-not-send="true"
 href="mailto:jOrgan-user@...>
    <div style="margin: 0px;"><a moz-do-not-send="true"
 href="https://lists.sourceforge.net/lists/listinfo/jorgan-user">https://lists.sourceforge.net/lists/listinfo/jorgan-user</a></div>
  </blockquote>
  </div>
  </div>
</blockquote>
</body>
</html>

Matt Pestle wrote:
> Now that's just showing off!
>
> Yes, this is exactly the thing I have in my long term plan to be able 
> to do and I am well impressed.
>
> And while you're busy solving all of my 
> way-in-the-future-hard-problems, do you by any chance have a 
> disposition, or a little app you threw together, that implements 
> "programmable pistons" - whereby pushing and holding down say piston 
> "3", followed by pushing another piston (say the one marked "Prog"), 
> makes subsequent pushes of piston 3 return all SAMs to the position 
> they were in when you pressed "Prog"? Or is this functionality already 
> somewhere in jOrgan that I haven't yet discovered?
>
> Cheers
>
>
> Trevor wrote:
>> Paul (and everyone else!),
>>
>> I have my two latest disposition files available at the bottom of 
>> this page:
>>
>> http://www.acmeorgan.com/trevordodd/player.html
>>
>> Maybe someone can find them helpful?
>>
>> I also made a better SAM demonstration video today.  That can be 
>> found here:
>>
>> http://www.youtube.com/watch?v=28vcTuWDJw8
>>
>> -Trevor
>>
>>  
>> On Feb 17, 2010, at 9:28 AM, Paul Kealy wrote:
>>
>>> Trevor,
>>> Great news - can hardly wait to follow up on your applications.
>>> More later!   :>)
>>> PK
>>> StentorVox
>>>
>>> --- On *Tue, 2/16/10, Trevor * <oddrocketboy> wrote:
>>>
>>> <snip>
>>> Paul,
>>> I have both SAMs and pipes (swell shutters/percussions/traps too)
>>> operating through jOrgan. 
>>> Everything you're trying to do should be a piece of cake!
>>> I haven't had time to try jOrgan's new SAMs feature yet,
>>> but I do have SAMs operating through a little app I threw together. 
>>> Here are a couple of videos showing some of the capabilities of
>>> jOrgan with a TPO.
>>> http://www.youtube.com/watch?v=0eVfj6QGiUg
>>> http://www.youtube.com/watch?v=lFnQUluP-d8
>>> <snip>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> SOLARIS 10 is the OS for Data Centers - provides features such as 
>>> DTrace,
>>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>>> http://p.sf.net/sfu/solaris-dev2dev_______________________________________________
>>> jOrgan-user mailing list
>>> jOrgan-user@... 
>>> <mailto:jOrgan-user@...>
>>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ------------------------------------------------------------------------
>
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>   
I apologise if it seems like showing off. You must realize that there 
are big holes in my knowlege base. I have made jorgan work (like a lot 
of other people) but going on to 3.9 gets so much more complicated. The 
reason I posted in the first place was so that I could get rid of this 
"awful to wire" physical combo-action and use jorgan for the job of 
making the pistons activate and lite the stop lites. Using 2.4 makes it 
so easy to "activate" and "deactivate" stops just using a MIDI note for 
each stop. Its my physical combo-action that makes the combo pistons 
work, not jorgan. The physical combo-action powers the lights and sends 
a 5VDC signal to a MIDI note on one of the MIDI interfaces which 
activates or deactivates a stop in my jorgan disposition. That is what I 
am asking for help with.
If you want to use jorgan to make combo pistons work, you could use the 
same method as making stops work, wire a MIDI note to a physical piston 
(I assume you are talking about real physical pistons??) I would be glad 
to send you my disposition but it doesn't solve the problem you are 
talking about. I use an Intermidi (no longer in business) MIDI interface 
for my 3 keyboards and pedals and 4  61 note Syndyne MIDI interfaces for 
all the stops. The Syndynes can be daisy chained so that you don't have 
to use a MIDI merger to combine them all I do use a MIDI merger to 
combine the Intermidi and Syndye interfaces.
I have found the "Alive" program easy to use to make soundfonts using 
other soundfont voices that already exist.
Don

Thank you, Matt!

You would use a Captor for setting pistons.  In jOrgan, a Captor  
button is locking, since your mouse can only be in one place at one  
time, but in the real organ world, a Captor button is momentary.   
Another thing you should know is that the Captor button is pressed  
before the piston.  If you pressed piston "3" first before pressing  
the Captor, it would recall the previous settings before you'd be  
able to set your new registration.  All you would need to do would be  
to create a Captor, and reference it to your pistons and console!  I  
did this in the Style E disposition with 11 pistons and in the R roll  
disposition with one (General Cancel) piston.

-Trevor

On Feb 18, 2010, at 1:32 PM, Matt Pestle wrote:

> Now that's just showing off!
>
> Yes, this is exactly the thing I have in my long term plan to be  
> able to do and I am well impressed.
>
> And while you're busy solving all of my way-in-the-future-hard- 
> problems, do you by any chance have a disposition, or a little app  
> you threw together, that implements "programmable pistons" -  
> whereby pushing and holding down say piston "3", followed by  
> pushing another piston (say the one marked "Prog"), makes  
> subsequent pushes of piston 3 return all SAMs to the position they  
> were in when you pressed "Prog"? Or is this functionality already  
> somewhere in jOrgan that I haven't yet discovered?
>
> Cheers
>
>
> Trevor wrote:
>>
>> Paul (and everyone else!),
>>
>> I have my two latest disposition files available at the bottom of  
>> this page:
>>
>> http://www.acmeorgan.com/trevordodd/player.html
>>
>> Maybe someone can find them helpful?
>>
>> I also made a better SAM demonstration video today.  That can be  
>> found here:
>>
>> http://www.youtube.com/watch?v=28vcTuWDJw8
>>
>> -Trevor
>>
>>
>> On Feb 17, 2010, at 9:28 AM, Paul Kealy wrote:
>>
>>> Trevor,
>>> Great news - can hardly wait to follow up on your applications.
>>> More later!   :>)
>>> PK
>>> StentorVox
>>>
>>> --- On Tue, 2/16/10, Trevor  <oddrocketboy> wrote:
>>>
>>> <snip>
>>> Paul,
>>> I have both SAMs and pipes (swell shutters/percussions/traps too)
>>> operating through jOrgan.
>>> Everything you're trying to do should be a piece of cake!
>>> I haven't had time to try jOrgan's new SAMs feature yet,
>>> but I do have SAMs operating through a little app I threw together.
>>> Here are a couple of videos showing some of the capabilities of
>>> jOrgan with a TPO.
>>> http://www.youtube.com/watch?v=0eVfj6QGiUg
>>> http://www.youtube.com/watch?v=lFnQUluP-d8
>>> <snip>
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> ----------
>>> SOLARIS 10 is the OS for Data Centers - provides features such as  
>>> DTrace,
>>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>>> http://p.sf.net/sfu/solaris- 
>>> dev2dev_______________________________________________
>>> jOrgan-user mailing list
>>> jOrgan-user@...
>>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
> ---------------------------------------------------------------------- 
> --------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw- 
> dev_______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

You may have already done this, but it's helpful to get a 1 FARAD 
capacitor and place it across your SAM power supply to get more Oomph 
when doing a general cancel or changing more than a few SAMS at once. 
They are available from store that sell/install car stereo systems.
Ron
>>
>> Trevor wrote:
>>>
>>>
>>> I also made a better SAM demonstration video today.  That can be 
>>> found here:
>>>
>>> http://www.youtube.com/watch?v=28vcTuWDJw8
>>>
>>> -Trevor
>>>

Thank you Rick, MIDIO128 system DOUT cards running into my ancient magnet
driver boards (they use UDN2982A chips) appear to be a way to drive my
lighted stopswitches (which are 50ma each), also my lighted pistons.
Don

-- 
View this message in context: http://n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p1562080.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

This is great work.  Thank you for sharing Trevor.

Regards
Rick

Trevor wrote:
> Paul,
>
> I have both SAMs and pipes (swell shutters/percussions/traps too) 
> operating through jOrgan.  Everything you're trying to do should be a 
> piece of cake!
>
> I haven't had time to try jOrgan's new SAMs feature yet, but I do have 
> SAMs operating through a little app I threw together.  Here are a 
> couple of videos showing some of the capabilities of jOrgan with a TPO.
>
> http://www.youtube.com/watch?v=0eVfj6QGiUg
> http://www.youtube.com/watch?v=lFnQUluP-d8
>
> -Trevor
>
> On Feb 16, 2010, at 10:31 PM, Paul Kealy wrote:
>
>> Don,
>> I'd love to hear more about your application.
>> I'm seeking to operate both SAMS and pipes,
>> and what your project entails may be a solution
>> to the problems I face.
>>
>> I'd love more details, off-list is probably best, since
>> most folks tell me what I seek is beyond the capabilities
>> of j-Organ, but I will persist until I have pipes and SAMS
>> on the 260 organ and pipes and LED indicators above the
>> stoptabs and within the pistons for blind registrations
>> on the 216.  (just a few ranks of pipes, since most my
>> ranks are MIDIfied soundfonts)  H e l p!
>>
>> PK
>> StentorVox.com
>>
>>
>>
>> --- On *Mon, 2/15/10, Don Becker /<soniccr@... 
>> <mailto:soniccr@...>>/* wrote:
>>
>> From: Don Becker <soniccr@... <mailto:soniccr@...>>
>> Subject: Re: [jOrgan-user] SAMS and lighted pistons
>> To: jorgan-user@... 
>> <mailto:jorgan-user@...>
>> Date: Monday, February 15, 2010, 1:30 PM
>>
>> Has anyone yet figured out how to use jorgan to operate
>> lighted pushbutton SAMS????? My old combination action
>> is getting complicated and overloaded.
>> It has about 2,000,188 physical wires (seems like).
>> Don Becker
>>
>>
>> ------------------------------------------------------------------------------
>> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>> http://p.sf.net/sfu/solaris-dev2dev_______________________________________________
>> jOrgan-user mailing list
>> jOrgan-user@... 
>> <mailto:jOrgan-user@...>
>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> ------------------------------------------------------------------------
>
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

I'm back to lighting the stopswitches problem because I'm not sure how to go
about it. For each stop I have a pushbutton for ON that turns on a 50ma 5v
dc bulb and one for OFF that turns it off. The lites shine thru an engraved
piece of translucent plastic. 
All of my lighted SSW assemblies are made, each 32 stop jamb (8 of them) is 
a pcb assy.  So far, 1 of the assys and 2 add'l jambs (using house wiring
type wall switches) are wired to a physical combo-action (5' long 8 wire
cables) for Stop on, stop off and stopswitch signal (the SSW signal, 5VDC)
goes to Syndyne MIDI interface notes, the MIDI output of each 61 note
Syndyne board goes to my jorgan disposition and everything works. I have
programmed it so far using the "activate and deactivate" commands in jorgan
2.4.  Can anyone suggest what else I need to make this work (getting rid of
my physical combo-action in the process). I can go the MIDEO128 route or
anything else anyone can suggest.
I have 10  37 note magnet driver boards using UDN2982A drivers that output
5V  @ a max of 600ma for ea. note with a couple of ma in that I can use. 
Thanks, Don Becker
-- 
View this message in context: http://n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p1563061.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hello Don

What you need to do is separate your bulb lighting from your switching.  
The switching stays exactly as it is sending Midi to jOrgan, but your 
bulb illumination must come from jOrgan Midi out with no connection to 
your switches at all.
This Midi out can be achieved using uCapps MidiBox.  ( 
http://www.ucapps.de/ )
(purchase from   http://www.avishowtech.com/mbhp/index.html )
You will need a "CORE" (which is the brains and the Midi connection) and 
"DOUT" cards (the output trigger cards).  Each "DOUT" has 32 outputs.  I 
am not sure how much current they can drive or sink so your driver 
boards may come in handy.  Each "CORE" can take up to 4x "DOUT" so 
(4x32=) 128 outputs.  If you need more, you link another "CORE" and up 
to 4x "DOUT" using the MidiBox built in "Merger" function.
You haven't mentioned if you have any combination pistons.  In the 
system I have described, combination pistons will make changes to jOrgan 
which will change the illumination of your bulbs.  So using this method 
you can change your organ by pistons and/or by stop switches (or by 
mouse on the PC), jOrgan handles the logic of what should be on or off 
and matches the illumination of your bulbs to what it has on its screen 
(in your situation the screen could be hidden and not needed).
The Midi output is already a function of jOrgan, simply a reversal of 
the input triggers you are sending from your switches.  You will not 
need the new SAM's extension as you want your bulbs to stay 
illuminated.  The SAM's extension is designed to limit the output 
messages to a defined period of time enough to move the magnet action 
and then not continue to energise the coils continuously.

Regards
Rick

Don Becker wrote:
> I'm back to lighting the stopswitches problem because I'm not sure how to go
> about it. For each stop I have a pushbutton for ON that turns on a 50ma 5v
> dc bulb and one for OFF that turns it off. The lites shine thru an engraved
> piece of translucent plastic. 
> All of my lighted SSW assemblies are made, each 32 stop jamb (8 of them) is 
> a pcb assy.  So far, 1 of the assys and 2 add'l jambs (using house wiring
> type wall switches) are wired to a physical combo-action (5' long 8 wire
> cables) for Stop on, stop off and stopswitch signal (the SSW signal, 5VDC)
> goes to Syndyne MIDI interface notes, the MIDI output of each 61 note
> Syndyne board goes to my jorgan disposition and everything works. I have
> programmed it so far using the "activate and deactivate" commands in jorgan
> 2.4.  Can anyone suggest what else I need to make this work (getting rid of
> my physical combo-action in the process). I can go the MIDEO128 route or
> anything else anyone can suggest.
> I have 10  37 note magnet driver boards using UDN2982A drivers that output
> 5V  @ a max of 600ma for ea. note with a couple of ma in that I can use. 
> Thanks, Don Becker
>

Don,
You need to check into the different revisions to the dout cards available
from smash tv.  The stock dout has limited ouput, however there is one
version that has space to install ULN 2903 driver chips that can power
almost .5 amps, using a separate 12 volt dc power supply.  I built a 5 rank
pipe organ using the driver/dout cards. the work very well.
Johnc

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3326183.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Trevor,
I am attempting to construct your SAMS driver system using your disposition,
but am at a loss as to how to implement the Java app that your wrote.  I am
assuming that the app must be integrated with jOrgan ver. 3.3 for the
disposition to work. Any help you can provide will be greatly appreciated.
Johnc

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3326187.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Ah, now I see: You're after this solution *just* because you don't have 
Java 6 on your machine?

We might be able to build jOrgan for Java 5, that should be easier than 
bringing that Java snippet from the forum to production.

Regards

Sven

On 02/26/2011 08:44 PM, Johnc wrote:
> Trevor,
> I am attempting to construct your SAMS driver system using your disposition,
> but am at a loss as to how to implement the Java app that your wrote.  I am
> assuming that the app must be integrated with jOrgan ver. 3.3 for the
> disposition to work. Any help you can provide will be greatly appreciated.
> Johnc
>

Sven,
Well, yes and no.  I will get my P4, XP machine back ( its on loan to my 
daughter) for the final installation of ver 2.12 with SAMS.  The organ I am 
building will use only the Artisan  sound Engine which is a computer 
programmed in linux ubuntu running a custom program, with organ samples both 
classical and theatrer.  It accepts midi messages to key all the necessary 
functions to plan music.  However it totally lacks the functionality of a 
relay, which  jOrgan provides.  What it also means is that you don't need to 
deal with all the issues of soundcards, creative drivers, soundfonts, etc. 
and the processor speed that was required. You define what divisions you 
have, and what stops you have in a config. text file and off you go.
With regard to jOrgan  The organ will be played without monitor, as all 
stops, couplers, pistons, swell and keyboard notes come from tabs, switches, 
etc on the console.  Soundcard synths are not needed, only the midi out/in 
on the soundcard.  All midi messages are sent out through the console 
generic midi out as was the case with pipe decoders.  However, to key the 
stops, you only need a single midi note output on a predefined channel  the 
sound engine is configured to accept the same midi note on the same channel 
and turns the stop on.  So the stop designations in jOrgan and in the sound 
engine must match.  The sound samples are in ranks in the sound engine.  The 
division definitions consists of <division> <footage><number of 
notes><channel number><lowest note> i.e. *division Solo 8 61 c1n36.
Same arrangement for each division.
With SAMS in the mix, the generic soundsource, midi ouput must also include 
the outputs to drive the SAMS magnets.
Correct me if I am wrong, but  except for the SAMS feature in ver 3.12, 
Ver. 3.3 is perfectly capable of running the organ, and you really don't 
require a fast computer, especially since the synth buisness with soundcards 
is eliminated.
Looking at it in $ and cents,  Artisan sells the micro midi system of 
encoders, decoders, drivers, etc. that are similar to midibox, except 
commercially manufactured, and worth probably $3000-$4,000. these modules 
are the relay  and one of the micro midi units can be programmed to provide 
the combination action function.
jOrgan can do it all and for $0!!!
One downside is that the sound engine sells for $1,100 and the different 
ranks for $50 each
So if the SAMS function can be added to ver. 3.3, 3.4 or so, on an older 
machine, then you can build a pretty impressive organ for $2,000 to $3,000 
with sound quality comparable to Hauptwerk.
My interest is not just because I don't have a java  6 machine (I do have), 
its also because I want to know how it works, as was the case when we first 
started to talk about driving SAMS with jOrgan, remember!
Long story, hope you stayed with me!
Thanks again!
johnc

----- Original Message ----- 
From: "Sven Meier" <sven@...>
To: <jorgan-user@...>
Sent: Saturday, February 26, 2011 1:51 PM
Subject: Re: [jOrgan-user] Pipes and SAMs


> Ah, now I see: You're after this solution *just* because you don't have
> Java 6 on your machine?
>
> We might be able to build jOrgan for Java 5, that should be easier than
> bringing that Java snippet from the forum to production.
>
> Regards
>
> Sven
>
> On 02/26/2011 08:44 PM, Johnc wrote:
>> Trevor,
>> I am attempting to construct your SAMS driver system using your 
>> disposition,
>> but am at a loss as to how to implement the Java app that your wrote.  I 
>> am
>> assuming that the app must be integrated with jOrgan ver. 3.3 for the
>> disposition to work. Any help you can provide will be greatly 
>> appreciated.
>> Johnc
>>
>
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT 
> data
> generated by your applications, servers and devices whether physical, 
> virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi John,

>Correct me if I am wrong, but  except for the SAMS feature in ver 3.12,
>Ver. 3.3 is perfectly capable of running the organ, and you really don't
>require a fast computer, especially since the synth buisness with soundcards
>is eliminated.

there's no difference between 3.3 and 3.12 in regards to performance. But yes, 3.3. should be capable for everything except the SAMs.

>So if the SAMS function can be added to ver. 3.3, 3.4 or so, on an older
>machine

IMHO it would be easier to install Linux and use 3.12, but to each his own.

>My interest is not just because I don't have a java  6 machine (I do have),
>its also because I want to know how it works

Great, perhaps you could help with questions on what is missing on the SAMS console page:
	http://jorgan.sf.net/SAMs_console

Best regards

Sven

Johnc,
Thanks for the idea. Never have gotten my old magnet driver boards (with the
UDN2982A chips) to work but you just gave me the idea to try the UDN2982A
chips in the 8 Dout boards that I built (along with the 2 PicChip boards)
but have never installed in place of my old combination action (wires
everywhere). They look interchangeable with the ULN 2803 Driver chips. The
internal suppression diodes are in the opposite direction but I can't see
how that will matter. Did you ever make any kind of wiring diagram for what
you did?????? It might be simpler than it looks.
Don

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3327132.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Don,  If the diodes are reverse in order, i think that reverses the polarity, so be careful...  I think if you swap chips, you must also swap polarity, ie what was a negative common now becomes positive...
 
  Just a thought/word of caution...
 
Al

--- On Sun, 2/27/11, Don Becker <soniccr@...> wrote:


From: Don Becker <soniccr@...>
Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Sunday, February 27, 2011, 4:11 PM


Johnc,
Thanks for the idea. Never have gotten my old magnet driver boards (with the
UDN2982A chips) to work but you just gave me the idea to try the UDN2982A
chips in the 8 Dout boards that I built (along with the 2 PicChip boards)
but have never installed in place of my old combination action (wires
everywhere). They look interchangeable with the ULN 2803 Driver chips. The
internal suppression diodes are in the opposite direction but I can't see
how that will matter. Did you ever make any kind of wiring diagram for what
you did?????? It might be simpler than it looks.
Don

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3327132.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user

John C,

Can you describe in more detail how your SAMS driver board operates?

Specifically:

Does the driver board (A.) engage the SAMS' On and Off magnets for a FIXED amount of time? 
(a few milliseconds) and then automatically cut off the current to the magnets after that 
interval expires?  Or (B.) does the SAMS driver turn on the magnet current when it gets a 
certain MIDI message, and LEAVE the current ON until it receives another different MIDI 
message that instructs the driver to turn off the current to the SAMS magnet?

If your answer is (A.), you do not need to have the jOrgan SAMS Extension installed, and 
therefore you can use an earlier version of jOrgan that is compatible with your Java version.

CLW
----------------------------------------------------------------------------------

On 2/26/2011 2:44 PM, Johnc wrote:
> Trevor,
> I am attempting to construct your SAMS driver system using your disposition,
> but am at a loss as to how to implement the Java app that your wrote.  I am
> assuming that the app must be integrated with jOrgan ver. 3.3 for the
> disposition to work. Any help you can provide will be greatly appreciated.
> Johnc
>

Don,
You need to get on the midibox forum and search the midification thread for
posts regarding the douts with the uln2903.  basically, the dout with the 4
uln2903s installed can power 32 stop magnets.  With the ULN2903,  the common
pin sits at 12 vdc if thats what voltage you are using, so one side of the
magnets is at 12vdc.  The other side of the magnets connects to the output
pin on the chip.  Since the chip is 3 state the ouput is normally in the
high impedence state.   When the chip is energized, the pin goes to pretty
near ground, and the magnet is energized.  
If I'm not mistaken, the ULN2982 is the reverse.  the common side of the
magnet is at ground, and the uln2982 connects it to 12volts ( i have not
used the 2982),   Since the ULN2903 worked so well for me, i did not explore
the ULN2982.  The 12vdc is a separate supply from the 5vdc used by the
midibox core and douts.
Again,  take a look at midibox.org, and also google ULN2903.
Johnc

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3327233.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Sven,
I spent some time reading through the SAMS console material and found it 
cryptic in a way.  Perhaps I was looking for more derail then presented.  So 
I downloaded and booted up ver. 3.12 (on our house computer) and spent some 
time parusing the different dispositions, and was able to answer many of my 
questions, like  the word "duration" on the message chart on the SAMS 
console.  I new it had to be there, but I had not come across it before in 
jOrgan properties.  (my fault for not keeping up).  Seeing the complete 
messages in the dispositions is a big help.  Granted, I am probing much 
deeper then necessary in order to implement ver 3.12.
As a matter of fact, you are correct in your statement suggesting running 
Linux and the full 3.12. Actually, the older machine will run faster with 
linux, then windows anyway.  I get annoyed with the computer/software 
spiral, where you have to continuously upgrade your computer in order to 
continue using software you have used for years.
I am closing the book on running SAMS under win98SE and will try my hand at 
linux.  I am a little familiar with puppy, but not Ubuntu.  Which is most 
user friendly, and which do you recommend?  I  see words on the wiki about 
both, so some reading is in order.
Thanks for your patience and help.
johnc


----- Original Message ----- 
From: "Sven Meier" <sven@...>
To: <jorgan-user@...>
Sent: Sunday, February 27, 2011 5:22 AM
Subject: Re: [jOrgan-user] Pipes and SAMs


> Hi John,
>
>>Correct me if I am wrong, but  except for the SAMS feature in ver 3.12,
>>Ver. 3.3 is perfectly capable of running the organ, and you really don't
>>require a fast computer, especially since the synth buisness with 
>>soundcards
>>is eliminated.
>
> there's no difference between 3.3 and 3.12 in regards to performance. But 
> yes, 3.3. should be capable for everything except the SAMs.
>
>>So if the SAMS function can be added to ver. 3.3, 3.4 or so, on an older
>>machine
>
> IMHO it would be easier to install Linux and use 3.12, but to each his 
> own.
>
>>My interest is not just because I don't have a java  6 machine (I do 
>>have),
>>its also because I want to know how it works
>
> Great, perhaps you could help with questions on what is missing on the 
> SAMS console page:
> http://jorgan.sf.net/SAMs_console
>
> Best regards
>
> Sven
>
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT 
> data
> generated by your applications, servers and devices whether physical, 
> virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Johnc wrote:
> Don,
> You need to get on the midibox forum and search the midification thread for
> posts regarding the douts with the uln2903.  basically, the dout with the 4
> uln2903s installed can power 32 stop magnets.  With the ULN2903,  the common
> pin sits at 12 vdc if thats what voltage you are using, so one side of the
> magnets is at 12vdc.  The other side of the magnets connects to the output
> pin on the chip.  Since the chip is 3 state the ouput is normally in the
> high impedence state.   When the chip is energized, the pin goes to pretty
> near ground, and the magnet is energized.  
> If I'm not mistaken, the ULN2982 is the reverse.  the common side of the
> magnet is at ground, and the uln2982 connects it to 12volts ( i have not
> used the 2982),   Since the ULN2903 worked so well for me, i did not explore
> the ULN2982.  The 12vdc is a separate supply from the 5vdc used by the
> midibox core and douts.
> Again,  take a look at midibox.org, and also google ULN2903.
> Johnc
>
>   
The thing I am trying to do is turn the stopswitch lights on and off. 
That is all. Each 5V lamp draws 50ma. That is now done by my 
combo-action but as I say, wires are everywhere and I have only 62 stops 
wired so far. I try to do too many things at once in my life and have 
used only the 62 stops for a while now. But I have built jambs for  256 
stops with on push buttons and off pushbuttons. I made translucent 
strips and engraved the stop names on them (20 minutes/2 names / strip, 
what a lot of effort) using a Scott Engraving machine. 96 stopnames are 
engraved so far. They work great. I used long throw keyswitch 
pushbuttons that Mouser Electronics has stopped carrying. The 
pushbuttons are mounted on circuit boards (I made circuit boards for the 
jambs). Everything is connected using .1 spacing Amp MTA connectors. The 
pushbuttons run the stops on my jorgan disposition. I was trying to use 
the UDN2982A chips because they were sitting here, but its only about 
$30 if I buy the ULN 2803s. Found them today at Allied. Didn't realize 
the common on the 2803s is on the 12VDC line on the Dout board. The 
common on the 2982 is ground.
Don

Johnc wrote:
> 
> ... I am a little familiar with puppy, but not Ubuntu.  ...
> 

I am more familiar with Ubuntu than Puppy (although with GrahamG's excellent
jOrgan wiki tutorial I was easily able to install jOrgan on Puppy).

I have never had much luck with Ubuntu and audio apps.  Rumor has it that it
is better now, but I first started trying to use Ubuntu Studio about the
time Pulse Audio first came out and I had no end of grief.  Keep in mind
that this may be partly due to my inability to wrap my head around the
various permissions required (which apps should be in the audio group etc),
but finally gave up and installed 64Studio which worked 'out of the box' and
that was my main Linux Audio workstation until I installed Puppy/Java/jOrgan
on another box  (1.7Ghz, 768mb ram) with Graham's instructions.   I am very
impressed with the performance, even though I am using Fluid Synth as my
sound source.

In other words, my vote would be for Puppy, and your slight familiarity with
it is just a bonus.  I see no reason to go with Ubuntu even with the real
time kernel as it seems like needless bulk.   Unless of course you need that
distro for more general applications.  Keep in mind, Ubuntu is likely to
become the Mac or PC of the linux world - ie. a target for hackers etc
(although given the similarities with Puppy, some of the vulnerabilities may
be shared, esp. with java RE).


-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3327462.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Del,
Thanks much for your comments and suggestions.  Actually I was leaning 
toward Puppy, and find it not a drastic departure from windows. What I like 
is that it is fast.  I did look at Grahams material on jOrgan and puppy 
linux, but stayed with windows xp.  That was when jOrgan was at ver. 3.3. 
During these many months, I have fallen behind on keeping up with jOrgan and 
will have to spend many hours re-learning, so adding to that the need to 
learn linux puppy complicates things.
Thanks again
johnc
----- Original Message ----- 
From: "DellAnderson" <design2@...>
To: <jorgan-user@...>
Sent: Sunday, February 27, 2011 10:13 PM
Subject: Re: [jOrgan-user] Pipes and SAMs


>
> Johnc wrote:
>>
>> ... I am a little familiar with puppy, but not Ubuntu.  ...
>>
>
> I am more familiar with Ubuntu than Puppy (although with GrahamG's 
> excellent
> jOrgan wiki tutorial I was easily able to install jOrgan on Puppy).
>
> I have never had much luck with Ubuntu and audio apps.  Rumor has it that 
> it
> is better now, but I first started trying to use Ubuntu Studio about the
> time Pulse Audio first came out and I had no end of grief.  Keep in mind
> that this may be partly due to my inability to wrap my head around the
> various permissions required (which apps should be in the audio group 
> etc),
> but finally gave up and installed 64Studio which worked 'out of the box' 
> and
> that was my main Linux Audio workstation until I installed 
> Puppy/Java/jOrgan
> on another box  (1.7Ghz, 768mb ram) with Graham's instructions.   I am 
> very
> impressed with the performance, even though I am using Fluid Synth as my
> sound source.
>
> In other words, my vote would be for Puppy, and your slight familiarity 
> with
> it is just a bonus.  I see no reason to go with Ubuntu even with the real
> time kernel as it seems like needless bulk.   Unless of course you need 
> that
> distro for more general applications.  Keep in mind, Ubuntu is likely to
> become the Mac or PC of the linux world - ie. a target for hackers etc
> (although given the similarities with Puppy, some of the vulnerabilities 
> may
> be shared, esp. with java RE).
>
>
> -- 
> View this message in context: 
> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3327462.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT 
> data
> generated by your applications, servers and devices whether physical, 
> virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi,

studying the sams-example.disposition is probably the best way to start.
I'm continuously improving the documentation on 
http://jorgan.sf.net/SAMs_console so hopefully we'll be able to make 
this work for you.

>I am a little familiar with puppy, but not Ubuntu.  Which is most
>user friendly, and which do you recommend?

I'm an Ubuntu advocate. *But* I'm not tuning my system for optimal sound 
output here. If you need that, you're probably better off following 
Graham on the Puppy route.

Best regards

Sven


On 02/28/2011 12:08 AM, John W. Couvillon wrote:
> Sven,
> I spent some time reading through the SAMS console material and found it
> cryptic in a way.  Perhaps I was looking for more derail then presented.  So
> I downloaded and booted up ver. 3.12 (on our house computer) and spent some
> time parusing the different dispositions, and was able to answer many of my
> questions, like  the word "duration" on the message chart on the SAMS
> console.  I new it had to be there, but I had not come across it before in
> jOrgan properties.  (my fault for not keeping up).  Seeing the complete
> messages in the dispositions is a big help.  Granted, I am probing much
> deeper then necessary in order to implement ver 3.12.
> As a matter of fact, you are correct in your statement suggesting running
> Linux and the full 3.12. Actually, the older machine will run faster with
> linux, then windows anyway.  I get annoyed with the computer/software
> spiral, where you have to continuously upgrade your computer in order to
> continue using software you have used for years.
> I am closing the book on running SAMS under win98SE and will try my hand at
> linux.  I am a little familiar with puppy, but not Ubuntu.  Which is most
> user friendly, and which do you recommend?  I  see words on the wiki about
> both, so some reading is in order.
> Thanks for your patience and help.
> johnc
>
>
> ----- Original Message -----
> From: "Sven Meier"<sven@...>
> To:<jorgan-user@...>
> Sent: Sunday, February 27, 2011 5:22 AM
> Subject: Re: [jOrgan-user] Pipes and SAMs
>
>
>> Hi John,
>>
>>> Correct me if I am wrong, but  except for the SAMS feature in ver 3.12,
>>> Ver. 3.3 is perfectly capable of running the organ, and you really don't
>>> require a fast computer, especially since the synth buisness with
>>> soundcards
>>> is eliminated.
>> there's no difference between 3.3 and 3.12 in regards to performance. But
>> yes, 3.3. should be capable for everything except the SAMs.
>>
>>> So if the SAMS function can be added to ver. 3.3, 3.4 or so, on an older
>>> machine
>> IMHO it would be easier to install Linux and use 3.12, but to each his
>> own.
>>
>>> My interest is not just because I don't have a java  6 machine (I do
>>> have),
>>> its also because I want to know how it works
>> Great, perhaps you could help with questions on what is missing on the
>> SAMS console page:
>> http://jorgan.sf.net/SAMs_console
>>
>> Best regards
>>
>> Sven
>>
>>
>> ------------------------------------------------------------------------------
>> Free Software Download: Index, Search&  Analyze Logs and other IT data in
>> Real-Time with Splunk. Collect, index and harness all the fast moving IT
>> data
>> generated by your applications, servers and devices whether physical,
>> virtual
>> or in the cloud. Deliver compliance at lower cost and gain new business
>> insights. http://p.sf.net/sfu/splunk-dev2dev
>> _______________________________________________
>> jOrgan-user mailing list
>> jOrgan-user@...
>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search&  Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Thanks for your help John C and Al,
I'm still confused. The diagram of the Dout board running the relays using
the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
ULN2803 gates and the outputs of the 2803 gates going to one side of the
relays and the other side of the relays (and also pin 10 of the 2803) going
to +DC voltage. I'm trying to use this configuration , not to turn relays on
and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
way they are mounted on my jamb circuit bds. 
This doesn't look like it is going to work. What am I missing???
Don

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hi, Don,

            No, you're right, it's not going to work. With that type of driver IC you must have the lamps common to +5V. I don't know what voltage your supplies are but if they a more than 5V you'll also need to fit a regulator IC and a few more bits around it.

    Have fun,

        Roy.

--- On Tue, 1/3/11, Don Becker <soniccr@...> wrote:

From: Don Becker <soniccr@...>
Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Tuesday, 1 March, 2011, 22:35

Thanks for your help John C and Al,
I'm still confused. The diagram of the Dout board running the relays using
the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
ULN2803 gates and the outputs of the 2803 gates going to one side of the
relays and the other side of the relays (and also pin 10 of the 2803) going
to +DC voltage. I'm trying to use this configuration , not to turn relays on
and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
way they are mounted on my jamb circuit bds. 
This doesn't look like it is going to work. What am I missing???
Don

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hello,<br>
<br>
I see 2 possibilities:<br>
<br>
1) use relays as in the diagram in the file relay_example.pdf&nbsp; (If
attachment fails, see <a
 href="http://www.ucapps.de/midio128/relay_example.pdf" class="bbc_url"
 title="External link" rel="nofollow external">http://www.ucapps.de...lay_example.pdf</a>)<br>
The lamps can then be connected one leg to ground, the other to a
contact that is open when the relay is OFF, and the other corresponding
contact of the relay connected to + V<br>
<br>
2) disconnect all lamps from ground (sorry, even more wires) and
connect them in series with the ULM2803 outputs, replacing the relays
in the diagram.<br>
<br>
All the best.<br>
<br>
Erik.<br>
---------------------------------------------------<br>
<br>
Don Becker wrote:
<blockquote cite="mid:1299018936130-3330731.post@..."
 type="cite">
  <pre wrap="">Thanks for your help John C and Al,
I'm still confused. The diagram of the Dout board running the relays using
the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
ULN2803 gates and the outputs of the 2803 gates going to one side of the
relays and the other side of the relays (and also pin 10 of the 2803) going
to +DC voltage. I'm trying to use this configuration , not to turn relays on
and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
way they are mounted on my jamb circuit bds. 
This doesn't look like it is going to work. What am I missing???
Don

  </pre>
</blockquote>
</body>
</html>

Hi, Don,

           Sorry if this appears twice but the first attempt doesn't seem to be going anywhere!

          No, you're right, it's not going to work. 
With that type of driver IC you must have the lamps common to +5V. I 
don't know what voltage your supplies are but if they a more than 5V 
you'll also need to fit a regulator IC and a few more bits around it.

    Have fun,

        Roy.

--- On Tue, 1/3/11, Don Becker <soniccr@...> wrote:

From: Don Becker <soniccr@...>
Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Tuesday, 1 March, 2011, 22:35

Thanks for your help John C and Al,
I'm still confused. The diagram of the Dout board running the relays using
the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
ULN2803 gates and the outputs of the 2803 gates going to one side of the
relays and the other side of the relays (and also pin 10 of the 2803) going
to +DC voltage. I'm trying to use this configuration , not to turn relays on
and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
way they are mounted on my jamb circuit bds. 
This doesn't look like it is going to work. What am I missing???
Don

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user

DOn, Roy, soory but I just jumped into this conversation. If it is only
driving power that you need, the simplest solution is to have a transistor
behind the gate's output driving the lamp. 50mA can be delivered by any
small signal device.

Greetings,

Geert

2011/3/2 Roy Radford <roy.radford42@...>

> Hi, Don,
>
>            Sorry if this appears twice but the first attempt doesn't seem
> to be going anywhere!
>
>
>           No, you're right, it's not going to work. With that type of
> driver IC you must have the lamps common to +5V. I don't know what voltage
> your supplies are but if they a more than 5V you'll also need to fit a
> regulator IC and a few more bits around it.
>
>     Have fun,
>
>         Roy.
>
> --- On *Tue, 1/3/11, Don Becker <soniccr@...>* wrote:
>
>
> From: Don Becker <soniccr@...>
> Subject: Re: [jOrgan-user] SAMS and lighted pistons
> To: jorgan-user@...
> Date: Tuesday, 1 March, 2011, 22:35
>
> Thanks for your help John C and Al,
> I'm still confused. The diagram of the Dout board running the relays using
> the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
> ULN2803 gates and the outputs of the 2803 gates going to one side of the
> relays and the other side of the relays (and also pin 10 of the 2803) going
> to +DC voltage. I'm trying to use this configuration , not to turn relays
> on
> and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
> lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
> way they are mounted on my jamb circuit bds.
> This doesn't look like it is going to work. What am I missing???
> Don
>
> --
> View this message in context:
> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT
> data
> generated by your applications, servers and devices whether physical,
> virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@... href="http://mc/compose?to=jOrgan-user@..." target="_new">http://mc/compose?to=jOrgan-user@...>>
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT
> data
> generated by your applications, servers and devices whether physical,
> virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>

Hi, Geert,

              I'm not quite sure what you mean by "Behind the lamp". Are you using the transistors as emitter followers driven by the IC? It sounds like a lot more bits.
 
   Of course, the main question is the layout of the instrument... Just how difficult it would  be to rewire the lamps to common +ive.


     Have fun,

         Roy.

--- On Thu, 3/3/11, orgel jeux <jeuxorgel@...> wrote:

From: orgel jeux <jeuxorgel@...>
Subject: Re: [jOrgan-user] [SPAM] Re: SAMS and lighted pistons
To: jorgan-user@...
Date: Thursday, 3 March, 2011, 7:24

DOn, Roy, soory but I just jumped into this conversation. If it is only driving power that you need, the simplest solution is to have a transistor behind the gate's output driving the lamp. 50mA can be delivered by any small signal device.


Greetings,

Geert

2011/3/2 Roy Radford <roy.radford42@...>

Hi, Don,

           Sorry if this appears twice but the first attempt doesn't seem to be going anywhere!


          No, you're right, it's not going to work. 
With that type of driver IC you must have the lamps common to +5V. I 
don't know what voltage your supplies are but if they a more than 5V 
you'll also need to fit a regulator IC and a few more bits around it.

    Have fun,

        Roy.

--- On Tue, 1/3/11, Don Becker <soniccr@...> wrote:


From: Don Becker <soniccr@...>

Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Tuesday, 1 March, 2011, 22:35


Thanks for your help John C and Al,
I'm still confused. The diagram of the Dout board running the relays using
the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
ULN2803 gates and the outputs of the 2803 gates going to one side of the

relays and the other side of the relays (and also pin 10 of the 2803) going
to +DC voltage. I'm trying to use this configuration
 , not to turn relays on
and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
way they are mounted on my jamb circuit bds. 

This doesn't look like it is going to work. What am I missing???
Don

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html

Sent from the jOrgan - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 

Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver
 compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
jOrgan-user mailing list

jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user


------------------------------------------------------------------------------

Free Software Download: Index, Search & Analyze Logs and other IT data in

Real-Time with Splunk. Collect, index and harness all the fast moving IT data

generated by your applications, servers and devices whether physical, virtual

or in the cloud. Deliver compliance at lower cost and gain new business

insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________

jOrgan-user mailing list

jOrgan-user@...

https://lists.sourceforge.net/lists/listinfo/jorgan-user





-----Inline Attachment Follows-----

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
-----Inline Attachment Follows-----

_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi again, Geert,

                      Oops, I see I misquoted you slightly there, traded "lamps" for "gates".... Doesn't alter the gist of my comment.

   This is one of those cases where a picture is worth a thousand words, describing a circuit diagram is a very unreliable exercise. This cuts across another thread but one of the things a Yahoo group has and a mailing lists doesn't is a "Files" area where members can share ANY sort of file, music, pictures etc.


      Have fun,

          Roy.

--- On Thu, 3/3/11, orgel jeux <jeuxorgel@...> wrote:

From: orgel jeux <jeuxorgel@...>
Subject: Re: [jOrgan-user] [SPAM] Re: SAMS and lighted pistons
To: jorgan-user@...
Date: Thursday, 3 March, 2011, 7:24

DOn, Roy, soory but I just jumped into this conversation. If it is only driving power that you need, the simplest solution is to have a transistor behind the gate's output driving the lamp. 50mA can be delivered by any small signal device.


Greetings,

Geert

2011/3/2 Roy Radford <roy.radford42@...>

Hi, Don,

           Sorry if this appears twice but the first attempt doesn't seem to be going anywhere!


          No, you're right, it's not going to work. 
With that type of driver IC you must have the lamps common to +5V. I 
don't know what voltage your supplies are but if they a more than 5V 
you'll also need to fit a regulator IC and a few more bits around it.

    Have fun,

        Roy.

--- On Tue, 1/3/11, Don Becker <soniccr@...> wrote:


From: Don Becker <soniccr@...>

Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Tuesday, 1 March, 2011, 22:35


Thanks for your help John C and Al,
I'm still confused. The diagram of the Dout board running the relays using
the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
ULN2803 gates and the outputs of the 2803 gates going to one side of the

relays and the other side of the relays (and also pin 10 of the 2803) going
to +DC voltage. I'm trying to use this configuration
 , not to turn relays on
and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
way they are mounted on my jamb circuit bds. 

This doesn't look like it is going to work. What am I missing???
Don

-- 
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html

Sent from the jOrgan - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 

Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver
 compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
jOrgan-user mailing list

jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user


------------------------------------------------------------------------------

Free Software Download: Index, Search & Analyze Logs and other IT data in

Real-Time with Splunk. Collect, index and harness all the fast moving IT data

generated by your applications, servers and devices whether physical, virtual

or in the cloud. Deliver compliance at lower cost and gain new business

insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________

jOrgan-user mailing list

jOrgan-user@...

https://lists.sourceforge.net/lists/listinfo/jorgan-user





-----Inline Attachment Follows-----

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
-----Inline Attachment Follows-----

_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi Don,
The last time I spoke to you on some other site was 12 years ago(about organs of course).
I haven't spoken to our friend Owen for a good while.
I'm glad you are here having fun with Jorgan.
I retired but got pulled back and was away from jorgan for a very long time.
Really interrupted my jorgan project !!

Your plan for the bulbs is OK !!
1-You need to have a +5VDC power supply with enough current capability to drive 
HOWEVER MANY BULBS you think you might drive at ONE TIME. !!
You know how it is... some say 'oh only 3 stops at a time'. But the design will 
allow some one to walk up to you organ and turn them all on if they can they will.
This should not be any problem at all.

2-You need to use the UDN2982A for your drivers.
Be aware these are noninverting.
3-The outputs from your HC595's are all wired to the inputs (pins 1-8) of the UDN2982A's 
and the outputs from the 2982A's are connected directly to your bulbs.
4-The UDN2982A pin-9 is connected to your +5VDC source.
5-The UDN2982A pin_10 gets connected to your ground.

6-The 'noninverting' means that when your software sends a positive signal 
to your HC595 inputs, this will turn ON your bulb. 

If I can help any further, just ask or email me directly.
DaveT





On 1 Mar 2011 at 14:35, Don Becker wrote:

> Thanks for your help John C and Al,
> I'm still confused. The diagram of the Dout board running the relays using
> the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
> ULN2803 gates and the outputs of the 2803 gates going to one side of the
> relays and the other side of the relays (and also pin 10 of the 2803) going
> to +DC voltage. I'm trying to use this configuration , not to turn relays on
> and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
> lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
> way they are mounted on my jamb circuit bds. 
> This doesn't look like it is going to work. What am I missing???
> Don
> 
> -- 
> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in 
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business 
> insights. http://p.sf.net/sfu/splunk-dev2dev 
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi, Dave,

            Ah, I didn't know there was a downside-up equivalent to the ULN2803. That's a MUCH better solution... Just shows how out-of-touch I'm getting in my old age!   

    Have fun,

        Roy.


--- On Fri, 4/3/11, davetutlo@... <davetutlo@...> wrote:

From: davetutlo@... <davetutlo@...>
Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Friday, 4 March, 2011, 4:22

Hi Don,
The last time I spoke to you on some other site was 12 years ago(about organs of course).
I haven't spoken to our friend Owen for a good while.
I'm glad you are here having fun with Jorgan.
I retired but got pulled back and was away from jorgan for a very long time.
Really interrupted my jorgan project !!

Your plan for the bulbs is OK !!
1-You need to have a +5VDC power supply with enough current capability to drive 
HOWEVER MANY BULBS you think you might drive at ONE TIME. !!
You know how it is... some say 'oh only 3 stops at a time'. But the design will 
allow some one to walk up to you organ and turn them all on if they can they will.
This should not be any problem at all.

2-You need to use the UDN2982A for your drivers.
Be aware these are noninverting.
3-The outputs from your HC595's are all wired to the inputs (pins 1-8) of the UDN2982A's 
and the outputs from the 2982A's are connected directly to your bulbs.
4-The UDN2982A pin-9 is connected to your +5VDC source.
5-The UDN2982A pin_10 gets connected to your ground.

6-The 'noninverting' means that when your software sends a positive signal 
to your HC595 inputs, this will turn ON your bulb. 

If I can help any further, just ask or email me directly.
DaveT





On 1 Mar 2011 at 14:35, Don Becker wrote:

> Thanks for your help John C and Al,
> I'm still confused. The diagram of the Dout board running the relays using
> the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
> ULN2803 gates and the outputs of the 2803 gates going to one side of the
> relays and the other side of the relays (and also pin 10 of the 2803) going
> to +DC voltage. I'm trying to use this configuration , not to turn relays on
> and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
> lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats the
> way they are mounted on my jamb circuit bds. 
> This doesn't look like it is going to work. What am I missing???
> Don
> 
> -- 
> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in 
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business 
> insights. http://p.sf.net/sfu/splunk-dev2dev 
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user



------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user

Yeah, it is of course always easier to use a IC that can drive a lamp
directly.

Perhaps it is also an idea to replace the lamps for white Leds, which draw
much less current and have much biggter lifetime.

Greetings,

Geert

2011/3/4 Roy Radford <roy.radford42@...>

> Hi, Dave,
>
>             Ah, I didn't know there was a downside-up equivalent to the
> ULN2803. That's a MUCH better solution... Just shows how out-of-touch I'm
> getting in my old age!
>
>     Have fun,
>
>         Roy.
>
>
> --- On *Fri, 4/3/11, davetutlo@... <davetutlo@...>* wrote:
>
>
> From: davetutlo@... <davetutlo@...>
>
> Subject: Re: [jOrgan-user] SAMS and lighted pistons
> To: jorgan-user@...
> Date: Friday, 4 March, 2011, 4:22
>
>
> Hi Don,
> The last time I spoke to you on some other site was 12 years ago(about
> organs of course).
> I haven't spoken to our friend Owen for a good while.
> I'm glad you are here having fun with Jorgan.
> I retired but got pulled back and was away from jorgan for a very long
> time.
> Really interrupted my jorgan project !!
>
> Your plan for the bulbs is OK !!
> 1-You need to have a +5VDC power supply with enough current capability to
> drive
> HOWEVER MANY BULBS you think you might drive at ONE TIME. !!
> You know how it is... some say 'oh only 3 stops at a time'. But the design
> will
> allow some one to walk up to you organ and turn them all on if they can
> they will.
> This should not be any problem at all.
>
> 2-You need to use the UDN2982A for your drivers.
> Be aware these are noninverting.
> 3-The outputs from your HC595's are all wired to the inputs (pins 1-8) of
> the UDN2982A's
> and the outputs from the 2982A's are connected directly to your bulbs.
> 4-The UDN2982A pin-9 is connected to your +5VDC source.
> 5-The UDN2982A pin_10 gets connected to your ground.
>
> 6-The 'noninverting' means that when your software sends a positive signal
> to your HC595 inputs, this will turn ON your bulb.
>
> If I can help any further, just ask or email me directly.
> DaveT
>
>
>
>
>
> On 1 Mar 2011 at 14:35, Don Becker wrote:
>
> > Thanks for your help John C and Al,
> > I'm still confused. The diagram of the Dout board running the relays
> using
> > the 2803 chips, shows the outputs of the 74HC595 going to the inputs of
> the
> > ULN2803 gates and the outputs of the 2803 gates going to one side of the
> > relays and the other side of the relays (and also pin 10 of the 2803)
> going
> > to +DC voltage. I'm trying to use this configuration , not to turn relays
> on
> > and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
> > lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats
> the
> > way they are mounted on my jamb circuit bds.
> > This doesn't look like it is going to work. What am I missing???
> > Don
> >
> > --
> > View this message in context:
> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html
> > Sent from the jOrgan - User mailing list archive at Nabble.com.
> >
> >
> ------------------------------------------------------------------------------
> > Free Software Download: Index, Search & Analyze Logs and other IT data in
>
> > Real-Time with Splunk. Collect, index and harness all the fast moving IT
> data
> > generated by your applications, servers and devices whether physical,
> virtual
> > or in the cloud. Deliver compliance at lower cost and gain new business
> > insights. http://p.sf.net/sfu/splunk-dev2dev
> > _______________________________________________
> > jOrgan-user mailing list
> > jOrgan-user@... href="http://mc/compose?to=jOrgan-user@..." target="_new">http://mc/compose?to=jOrgan-user@...>>
> > https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@... href="http://mc/compose?to=jOrgan-user@..." target="_new">http://mc/compose?to=jOrgan-user@...>>
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>

    True, though as I'm sure you know, but others may not, you need to add a resistor to each and, unlike filament lamps, it DOES matter which way round you connect the LEDS!

     Have fun,

        Roy.


--- On Sat, 5/3/11, orgel jeux <jeuxorgel@...> wrote:

From: orgel jeux <jeuxorgel@...>
Subject: Re: [jOrgan-user] [SPAM] Re: SAMS and lighted pistons
To: jorgan-user@...
Date: Saturday, 5 March, 2011, 12:11

Yeah, it is of course always easier to use a IC that can drive a lamp directly.

Perhaps it is also an idea to replace the lamps for white Leds, which draw much less current and have much biggter lifetime.

Greetings,


Geert

2011/3/4 Roy Radford <roy.radford42@...>

Hi, Dave,

            Ah, I didn't know there was a downside-up equivalent to the ULN2803. That's a MUCH better solution... Just shows how out-of-touch I'm getting in my old age!   


    Have fun,

        Roy.


--- On Fri, 4/3/11, davetutlo@... <davetutlo@...> wrote:


From: davetutlo@... <davetutlo@...>

Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Friday, 4 March, 2011, 4:22


Hi Don,
The last time I
 spoke to you on some other site was 12 years ago(about organs of course).
I haven't spoken to our friend Owen for a good while.
I'm glad you are here having fun with Jorgan.
I retired but got pulled back and was away from jorgan for a very long time.

Really interrupted my jorgan project !!

Your plan for the bulbs is OK !!
1-You need to have a +5VDC power supply with enough current capability to drive 
HOWEVER MANY BULBS you think you might drive at ONE TIME. !!

You know how it is... some say 'oh only 3 stops at a time'. But the design will 
allow some one to walk up to you organ and turn them all on if they can they will.
This should not be any problem at all.


2-You need to use the UDN2982A for your drivers.
Be aware these are noninverting.
3-The outputs from your HC595's are all wired to the inputs (pins 1-8) of the UDN2982A's 
and the outputs from the 2982A's are connected directly to your
 bulbs.
4-The UDN2982A pin-9 is connected to your +5VDC source.
5-The UDN2982A pin_10 gets connected to your ground.

6-The 'noninverting' means that when your software sends a positive signal 
to your HC595 inputs, this will turn ON your bulb. 


If I can help any further, just ask or email me directly.
DaveT





On 1 Mar 2011 at 14:35, Don Becker wrote:

> Thanks for your help John C and Al,
> I'm still confused. The diagram of the Dout board running the relays using

> the 2803 chips, shows the outputs of the 74HC595 going to the inputs of the
> ULN2803 gates and the outputs of the 2803 gates going to one side of the
> relays and the other side of the relays (and also pin 10 of the 2803) going

> to +DC voltage. I'm trying to use this configuration , not to turn relays on
> and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
> lamps need an
 input of +5VDC to turn on. Their outputs go to Gnd. Thats the
> way they are mounted on my jamb circuit bds. 
> This doesn't look like it is going to work. What am I missing???
> Don
> 
> -- 

> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html

> Sent from the jOrgan - User mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in 

> Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business 

>
 insights. http://p.sf.net/sfu/splunk-dev2dev 
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...

> https://lists.sourceforge.net/lists/listinfo/jorgan-user



------------------------------------------------------------------------------

What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d

_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user


------------------------------------------------------------------------------

What You Don't Know About Data Connectivity CAN Hurt You

This paper provides an overview of data connectivity, details

its effect on application quality, and explores various alternative

solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________

jOrgan-user mailing list

jOrgan-user@...

https://lists.sourceforge.net/lists/listinfo/jorgan-user





-----Inline Attachment Follows-----

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
-----Inline Attachment Follows-----

_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user

Yep.

2011/3/5 Roy Radford <roy.radford42@...>

>     True, though as I'm sure you know, but others may not, you need to add
> a resistor to each and, unlike filament lamps, it DOES matter which way
> round you connect the LEDS!
>
>      Have fun,
>
>         Roy.
>
>
>
> --- On *Sat, 5/3/11, orgel jeux <jeuxorgel@...>* wrote:
>
>
> From: orgel jeux <jeuxorgel@...>
> Subject: Re: [jOrgan-user] [SPAM] Re: SAMS and lighted pistons
>
> To: jorgan-user@...
> Date: Saturday, 5 March, 2011, 12:11
>
>
> Yeah, it is of course always easier to use a IC that can drive a lamp
> directly.
>
> Perhaps it is also an idea to replace the lamps for white Leds, which draw
> much less current and have much biggter lifetime.
>
> Greetings,
>
> Geert
>
> 2011/3/4 Roy Radford <roy.radford42@... href="http://mc/compose?to=roy.radford42@..." target="_new">http://mc/compose?to=roy.radford42@...>>
> >
>
> Hi, Dave,
>
>             Ah, I didn't know there was a downside-up equivalent to the
> ULN2803. That's a MUCH better solution... Just shows how out-of-touch I'm
> getting in my old age!
>
>     Have fun,
>
>         Roy.
>
>
> --- On *Fri, 4/3/11, davetutlo@... href="http://mc/compose?to=davetutlo@..." target="_new">http://mc/compose?to=davetutlo@...>>
> <davetutlo@... <http://mc/compose?to=davetutlo@...>:
>
>
> From: davetutlo@... <http://mc/compose?to=davetutlo@...>> <
> davetutlo@... <http://mc/compose?to=davetutlo@...>>>
>
> Subject: Re: [jOrgan-user] SAMS and lighted pistons
> To: jorgan-user@... href="http://mc/compose?to=jorgan-user@..." target="_new">http://mc/compose?to=jorgan-user@...>>
> Date: Friday, 4 March, 2011, 4:22
>
>
> Hi Don,
> The last time I spoke to you on some other site was 12 years ago(about
> organs of course).
> I haven't spoken to our friend Owen for a good while.
> I'm glad you are here having fun with Jorgan.
> I retired but got pulled back and was away from jorgan for a very long
> time.
> Really interrupted my jorgan project !!
>
> Your plan for the bulbs is OK !!
> 1-You need to have a +5VDC power supply with enough current capability to
> drive
> HOWEVER MANY BULBS you think you might drive at ONE TIME. !!
> You know how it is... some say 'oh only 3 stops at a time'. But the design
> will
> allow some one to walk up to you organ and turn them all on if they can
> they will.
> This should not be any problem at all.
>
> 2-You need to use the UDN2982A for your drivers.
> Be aware these are noninverting.
> 3-The outputs from your HC595's are all wired to the inputs (pins 1-8) of
> the UDN2982A's
> and the outputs from the 2982A's are connected directly to your bulbs.
> 4-The UDN2982A pin-9 is connected to your +5VDC source.
> 5-The UDN2982A pin_10 gets connected to your ground.
>
> 6-The 'noninverting' means that when your software sends a positive signal
> to your HC595 inputs, this will turn ON your bulb.
>
> If I can help any further, just ask or email me directly.
> DaveT
>
>
>
>
>
> On 1 Mar 2011 at 14:35, Don Becker wrote:
>
> > Thanks for your help John C and Al,
> > I'm still confused. The diagram of the Dout board running the relays
> using
> > the 2803 chips, shows the outputs of the 74HC595 going to the inputs of
> the
> > ULN2803 gates and the outputs of the 2803 gates going to one side of the
> > relays and the other side of the relays (and also pin 10 of the 2803)
> going
> > to +DC voltage. I'm trying to use this configuration , not to turn relays
> on
> > and off but to turn my stopswitch lamps (50ma @ +5VDC) on and off and the
> > lamps need an input of +5VDC to turn on. Their outputs go to Gnd. Thats
> the
> > way they are mounted on my jamb circuit bds.
> > This doesn't look like it is going to work. What am I missing???
> > Don
> >
> > --
> > View this message in context:
> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3330731.html
> > Sent from the jOrgan - User mailing list archive at Nabble.com.
> >
> >
> ------------------------------------------------------------------------------
> > Free Software Download: Index, Search & Analyze Logs and other IT data in
>
> > Real-Time with Splunk. Collect, index and harness all the fast moving IT
> data
> > generated by your applications, servers and devices whether physical,
> virtual
> > or in the cloud. Deliver compliance at lower cost and gain new business
> > insights. http://p.sf.net/sfu/splunk-dev2dev
> > _______________________________________________
> > jOrgan-user mailing list
> > jOrgan-user@... href="http://mc/compose?to=jOrgan-user@..." target="_new">http://mc/compose?to=jOrgan-user@...>>
> > https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@... href="http://mc/compose?to=jOrgan-user@..." target="_new">http://mc/compose?to=jOrgan-user@...>>
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@... href="http://mc/compose?to=jOrgan-user@..." target="_new">http://mc/compose?to=jOrgan-user@...>>
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>
>
> -----Inline Attachment Follows-----
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
>
> -----Inline Attachment Follows-----
>
>
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@... href="http://mc/compose?to=jOrgan-user@..." target="_new">http://mc/compose?to=jOrgan-user@...>>
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
>

BUT Roy and Geert and Erik,
I already have 256 incandescent 6VDC blubs (I'm running them at 5VDC)
soldered to circuit boards (A LOT OF EFFORT) and UDN2874s are sitting here,
all I need to do is unsolder the resistor packs, solder 18 pin sockets, run
jumper wires for +5VDC and ground and as Dave suggests use plenty of 5VDC
power supplies (which I have sitting here). Now I have to finish Rick's
great tutorial on understanding the MIDI code and putting the MIDI code into
the cores (which I am beginning to grasp) and meybe this whole thing will
work. Thank you all for your help.
Don

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3338096.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hi, Don,

           Oh, yes, in that situation, so long as your power supplies have the muscle to drive that little lot, leave well alone!

     Have fun,

        Roy.


--- On Sun, 6/3/11, Don Becker <soniccr@...> wrote:

From: Don Becker <soniccr@...>
Subject: Re: [jOrgan-user] SAMS and lighted pistons
To: jorgan-user@...
Date: Sunday, 6 March, 2011, 21:35

BUT Roy and Geert and Erik,
I already have 256 incandescent 6VDC blubs (I'm running them at 5VDC)
soldered to circuit boards (A LOT OF EFFORT) and UDN2874s are sitting here,
all I need to do is unsolder the resistor packs, solder 18 pin sockets, run
jumper wires for +5VDC and ground and as Dave suggests use plenty of 5VDC
power supplies (which I have sitting here). Now I have to finish Rick's
great tutorial on understanding the MIDI code and putting the MIDI code into
the cores (which I am beginning to grasp) and meybe this whole thing will
work. Thank you all for your help.
Don

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3338096.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
jOrgan-user mailing list
jOrgan-user@...
https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi Don

I am here in the background watching your posts.  Let me know if I can 
be of any help outside existing documentation.

Do you have the latest MIOS Studio V2.1?  This new software for the 
MidiBox system has greatly simplified the programming and testing of the 
MIDIO128 system.  (There is now no need to run notepad files through 
Perl script to create the HEX files to upload.)
Do you have the special MIDIO128 HEX file that includes 3x Analogue 
inputs from the MidiBox Core?  This allows swell and crescendo from any 
of your CORE cards.

I have not done anything with the MIDI output back to lamps or SAMS, but 
should be able to help in other ways.

Regards
Rick

On 7/03/2011 7:35 a, Don Becker wrote:
> BUT Roy and Geert and Erik,
> I already have 256 incandescent 6VDC blubs (I'm running them at 5VDC)
> soldered to circuit boards (A LOT OF EFFORT) and UDN2874s are sitting here,
> all I need to do is unsolder the resistor packs, solder 18 pin sockets, run
> jumper wires for +5VDC and ground and as Dave suggests use plenty of 5VDC
> power supplies (which I have sitting here). Now I have to finish Rick's
> great tutorial on understanding the MIDI code and putting the MIDI code into
> the cores (which I am beginning to grasp) and meybe this whole thing will
> work. Thank you all for your help.
> Don
>
> --
> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3338096.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

Don,
There are a million kinds of leds out there.
You can easily 'google for the color you want 
AND get them with integrated "limiting resistors" (already built in).
That is -- if you decide to change to leds.
DaveT





On 6 Mar 2011 at 13:35, Don Becker wrote:

> BUT Roy and Geert and Erik,
> I already have 256 incandescent 6VDC blubs (I'm running them at 5VDC)
> soldered to circuit boards (A LOT OF EFFORT) and UDN2874s are sitting here,
> all I need to do is unsolder the resistor packs, solder 18 pin sockets, run
> jumper wires for +5VDC and ground and as Dave suggests use plenty of 5VDC
> power supplies (which I have sitting here). Now I have to finish Rick's
> great tutorial on understanding the MIDI code and putting the MIDI code into
> the cores (which I am beginning to grasp) and meybe this whole thing will
> work. Thank you all for your help.
> Don
> 
> --
> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3338096.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi Rick (and anyone else willing to help),
I've spent several entire days trying to somehow get my hex numbers into
some form that MIOS Studio 2 will accept. These hex numbers read on Midiox
as I pushed the On and Off buttons on each stopswitch (My limited size
hardware combo-action still works).
Ex: 1st 2 stopswitches using separate on button and off button for each
stop.
1 = 97  24  40  87  24  00
2 = 97  25  40  87  25  00
I added the 1= and 2=, 97 is for ch 8 (don't know what the 9 stands for), 24
is C1 of MIDI Interface, 40 to turn on stopswitch, 87  is for ch 8 (don't
know what the 8 stands for), 24 is C1, 00 to turn off stopswitch.
I have all these hex numbers for the 32 Swell stops, can't seem to make them
into a .hex  file I can open up in MIOS Studio to upload to the core. Can't
seem to make the Midio128 tool in Mios Studio do anything useful. The core
readout in MIOS Studio says "application is up and running". HELP!!!
Don Becker


--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3391288.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

"9" is the MIDI command for "Note-On" in hexadecimal, and "8" is the MIDI command for 
"Note-Off" in hex.

Sorry, I can't help with MIOS Studio 2, as I have never used it.

CLW
-----------------------------------------------------------------

On 3/20/2011 11:48 AM, Don Becker wrote:
> Hi Rick (and anyone else willing to help),
> I've spent several entire days trying to somehow get my hex numbers into
> some form that MIOS Studio 2 will accept. These hex numbers read on Midiox
> as I pushed the On and Off buttons on each stopswitch (My limited size
> hardware combo-action still works).
> Ex: 1st 2 stopswitches using separate on button and off button for each
> stop.
> 1 = 97  24  40  87  24  00
> 2 = 97  25  40  87  25  00
> I added the 1= and 2=, 97 is for ch 8 (don't know what the 9 stands for), 24
> is C1 of MIDI Interface, 40 to turn on stopswitch, 87  is for ch 8 (don't
> know what the 8 stands for), 24 is C1, 00 to turn off stopswitch.
> I have all these hex numbers for the 32 Swell stops, can't seem to make them
> into a .hex  file I can open up in MIOS Studio to upload to the core. Can't
> seem to make the Midio128 tool in Mios Studio do anything useful. The core
> readout in MIOS Studio says "application is up and running". HELP!!!
> Don Becker
>
>
> --
> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3391288.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

Hello Don

As I have mentioned, I have no experience with [MIDI_IN] of MidiBox and 
have no way to actually test it to give you a live example.

I suspect from the way you have written your question that we haven't 
clarified the MIDI messages enough yet.  I actually think you are trying 
to make it more complicated than it needs to be.

"Don wrote:
1 = 97  24  40  87  24  00
2 = 97  25  40  87  25  00
I added the 1= and 2=, 97 is for ch 8 (don't know what the 9 stands for), 24
is C1 of MIDI Interface, 40 to turn on stopswitch, 87  is for ch 8 (don't
know what the 8 stands for), 24 is C1, 00 to turn off stopswitch.

In your example above (this is HEX) I suspect it is the MIDI_OUT
section (You need to be working on MIDI_IN).   "9" is Note On, "7" is
channel 8, "24" is the lowest "C" note on an organ keyboard but totally
irrelevant in your application.  You can assign it to be either an
activate or deactivate magnet of any one of your stops.  The "40" is the
  velocity at which the note is struck and again totally irrelevant in
your application.  The next set of 3x pairs of information is the
Note_Off message for the same note.  The MIDI_IN you will be working
with is not looking for this second half of the message.

I have all these hex numbers for the 32 Swell stops, can't seem to make them
into a .hex  file I can open up in MIOS Studio to upload to the core. Can't
seem to make the Midio128 tool in Mios Studio do anything useful. The core
readout in MIOS Studio says "application is up and running". HELP!!!"

What version of MIOS Studio are you using?  (The latest is V2.1)
Have you used MidiBox to send note information from a key-switch to jOrgan, or are you just trying to learn how to use MidiBox just to get information from jOrgan and convert it to an electronic output (MIDI_IN)?


Below I have copied the documentation from the MidiBox configuration 
file.  This is the old way to configure MidiBox.  MIOS studio2.x has a 
simplified way of configuring this information but I would need to be 
connected to a device to see the config screen.

################################################################################
# The MIDI_IN and MIDI_OUT sections include all settings for the IO pins
#
################################################################################
# Syntax for a MIDI IN entry (MIDI event controls output pin):
# <pin-number> = <byte 0> <byte 1>
#
# The maximum allowed number of output pins is 128
#
# Supported MIDI events (. stands for hex digit, vv stands for 00 or 7F)
#   9. .. (Note On)            Example: 90 30   (MIDIO128 receives 90 30 vv)
#   A. .. (Poly Aftertouch)    Example: A0 30   (MIDIO128 receives A0 30 vv)
#   B. .. (Controller)         Example: B0 07   (MIDIO128 receives B0 07 vv)
#   C. .. (Program Change)     Example: C0 30   (MIDIbox receives C0 30)
#   D. .. (Channel Aftertouch) Example: D0 30   (MIDIbox receives D0 30)
#   E. .. (Pitch Bender)       Example: E0 7F   (MIDIbox receives E0 7F vv)
#
# - On 2-byte events (C. and D.), the output pins just toggle (0->1 or 1->0)
################################################################################

[MIDI_IN]
     1 =  90 30
     2 =  90 31
     3 =  90 32
     4 =  90 33
     5 =  90 34
     6 =  90 35
     7 =  90 36
     8 =  90 37
     9 =  90 38
    10 =  90 39
    11 =  90 3A
    12 =  90 3B
    13 =  90 3C
    14 =  90 3D
    15 =  90 3E
    16 =  90 3F

    17 =  90 40
    18 =  90 41
    19 =  90 42

If we take this last example, Output number 19 will turn on if it gets a 
HEX message 90 42.
If we convert it to DEC it is 144 66.

I suspect if you create an "Activate" command in jOrgan of 144 66 127 
(you may or may not need to add the 127 at the end) It will activate 
this output.  This one will activate a magnet to turn a tab on.  You 
will then need another command in jOrgan to activate the other magnet to 
turn a tab off.

This particular example is:
(hex) "9" means NOTE ON
(hex) "0" means CHANNEL 1
(dec) "144" means both of the above combined NOTE ON, CHANNEL 1.
eg. "145" would mean NOTE ON, CHANNEL 2.

(hex) "42" is note number hex 42 on a scale of 0 to 7F
(dec) "66" is the same note number on a scale of 0 to 127

You will need to set an arbitrary list of what messages your MidiBox 
Midi_In is looking for (or start with the default (remembering they are 
in HEX).  You will need to write your own list of which tabs these are 
connceted to and if they are the activate magnet or the deactivate 
magnet.  You will then need to decide which tab in jOrgan needs to link 
to the specific MidiBox Midi_In and enter its message (remembering it 
needs to be in DEC).

I suspect jOrgan should send out the trigger message to that MidiBox 
Midi_In (output number) for the duration set in its jOrgan parameters.  
It will then stop driving the output.

I hope this gives you something more to take another step in getting 
this working.

Regards
Rick

On 21/03/2011 1:48 a, Don Becker wrote:
> Hi Rick (and anyone else willing to help),
> I've spent several entire days trying to somehow get my hex numbers into
> some form that MIOS Studio 2 will accept. These hex numbers read on Midiox
> as I pushed the On and Off buttons on each stopswitch (My limited size
> hardware combo-action still works).
> Ex: 1st 2 stopswitches using separate on button and off button for each
> stop.
> 1 = 97  24  40  87  24  00
> 2 = 97  25  40  87  25  00
> I added the 1= and 2=, 97 is for ch 8 (don't know what the 9 stands for), 24
> is C1 of MIDI Interface, 40 to turn on stopswitch, 87  is for ch 8 (don't
> know what the 8 stands for), 24 is C1, 00 to turn off stopswitch.
> I have all these hex numbers for the 32 Swell stops, can't seem to make them
> into a .hex  file I can open up in MIOS Studio to upload to the core. Can't
> seem to make the Midio128 tool in Mios Studio do anything useful. The core
> readout in MIOS Studio says "application is up and running". HELP!!!
> Don Becker
>
>
> --
> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3391288.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

Hi Rick,
Thanks for the help. I think I loaded the core. I used the Midio128 tool in
Mios Studio 2 but still don't understand some things. For instance, What
does Parameter mean? It starts with 48, goes up to 111 for the 64th Dout
(#63), then starts with 16 for Dout 64 and goes up to 79 for 127th Dout
(#128). I just left them all as is and changed all the events to Note On.
Saved it as a .sys document. Sent it to the core, closed out Mios, then
reopened it , went to Midio128 Tool, pressed Receive, and the same numbers I
sent, came back. In the Mios Studio window, I don't understand the really
weird assortment of letters and numbers. I don't understand either why you
started with 30 in your example  1 = 90  30
Won't know whether this all works until I get the Dout boards wired in place
and figure out how to change the messages in my disposition. I'm using my
old combo-action bds. (without the memory stuff connected) to connect the
momentary pushbutton switches to the MIDI Interface notes I'm using to turn
on stops in my disposition and the Dout bds with the UDN2807s to turn the
lamps on when a stop is activated.
Thanks much for the help.
Don

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3397929.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hello Don

Parameter 1 is crucial to getting this to work.

In the normal context of MIDI.  Parameter 1 specifies which note is 
triggered by a MIDI message.  (There is a look-up chart in my 
documentation.)
http://www.tosa-qld.org/VTPO/docs/Simple_MIDI_for_Miditzer.pdf    (page 11)
http://www.tosa-qld.org/VTPO/docs/Midification_of_an_Organ.pdf

In your application Parameter 1 will specify which magnet is triggered 
by a MIDI message.  You will need to make your own list of this based on 
which output number on your DOUT card is physically wired to which 
magnet.  Each stop will have an activate magnet and a de-activate magnet.

If you have 64 stops (each have 2x Parameter 1 values), then all of your 
Parameter 1 values can be on a single MIDI channel.  For example you 
could choose to put all your stop messages on MIDI channel 16 and use 
Parameter 1 values 0 to 127 as the controls for 64 stops.

If you have more than 64 stops you will use an extra one or more 
channels to end up with the number you need.

(HEX, MidiBox) 9F 00  =  (DEC, jOrgan) 159 000       this is the first 
identifiable item on MIDI channel 16, note on
(HEX, MidiBox) 9F 01  =  (DEC, jOrgan) 159 001       this is the next 
identifiable item on MIDI channel 16, note on

Parameter 2 in normal MIDI is the velocity value.  I don't think this is 
needed in your application.  In note control, any value greater than 00 
will activate a note (and in some MIDI applications will determine the 
volume) where a MIDI note on message with a 00 value will effectively be 
a MIDI note off message.  The actual MIDI note off message is rarely used.

Regards
Rick


On 23/03/2011 8:19 a, Don Becker wrote:
> Hi Rick,
> Thanks for the help. I think I loaded the core. I used the Midio128 tool in
> Mios Studio 2 but still don't understand some things. For instance, What
> does Parameter mean? It starts with 48, goes up to 111 for the 64th Dout
> (#63), then starts with 16 for Dout 64 and goes up to 79 for 127th Dout
> (#128). I just left them all as is and changed all the events to Note On.
> Saved it as a .sys document. Sent it to the core, closed out Mios, then
> reopened it , went to Midio128 Tool, pressed Receive, and the same numbers I
> sent, came back. In the Mios Studio window, I don't understand the really
> weird assortment of letters and numbers. I don't understand either why you
> started with 30 in your example  1 = 90  30
> Won't know whether this all works until I get the Dout boards wired in place
> and figure out how to change the messages in my disposition. I'm using my
> old combo-action bds. (without the memory stuff connected) to connect the
> momentary pushbutton switches to the MIDI Interface notes I'm using to turn
> on stops in my disposition and the Dout bds with the UDN2807s to turn the
> lamps on when a stop is activated.
> Thanks much for the help.
> Don
>
> --
> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3397929.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

Hi Rick, 
Herein lies my confusion. As of now, I have been using my big hardware
combo-action. My  lighted drawknob stopswitch bds (in the combo-action) have
8 stopswitch circuits on ea. bd + an EEProm . Each stopswitch circuit has an
"On" pin and an "Off" pin to which I connect my "On" pushbutton and "Off"
pushbutton for each stop. There are no magnets. The "On" pin turns on a
flipflop, the output of which sends 5VDC to a note on a Syndyne 61 note MIDI
Interface turning on a stop in jorgan. The "Off" pin turns off the flipflop,
turning off the MIDI Interface note (turning off the stop in jorgan). In
addition to sending the +5VDC to the MIDI Interface note, the "On" pin is
also connected to a xstr drive circuit which is connected to a +5vDC lamp
which is behind a transluscent plastic engraved stop nameplate (under the
"On" and "Off" pushbuttons),which lights up when the "On" pushbutton is
pushed. When the "Off" pushbutton (connected to the "Off" pin on the
stopswitch bd.) is pushed, it turns off the lamp. I have enough lighted
drawknob stopswitch bds. to complete my organ but the EEProms are no longer
made and I only have enough EEProms for half of my stopswitch bds. The
stopswitch bds. do work (without the EEProm) and light up the lamps but if I
use the combo-action that is built into jorgan and connect my combination
pistons to more MIDI Interface notes to operate the jorgan combinations, my
lights don't light up when I push a piston (because jorgan is turning the
stops on in my disposition but not sending any message back that would turn
on the lamps in those stops the combination is turning on). That is the main
reason I wanted to use the Dout bds (to light my lamps instead of using the
lamp circuit part of the stopswitch bd.). I really had hoped to use my
pushbuttons to operate the stops in jorgan directly (by operating my MIDI
Interface notes which turn on each stop) and not use my stopswitch bds. at
all, but that will not work, so I'll have to use my stopswitch bds to turn
the stops on and off and the Douts only to light the lamps.
So what will the Parameter 1 specify since the outputs of the UDN2807
drivers I'm installing on the Dout bds are only connected to lamps? I am
really a confused person!!
Regards,
Don

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3400606.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hello Don

My apologies for making assumptions that don't fit your requirement.  I 
probably should have taken more notice of your earlier posts before I 
started to try to help.

Lets take your application as two separate issues.
1/ illuminated stops
2/ stop to jOrgan control

Number 1/ is what we have been concentrating on.  With the detail of 
your last message I believe we are able to simplify what we are trying 
to do.  You don't need two outputs per stop.

Now this is the part that you will need to do a little experiment.  I 
don't know exactly how the DOUT card will respond to MIDI commands.  It 
would seems to me that a Note On message (on the specified channel and 
the specified Par1 value) will turn On the output (your connected 
bulb).  I suspect this stays on till it gets a Note Off message (on the 
specified channel and the specified Par1 value).  If this is how it 
works, I believe you will put in the jOrgan SAM's Element an Activate 
message (note on MIDI code) and a deactivate message (note off MIDI 
code).  You will need to disable the timer function that has been put in 
for magnet activation so the deactivate only occurs when the tab turns 
off (not after a timer period).

Do you think you would find it easier to connect a simple keyboard to 
the MidiBox and DOUT for your first test so jOrgan is not required?  Do 
you have a MIDI keyboard sending out on MIDI channel 1?  Connect this to 
your MIDI Box, set your MidiBox DOUT 1 to (HEX) 90 24.  (Bottom "C" on a 
5 octave keyboard.) (or HEX 90 60, top "C" on a 5 octave keyboard)
Does the output come on when you press this key?  Does it stay on till 
you release the key?

Number 2/ so you have an On switch and an Off switch.  These go through 
a Flip- Flop.  The output of the Flip-Flop could be your input to 
jOrgan, but if tabs are changed on the PC screen or by the jOrgan 
combination action, the Flip-Flop will be out of sync with the sounding 
stop.

The best option would need you to have double the MIDI switch inputs.  
You would have one input for tab on, and a separate input for tab off.  
You will need the programming capability of MidiBox DIN to do this, as I 
don't think "normal" midi inputs would allow you to NOT send a note off 
when your momentary switch is released.

Does this make any sense?

Regards
Rick


On 24/03/2011 6:24 a, Don Becker wrote:
> Hi Rick,
> Herein lies my confusion. As of now, I have been using my big hardware
> combo-action. My  lighted drawknob stopswitch bds (in the combo-action) have
> 8 stopswitch circuits on ea. bd + an EEProm . Each stopswitch circuit has an
> "On" pin and an "Off" pin to which I connect my "On" pushbutton and "Off"
> pushbutton for each stop. There are no magnets. The "On" pin turns on a
> flipflop, the output of which sends 5VDC to a note on a Syndyne 61 note MIDI
> Interface turning on a stop in jorgan. The "Off" pin turns off the flipflop,
> turning off the MIDI Interface note (turning off the stop in jorgan). In
> addition to sending the +5VDC to the MIDI Interface note, the "On" pin is
> also connected to a xstr drive circuit which is connected to a +5vDC lamp
> which is behind a transluscent plastic engraved stop nameplate (under the
> "On" and "Off" pushbuttons),which lights up when the "On" pushbutton is
> pushed. When the "Off" pushbutton (connected to the "Off" pin on the
> stopswitch bd.) is pushed, it turns off the lamp. I have enough lighted
> drawknob stopswitch bds. to complete my organ but the EEProms are no longer
> made and I only have enough EEProms for half of my stopswitch bds. The
> stopswitch bds. do work (without the EEProm) and light up the lamps but if I
> use the combo-action that is built into jorgan and connect my combination
> pistons to more MIDI Interface notes to operate the jorgan combinations, my
> lights don't light up when I push a piston (because jorgan is turning the
> stops on in my disposition but not sending any message back that would turn
> on the lamps in those stops the combination is turning on). That is the main
> reason I wanted to use the Dout bds (to light my lamps instead of using the
> lamp circuit part of the stopswitch bd.). I really had hoped to use my
> pushbuttons to operate the stops in jorgan directly (by operating my MIDI
> Interface notes which turn on each stop) and not use my stopswitch bds. at
> all, but that will not work, so I'll have to use my stopswitch bds to turn
> the stops on and off and the Douts only to light the lamps.
> So what will the Parameter 1 specify since the outputs of the UDN2807
> drivers I'm installing on the Dout bds are only connected to lamps? I am
> really a confused person!!
> Regards,
> Don
>
> --
> View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3400606.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

I don't have a MIDI keyboard but I do have a spare Syndyne MIDI Interface. I
can try the 1st experiment using that, just touching +5V to C1. I'll try it
tomorrow. Then I'll proceed from that point.
Regards
Don

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3401434.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hi Rick,
As I was starting to do the things you suggested, my Midisport Uno USB Midi
Interface quit working and I will have to wait till a replacement arrives to
continue (hopefully late this week). Can't use my spare Syndyne Midi
Interface because it only has MIDI In, MIDI out and MIDI Thru but no way to
connect it both to the core and back to the computer (no USB connection).
Your questions to John W. and his answers about the Sams Console were very
helpful to me. Thank you both.
Regards to you both,
Don Becker

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3409406.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hey Don, , Rick:
I spent a good deal of time setting up a second SAMS console to operate on a 
different channel, and finally got it working, with one stop on each SAMS 
console.   Finally realized that you don't need the rank element along with 
the stop elements when using the SAMS console, so I deleted all the ranks 
with no ill effect.  since I am using an artisan sound engine,  Ranks are 
internal to the sound engine programming anyway.
What I had a problem with was  using the "send to"  feature in moving 
elements from the SAMS console display to the main console.  At first, I was 
confused by the nomenclature of the SAMS Console, because of the use of the 
word "console"  which was also in the list of elements.  My assumption is 
that you need a "Console",  but also a SAMS console.  I started with a SAMS 
console, my primary interest being getting the SAMS console to work with my 
midibox core and DOUTS.  Then I started building the overall  disposition 
and noticed the "console" element which has essentially the same properties, 
except the console doesn't have the duration property.  In thinking about 
it, I am not sure that I really need the "console" element, as the liest of 
outputs are the same for both consoles.  Perhaps someone on the List will 
comment about that.
Anyway, I used the "Send to" feature and moved all screen elements from the 
two SAMS consoles to the "console", and so far. that is working.  Had a 
problem with the Skins on the SAMS console display screens.  I could not and 
have not been able to remove "skinned elements", like labels that I didn't 
move.  Then all of a sudden I had a full screen of labels, and no way to 
remove them from one of the SAMS console screen.  is it possible to remove 
the SAMS console screens without removing the SAMS console element?  I still 
have three tabs on the display;  Console,  SAMS console 1,  SAMS console 2. 
All stops, pistons, etc. are on the Console and the two SAMS consoles are 
blank.   Seems like there should be a way to remove the blank screens.
If you are lighting stops rather then operating SAMS, your disposition would 
be similar, except I don't think that the SAMS console would benefit you. 
However, I am not familiar with your situation.
Johnc

----- Original Message ----- 
From: "Don Becker" <soniccr@...>
To: <jorgan-user@...>
Sent: Sunday, March 27, 2011 8:39 AM
Subject: Re: [jOrgan-user] SAMS and lighted pistons


> Hi Rick,
> As I was starting to do the things you suggested, my Midisport Uno USB 
> Midi
> Interface quit working and I will have to wait till a replacement arrives 
> to
> continue (hopefully late this week). Can't use my spare Syndyne Midi
> Interface because it only has MIDI In, MIDI out and MIDI Thru but no way 
> to
> connect it both to the core and back to the computer (no USB connection).
> Your questions to John W. and his answers about the Sams Console were very
> helpful to me. Thank you both.
> Regards to you both,
> Don Becker
>
> --
> View this message in context: 
> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3409406.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user

Hi Rick and John C.,
I am seriously lost trying to make this work. There was a 1  1/2 week wait
for a new E-Mu USB MIDI Interface. since then I have been trying to use the
MIOS Studio 2.1 Midio 128 Tool to program the PIC Chip. I have used the MIDI
messages appearing on the MIDI-Ox display which affirmed the fact that I had
set the Syndyne MIDI Interface (used for my stops) to Channel 8 and started
my first 32 Swell stopswitches at note #C1 on the Syndyne MIDI Interface and
went with the Swell stops thru note 32. When I pressed the 1st stop button,
for some reason the first message on the MIDI-OX was  97  24  40  which I
assume is  9(note on) 7(channel 8 on the MIDI Interface), 24 (C1 on the MIDI
Interface) and 40(don't know what that is). On the Midio 128 tool  I used
Channel 8, Note On and started with 24 for Par. 1. I did the Par. 1 numbers
consecutively as in 25, 26, 27 etc thru 56 and sent it to MIOS. In order to
have MIOS send back any signal at all, I had to unplug the MIDI Out cable on
the E-Mu MIDI Interface (Which was plugged into the In MIDI connector on the
Core board), and plug in a MIDI cable from my MIDI Patch Bay. Cables from my
main MIDI Interface(an Intermidi MIDI Interface ((Intermidi is no longer in
business but the Interface has been 100% reliable since 1995))for 3
keyboards and Pedals that the organ keyboards are connected to the MIDI
patchbay from, and a cable from the Patchbay goes to the jorgan computer. So
now I have one MIDI cable from the patchbay to the jorgan computer and
another MIDI cable from the patchbay to the Core board MIDI In. The problem
is that when I press On Buttons from the organ stopswitches,  different
lamps light up at different times. I can turn on the same 6 stopswitch On
buttons, they will light up 6 lamps and then if I turn everything off, turn
everything back on and 6 different lamps light up. 
BooHoo, don't know how to proceed.
Thanks in advance if you still feel like helping. I'm sure its just as
confusing to read as it has been confusing to keep track of.
Have been enjoying the conversation between you (Rick) and you (John C.)
about the Sams console and Midio problems, since my last post. Wish I
understood as much as you two do about Midio.
Don

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3450186.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hello Don

See comments in the text below.  I am a bit confused but can offer a 
couple of pointers that may be of some assistance.

Regards
Rick

On 15/04/2011 3:01 a, Don Becker wrote:
> Hi Rick and John C.,
> I am seriously lost trying to make this work. There was a 1  1/2 week wait
> for a new E-Mu USB MIDI Interface. since then I have been trying to use the
> MIOS Studio 2.1 Midio 128 Tool to program the PIC Chip. I have used the MIDI
> messages appearing on the MIDI-Ox display which affirmed the fact that I had
> set the Syndyne MIDI Interface (used for my stops) to Channel 8 and started
> my first 32 Swell stopswitches at note #C1 on the Syndyne MIDI Interface and
> went with the Swell stops thru note 32. When I pressed the 1st stop button,
> for some reason the first message on the MIDI-OX was  97  24  40  which I
> assume is  9(note on) 7(channel 8 on the MIDI Interface), 24 (C1 on the MIDI
> Interface) and 40(don't know what that is).
Please be aware these are HEX numbers.  The 40 is Par.2 which is 
Velocity.  As long as the velocity is not "0" other values shouldn't 
affect this experiment.  Velocity is like from a piano keyboard which 
will affect the volume of the note.  Velocity "0" is sometimes used 
instead of "Note Off"
>   On the Midio 128 tool  I used
> Channel 8, Note On and started with 24 for Par. 1. I did the Par. 1 numbers
> consecutively as in 25, 26, 27 etc thru 56 and sent it to MIOS. In order to
> have MIOS send back any signal at all, I had to unplug the MIDI Out cable on
> the E-Mu MIDI Interface (Which was plugged into the In MIDI connector on the
> Core board), and plug in a MIDI cable from my MIDI Patch Bay. Cables from my
> main MIDI Interface(an Intermidi MIDI Interface ((Intermidi is no longer in
> business but the Interface has been 100% reliable since 1995))for 3
> keyboards and Pedals that the organ keyboards are connected to the MIDI
> patchbay from, and a cable from the Patchbay goes to the jorgan computer. So
> now I have one MIDI cable from the patchbay to the jorgan computer and
> another MIDI cable from the patchbay to the Core board MIDI In.
You need to be careful you don't create a MIDI loop.  If possible use a 
different MIDI interface to get MIDI information from your console, from 
the device you use to send MIDI to your light output device (at least 
just for initial testing)
>   The problem
> is that when I press On Buttons from the organ stopswitches,  different
> lamps light up at different times. I can turn on the same 6 stopswitch On
> buttons, they will light up 6 lamps and then if I turn everything off, turn
> everything back on and 6 different lamps light up.
> BooHoo, don't know how to proceed.
Do you have jOrgan in this configuration?  For testing purposes, I would 
start with feeding known MIDI signals direct to the CORE with the DOUT 
card (no jOrgan at all till you understand how this functions)
Are the stop switches reliably sending the same code every time?
If you feed the stop switches directly to the CORE with the DOUT (and 
program the unit to accept the matching MIDI codes) do they give a 
reliable repeatable output?
> Thanks in advance if you still feel like helping. I'm sure its just as
> confusing to read as it has been confusing to keep track of.
> Have been enjoying the conversation between you (Rick) and you (John C.)
> about the Sams console and Midio problems, since my last post. Wish I
> understood as much as you two do about Midio.
> Don
I hope this is of some help.

Hi Rick,
Thanks again for your help. Do you mean that, since can't easily disconnect
my organ keyboard from the MIDI INterface that is connected to my jorgan
computer and I don't have another MIDI keyboard but I do have another MIDI
Interface (I have an extra Syndyne 61 note MIDI Interface) and if I feed the
MIDI message (for instance 97 24  40 which is what I ALWAYS get at the
output when I touch +5VDC to pin 1 of the MIDI Interface input that is set
for ch 8. But that is in hex) to the core. Doesn't the input to the core
have to be in  .sys form? If it does, how can I do this for 1 note just to
try it? (By the way, I always get the same MIDI messages in MIDI OX when
pressing the ON Buttons of the stopswitches).
Hope you can make some sense out of my message
Regards, Don

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3473289.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hello Don

What I suggest you do is, with whatever MIDI devices you have at the 
moment, make a list of the MIDI messages you get from about 10 
consecutive triggers.  I suggest you use your Stop On and relating Stop 
Off buttons for 5 consecutive stops.  Write down the MIDI messages you 
see in MIDIOX (in HEX) listing Stop On, Stop Off with the messages you 
see for each.

Now, have you used MIOS Studio 2 to configure any of your DOUT pins yet?

Your first DOUT card attached to your CORE will have output pins 1 
through 32.  You will need to configure the [MIDI_IN] section of the 
MIDIO128 configuration file with the "Stop On" messages you have noted 
above.
(if we use the example you have given you should configure [MIDI_IN] 1 = 
97 24 (don't enter the 40)
Do this in consecutive order for the Stop On information you have 
written above.
MIOS Studio 2 will look after the SYX file, you don't even need to worry 
about it.  Once you have worked out what messages you want these to be 
you will set them and only ever come back if you want to change 
something, most likely you will never need to go back to it.

Now, disconnect your computer from all your MIDI cables, connect a 
single MIDI cable from the MIDI OUT of the card that sends out the MIDI 
messages from your stops, and connect it directly to the MIDI IN on the 
MIDIBOX CORE that you have your DOUT card connected to.
When you press a particular Stop On switch it should activate your light 
on the DOUT pin you designated with that MIDI message.

If as you say it is too complicated to remove your computer from the 
MIDI path, then do all of the above using the first 5 inputs on your 
spare card.  So then you will end up with the spare card connected 
directly to the MIDIBOX CORE, MIDI IN with no computer in the loop at all.

Once you have done this you should see how the MIDIBOX CORE and DOUT are 
working.

Next you want to get jOrgan to be in the middle of all this.  jOrgan 
will need to be configured to read the messages coming from your stops.  
You should see stops on your jOrgan screen change as you change your 
stops.  You will then need to tell jOrgan what MIDI message you need 
sent out to the MIDIBOX CORE to activate your lights.
I have only suggested you configure the MIDIBOX CORE with the messages 
above so you can do an easy test without the computer (and jOrgan) 
involved in the loop.  For your final setup you can choose to configure 
the MIDIBOX CORE with whatever [MIDI_IN] messages you like to trigger 
its DOUT pins.  You will just need to set jOrgan to send the correct 
messages to match whatever you have configured in the MIDIBOX CORE 
configuration.

In normal use the messages to the MIDIBOX CORE MIDI IN connection are 
MIDI messages.  It is only the initial configuration made by MIOS Studio 
2 that is a SYX file.

Is this making any sense?

Regards
Rick

On 26/04/2011 12:44 a, Don Becker wrote:
> Hi Rick,
> Thanks again for your help. Do you mean that, since can't easily disconnect
> my organ keyboard from the MIDI INterface that is connected to my jorgan
> computer and I don't have another MIDI keyboard but I do have another MIDI
> Interface (I have an extra Syndyne 61 note MIDI Interface) and if I feed the
> MIDI message (for instance 97 24  40 which is what I ALWAYS get at the
> output when I touch +5VDC to pin 1 of the MIDI Interface input that is set
> for ch 8. But that is in hex) to the core. Doesn't the input to the core
> have to be in  .sys form? If it does, how can I do this for 1 note just to
> try it? (By the way, I always get the same MIDI messages in MIDI OX when
> pressing the ON Buttons of the stopswitches).
> Hope you can make some sense out of my message
> Regards, Don

Rick the Greenfox,
Thank  you for that posting.
Together we can make a difference as re stretch the potential of jOrgan
to provide our particular needs.
With folks like you and JohnCouvillon there is hope for the rest of us!
 
Paul
StentorVox.com
 

On 4/25/2011 11:08 PM, Rick (greenfox) wrote:
> Hello Don
>
> What I suggest you do is, with whatever MIDI devices you have at the 
> moment, make a list of the MIDI messages you get from about 10 
> consecutive triggers.  I suggest you use your Stop On and relating Stop 
> Off buttons for 5 consecutive stops.  Write down the MIDI messages you 
> see in MIDIOX (in HEX) listing Stop On, Stop Off with the messages you 
> see for each.

Hi again Rick,
I have  done this a # of times  and the MIDI messages (in HEX) in MIDIOX
have always been consistent. Here they are:
97 24 40
87 24 00
97 25 40
87 25 00
97 26 40
87 26 00
97 27 40
87 27 00
97 28 40
87 28 00

> Now, have you used MIOS Studio 2 to configure any of your DOUT pins yet?

Yes, I used MIOS Studio MIDIO128, the DOUT tool (which I hope is MIDI in). I
connected the USB MIDI Interface so that the MIDI Out Connector of the USB
Interface goes to the IN connector of the core and the MIDI IN connector of
the USB Interface goes to the OUT connector of the core. I used the MIDI
Device routing in MIOS Studio to connect things. Just to find out, I tried
connecting them wrongly and MIOS Studio query showed nothing working.

> Your first DOUT card attached to your CORE will have output pins 1 
> through 32.  You will need to configure the [MIDI_IN] section of the 
> MIDIO128 configuration file with the "Stop On" messages you have noted 
> above.
> (if we use the example you have given you should configure [MIDI_IN] 1 = 
> 97 24 (don't enter the 40)
> Do this in consecutive order for the Stop On information you have 
> written above.
> MIOS Studio 2 will look after the SYX file, you don't even need to worry 
> about it.  Once you have worked out what messages you want these to be 
> you will set them and only ever come back if you want to change 
> something, most likely you will never need to go back to it.

I did this. On the MIOS Studio 2 MIDIO128   DOUT chart, I put in CH 8 for
all and NOTE ON for all and put in 24 thru 28 consecutively in the Par 1
column for  1/D7, 1/D6, 1/D5, 1/D4 and 1/D3. Then I pressed SEND and it
slowly went from 0% to 100%.
>
> Now, disconnect your computer from all your MIDI cables, connect a 
> single MIDI cable from the MIDI OUT of the card that sends out the MIDI 
> messages from your stops, and connect it directly to the MIDI IN on the 
> MIDIBOX CORE that you have your DOUT card connected to.
> When you press a particular Stop On switch it should activate your light 
> on the DOUT pin you designated with that MIDI message.

No, it activates Lights randomly, never the correct lights. It wasn't
complicated to remove the jorgan computer from the output of MIDI Interface,
but nothing has changed. I don't have a clue what the core actually has in
it (and don't have a clue to finding out) except MIOS Studio  last said
"application is up and running (before I disconnected the USB MIDI Interface
and connected the MIDI cable from the MIDI out of the card that sends out
the MIDI messages from the stops). I did try my other core board and loaded
it?? ( It was Device ID  1. The first core board was Device ID  0.
>
> If as you say it is too complicated to remove your computer from the 
> MIDI path, then do all of the above using the first 5 inputs on your 
> spare card.  So then you will end up with the spare card connected 
> directly to the MIDIBOX CORE, MIDI IN with no computer in the loop at all.
>
> Once you have done this you should see how the MIDIBOX CORE and DOUT are 
> working.
>
> Next you want to get jOrgan to be in the middle of all this.  jOrgan 
> will need to be configured to read the messages coming from your stops.  
> You should see stops on your jOrgan screen change as you change your 
> stops.  You will then need to tell jOrgan what MIDI message you need 
> sent out to the MIDIBOX CORE to activate your lights.
> I have only suggested you configure the MIDIBOX CORE with the messages 
> above so you can do an easy test without the computer (and jOrgan) 
> involved in the loop.  For your final setup you can choose to configure 
> the MIDIBOX CORE with whatever [MIDI_IN] messages you like to trigger 
> its DOUT pins.  You will just need to set jOrgan to send the correct 
> messages to match whatever you have configured in the MIDIBOX CORE 
> configuration.

I configured Jorgan a couple of years ago to use this Syndyne MIDI Interface
to turn the stops on and off (using my old combo-action). It has worked
finely for 32 stops on the Swell, 18 on the Great and 18 on the Pedal. When
I press any "On" button, the correct stop ALWAYS comes on and jorgan
recognizes it.  The stop also turns on and off in the little boxes on the
jorgan desktop ( I don't use any skins because it is easier just to have the
stop names shown). It has also turned the lights on and off. Using the old
jorgan 2.4.3 , activating and deactivating the stops was as easy as it is in
3.12. I just didn't have to become acquainted with MIDI messages. I'm glad
that you have taught me the meaning of some of the MIDI messages and I thank
you for it. I also thank you for your effort in trying to help me get the
core and DOUTs working. Also I'm getting acquainted with the MIDI messages
shown on the screen (had to change a bunch of them to get the correct stops
to work when I opened my disposition in 3.12). In order to expand the organ
past the limitation of my combo-action, and also to have the combo-action in
jorgan turn the stopswitch lights on when I press a piston, I was trying
(unsuccessfully) to use the MIDIBOX and MIOS Studio.
>
> In normal use the messages to the MIDIBOX CORE MIDI IN connection are 
> MIDI messages.  It is only the initial configuration made by MIOS Studio 
> 2 that is a SYX file.
>
> Is this making any sense?

Yes, you have made marvelous sense. It just doesn't want to work.
Thanks so much for your help. We tried.
Regards,
Don
>


--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3479824.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hello again Don

I am sure we will crack this soon.  (as I have mentioned, I don't have 
any DOUT cards so am trying to assist you based only on my experience 
with DIN function so am needing you to be my eyes and ears for the tests.)

Graham Goode's question prompts me to take one step back and ask if you 
have loaded the MIDIO128 main.hex file?
This file is loaded using MIOS Studio 2.  This loads the main program 
into the CORE micro processor.  The .syx file we have been tinkering 
with, then loads specific IO configuration.  The .syx file won't work if 
the main.hex file is not loaded first.

Do you have a DIN card for your MidiBox system?  If you do we could 
check that contact closures on terminals of your DIN were sending MIDI 
messages OUT from your CORE.

When testing your DOUT card there is no need for the OUT MIDI connector 
on your core to be plugged to anything.  (you do need it for updating 
your configuration file though)

Regards
Rick

On 28/04/2011 10:46 a, Don Becker wrote:
> On 4/25/2011 11:08 PM, Rick (greenfox) wrote:
>> Hello Don
>>
>> What I suggest you do is, with whatever MIDI devices you have at the
>> moment, make a list of the MIDI messages you get from about 10
>> consecutive triggers.  I suggest you use your Stop On and relating Stop
>> Off buttons for 5 consecutive stops.  Write down the MIDI messages you
>> see in MIDIOX (in HEX) listing Stop On, Stop Off with the messages you
>> see for each.
> Hi again Rick,
> I have  done this a # of times  and the MIDI messages (in HEX) in MIDIOX
> have always been consistent. Here they are:
> 97 24 40
> 87 24 00
> 97 25 40
> 87 25 00
> 97 26 40
> 87 26 00
> 97 27 40
> 87 27 00
> 97 28 40
> 87 28 00
>
>> Now, have you used MIOS Studio 2 to configure any of your DOUT pins yet?
> Yes, I used MIOS Studio MIDIO128, the DOUT tool (which I hope is MIDI in). I
> connected the USB MIDI Interface so that the MIDI Out Connector of the USB
> Interface goes to the IN connector of the core and the MIDI IN connector of
> the USB Interface goes to the OUT connector of the core. I used the MIDI
> Device routing in MIOS Studio to connect things. Just to find out, I tried
> connecting them wrongly and MIOS Studio query showed nothing working.
>
>> Your first DOUT card attached to your CORE will have output pins 1
>> through 32.  You will need to configure the [MIDI_IN] section of the
>> MIDIO128 configuration file with the "Stop On" messages you have noted
>> above.
>> (if we use the example you have given you should configure [MIDI_IN] 1 =
>> 97 24 (don't enter the 40)
>> Do this in consecutive order for the Stop On information you have
>> written above.
>> MIOS Studio 2 will look after the SYX file, you don't even need to worry
>> about it.  Once you have worked out what messages you want these to be
>> you will set them and only ever come back if you want to change
>> something, most likely you will never need to go back to it.
> I did this. On the MIOS Studio 2 MIDIO128   DOUT chart, I put in CH 8 for
> all and NOTE ON for all and put in 24 thru 28 consecutively in the Par 1
> column for  1/D7, 1/D6, 1/D5, 1/D4 and 1/D3. Then I pressed SEND and it
> slowly went from 0% to 100%.
>> Now, disconnect your computer from all your MIDI cables, connect a
>> single MIDI cable from the MIDI OUT of the card that sends out the MIDI
>> messages from your stops, and connect it directly to the MIDI IN on the
>> MIDIBOX CORE that you have your DOUT card connected to.
>> When you press a particular Stop On switch it should activate your light
>> on the DOUT pin you designated with that MIDI message.
> No, it activates Lights randomly, never the correct lights. It wasn't
> complicated to remove the jorgan computer from the output of MIDI Interface,
> but nothing has changed. I don't have a clue what the core actually has in
> it (and don't have a clue to finding out) except MIOS Studio  last said
> "application is up and running (before I disconnected the USB MIDI Interface
> and connected the MIDI cable from the MIDI out of the card that sends out
> the MIDI messages from the stops). I did try my other core board and loaded
> it?? ( It was Device ID  1. The first core board was Device ID  0.
>> If as you say it is too complicated to remove your computer from the
>> MIDI path, then do all of the above using the first 5 inputs on your
>> spare card.  So then you will end up with the spare card connected
>> directly to the MIDIBOX CORE, MIDI IN with no computer in the loop at all.
>>
>> Once you have done this you should see how the MIDIBOX CORE and DOUT are
>> working.
>>
>> Next you want to get jOrgan to be in the middle of all this.  jOrgan
>> will need to be configured to read the messages coming from your stops.
>> You should see stops on your jOrgan screen change as you change your
>> stops.  You will then need to tell jOrgan what MIDI message you need
>> sent out to the MIDIBOX CORE to activate your lights.
>> I have only suggested you configure the MIDIBOX CORE with the messages
>> above so you can do an easy test without the computer (and jOrgan)
>> involved in the loop.  For your final setup you can choose to configure
>> the MIDIBOX CORE with whatever [MIDI_IN] messages you like to trigger
>> its DOUT pins.  You will just need to set jOrgan to send the correct
>> messages to match whatever you have configured in the MIDIBOX CORE
>> configuration.
> I configured Jorgan a couple of years ago to use this Syndyne MIDI Interface
> to turn the stops on and off (using my old combo-action). It has worked
> finely for 32 stops on the Swell, 18 on the Great and 18 on the Pedal. When
> I press any "On" button, the correct stop ALWAYS comes on and jorgan
> recognizes it.  The stop also turns on and off in the little boxes on the
> jorgan desktop ( I don't use any skins because it is easier just to have the
> stop names shown). It has also turned the lights on and off. Using the old
> jorgan 2.4.3 , activating and deactivating the stops was as easy as it is in
> 3.12. I just didn't have to become acquainted with MIDI messages. I'm glad
> that you have taught me the meaning of some of the MIDI messages and I thank
> you for it. I also thank you for your effort in trying to help me get the
> core and DOUTs working. Also I'm getting acquainted with the MIDI messages
> shown on the screen (had to change a bunch of them to get the correct stops
> to work when I opened my disposition in 3.12). In order to expand the organ
> past the limitation of my combo-action, and also to have the combo-action in
> jorgan turn the stopswitch lights on when I press a piston, I was trying
> (unsuccessfully) to use the MIDIBOX and MIOS Studio.
>> In normal use the messages to the MIDIBOX CORE MIDI IN connection are
>> MIDI messages.  It is only the initial configuration made by MIOS Studio
>> 2 that is a SYX file.
>>
>> Is this making any sense?
> Yes, you have made marvelous sense. It just doesn't want to work.
> Thanks so much for your help. We tried.
> Regards,
> Don

Hi Don and Rick,

If your DOUT boards are configured for MIDI Note On and MIDI Note Off
then you should be able to use the MIDI keyboard in MIOS Studio (once
you've sent the configuration) to send the MIDI signals to engage and
disengage, and test things right there and then.. I did this with a
project last year that used DOUTs to light diodes. Pressing the right
key on the keyboard sent the correct MIDI message (note on) to light
the LED, releasing the key (note off) then turned it off.

I don't have any DOUT boards in the project that I'm currently working
on, but I have worked with them in the past...

GrahamG

On 4/28/11, Rick (greenfox) <greenfox4075@...> wrote:
> Hello again Don
>
> I am sure we will crack this soon.  (as I have mentioned, I don't have
> any DOUT cards so am trying to assist you based only on my experience
> with DIN function so am needing you to be my eyes and ears for the tests.)
>
> Graham Goode's question prompts me to take one step back and ask if you
> have loaded the MIDIO128 main.hex file?
> This file is loaded using MIOS Studio 2.  This loads the main program
> into the CORE micro processor.  The .syx file we have been tinkering
> with, then loads specific IO configuration.  The .syx file won't work if
> the main.hex file is not loaded first.
>
> Do you have a DIN card for your MidiBox system?  If you do we could
> check that contact closures on terminals of your DIN were sending MIDI
> messages OUT from your CORE.
>
> When testing your DOUT card there is no need for the OUT MIDI connector
> on your core to be plugged to anything.  (you do need it for updating
> your configuration file though)
>
> Regards
> Rick

On 4/28/2011 5:08 AM, greenfox [via jOrgan] wrote:
> Hello again Don
>
> I am sure we will crack this soon.  (as I have mentioned, I don't have
> any DOUT cards so am trying to assist you based only on my experience
> with DIN function so am needing you to be my eyes and ears for the tests.)
>
> Graham Goode's question prompts me to take one step back and ask if you
> have loaded the MIDIO128 main.hex file?
Hi again Rick and Graham and John C.,
I loaded the MIDIO128 main.hex file months ago using MIOS Studio Beta9 4.

When I open MIOS Studio 2.1, In the little window to the right of Device ID
(I am now using device ID 1), after clicking on Query, it says :
operating system:MIOS8
board: MBHP core or similar
core family: PIC18F
application is up & running

I changed the device ID to 0 and clicked on Query  and it now says:
no response from MIOS8 or MIOS32 core!
check MIDI IN/OUT connections
and Device ID!

I changed the Device ID back to 1 and it now says:
operating system:MIOS8
board: MBHP core or similar
core family: PIC18F
application is up & running

 I can go back and start all over again and reload the MIDIO128 main.hex
file but I can't find anything in MIOS Studio 2 that allows to do that as I
did it using MIOS Studio Beta9 4. How do you program the core using MIOS
Studio 2. On opening the program I can't find anything pertaining to loading
MIDIO128 main.hex file.

Here is what I did after MIOS Studio 2 said the application was up and
running. The steps were:
1) Change the channel numbers in the MIDIO128 chart to channel 8.
2) Leave the Events  Note On
3) Change Parameters to the same MIDI notes that were shown on the MIDIOX
display when pressing the On Buttons for the stops (24, 25, 26, 27, 28)
4) Put the correct Device ID in the Device ID box at the top of the page.
5) Press Send.

> This file is loaded using MIOS Studio 2.  This loads the main program
> into the CORE micro processor.  The .syx file we have been tinkering
> with, then loads specific IO configuration.  The .syx file won't work if
> the main.hex file is not loaded first.
>
> Do you have a DIN card for your MidiBox system?  If you do we could
> check that contact closures on terminals of your DIN were sending MIDI
> messages OUT from your CORE.

Sorry, I don't have any DIN cards. I have 8 DOUT cards and 2 cores.
Regards to you,
Don
>
> When testing your DOUT card there is no need for the OUT MIDI connector
> on your core to be plugged to anything.  (you do need it for updating
> your configuration file though)
>
> Regards 
Rick 

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3483766.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hi Don,

I have MIOS Studio 2.1, and it is very evident on the page where to
browse for the HEX file and start the upload...

It says (choose a .hex file to upload) with a Browse button, then once
you've loaded the .hex file you press the Start button on the right
side and off it goes.

Are you running the CORE boards in sequence (i.e. you need to have the
ID set to 1)?

GrahamG

On 4/29/11, Don Becker <soniccr@...> wrote:
> On 4/28/2011 5:08 AM, greenfox [via jOrgan] wrote:
>> Hello again Don
>>
>> I am sure we will crack this soon.  (as I have mentioned, I don't have
>> any DOUT cards so am trying to assist you based only on my experience
>> with DIN function so am needing you to be my eyes and ears for the tests.)
>>
>> Graham Goode's question prompts me to take one step back and ask if you
>> have loaded the MIDIO128 main.hex file?
> Hi again Rick and Graham and John C.,
> I loaded the MIDIO128 main.hex file months ago using MIOS Studio Beta9 4.
>
> When I open MIOS Studio 2.1, In the little window to the right of Device ID
> (I am now using device ID 1), after clicking on Query, it says :
> operating system:MIOS8
> board: MBHP core or similar
> core family: PIC18F
> application is up & running
>
> I changed the device ID to 0 and clicked on Query  and it now says:
> no response from MIOS8 or MIOS32 core!
> check MIDI IN/OUT connections
> and Device ID!
>
> I changed the Device ID back to 1 and it now says:
> operating system:MIOS8
> board: MBHP core or similar
> core family: PIC18F
> application is up & running
>
>  I can go back and start all over again and reload the MIDIO128 main.hex
> file but I can't find anything in MIOS Studio 2 that allows to do that as I
> did it using MIOS Studio Beta9 4. How do you program the core using MIOS
> Studio 2. On opening the program I can't find anything pertaining to loading
> MIDIO128 main.hex file.
>
> Here is what I did after MIOS Studio 2 said the application was up and
> running. The steps were:
> 1) Change the channel numbers in the MIDIO128 chart to channel 8.
> 2) Leave the Events  Note On
> 3) Change Parameters to the same MIDI notes that were shown on the MIDIOX
> display when pressing the On Buttons for the stops (24, 25, 26, 27, 28)
> 4) Put the correct Device ID in the Device ID box at the top of the page.
> 5) Press Send.
>
>> This file is loaded using MIOS Studio 2.  This loads the main program
>> into the CORE micro processor.  The .syx file we have been tinkering
>> with, then loads specific IO configuration.  The .syx file won't work if
>> the main.hex file is not loaded first.
>>
>> Do you have a DIN card for your MidiBox system?  If you do we could
>> check that contact closures on terminals of your DIN were sending MIDI
>> messages OUT from your CORE.
>
> Sorry, I don't have any DIN cards. I have 8 DOUT cards and 2 cores.
> Regards to you,
> Don
>>
>> When testing your DOUT card there is no need for the OUT MIDI connector
>> on your core to be plugged to anything.  (you do need it for updating
>> your configuration file though)
>>
>> Regards
> Rick
>
> --
> View this message in context:
> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3483766.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>

Hi Graham and Rick,
Have I messed up completely? I thought that I had loaded the core long ago.
When I open MIOS Studio 2 it says (in the little window just to the right of
Device ID (which I have as 1):

operating system:MIOS8
 board: MBHP core or similar
 core family: PIC18F
 application is up & running

doesn't it mean that the core is loaded with the MIDIO128 main.hex file?
AND, if not, is there a peaceful way to find out whether I am using the core
that is ID  0 or ID 1?
If I need to start over, can you suggest how to go about it?

Then, if I am OK to this point, if I have used the MIDIO128 tool (DOUT
section), if I filled in the Channel # (which in this case, for the 1st 61
lights) will be CH 8, and in the Event column, it always is Note On, and in
the Parameter column, my numbers for the 1st 32 stops will be 24 thru 55. I
have the ID as 1 and press send. 
Can you tell me what I have  missed or what did I do wrong?????
Regards,
Don

--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3484434.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

Hi Don,

There are typically four steps to programming the PIC Core.

1) Load the bootloader HEX using a PIC Programmer. If you bought your
PIC chip with your MIDIbox boards this is probably already done.
2) In MIOS Studio (with your PIC inserted on the CORE board, powered
up and connected to your computer by MIDI cables) you then load the
MIOS operating system. This is the stage at which the ID is set. For
my project this file is the mios_v1_9g_pic18f452.hex
3) Once the MIOS OS is up and running you will get the message:

operating system:MIOS8
 board: MBHP core or similar
 core family: PIC18F
 application is up & running

It is now time to load the application - which for us is either the
plain MIDIO128 (setup_midio128.hex) or the 128 with 3 CC (Swells) hex
. Again, this is loaded through the MIDI cable from within MIOS
Studio.
4) Once the application is loaded, we can then program it. This is
done either via the SYSEX file, or via the MIDIO128 tool in MIOS
Studio. It is at this stage that you can program what each Input and
Output contact is in MIDI language.


So, Don, it looks like you have the MIOS OS loaded (although from what
you indicated earlier it is set for ID 1 and not ID 0). It can't hurt
to load the setup_midio128.hex (again) and then start programming the
MIDI DOUT messages....

Let us know if this helps,

GrahamG



On 4/29/11, Don Becker <soniccr@...> wrote:
> Hi Graham and Rick,
> Have I messed up completely? I thought that I had loaded the core long ago.
> When I open MIOS Studio 2 it says (in the little window just to the right of
> Device ID (which I have as 1):
>
> operating system:MIOS8
>  board: MBHP core or similar
>  core family: PIC18F
>  application is up & running
>
> doesn't it mean that the core is loaded with the MIDIO128 main.hex file?
> AND, if not, is there a peaceful way to find out whether I am using the core
> that is ID  0 or ID 1?
> If I need to start over, can you suggest how to go about it?
>
> Then, if I am OK to this point, if I have used the MIDIO128 tool (DOUT
> section), if I filled in the Channel # (which in this case, for the 1st 61
> lights) will be CH 8, and in the Event column, it always is Note On, and in
> the Parameter column, my numbers for the 1st 32 stops will be 24 thru 55. I
> have the ID as 1 and press send.
> Can you tell me what I have  missed or what did I do wrong?????
> Regards,
> Don
>
> --
> View this message in context:
> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3484434.html
> Sent from the jOrgan - User mailing list archive at Nabble.com.

Opps, a couple of errors slipped in there...

At the beginning of point 2 you should see:

operating system:MIOS8
 board: MBHP core or similar
 core family: PIC18F
 Bootloader is up & running

[notice 'Bootloader' and not 'application']...

I can't remember now if 'application' shows up after installing the
MIOS hex or the MIDIO128 hex... but you get the drift :)

GrahamG



On 4/29/11, Graham Goode <ggoode.sa@...> wrote:
> Hi Don,
>
> There are typically four steps to programming the PIC Core.
>
> 1) Load the bootloader HEX using a PIC Programmer. If you bought your
> PIC chip with your MIDIbox boards this is probably already done.
> 2) In MIOS Studio (with your PIC inserted on the CORE board, powered
> up and connected to your computer by MIDI cables) you then load the
> MIOS operating system. This is the stage at which the ID is set. For
> my project this file is the mios_v1_9g_pic18f452.hex
> 3) Once the MIOS OS is up and running you will get the message:
>
> operating system:MIOS8
>  board: MBHP core or similar
>  core family: PIC18F
>  application is up & running
>
> It is now time to load the application - which for us is either the
> plain MIDIO128 (setup_midio128.hex) or the 128 with 3 CC (Swells) hex
> . Again, this is loaded through the MIDI cable from within MIOS
> Studio.
> 4) Once the application is loaded, we can then program it. This is
> done either via the SYSEX file, or via the MIDIO128 tool in MIOS
> Studio. It is at this stage that you can program what each Input and
> Output contact is in MIDI language.
>
>
> So, Don, it looks like you have the MIOS OS loaded (although from what
> you indicated earlier it is set for ID 1 and not ID 0). It can't hurt
> to load the setup_midio128.hex (again) and then start programming the
> MIDI DOUT messages....
>
> Let us know if this helps,
>
> GrahamG
>
>
>
> On 4/29/11, Don Becker <soniccr@...> wrote:
>> Hi Graham and Rick,
>> Have I messed up completely? I thought that I had loaded the core long
>> ago.
>> When I open MIOS Studio 2 it says (in the little window just to the right
>> of
>> Device ID (which I have as 1):
>>
>> operating system:MIOS8
>>  board: MBHP core or similar
>>  core family: PIC18F
>>  application is up & running
>>
>> doesn't it mean that the core is loaded with the MIDIO128 main.hex file?
>> AND, if not, is there a peaceful way to find out whether I am using the
>> core
>> that is ID  0 or ID 1?
>> If I need to start over, can you suggest how to go about it?
>>
>> Then, if I am OK to this point, if I have used the MIDIO128 tool (DOUT
>> section), if I filled in the Channel # (which in this case, for the 1st
>> 61
>> lights) will be CH 8, and in the Event column, it always is Note On, and
>> in
>> the Parameter column, my numbers for the 1st 32 stops will be 24 thru 55.
>> I
>> have the ID as 1 and press send.
>> Can you tell me what I have  missed or what did I do wrong?????
>> Regards,
>> Don
>>
>> --
>> View this message in context:
>> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3484434.html
>> Sent from the jOrgan - User mailing list archive at Nabble.com.
>

Hi Graham and Rick,
The application seems to be correctly uploaded, I bought the Picchips
already loaded with the bootloader. I reloaded the MIDIO128 hex and
everything showed up in the righthand pane, seemed like it took about 5 min.
to load. Reloaded the DOUT stuff and the lights still behave randomly. Tried
another DOUT board and it was random also. Am I supposed to be shorting any
of the pins on the output side of the DOUT bd. to gnd ( because its not
going on to another DOUT bd???)
Thanks,
Don--
View this message in context: http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3486049.html
Sent from the jOrgan - User mailing list archive at Nabble.com.

On 4/29/2011 2:29 PM, Graham Goode wrote:
> Opps, a couple of errors slipped in there...
>
> At the beginning of point 2 you should see:
>
> operating system:MIOS8
>   board: MBHP core or similar
>   core family: PIC18F
>   Bootloader is up&  running
>
> [notice 'Bootloader' and not 'application']...
>
> I can't remember now if 'application' shows up after installing the
> MIOS hex or the MIDIO128 hex... but you get the drift :)
>
> GrahamG
>
>
>
> On 4/29/11, Graham Goode<ggoode.sa@...>  wrote:
>> Hi Don,
>>
>> There are typically four steps to programming the PIC Core.
>>
>> 1) Load the bootloader HEX using a PIC Programmer. If you bought your
>> PIC chip with your MIDIbox boards this is probably already done.
>> 2) In MIOS Studio (with your PIC inserted on the CORE board, powered
>> up and connected to your computer by MIDI cables) you then load the
>> MIOS operating system. This is the stage at which the ID is set. For
>> my project this file is the mios_v1_9g_pic18f452.hex
>> 3) Once the MIOS OS is up and running you will get the message:
>>
>> operating system:MIOS8
>>   board: MBHP core or similar
>>   core family: PIC18F
>>   application is up&  running
>>
>> It is now time to load the application - which for us is either the
>> plain MIDIO128 (setup_midio128.hex) or the 128 with 3 CC (Swells) hex
>> . Again, this is loaded through the MIDI cable from within MIOS
>> Studio.
>> 4) Once the application is loaded, we can then program it. This is
>> done either via the SYSEX file, or via the MIDIO128 tool in MIOS
>> Studio. It is at this stage that you can program what each Input and
>> Output contact is in MIDI language.
>>
>>
>> So, Don, it looks like you have the MIOS OS loaded (although from what
>> you indicated earlier it is set for ID 1 and not ID 0). It can't hurt
>> to load the setup_midio128.hex (again) and then start programming the
>> MIDI DOUT messages....
>>
>> Let us know if this helps,
>>
>> GrahamG
>>
>>
>>
>> On 4/29/11, Don Becker<soniccr@...>  wrote:
>>> Hi Graham and Rick,
>>> Have I messed up completely? I thought that I had loaded the core long
>>> ago.
>>> When I open MIOS Studio 2 it says (in the little window just to the right
>>> of
>>> Device ID (which I have as 1):
>>>
>>> operating system:MIOS8
>>>   board: MBHP core or similar
>>>   core family: PIC18F
>>>   application is up&  running
>>>
>>> doesn't it mean that the core is loaded with the MIDIO128 main.hex file?
>>> AND, if not, is there a peaceful way to find out whether I am using the
>>> core
>>> that is ID  0 or ID 1?
>>> If I need to start over, can you suggest how to go about it?
>>>
>>> Then, if I am OK to this point, if I have used the MIDIO128 tool (DOUT
>>> section), if I filled in the Channel # (which in this case, for the 1st
>>> 61
>>> lights) will be CH 8, and in the Event column, it always is Note On, and
>>> in
>>> the Parameter column, my numbers for the 1st 32 stops will be 24 thru 55.
>>> I
>>> have the ID as 1 and press send.
>>> Can you tell me what I have  missed or what did I do wrong?????
>>> Regards,
>>> Don
>>>
>>> --
>>> View this message in context:
>>> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3484434.html
>>> Sent from the jOrgan - User mailing list archive at Nabble.com.
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
Hi Graham and Rick,
The application seems to be correctly uploaded, I bought the Picchips 
already loaded with the bootloader. I reloaded the MIDIO128 hex and 
everything showed up in the righthand pane, seemed like it took about 5 
min. to load. Reloaded the DOUT stuff and the lights still behave 
randomly. Tried another DOUT board and it was random also. Am I supposed 
to be shorting any of the pins on the output side of the DOUT bd. to gnd 
( because its not going on to another DOUT bd???
Thanks,
Don

Hi Don.,

It should not be taking 5 mins to load the hex file...!! That takes
about 30 seconds here. In the MIDIO128 Tool screen can you Send and
Receive?

GrahamG

On 4/30/11, don <soniccr@...> wrote:
> On 4/29/2011 2:29 PM, Graham Goode wrote:
>> Opps, a couple of errors slipped in there...
>>
>> At the beginning of point 2 you should see:
>>
>> operating system:MIOS8
>>   board: MBHP core or similar
>>   core family: PIC18F
>>   Bootloader is up&  running
>>
>> [notice 'Bootloader' and not 'application']...
>>
>> I can't remember now if 'application' shows up after installing the
>> MIOS hex or the MIDIO128 hex... but you get the drift :)
>>
>> GrahamG
>>
>>
>>
>> On 4/29/11, Graham Goode<ggoode.sa@...>  wrote:
>>> Hi Don,
>>>
>>> There are typically four steps to programming the PIC Core.
>>>
>>> 1) Load the bootloader HEX using a PIC Programmer. If you bought your
>>> PIC chip with your MIDIbox boards this is probably already done.
>>> 2) In MIOS Studio (with your PIC inserted on the CORE board, powered
>>> up and connected to your computer by MIDI cables) you then load the
>>> MIOS operating system. This is the stage at which the ID is set. For
>>> my project this file is the mios_v1_9g_pic18f452.hex
>>> 3) Once the MIOS OS is up and running you will get the message:
>>>
>>> operating system:MIOS8
>>>   board: MBHP core or similar
>>>   core family: PIC18F
>>>   application is up&  running
>>>
>>> It is now time to load the application - which for us is either the
>>> plain MIDIO128 (setup_midio128.hex) or the 128 with 3 CC (Swells) hex
>>> . Again, this is loaded through the MIDI cable from within MIOS
>>> Studio.
>>> 4) Once the application is loaded, we can then program it. This is
>>> done either via the SYSEX file, or via the MIDIO128 tool in MIOS
>>> Studio. It is at this stage that you can program what each Input and
>>> Output contact is in MIDI language.
>>>
>>>
>>> So, Don, it looks like you have the MIOS OS loaded (although from what
>>> you indicated earlier it is set for ID 1 and not ID 0). It can't hurt
>>> to load the setup_midio128.hex (again) and then start programming the
>>> MIDI DOUT messages....
>>>
>>> Let us know if this helps,
>>>
>>> GrahamG
>>>
>>>
>>>
>>> On 4/29/11, Don Becker<soniccr@...>  wrote:
>>>> Hi Graham and Rick,
>>>> Have I messed up completely? I thought that I had loaded the core long
>>>> ago.
>>>> When I open MIOS Studio 2 it says (in the little window just to the
>>>> right
>>>> of
>>>> Device ID (which I have as 1):
>>>>
>>>> operating system:MIOS8
>>>>   board: MBHP core or similar
>>>>   core family: PIC18F
>>>>   application is up&  running
>>>>
>>>> doesn't it mean that the core is loaded with the MIDIO128 main.hex file?
>>>> AND, if not, is there a peaceful way to find out whether I am using the
>>>> core
>>>> that is ID  0 or ID 1?
>>>> If I need to start over, can you suggest how to go about it?
>>>>
>>>> Then, if I am OK to this point, if I have used the MIDIO128 tool (DOUT
>>>> section), if I filled in the Channel # (which in this case, for the 1st
>>>> 61
>>>> lights) will be CH 8, and in the Event column, it always is Note On, and
>>>> in
>>>> the Parameter column, my numbers for the 1st 32 stops will be 24 thru
>>>> 55.
>>>> I
>>>> have the ID as 1 and press send.
>>>> Can you tell me what I have  missed or what did I do wrong?????
>>>> Regards,
>>>> Don
>>>>
>>>> --
>>>> View this message in context:
>>>> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3484434.html
>>>> Sent from the jOrgan - User mailing list archive at Nabble.com.
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> jOrgan-user mailing list
>> jOrgan-user@...
>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>>
> Hi Graham and Rick,
> The application seems to be correctly uploaded, I bought the Picchips
> already loaded with the bootloader. I reloaded the MIDIO128 hex and
> everything showed up in the righthand pane, seemed like it took about 5
> min. to load. Reloaded the DOUT stuff and the lights still behave
> randomly. Tried another DOUT board and it was random also. Am I supposed
> to be shorting any of the pins on the output side of the DOUT bd. to gnd
> ( because its not going on to another DOUT bd???
> Thanks,
> Don
>

On 4/30/2011 10:03 AM, Graham Goode wrote:
> Hi Don.,
>
> It should not be taking 5 mins to load the hex file...!! That takes
> about 30 seconds here. In the MIDIO128 Tool screen can you Send and
> Receive?
>
> GrahamG
>
> On 4/30/11, don<soniccr@...>  wrote:
>> On 4/29/2011 2:29 PM, Graham Goode wrote:
>>> Opps, a couple of errors slipped in there...
>>>
>>> At the beginning of point 2 you should see:
>>>
>>> operating system:MIOS8
>>>    board: MBHP core or similar
>>>    core family: PIC18F
>>>    Bootloader is up&   running
>>>
>>> [notice 'Bootloader' and not 'application']...
>>>
>>> I can't remember now if 'application' shows up after installing the
>>> MIOS hex or the MIDIO128 hex... but you get the drift :)
>>>
>>> GrahamG
>>>
>>>
>>>
>>> On 4/29/11, Graham Goode<ggoode.sa@...>   wrote:
>>>> Hi Don,
>>>>
>>>> There are typically four steps to programming the PIC Core.
>>>>
>>>> 1) Load the bootloader HEX using a PIC Programmer. If you bought your
>>>> PIC chip with your MIDIbox boards this is probably already done.
>>>> 2) In MIOS Studio (with your PIC inserted on the CORE board, powered
>>>> up and connected to your computer by MIDI cables) you then load the
>>>> MIOS operating system. This is the stage at which the ID is set. For
>>>> my project this file is the mios_v1_9g_pic18f452.hex
>>>> 3) Once the MIOS OS is up and running you will get the message:
>>>>
>>>> operating system:MIOS8
>>>>    board: MBHP core or similar
>>>>    core family: PIC18F
>>>>    application is up&   running
>>>>
>>>> It is now time to load the application - which for us is either the
>>>> plain MIDIO128 (setup_midio128.hex) or the 128 with 3 CC (Swells) hex
>>>> . Again, this is loaded through the MIDI cable from within MIOS
>>>> Studio.
>>>> 4) Once the application is loaded, we can then program it. This is
>>>> done either via the SYSEX file, or via the MIDIO128 tool in MIOS
>>>> Studio. It is at this stage that you can program what each Input and
>>>> Output contact is in MIDI language.
>>>>
>>>>
>>>> So, Don, it looks like you have the MIOS OS loaded (although from what
>>>> you indicated earlier it is set for ID 1 and not ID 0). It can't hurt
>>>> to load the setup_midio128.hex (again) and then start programming the
>>>> MIDI DOUT messages....
>>>>
>>>> Let us know if this helps,
>>>>
>>>> GrahamG
>>>>
>>>>
>>>>
>>>> On 4/29/11, Don Becker<soniccr@...>   wrote:
>>>>> Hi Graham and Rick,
>>>>> Have I messed up completely? I thought that I had loaded the core long
>>>>> ago.
>>>>> When I open MIOS Studio 2 it says (in the little window just to the
>>>>> right
>>>>> of
>>>>> Device ID (which I have as 1):
>>>>>
>>>>> operating system:MIOS8
>>>>>    board: MBHP core or similar
>>>>>    core family: PIC18F
>>>>>    application is up&   running
>>>>>
>>>>> doesn't it mean that the core is loaded with the MIDIO128 main.hex file?
>>>>> AND, if not, is there a peaceful way to find out whether I am using the
>>>>> core
>>>>> that is ID  0 or ID 1?
>>>>> If I need to start over, can you suggest how to go about it?
>>>>>
>>>>> Then, if I am OK to this point, if I have used the MIDIO128 tool (DOUT
>>>>> section), if I filled in the Channel # (which in this case, for the 1st
>>>>> 61
>>>>> lights) will be CH 8, and in the Event column, it always is Note On, and
>>>>> in
>>>>> the Parameter column, my numbers for the 1st 32 stops will be 24 thru
>>>>> 55.
>>>>> I
>>>>> have the ID as 1 and press send.
>>>>> Can you tell me what I have  missed or what did I do wrong?????
>>>>> Regards,
>>>>> Don
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3484434.html
>>>>> Sent from the jOrgan - User mailing list archive at Nabble.com.
>>> ------------------------------------------------------------------------------
>>> WhatsUp Gold - Download Free Network Management Software
>>> The most intuitive, comprehensive, and cost-effective network
>>> management toolset available today.  Delivers lowest initial
>>> acquisition cost and overall TCO of any competing solution.
>>> http://p.sf.net/sfu/whatsupgold-sd
>>> _______________________________________________
>>> jOrgan-user mailing list
>>> jOrgan-user@...
>>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>>>
>> Hi Graham and Rick,
>> The application seems to be correctly uploaded, I bought the Picchips
>> already loaded with the bootloader. I reloaded the MIDIO128 hex and
>> everything showed up in the righthand pane, seemed like it took about 5
>> min. to load. Reloaded the DOUT stuff and the lights still behave
>> randomly. Tried another DOUT board and it was random also. Am I supposed
>> to be shorting any of the pins on the output side of the DOUT bd. to gnd
>> ( because its not going on to another DOUT bd???
>> Thanks,
>> Don
>>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
Yes Graham,
I just reconnected the USB MIDI Interface and on the MIDIO128 page 
pressed receive and the chart changed to all Channels  reading 8 and the 
Parameters reading 24, 25, 26, etc. like I had sent to the core earlier 
by pressing the send button. I then disconnected the USB MIDI Internet 
connector from the core and pressed the 1st 4 stopswitch "On" buttons 
that turn on 24, 25, 26, 27 and it turned on pins J4/3, J4/2, J4/1, J4/0 
and J5/3, J5/2, J5/1 and J5/0 on the DOUT board. According to the 
MIDIO128 chart it should be turning on pins J3/7, J3/6, J3/5 and J3/4.
Don

On 4/30/2011 10:03 AM, Graham Goode wrote:
> Hi Don.,
>
> It should not be taking 5 mins to load the hex file...!! That takes
> about 30 seconds here. In the MIDIO128 Tool screen can you Send and
> Receive?
>
> GrahamG
>
> On 4/30/11, don<soniccr@...>  wrote:
>> On 4/29/2011 2:29 PM, Graham Goode wrote:
>>> Opps, a couple of errors slipped in there...
>>>
>>> At the beginning of point 2 you should see:
>>>
>>> operating system:MIOS8
>>>    board: MBHP core or similar
>>>    core family: PIC18F
>>>    Bootloader is up&   running
>>>
>>> [notice 'Bootloader' and not 'application']...
>>>
>>> I can't remember now if 'application' shows up after installing the
>>> MIOS hex or the MIDIO128 hex... but you get the drift :)
>>>
>>> GrahamG
>>>
>>>
>>>
>>> On 4/29/11, Graham Goode<ggoode.sa@...>   wrote:
>>>> Hi Don,
>>>>
>>>> There are typically four steps to programming the PIC Core.
>>>>
>>>> 1) Load the bootloader HEX using a PIC Programmer. If you bought your
>>>> PIC chip with your MIDIbox boards this is probably already done.
>>>> 2) In MIOS Studio (with your PIC inserted on the CORE board, powered
>>>> up and connected to your computer by MIDI cables) you then load the
>>>> MIOS operating system. This is the stage at which the ID is set. For
>>>> my project this file is the mios_v1_9g_pic18f452.hex
>>>> 3) Once the MIOS OS is up and running you will get the message:
>>>>
>>>> operating system:MIOS8
>>>>    board: MBHP core or similar
>>>>    core family: PIC18F
>>>>    application is up&   running
>>>>
>>>> It is now time to load the application - which for us is either the
>>>> plain MIDIO128 (setup_midio128.hex) or the 128 with 3 CC (Swells) hex
>>>> . Again, this is loaded through the MIDI cable from within MIOS
>>>> Studio.
>>>> 4) Once the application is loaded, we can then program it. This is
>>>> done either via the SYSEX file, or via the MIDIO128 tool in MIOS
>>>> Studio. It is at this stage that you can program what each Input and
>>>> Output contact is in MIDI language.
>>>>
>>>>
>>>> So, Don, it looks like you have the MIOS OS loaded (although from what
>>>> you indicated earlier it is set for ID 1 and not ID 0). It can't hurt
>>>> to load the setup_midio128.hex (again) and then start programming the
>>>> MIDI DOUT messages....
>>>>
>>>> Let us know if this helps,
>>>>
>>>> GrahamG
>>>>
>>>>
>>>>
>>>> On 4/29/11, Don Becker<soniccr@...>   wrote:
>>>>> Hi Graham and Rick,
>>>>> Have I messed up completely? I thought that I had loaded the core long
>>>>> ago.
>>>>> When I open MIOS Studio 2 it says (in the little window just to the
>>>>> right
>>>>> of
>>>>> Device ID (which I have as 1):
>>>>>
>>>>> operating system:MIOS8
>>>>>    board: MBHP core or similar
>>>>>    core family: PIC18F
>>>>>    application is up&   running
>>>>>
>>>>> doesn't it mean that the core is loaded with the MIDIO128 main.hex file?
>>>>> AND, if not, is there a peaceful way to find out whether I am using the
>>>>> core
>>>>> that is ID  0 or ID 1?
>>>>> If I need to start over, can you suggest how to go about it?
>>>>>
>>>>> Then, if I am OK to this point, if I have used the MIDIO128 tool (DOUT
>>>>> section), if I filled in the Channel # (which in this case, for the 1st
>>>>> 61
>>>>> lights) will be CH 8, and in the Event column, it always is Note On, and
>>>>> in
>>>>> the Parameter column, my numbers for the 1st 32 stops will be 24 thru
>>>>> 55.
>>>>> I
>>>>> have the ID as 1 and press send.
>>>>> Can you tell me what I have  missed or what did I do wrong?????
>>>>> Regards,
>>>>> Don
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://jorgan.999862.n4.nabble.com/jOrgan-3-3-first-beta-tp1001907p3484434.html
>>>>> Sent from the jOrgan - User mailing list archive at Nabble.com.
>>> ------------------------------------------------------------------------------
>>> WhatsUp Gold - Download Free Network Management Software
>>> The most intuitive, comprehensive, and cost-effective network
>>> management toolset available today.  Delivers lowest initial
>>> acquisition cost and overall TCO of any competing solution.
>>> http://p.sf.net/sfu/whatsupgold-sd
>>> _______________________________________________
>>> jOrgan-user mailing list
>>> jOrgan-user@...
>>> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>>>
>> Hi Graham and Rick,
>> The application seems to be correctly uploaded, I bought the Picchips
>> already loaded with the bootloader. I reloaded the MIDIO128 hex and
>> everything showed up in the righthand pane, seemed like it took about 5
>> min. to load. Reloaded the DOUT stuff and the lights still behave
>> randomly. Tried another DOUT board and it was random also. Am I supposed
>> to be shorting any of the pins on the output side of the DOUT bd. to gnd
>> ( because its not going on to another DOUT bd???
>> Thanks,
>> Don
>>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> jOrgan-user mailing list
> jOrgan-user@...
> https://lists.sourceforge.net/lists/listinfo/jorgan-user
>
OOPS!!

Yes Graham,
>  I just reconnected the USB MIDI Interface and on the MIDIO128 page
>  pressed receive and the chart changed to all Channels  reading 8 and
>  the Parameters reading 24, 25, 26, etc. like I had sent to the core
>  earlier by pressing the send button. I then disconnected the USB MIDI
>  Internet connector from the core, reconnected the MIDI cable from the
  stopswitches and pressed the 1st 4 stopswitch "On"
>  buttons that turn on 24, 25, 26, 27 and it turned on pins J4/3, J4/2,
>  J4/1, J4/0 and J5/3, J5/2, J5/1 and J5/0 on the DOUT board. According
>  to the MIDIO128 chart it should be turning on pins J3/7, J3/6, J3/5
>  and J3/4.
>  Don
This looks like it is getting to be a hopeless supernatural task so, if you and Rick
  want to let the problem lie where it now stands, we all seem to have done our best under the circumstances. I do much appreciate the time and thought and effort you both have put into it.
Thanks much,
Don