From @@@@@@@@@@@@@@@@@@@@@@@@@ Fri Oct  8 09:05:02 2010
Received: from isp.becroft.co.nz (isp [127.0.0.1])
	by isp.becroft.co.nz (8.14.3/8.14.3) with ESMTP id o97K4sKZ001630
	for <@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@>; Fri, 8 Oct 2010 09:04:54 +1300
Received: (from majordomo@localhost)
	by isp.becroft.co.nz (8.14.3/8.14.3/Submit) id o97K4s3n001629
	for notator-list; Fri, 8 Oct 2010 09:04:54 +1300
X-Authentication-Warning: isp.becroft.co.nz: majordomo set sender to @@@@@@@@@@@@@@@@@@@@@@@@@ using -f
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23])
	by isp.becroft.co.nz (8.14.3/8.14.3) with SMTP id o97K4iwN001621
	for <@@@@@@@@@@@@@@@@@@@>; Fri, 8 Oct 2010 09:04:45 +1300
Received: (qmail invoked by alias); 07 Oct 2010 20:04:38 -0000
Received: from g224020018.adsl.alicedsl.de (EHLO [192.168.1.25]) [92.224.20.18]
  by mail.gmx.net (mp067) with SMTP; 07 Oct 2010 22:04:38 +0200
X-Authenticated: #19473311
X-Provags-ID: V01U2FsdGVkX1/ltuI8LXrlNvuIaWHdTMSwkzAq69cwENGuP0MAiF
	Hdmk/4Y+IrqUWz
Message-ID: <@@@@@@@@@@@@@@@@@@@@@@@>
Date: Thu, 07 Oct 2010 22:04:38 +0200
From: PeWe <@@@@@@@@@@@@@@>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: @@@@@@@@@@@@@@@@@@@
Subject: Re: [NSL] Contact cleaner
References: <@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@>	<@@@@@@@@@@@@@@@@@@@@@@@>	<@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@> <@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@>
In-Reply-To: <@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
X-Spam-Status: No, score=-2.6 required=3.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on isp.becroft.co.nz
Sender: @@@@@@@@@@@@@@@@@@@@@@@@@
Precedence: bulk
Reply-To: @@@@@@@@@@@@@@@@@@@
X-URL: http://www.notator.org

 [Notator/Creator SL mailing list]


Hmm, not sure if this could be caused by dirt at all.
Never had that, but had to clean contacts of Unitor N and Unitor II, 
Midex/Midex+ and Combiners several times within the decades.

Don´t expect all these interfaces will last forever,- and to me, that 
looks like a possibly other damage too.
It´s just only electronics, you know ...

Atari MIDI port [Out A] has nothing to do with port [Out F], except the 
program is able to route MIDI to these ports,- so it would be more 
interesting what happens w/ [Out E] and the In ports I & II, just only  
´cause these are the PHYSICAL ports of that device.

If the program is loading without getting bombs and you can play MIDI to 
get aware of the prob "OUT F isn´t working",- any dongle issues 
(separate dongle, or built in dongle in Unitor C/N or LOG3) are sorted out.

You have to sort out the issue by testing your additional devices 
connected to the Atari one-by-one and best would be you´d have access to 
a 2nd Unitor/LOG3 to make sure which device introduces the failure.
The Atari itself can also be the cause,- the connected devices are 
powered by the Atari port they are connected to, so it can be, the Atari 
port is damaged or some voltage is out of spec occasionally and so on.

It´s hard to find out without having the Atari and the devices twice,- 
and if all this won´t help, some measurements would be necessary too,- 
tech wise.


Am 07.10.2010 21:14, schrieb Tim Johnson:
>
> MIDI was going fine out of port A last night
>
> but stopped completely going out of F.


 UNSUBSCRIBE?
 Send an email to:   @@@@@@@@@@@@@@@@@@@@@
 with the command:   UNSUBSCRIBE NOTATOR your@email
 (replace "your@email" with your own email address