* old artic transport, some ideas.
@ Linux for blind general discussion
` Linux for blind general discussion
0 siblings, 1 reply; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
Hi folks,
Realizing it may be solved by now, I did promise to ask another user.
His thoughts are below, if the person is still having issues let me know now
as he has offered to help them troubleshoot given he has used his own
unit with Linux for some time.
Karen
---------- Forwarded message ----------
Date: Mon, 22 May 2017 21:23:01 -0400 (EDT)
Subject: Re: artic transport question?
Ahh, yes, depending on which artic synthesizer he has, he may need to run a
program, or set it to synthesizer mode. If it's a spirit, nothing needs to be
done, it should just work. If it's a transtype, there is an option in the
menus to set it to speech mode, though that's the one where you can also run
the terminal program, and it will talk that way too, though not as readily or
as well as the synthewsizer mode will allow. If it's a transport, just setting
the linux side of things to 9600 8, n, 1 should take care of the problem, as
that is the default settings on the transport.
I think that covers all the possible options. If there are further issues,
feel free to pass my email address on to the individual having trouble.
Again, hope this helps.
>
>
> > If I remember correctly, (and assuming this person hasn't already solved
> > their issue), the keyword for the transport is txprt.
> > Passing that on the commandline along with the port (or it can scan for
> > the port automatically) should do the trick.
> > Hope this helps.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
old artic transport, some ideas Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
0 siblings, 2 replies; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
Mark Peveto here.
Issues mostly solved. If he could tell me how to set the clock on the thing, or even if it's possible For his info, the transport modle is 611
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
On Mon, 22 May 2017, Linux for blind general discussion wrote:
> Hi folks,
> Realizing it may be solved by now, I did promise to ask another user.
> His thoughts are below, if the person is still having issues let me know now
> as he has offered to help them troubleshoot given he has used his own unit
> with Linux for some time.
> Karen
>
>
> ---------- Forwarded message ----------
> Date: Mon, 22 May 2017 21:23:01 -0400 (EDT)
> Subject: Re: artic transport question?
>
> Ahh, yes, depending on which artic synthesizer he has, he may need to run a
> program, or set it to synthesizer mode. If it's a spirit, nothing needs to be
> done, it should just work. If it's a transtype, there is an option in the
> menus to set it to speech mode, though that's the one where you can also run
> the terminal program, and it will talk that way too, though not as readily or
> as well as the synthewsizer mode will allow. If it's a transport, just
> setting the linux side of things to 9600 8, n, 1 should take care of the
> problem, as that is the default settings on the transport.
> I think that covers all the possible options. If there are further issues,
> feel free to pass my email address on to the individual having trouble.
>
>
> Again, hope this helps.
>
>
> >
> >
> > > If I remember correctly, (and assuming this person hasn't already solved
> > > their issue), the keyword for the transport is txprt.
> > > Passing that on the commandline along with the port (or it can scan for >
> > the port automatically) should do the trick.
> > > Hope this helps.
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
1 sibling, 0 replies; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
I have asked, and will share once I hear back.
Kare
On Mon, 22 May 2017, Linux for blind general discussion wrote:
> Mark Peveto here.
> Issues mostly solved. If he could tell me how to set the clock on the thing, or even if it's possible For his info, the transport modle is 611
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Mon, 22 May 2017, Linux for blind general discussion wrote:
>
>> Hi folks,
>> Realizing it may be solved by now, I did promise to ask another user.
>> His thoughts are below, if the person is still having issues let me know now
>> as he has offered to help them troubleshoot given he has used his own unit
>> with Linux for some time.
>> Karen
>>
>>
>> ---------- Forwarded message ----------
>> Date: Mon, 22 May 2017 21:23:01 -0400 (EDT)
>> Subject: Re: artic transport question?
>>
>> Ahh, yes, depending on which artic synthesizer he has, he may need to run a
>> program, or set it to synthesizer mode. If it's a spirit, nothing needs to be
>> done, it should just work. If it's a transtype, there is an option in the
>> menus to set it to speech mode, though that's the one where you can also run
>> the terminal program, and it will talk that way too, though not as readily or
>> as well as the synthewsizer mode will allow. If it's a transport, just
>> setting the linux side of things to 9600 8, n, 1 should take care of the
>> problem, as that is the default settings on the transport.
>> I think that covers all the possible options. If there are further issues,
>> feel free to pass my email address on to the individual having trouble.
>>
>>
>> Again, hope this helps.
>>
>>
>>>
>>>
>>>> If I remember correctly, (and assuming this person hasn't already solved
>>>> their issue), the keyword for the transport is txprt.
>>>> Passing that on the commandline along with the port (or it can scan for >
>>> the port automatically) should do the trick.
>>>> Hope this helps.
>>
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
` Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
1 sibling, 2 replies; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
Hi Mark,
Santa has come early if you have an interest.
I have for you a copy of the documentation for the artic transport.
Yes there is a way to set the clock.
In any case, you may want to write me privately, but I do not know if I
put my address in here if the post will be flagged.
Let me know and we can work it out as the song goes.
Kare
On Mon, 22 May 2017, Linux for blind general discussion wrote:
> Mark Peveto here.
> Issues mostly solved. If he could tell me how to set the clock on the thing, or even if it's possible For his info, the transport modle is 611
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Mon, 22 May 2017, Linux for blind general discussion wrote:
>
>> Hi folks,
>> Realizing it may be solved by now, I did promise to ask another user.
>> His thoughts are below, if the person is still having issues let me know now
>> as he has offered to help them troubleshoot given he has used his own unit
>> with Linux for some time.
>> Karen
>>
>>
>> ---------- Forwarded message ----------
>> Date: Mon, 22 May 2017 21:23:01 -0400 (EDT)
>> Subject: Re: artic transport question?
>>
>> Ahh, yes, depending on which artic synthesizer he has, he may need to run a
>> program, or set it to synthesizer mode. If it's a spirit, nothing needs to be
>> done, it should just work. If it's a transtype, there is an option in the
>> menus to set it to speech mode, though that's the one where you can also run
>> the terminal program, and it will talk that way too, though not as readily or
>> as well as the synthewsizer mode will allow. If it's a transport, just
>> setting the linux side of things to 9600 8, n, 1 should take care of the
>> problem, as that is the default settings on the transport.
>> I think that covers all the possible options. If there are further issues,
>> feel free to pass my email address on to the individual having trouble.
>>
>>
>> Again, hope this helps.
>>
>>
>>>
>>>
>>>> If I remember correctly, (and assuming this person hasn't already solved
>>>> their issue), the keyword for the transport is txprt.
>>>> Passing that on the commandline along with the port (or it can scan for >
>>> the port automatically) should do the trick.
>>>> Hope this helps.
>>
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
1 sibling, 2 replies; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: blinux-list
On Fri, May 26, 2017 at 12:16:09PM AEST, Linux for blind general discussion wrote:
> Hi Mark,
> Santa has come early if you have an interest.
> I have for you a copy of the documentation for the artic transport.
Does that documentation happen to also contain the command set to talk to the
transport hardware?
Luke
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
1 sibling, 1 reply; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
Do you mean in Linux?
The documentation is that which came with the unit when sold, if that
makes sense.
Would you like a copy as well?
Kare
On Fri, 26 May 2017, Linux for blind general discussion wrote:
> On Fri, May 26, 2017 at 12:16:09PM AEST, Linux for blind general discussion wrote:
>> Hi Mark,
>> Santa has come early if you have an interest.
>> I have for you a copy of the documentation for the artic transport.
>
> Does that documentation happen to also contain the command set to talk to the
> transport hardware?
>
> Luke
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
` Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
1 sibling, 1 reply; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
I think the command set was a control-e followed by a character v for
volume, r for rate, p for pitch. Then you had nine levels
sample: control-er9 set the fastest rate.
Could be wrong.
On 5/25/2017 10:26 PM, Linux for blind general discussion wrote:
> On Fri, May 26, 2017 at 12:16:09PM AEST, Linux for blind general discussion wrote:
>> Hi Mark,
>> Santa has come early if you have an interest.
>> I have for you a copy of the documentation for the artic transport.
> Does that documentation happen to also contain the command set to talk to the
> transport hardware?
>
> Luke
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
0 siblings, 1 reply; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: blinux-list
On Fri, May 26, 2017 at 12:39:24PM AEST, Linux for blind general discussion wrote:
> Do you mean in Linux?
> The documentation is that which came with the unit when sold, if that makes
> sense.
I mean the protocol that software needs to use to talk to the hardware over
the serial interface.
> Would you like a copy as well?
If you can send it electronically, sure. If you'd prefer, I can email you off
list about this.
Luke
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
` Linux for blind general discussion
@ ` Linux for blind general discussion
1 sibling, 0 replies; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
Karen,
Nope, it didn't put your address in here. Seems I had it one time when we were discussing another issue, but I don't now. Here's mine.
southernprince73@gmail.com
Hth.
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
On Thu, 25 May 2017, Linux for blind general discussion wrote:
> Hi Mark,
> Santa has come early if you have an interest.
> I have for you a copy of the documentation for the artic transport.
> Yes there is a way to set the clock.
> In any case, you may want to write me privately, but I do not know if I put
> my address in here if the post will be flagged.
> Let me know and we can work it out as the song goes.
> Kare
>
>
> On Mon, 22 May 2017, Linux for blind general discussion wrote:
>
> > Mark Peveto here.
> > Issues mostly solved. If he could tell me how to set the clock on the
> > thing, or even if it's possible For his info, the transport modle is 611
> >
> >
> > Mark Peveto
> > Registered Linux user number 600552
> > Everything happens after coffee!
> >
> > On Mon, 22 May 2017, Linux for blind general discussion wrote:
> >
> > > Hi folks,
> > > Realizing it may be solved by now, I did promise to ask another user.
> > > His thoughts are below, if the person is still having issues let me know
> > > now
> > > as he has offered to help them troubleshoot given he has used his own
> > > unit
> > > with Linux for some time.
> > > Karen
> > >
> > >
> > > ---------- Forwarded message ----------
> > > Date: Mon, 22 May 2017 21:23:01 -0400 (EDT)
> > > Subject: Re: artic transport question?
> > >
> > > Ahh, yes, depending on which artic synthesizer he has, he may need to run
> > > a
> > > program, or set it to synthesizer mode. If it's a spirit, nothing needs
> > > to be
> > > done, it should just work. If it's a transtype, there is an option in the
> > > menus to set it to speech mode, though that's the one where you can also
> > > run
> > > the terminal program, and it will talk that way too, though not as readily
> > > or
> > > as well as the synthewsizer mode will allow. If it's a transport, just
> > > setting the linux side of things to 9600 8, n, 1 should take care of the
> > > problem, as that is the default settings on the transport.
> > > I think that covers all the possible options. If there are further
> > > issues,
> > > feel free to pass my email address on to the individual having trouble.
> > >
> > >
> > > Again, hope this helps.
> > >
> > >
> > > >
> > > >
> > > > > If I remember correctly, (and assuming this person hasn't already
> > > > > solved
> > > > > their issue), the keyword for the transport is txprt.
> > > > > Passing that on the commandline along with the port (or it can scan
> > > > > for >
> > > > the port automatically) should do the trick.
> > > > > Hope this helps.
> > >
> > >
> > >
> > > _______________________________________________
> > > Blinux-list mailing list
> > > Blinux-list@redhat.com
> > > https://www.redhat.com/mailman/listinfo/blinux-list
> > >
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> >
> >
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
0 siblings, 1 reply; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
hi Luke,
write me privately and I will send you the file.
Karen
On Fri, 26 May 2017, Linux for blind general discussion wrote:
> On Fri, May 26, 2017 at 12:39:24PM AEST, Linux for blind general discussion wrote:
>> Do you mean in Linux?
>> The documentation is that which came with the unit when sold, if that makes
>> sense.
>
> I mean the protocol that software needs to use to talk to the hardware over
> the serial interface.
>
>> Would you like a copy as well?
>
> If you can send it electronically, sure. If you'd prefer, I can email you off
> list about this.
>
> Luke
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
@ ` Linux for blind general discussion
0 siblings, 0 replies; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
Its in the manual I suspect.
On Thu, 25 May 2017, Linux for blind general discussion wrote:
> I think the command set was a control-e followed by a character v for volume,
> r for rate, p for pitch. Then you had nine levels
>
> sample: control-er9 set the fastest rate.
>
> Could be wrong.
>
>
>
>
> On 5/25/2017 10:26 PM, Linux for blind general discussion wrote:
>> On Fri, May 26, 2017 at 12:16:09PM AEST, Linux for blind general
>> discussion wrote:
>> > Hi Mark,
>> > Santa has come early if you have an interest.
>> > I have for you a copy of the documentation for the artic transport.
>> Does that documentation happen to also contain the command set to talk to
>> the
>> transport hardware?
>>
>> Luke
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
@ ` Linux for blind general discussion
` Linux for blind general discussion
0 siblings, 1 reply; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
Mark Peveto here,
Karen, I don't think he can, unless he already has your private email address. The list doesn't show our addresses anymore, to keep those spammers
away.
Everything now shows it comes from the blinux list.
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
On Tue, 30 May 2017, Linux for blind general discussion wrote:
> hi Luke,
> write me privately and I will send you the file.
> Karen
>
>
> On Fri, 26 May 2017, Linux for blind general discussion wrote:
>
> > On Fri, May 26, 2017 at 12:39:24PM AEST, Linux for blind general discussion
> > wrote:
> > > Do you mean in Linux?
> > > The documentation is that which came with the unit when sold, if that
> > > makes
> > > sense.
> >
> > I mean the protocol that software needs to use to talk to the hardware over
> > the serial interface.
> >
> > > Would you like a copy as well?
> >
> > If you can send it electronically, sure. If you'd prefer, I can email you
> > off
> > list about this.
> >
> > Luke
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
> >
> >
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: old artic transport, some ideas.
` Linux for blind general discussion
@ ` Linux for blind general discussion
0 siblings, 0 replies; 13+ messages in thread
From: Linux for blind general discussion @ UTC (permalink / raw)
To: Linux for blind general discussion
Hi mark,
I am playing catch up. I just noted our post with your email address,
sending the files along.
Indeed, the protection from one did slow down the train, but only slightly.
Kare
On Tue, 30 May 2017, Linux for blind general discussion wrote:
> Mark Peveto here,
> Karen, I don't think he can, unless he already has your private email address. The list doesn't show our addresses anymore, to keep those spammers
> away.
> Everything now shows it comes from the blinux list.
>
>
> Mark Peveto
> Registered Linux user number 600552
> Everything happens after coffee!
>
> On Tue, 30 May 2017, Linux for blind general discussion wrote:
>
>> hi Luke,
>> write me privately and I will send you the file.
>> Karen
>>
>>
>> On Fri, 26 May 2017, Linux for blind general discussion wrote:
>>
>>> On Fri, May 26, 2017 at 12:39:24PM AEST, Linux for blind general discussion
>>> wrote:
>>>> Do you mean in Linux?
>>>> The documentation is that which came with the unit when sold, if that
>>>> makes
>>>> sense.
>>>
>>> I mean the protocol that software needs to use to talk to the hardware over
>>> the serial interface.
>>>
>>>> Would you like a copy as well?
>>>
>>> If you can send it electronically, sure. If you'd prefer, I can email you
>>> off
>>> list about this.
>>>
>>> Luke
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>
>>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
old artic transport, some ideas Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).