OK, two discoveries:
1. You don't need to assign a Comm port to the clone as it is by
definition a receive-only device with no need for transmit control. I
just set mine to NONE and it appears to decode just fine.
2. I cannot recreate my MMTTY.INI updating error if as Gary suggests I
explicitly close down the clone window *before* I shutdown WL.
I don't think we've solved anything, but I think we have found how to
make it workable without too many dramatics.
Thanks for the help Ed, Gary and Jay.
One day to go.....
Dick
--
Dick Flanagan K7VC
dick@k7vc.com
On 1/5/2012 11:29 PM, Dick Flanagan wrote:
> That could be it. I will try manually closing the cloned window before
> I shut down WL.
>
> Dick
>
> --
> Dick Flanagan K7VC
> dick@k7vc.com
>
>
> On 1/5/2012 11:27 PM, Gary AL9A wrote:
>> Per my earlier message, when I changed COM ports in the clone window
>> everything seemed to work ok, but I haven't actually copied signals
>> over the air yet. I did not experience your problem with MMTTY.ini
>> not updating. But then I didn't start a second instance of MMTTY from
>> a different location and I closed the second MMTTY window and clone
>> RittyRite window before shutting down WL. Maybe that's the difference?
>>
>> 73,
>> Gary AL9A
>>
>>
>> ----- Original Message ----- From: "Dick Flanagan"<dick@k7vc.com>
>> To: "Gary AL9A"<al9a@mtaonline.net>; "WriteLog"
>> <writelog@contesting.com>
>> Sent: January 05, 2012 10:06 PM
>> Subject: Re: [WriteLog] WL/MMTTY Problem
>>
>>
>>> In the clone window, select the TU Type drop-down and then select
>>> MMTTY. A new MMTTY control panel should open, but it is tricky as it
>>> will exactly overlay the current MMTTY control panel. You will need
>>> to select it and move it out of the way.
>>>
>>> You should then be able to select a different profile for each MMTTY
>>> control panel.
>>>
>>> My problem was after I did that and then closed Writelog, I received
>>> an error that MMTTY.INI could not be updated. When I then re-opened
>>> Writelog, MMTTY could not communicate with the outside world. After
>>> again closing Writelog and then directly invoking MMTTY, I find that
>>> the FSK and Control ports have been reset to NONE.
>>>
>>> It acts like whatever caused the MMTTY.INI update error is causing
>>> the MMTTY FSK and control ports to be reset. Once that happens, you
>>> have to use MMTTY to configure them again.
>>>
>>> This works for Ed so I am assuming I have a configuration error. I
>>> will be curious to see how successful you are.
>>>
>>> Dick
>>>
>>> --
>>> Dick Flanagan K7VC
>>> dick@k7vc.com
>>>
>>>
>>> On 1/5/2012 10:44 PM, Gary AL9A wrote:
>>>> Ed,
>>>>
>>>> I can get the clone RittyRite window to open, but it didn't ask me
>>>> for the
>>>> path to MMTTY. Despite this it appears to be receiving and
>>>> decoding. But
>>>> per Dick's request how do you get another MMTTY window to function
>>>> with the
>>>> clone window so that you can choose a different Profile for the clone?
>>>>
>>>> 73,
>>>> Gary AL9A
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Ed Muns"<w0yk@msn.com>
>>>> To: "'Dick Flanagan'"<dick@k7vc.com>
>>>> Cc: "'WriteLog'"<writelog@contesting.com>
>>>> Sent: January 05, 2012 2:41 PM
>>>> Subject: Re: [WriteLog] WL/MMTTY Problem
>>>>
>>>>
>>>>> Ah, so, but you don't need two instances of MMTTY. You just
>>>>> "clone" the
>>>>> first Rttyrite window that has MMTTY as the TNC. In the Rttyrite File
>>>>> menu
>>>>> of the first Rttyrite/MMTTY window you bring up, click 'Clone' and
>>>>> when it
>>>>> asks you for the path to MMTTY, give it the path to the first
>>>>> instance of
>>>>> MMTTY. You can have any number of clones without resorting to
>>>>> additional
>>>>> instances of MMTTY.
>>>>>
>>>>> Ed - P49X (W0YK)
>>>>>
>>>>> Dick, K7YC, replied:
>>>>>> As per your NCCC presentation, I am looking for the opportunity to
>>>>>> have
>>>>>> two different profiles processing the same audio stream.
>>>>>>
>>>>>> Dick
>>>>>>
>>>>>> --
>>>>>> Dick Flanagan K7VC
>>>>>> dick@k7vc.com
>>>>>>
>>>>>>
>>>>>> On 1/5/2012 3:20 PM, Ed Muns wrote:
>>>>>>> I've had this happen once in a while, but not often, and not
>>>>>>> recently.
>>>>>> I've
>>>>>>> never worried about it or looked into it. But, I am curious
>>>>>>> about what
>>>>>> is
>>>>>>> going on.
>>>>>>>
>>>>>>> Why are you using two instances of MMTTY?
>>>>>>>
>>>>>>> Ed - P49X (W0YK)
>>>>>>>
>>>>>>> Dick, K7VC, wrote:
>>>>>>>> During today's RTTY RU practice, I noticed a problem running two
>>>>>>>> instances of MMTTY. When exiting WL I received an error message
>>>>>>>> that
>>>>>>>> MMTTY.INI cannot be updated. When I again invoke MMTTY, all port
>>>>>>>> settings have been set to NONE.
>>>>>>>>
>>>>>>>> Why is WL trying to update MMTTY.INI? What kind of circumstance
>>>>>>>> would
>>>>>>>> cause this kind of error? WRITELOG.INI has the correct path to the
>>>>>>>> MMTTY directory and MMTTY operates properly until I exit WL at
>>>>>>>> which
>>>>>>>> point the MMTTY ports are set to NONE and I need to reset them.
>>>>>>>>
>>>>>>>> Could the two instances of MMTTY be fighting over some resource?
>>>>>>>> Could
>>>>>>>> one instance be trying to update MMTTY.INI while the other instance
>>>>>>>> has
>>>>>>>> it open? Has anyone else experienced difficulties running two
>>>>>> instances
>>>>>>>> of MMTTY from within WL?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>> _______________________________________________
>>>>> WriteLog mailing list
>>>>> WriteLog@contesting.com
>>>>> http://lists.contesting.com/mailman/listinfo/writelog
>>>>> WriteLog on the web: http://www.writelog.com/
>>>> _______________________________________________
>>>> WriteLog mailing list
>>>> WriteLog@contesting.com
>>>> http://lists.contesting.com/mailman/listinfo/writelog
>>>> WriteLog on the web: http://www.writelog.com/
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
>
>
>
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|