I have, but not for sound, only for addresses and other non-sound
functions
Ian B

In message <ggubla+hrun@eGroups.com>, david516498
<david.illingworth1@...> writes
>
>Hello
>
>I've just purcahsed the ESU decoder tester and wondered if anyone has
>used Sprog II to program decoders on the ESU Profi-Prüfstand (Decoder
>Tester) rather than via a programming track?
>
>David
>Keighley
>W Yorks
>
>
>
>No virus found in this incoming message.
>Checked by AVG - http://www.avg.com
>Version: 8.0.176 / Virus Database: 270.9.11/1820 - Release Date:
>29/11/2008 18:52

--
Ian Birchenough
   ----------


   ----------


No virus found in this outgoing message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.11/1820 - Release Date: 29/11/2008
18:52


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

Do you have a particular problem, or just asking?

There should be no problem, so long as the decoder has a load
connected to the motor terminals, otherwise you will get "no loco
detected" errors in DecoderPro.

Andrew Crosland

--- In sprog-dcc@..., "david516498"
<david.illingworth1@...> wrote:
>
> Hello
>
> I've just purcahsed the ESU decoder tester and wondered if anyone has
> used Sprog II to program decoders on the ESU Profi-Prüfstand (Decoder
> Tester) rather than via a programming track?
>
> David
> Keighley
> W Yorks
>

If it's Item 51900 then it includes a motor and flywheel
Ian

In message <gh0omf+q1kp@eGroups.com>, andrew_croslanduk
<andrewcrosland@...> writes
>
>Do you have a particular problem, or just asking?
>
>There should be no problem, so long as the decoder has a load
>connected to the motor terminals, otherwise you will get "no loco
>detected" errors in DecoderPro.
>
>Andrew Crosland
>
>--- In sprog-dcc@..., "david516498"
><david.illingworth1@...> wrote:
>>
>> Hello
>>
>> I've just purcahsed the ESU decoder tester and wondered if anyone has
>> used Sprog II to program decoders on the ESU Profi-Prüfstand (Decoder
>> Tester) rather than via a programming track?
>>
>> David
>> Keighley
>> W Yorks
>>
>
>
>
>No virus found in this incoming message.
>Checked by AVG - http://www.avg.com
>Version: 8.0.176 / Virus Database: 270.9.12/1821 - Release Date:
>30/11/2008 17:53

--
Ian Birchenough
   ----------


   ----------


No virus found in this outgoing message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.12/1821 - Release Date: 30/11/2008
17:53


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

Many thanks for your answers
 
It is item 51900 with motor and flywheel and I was only asking before I use it.
 
David

--- On Mon, 1/12/08, Ian Birchenough <ian.birchenough@...> wrote:

From: Ian Birchenough <ian.birchenough@...>
Subject: Re: [sprog-dcc] Re: Sprog II and ESU decoder tester
To: sprog-dcc@...
Date: Monday, 1 December, 2008, 5:24 PM






If it's Item 51900 then it includes a motor and flywheel
Ian

In message <gh0omf+q1kp@ eGroups.com>, andrew_croslanduk
<andrewcrosland@ talktalk. net> writes
>
>Do you have a particular problem, or just asking?
>
>There should be no problem, so long as the decoder has a load
>connected to the motor terminals, otherwise you will get "no loco
>detected" errors in DecoderPro.
>
>Andrew Crosland
>
>--- In sprog-dcc@yahoogrou ps.co.uk, "david516498"
><david.illingworth 1@...> wrote:
>>
>> Hello
>>
>> I've just purcahsed the ESU decoder tester and wondered if anyone has
>> used Sprog II to program decoders on the ESU Profi-Prüfstand (Decoder
>> Tester) rather than via a programming track?
>>
>> David
>> Keighley
>> W Yorks
>>
>
>
>
>No virus found in this incoming message.
>Checked by AVG - http://www.avg. com
>Version: 8.0.176 / Virus Database: 270.9.12/1821 - Release Date:
>30/11/2008 17:53

--
Ian Birchenough
----------

----------

No virus found in this outgoing message.
Checked by AVG - http://www.avg. com
Version: 8.0.176 / Virus Database: 270.9.12/1821 - Release Date: 30/11/2008
17:53

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















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

David

I am reliably informed that there should be no problem, just treat the
tester as a programming track, it has all the relevent loads etc to function
as if the decoder were plugged into a loco.

It allows you to test and program a decoder before you start taking locos
apart, the only thing you may have to adjust is perhaps the speed curve
dependant on the characteristics of the loco it is then plugged into

Hope this is of use

Paul

-----Original Message-----
From: sprog-dcc@... [mailto:sprog-dcc@...] On
Behalf Of andrew_croslanduk
Sent: 01 December 2008 13:27
To: sprog-dcc@...
Subject: [sprog-dcc] Re: Sprog II and ESU decoder tester



Do you have a particular problem, or just asking?

There should be no problem, so long as the decoder has a load
connected to the motor terminals, otherwise you will get "no loco
detected" errors in DecoderPro.

Andrew Crosland

--- In sprog-dcc@yahoogrou <mailto:sprog-dcc%40yahoogroups.co.uk> ps.co.uk,
"david516498"
<david.illingworth1@...> wrote:
>
> Hello
>
> I've just purcahsed the ESU decoder tester and wondered if anyone has
> used Sprog II to program decoders on the ESU Profi-Prüfstand (Decoder
> Tester) rather than via a programming track?
>
> David
> Keighley
> W Yorks
>







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

David,

I have one of these ESU units, and it works very well with SPROG II. I
have used it for ESU decoders, but also for many other types. The
light and motor loads work very effectively, both for programming and
test running the decoder behavior (I had an apparently faulty one,
removed from the loco, and was easily able to check it out thoroughly
on this unit).

Bill
www.bbmgroup.com/sprog

--- In sprog-dcc@..., "PAUL LEWIS" <lewis4@...> wrote:
>
> David
>
> I am reliably informed that there should be no problem, just treat the
> tester as a programming track, it has all the relevent loads etc to
function
> as if the decoder were plugged into a loco.
>
> It allows you to test and program a decoder before you start taking
locos
> apart, the only thing you may have to adjust is perhaps the speed curve
> dependant on the characteristics of the loco it is then plugged into
>
> Hope this is of use
>
> Paul
>
> -----Original Message-----
> From: sprog-dcc@...
[mailto:sprog-dcc@...] On
> Behalf Of andrew_croslanduk
> Sent: 01 December 2008 13:27
> To: sprog-dcc@...
> Subject: [sprog-dcc] Re: Sprog II and ESU decoder tester
>
>
>
> Do you have a particular problem, or just asking?
>
> There should be no problem, so long as the decoder has a load
> connected to the motor terminals, otherwise you will get "no loco
> detected" errors in DecoderPro.
>
> Andrew Crosland
>
> --- In sprog-dcc@yahoogrou <mailto:sprog-dcc%40yahoogroups.co.uk>
ps.co.uk,
> "david516498"
> <david.illingworth1@> wrote:
> >
> > Hello
> >
> > I've just purcahsed the ESU decoder tester and wondered if anyone has
> > used Sprog II to program decoders on the ESU Profi-Prüfstand (Decoder
> > Tester) rather than via a programming track?
> >
> > David
> > Keighley
> > W Yorks
> >
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

Thanks to Utz -R. Kaufmann there is now a German translation of the
SPROG User Guide on the SPROG DCC download page. If anyone could help
in proof reading I would be very grateful.

We're still trying to find someone to do a French translation.

Andrew

>Thanks to Utz -R. Kaufmann there is now a German translation of the
>SPROG User Guide on the SPROG DCC download page. If anyone could help
>in proof reading I would be very grateful.
>
>We're still trying to find someone to do a French translation.

Anybody interested in updating the JMRI DecoderPro German and French
translations?

Starting in January, we also hope to be able to have translated
decoder definitions, so that decoder that are commonly used by e.g.
German and French users could have their variable names, etc, appear
in a more friendly form.  It'll require translation, of course, but
perhaps not as much as people might think.

Bob
--
Bob Jacobsen, UC Berkeley
jacobsen@... +1-510-486-7355 fax +1-510-643-8497 AIM, Skype JacobsenRG

Can anyone help me, maybe off-group, to adjust the volume of my
(mostly) Massoth xls decoders.
Also help to grasp Function mapping would be welcome.
Thanks,
Mike

Hi All,
I have a particular problem, I wonder if anyone can help please?
Whereas my Sprog II works fine in Service Mode Programming, plus the
throttle routine is good. However, in Ops Mode, I can't get anything to
run using the throttle for more than about 5 seconds. After that, the
loco stops, Decoder Pro freezes and a re-boot of the Sprog Power Supply
is required. Because of this, I haven't even tried programming in Ops
Mode.
Does anyone have the same experience as me? Incidently, I'm running on
Windows XP with USB 1 if that makes a difference.
Thanks in anticipation,
regards,
Keith
Droitwich Spa

John,

What do you mean by a reboot of the power supply? Turning it off and
on?

Does turning the track power off and on from the throttle help at all?

Could you open the SPROG command monitor and log the activity and
send it directly to me (use the contact e-mail on our web page)?

Regards,

Andrew Crosland

--- In sprog-dcc@..., "Keith Woodbridge"
<keithrwoodbridge@...> wrote:
>
> Hi All,
> I have a particular problem, I wonder if anyone can help please?
> Whereas my Sprog II works fine in Service Mode Programming, plus
the
> throttle routine is good. However, in Ops Mode, I can't get
anything to
> run using the throttle for more than about 5 seconds. After that,
the
> loco stops, Decoder Pro freezes and a re-boot of the Sprog Power
Supply
> is required. Because of this, I haven't even tried programming in
Ops
> Mode.
> Does anyone have the same experience as me? Incidently, I'm running
on
> Windows XP with USB 1 if that makes a difference.
> Thanks in anticipation,
> regards,
> Keith
> Droitwich Spa
>

--- In sprog-dcc@..., "andrew_croslanduk"
<andrewcrosland@...> wrote:
>
> John,
>
> What do you mean by a reboot of the power supply? Turning it off
and
> on?
>
> Does turning the track power off and on from the throttle help at
all?
>
> Could you open the SPROG command monitor and log the activity and
> send it directly to me (use the contact e-mail on our web page)?
>
> Regards,
>
> Andrew Crosland
>
> --- In sprog-dcc@..., "Keith Woodbridge"
> <keithrwoodbridge@> wrote:
> >
> > Hi All,
> > I have a particular problem, I wonder if anyone can help please?
> > Whereas my Sprog II works fine in Service Mode Programming, plus
> the
> > throttle routine is good. However, in Ops Mode, I can't get
> anything to
> > run using the throttle for more than about 5 seconds. After that,
> the
> > loco stops, Decoder Pro freezes and a re-boot of the Sprog Power
> Supply
> > is required. Because of this, I haven't even tried programming in
> Ops
> > Mode.
> > Does anyone have the same experience as me? Incidently, I'm
running
> on
> > Windows XP with USB 1 if that makes a difference.
> > Thanks in anticipation,
> > regards,
> > Keith
> > Droitwich Spa
> >
>
Hi Andrew,
Re-booting the Sprog Power Supply means turning it off and back on,
yes. Turning the trck power on and off at the throttle does not seem
to make any difference, bearing in mind that sometimes the throttle
will work for a short time, other times it won't work at all. I'll
send some Sprog Command Monitor Log Data over during this week.
Thanks for your reply.
Best regards,
Keith

Hi Keith,

It sounds more like a decoder pro problem than a SPROG problem. Which
version of Decoder Pro are you using? I have a really odd problem with it
too - it won't control more than one loco in command station mode - nothing
happens with one of them - it just won't respond! Decoder pro doesn't crash
on me though...

I need to run in programming mode and use one throttle at a time.

Andrew

On Sun, Dec 14, 2008 at 8:47 PM, andrew_croslanduk <
andrewcrosland@...> wrote:

>   John,
>
> What do you mean by a reboot of the power supply? Turning it off and
> on?
>
> Does turning the track power off and on from the throttle help at all?
>
> Could you open the SPROG command monitor and log the activity and
> send it directly to me (use the contact e-mail on our web page)?
>
> Regards,
>
> Andrew Crosland
>
> --- In sprog-dcc@... <sprog-dcc%40yahoogroups.co.uk>, "Keith
> Woodbridge"
> <keithrwoodbridge@...> wrote:
> >
> > Hi All,
> > I have a particular problem, I wonder if anyone can help please?
> > Whereas my Sprog II works fine in Service Mode Programming, plus
> the
> > throttle routine is good. However, in Ops Mode, I can't get
> anything to
> > run using the throttle for more than about 5 seconds. After that,
> the
> > loco stops, Decoder Pro freezes and a re-boot of the Sprog Power
> Supply
> > is required. Because of this, I haven't even tried programming in
> Ops
> > Mode.
> > Does anyone have the same experience as me? Incidently, I'm running
> on
> > Windows XP with USB 1 if that makes a difference.
> > Thanks in anticipation,
> > regards,
> > Keith
> > Droitwich Spa
> >
>
>
>


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

Andrew,

Sorry for the delay in your message. It got trapped as spam for some
reason and I didn't notice it waiting for my attention.

If you try to control multiple locos in command station mode, do they
all work individually? Is it always the same one that doesn't work?

Andrew C

PS I wrote the DecoderPro code for this feature so if there is a bug
it's in my code.


--- In sprog-dcc@..., "Andrew Berridge"
<andrew.berridge@...> wrote:
>
> Hi Keith,
>
> It sounds more like a decoder pro problem than a SPROG problem. Which
> version of Decoder Pro are you using? I have a really odd problem
with it
> too - it won't control more than one loco in command station mode -
nothing
> happens with one of them - it just won't respond! Decoder pro
doesn't crash
> on me though...
>
> I need to run in programming mode and use one throttle at a time.
>
> Andrew
>
> On Sun, Dec 14, 2008 at 8:47 PM, andrew_croslanduk <
> andrewcrosland@...> wrote:
>
> >   John,
> >
> > What do you mean by a reboot of the power supply? Turning it off and
> > on?
> >
> > Does turning the track power off and on from the throttle help at all?
> >
> > Could you open the SPROG command monitor and log the activity and
> > send it directly to me (use the contact e-mail on our web page)?
> >
> > Regards,
> >
> > Andrew Crosland
> >
> > --- In sprog-dcc@...
<sprog-dcc%40yahoogroups.co.uk>, "Keith
> > Woodbridge"
> > <keithrwoodbridge@> wrote:
> > >
> > > Hi All,
> > > I have a particular problem, I wonder if anyone can help please?
> > > Whereas my Sprog II works fine in Service Mode Programming, plus
> > the
> > > throttle routine is good. However, in Ops Mode, I can't get
> > anything to
> > > run using the throttle for more than about 5 seconds. After that,
> > the
> > > loco stops, Decoder Pro freezes and a re-boot of the Sprog Power
> > Supply
> > > is required. Because of this, I haven't even tried programming in
> > Ops
> > > Mode.
> > > Does anyone have the same experience as me? Incidently, I'm running
> > on
> > > Windows XP with USB 1 if that makes a difference.
> > > Thanks in anticipation,
> > > regards,
> > > Keith
> > > Droitwich Spa
> > >
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>

--- In sprog-dcc@..., "Andrew Berridge"
<andrew.berridge@...> wrote:
>
> Hi Keith,
>
> It sounds more like a decoder pro problem than a SPROG problem.
Which
> version of Decoder Pro are you using? I have a really odd problem
with it
> too - it won't control more than one loco in command station mode -
nothing
> happens with one of them - it just won't respond! Decoder pro
doesn't crash
> on me though...
>
> I need to run in programming mode and use one throttle at a time.
>
> Andrew
>
> On Sun, Dec 14, 2008 at 8:47 PM, andrew_croslanduk <
> andrewcrosland@...> wrote:
>
> >   John,
> >
> > What do you mean by a reboot of the power supply? Turning it off
and
> > on?
> >
> > Does turning the track power off and on from the throttle help at
all?
> >
> > Could you open the SPROG command monitor and log the activity and
> > send it directly to me (use the contact e-mail on our web page)?
> >
> > Regards,
> >
> > Andrew Crosland
> >
> > --- In sprog-dcc@... <sprog-dcc%
40yahoogroups.co.uk>, "Keith
> > Woodbridge"
> > <keithrwoodbridge@> wrote:
> > >
> > > Hi All,
> > > I have a particular problem, I wonder if anyone can help please?
> > > Whereas my Sprog II works fine in Service Mode Programming, plus
> > the
> > > throttle routine is good. However, in Ops Mode, I can't get
> > anything to
> > > run using the throttle for more than about 5 seconds. After
that,
> > the
> > > loco stops, Decoder Pro freezes and a re-boot of the Sprog Power
> > Supply
> > > is required. Because of this, I haven't even tried programming
in
> > Ops
> > > Mode.
> > > Does anyone have the same experience as me? Incidently, I'm
running
> > on
> > > Windows XP with USB 1 if that makes a difference.
> > > Thanks in anticipation,
> > > regards,
> > > Keith
> > > Droitwich Spa
> > >
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
Hi Andrew,
What you are saying does actually happen, in that, I can't get more
than one throttle to work at one time in command mode. The chances of
a throttle working first time in command mode are very slim. The
Decoder Pro I am using is version 2.3.7 and Java 1.6.0_11. Again, in
service mode, it all seems to work OK. I've added some 15 locos to
the roster over the last few days and fiddled with the speed tables
(in an attempt to sort out my consist running quality). By and large,
there have not been any serious hiccoughs.
Best regards,
Keith

Hi Andrew C,

No problem at all! I think (but can't confirm as I've not investigated
it too closely) that it's the second throttle that's opened that
doesn't work.

There's another problem with Decoder Pro in programming mode - if I
try to use multiple throttles, the second one always complains that
its address is in use by another throttle, and is therefore unusable.
I've not investigated the Decoder Pro code yet - I want to at some
stage. I'm a software developer by trade, so it does interest me!

I'll try and get up into the loft this evening to confirm exactly what
happens, and also to capture some SPROG command logs...

I'm currently using Decoder Pro 2.3.6 with a SPROG I

Thanks,

Andrew B


On Tue, Dec 16, 2008 at 5:33 PM, andrew_croslanduk
<andrewcrosland@...> wrote:
> Andrew,
>
> Sorry for the delay in your message. It got trapped as spam for some
> reason and I didn't notice it waiting for my attention.
>
> If you try to control multiple locos in command station mode, do they
> all work individually? Is it always the same one that doesn't work?
>
> Andrew C
>
> PS I wrote the DecoderPro code for this feature so if there is a bug
> it's in my code.
>
> --- In sprog-dcc@..., "Andrew Berridge"
>
> <andrew.berridge@...> wrote:
>>
>> Hi Keith,
>>
>> It sounds more like a decoder pro problem than a SPROG problem. Which
>> version of Decoder Pro are you using? I have a really odd problem
> with it
>> too - it won't control more than one loco in command station mode -
> nothing
>> happens with one of them - it just won't respond! Decoder pro
> doesn't crash
>> on me though...
>>
>> I need to run in programming mode and use one throttle at a time.
>>
>> Andrew
>>
>> On Sun, Dec 14, 2008 at 8:47 PM, andrew_croslanduk <
>> andrewcrosland@...> wrote:
>>
>> > John,
>> >
>> > What do you mean by a reboot of the power supply? Turning it off and
>> > on?
>> >
>> > Does turning the track power off and on from the throttle help at all?
>> >
>> > Could you open the SPROG command monitor and log the activity and
>> > send it directly to me (use the contact e-mail on our web page)?
>> >
>> > Regards,
>> >
>> > Andrew Crosland
>> >
>> > --- In sprog-dcc@...
> <sprog-dcc%40yahoogroups.co.uk>, "Keith
>> > Woodbridge"
>> > <keithrwoodbridge@> wrote:
>> > >
>> > > Hi All,
>> > > I have a particular problem, I wonder if anyone can help please?
>> > > Whereas my Sprog II works fine in Service Mode Programming, plus
>> > the
>> > > throttle routine is good. However, in Ops Mode, I can't get
>> > anything to
>> > > run using the throttle for more than about 5 seconds. After that,
>> > the
>> > > loco stops, Decoder Pro freezes and a re-boot of the Sprog Power
>> > Supply
>> > > is required. Because of this, I haven't even tried programming in
>> > Ops
>> > > Mode.
>> > > Does anyone have the same experience as me? Incidently, I'm running
>> > on
>> > > Windows XP with USB 1 if that makes a difference.
>> > > Thanks in anticipation,
>> > > regards,
>> > > Keith
>> > > Droitwich Spa
>> > >
>> >
>> >
>> >
>>
>>
>> [Non-text portions of this message have been removed]
>>
>
>

Hmmm... methinks this (at least my problem) is a red herring! Please
don't worry - I think it's working fine - it's just my loco and my
track. I'm still in the very early experimental stages, and I couldn't
get a loco to work on one track. I tried just now and everything's
fine. One of my sections of track appears not to have full continuity,
but I've not yet soldered droppers to it. Something to do over the
Christmas break!

The commands going to the SPROG look entirely correct...

Thanks,

Andrew

On Tue, Dec 16, 2008 at 6:50 PM, Andrew Berridge
<andrew.berridge@...> wrote:
> Hi Andrew C,
>
> No problem at all! I think (but can't confirm as I've not investigated
> it too closely) that it's the second throttle that's opened that
> doesn't work.
>
> There's another problem with Decoder Pro in programming mode - if I
> try to use multiple throttles, the second one always complains that
> its address is in use by another throttle, and is therefore unusable.
> I've not investigated the Decoder Pro code yet - I want to at some
> stage. I'm a software developer by trade, so it does interest me!
>
> I'll try and get up into the loft this evening to confirm exactly what
> happens, and also to capture some SPROG command logs...
>
> I'm currently using Decoder Pro 2.3.6 with a SPROG I
>
> Thanks,
>
> Andrew B
>
>
> On Tue, Dec 16, 2008 at 5:33 PM, andrew_croslanduk
> <andrewcrosland@...> wrote:
>> Andrew,
>>
>> Sorry for the delay in your message. It got trapped as spam for some
>> reason and I didn't notice it waiting for my attention.
>>
>> If you try to control multiple locos in command station mode, do they
>> all work individually? Is it always the same one that doesn't work?
>>
>> Andrew C
>>
>> PS I wrote the DecoderPro code for this feature so if there is a bug
>> it's in my code.
>>
>> --- In sprog-dcc@..., "Andrew Berridge"
>>
>> <andrew.berridge@...> wrote:
>>>
>>> Hi Keith,
>>>
>>> It sounds more like a decoder pro problem than a SPROG problem. Which
>>> version of Decoder Pro are you using? I have a really odd problem
>> with it
>>> too - it won't control more than one loco in command station mode -
>> nothing
>>> happens with one of them - it just won't respond! Decoder pro
>> doesn't crash
>>> on me though...
>>>
>>> I need to run in programming mode and use one throttle at a time.
>>>
>>> Andrew
>>>
>>> On Sun, Dec 14, 2008 at 8:47 PM, andrew_croslanduk <
>>> andrewcrosland@...> wrote:
>>>
>>> > John,
>>> >
>>> > What do you mean by a reboot of the power supply? Turning it off and
>>> > on?
>>> >
>>> > Does turning the track power off and on from the throttle help at all?
>>> >
>>> > Could you open the SPROG command monitor and log the activity and
>>> > send it directly to me (use the contact e-mail on our web page)?
>>> >
>>> > Regards,
>>> >
>>> > Andrew Crosland
>>> >
>>> > --- In sprog-dcc@...
>> <sprog-dcc%40yahoogroups.co.uk>, "Keith
>>> > Woodbridge"
>>> > <keithrwoodbridge@> wrote:
>>> > >
>>> > > Hi All,
>>> > > I have a particular problem, I wonder if anyone can help please?
>>> > > Whereas my Sprog II works fine in Service Mode Programming, plus
>>> > the
>>> > > throttle routine is good. However, in Ops Mode, I can't get
>>> > anything to
>>> > > run using the throttle for more than about 5 seconds. After that,
>>> > the
>>> > > loco stops, Decoder Pro freezes and a re-boot of the Sprog Power
>>> > Supply
>>> > > is required. Because of this, I haven't even tried programming in
>>> > Ops
>>> > > Mode.
>>> > > Does anyone have the same experience as me? Incidently, I'm running
>>> > on
>>> > > Windows XP with USB 1 if that makes a difference.
>>> > > Thanks in anticipation,
>>> > > regards,
>>> > > Keith
>>> > > Droitwich Spa
>>> > >
>>> >
>>> >
>>> >
>>>
>>>
>>> [Non-text portions of this message have been removed]
>>>
>>
>>
>

Andrew,

Thanks for letting us know.

The Yahoo spam filter doesn't like you for some reason!

Andrew C

--- In sprog-dcc@..., "Andrew Berridge"
<andrew.berridge@...> wrote:
>
> Hmmm... methinks this (at least my problem) is a red herring! Please
> don't worry - I think it's working fine - it's just my loco and my
> track. I'm still in the very early experimental stages, and I
couldn't
> get a loco to work on one track. I tried just now and everything's
> fine. One of my sections of track appears not to have full
continuity,
> but I've not yet soldered droppers to it. Something to do over the
> Christmas break!
>
> The commands going to the SPROG look entirely correct...
>
> Thanks,
>
> Andrew
>
> On Tue, Dec 16, 2008 at 6:50 PM, Andrew Berridge
> <andrew.berridge@...> wrote:
> > Hi Andrew C,
> >
> > No problem at all! I think (but can't confirm as I've not
investigated
> > it too closely) that it's the second throttle that's opened that
> > doesn't work.
> >
> > There's another problem with Decoder Pro in programming mode - if
I
> > try to use multiple throttles, the second one always complains
that
> > its address is in use by another throttle, and is therefore
unusable.
> > I've not investigated the Decoder Pro code yet - I want to at some
> > stage. I'm a software developer by trade, so it does interest me!
> >
> > I'll try and get up into the loft this evening to confirm exactly
what
> > happens, and also to capture some SPROG command logs...
> >
> > I'm currently using Decoder Pro 2.3.6 with a SPROG I
> >
> > Thanks,
> >
> > Andrew B
> >
> >
> > On Tue, Dec 16, 2008 at 5:33 PM, andrew_croslanduk
> > <andrewcrosland@...> wrote:
> >> Andrew,
> >>
> >> Sorry for the delay in your message. It got trapped as spam for
some
> >> reason and I didn't notice it waiting for my attention.
> >>
> >> If you try to control multiple locos in command station mode, do
they
> >> all work individually? Is it always the same one that doesn't
work?
> >>
> >> Andrew C
> >>
> >> PS I wrote the DecoderPro code for this feature so if there is a
bug
> >> it's in my code.
> >>
> >> --- In sprog-dcc@..., "Andrew Berridge"
> >>
> >> <andrew.berridge@> wrote:
> >>>
> >>> Hi Keith,
> >>>
> >>> It sounds more like a decoder pro problem than a SPROG problem.
Which
> >>> version of Decoder Pro are you using? I have a really odd
problem
> >> with it
> >>> too - it won't control more than one loco in command station
mode -
> >> nothing
> >>> happens with one of them - it just won't respond! Decoder pro
> >> doesn't crash
> >>> on me though...
> >>>
> >>> I need to run in programming mode and use one throttle at a
time.
> >>>
> >>> Andrew
> >>>
> >>> On Sun, Dec 14, 2008 at 8:47 PM, andrew_croslanduk <
> >>> andrewcrosland@> wrote:
> >>>
> >>> > John,
> >>> >
> >>> > What do you mean by a reboot of the power supply? Turning it
off and
> >>> > on?
> >>> >
> >>> > Does turning the track power off and on from the throttle
help at all?
> >>> >
> >>> > Could you open the SPROG command monitor and log the activity
and
> >>> > send it directly to me (use the contact e-mail on our web
page)?
> >>> >
> >>> > Regards,
> >>> >
> >>> > Andrew Crosland
> >>> >
> >>> > --- In sprog-dcc@...
> >> <sprog-dcc%40yahoogroups.co.uk>, "Keith
> >>> > Woodbridge"
> >>> > <keithrwoodbridge@> wrote:
> >>> > >
> >>> > > Hi All,
> >>> > > I have a particular problem, I wonder if anyone can help
please?
> >>> > > Whereas my Sprog II works fine in Service Mode Programming,
plus
> >>> > the
> >>> > > throttle routine is good. However, in Ops Mode, I can't get
> >>> > anything to
> >>> > > run using the throttle for more than about 5 seconds. After
that,
> >>> > the
> >>> > > loco stops, Decoder Pro freezes and a re-boot of the Sprog
Power
> >>> > Supply
> >>> > > is required. Because of this, I haven't even tried
programming in
> >>> > Ops
> >>> > > Mode.
> >>> > > Does anyone have the same experience as me? Incidently, I'm
running
> >>> > on
> >>> > > Windows XP with USB 1 if that makes a difference.
> >>> > > Thanks in anticipation,
> >>> > > regards,
> >>> > > Keith
> >>> > > Droitwich Spa
> >>> > >
> >>> >
> >>> >
> >>> >
> >>>
> >>>
> >>> [Non-text portions of this message have been removed]
> >>>
> >>
> >>
> >
>

Actually - I'm not sure that it is a red herring. I set up a loco with
a brand new decoder this afternoon. It worked perfectly in program
mode, but not in command station mode. I even had it on the same track
in the same location and switched between the two modes. This kind of
thing doesn't seem to be entirely predictable, but I will try to
figure out what causes the issue and when it occurs. Here are a couple
of sets of outputs (by the way, I've not yet researched how the
commands to the SPROG work - that might be the next thing I do..):

1) Working in program mode:

cmd: ">1"
rep: "P> "
cmd: ">41"
cmd: ">41"
rep: "P> "
rep: "P> "
cmd: ">76"
cmd: ">76"
rep: "P> "
rep: "P> "
cmd: ">0"
cmd: ">0"
rep: "P> "
rep: "P> "
cmd: "<0"
rep: "P> "
cmd: "<68"
cmd: "<68"
rep: "P> "
rep: "P> "
cmd: "<0"
cmd: "<0"
cmd: "<0"
rep: "P> "
rep: "P> "
rep: "P> "

In operation mode:

cmd: ">1"
rep: "P> "
cmd: ">41"
cmd: ">41"
rep: "P> "
rep: "P> "
cmd: ">76"
cmd: ">76"
rep: "P> "
rep: "P> "
cmd: ">0"
cmd: ">0"
rep: "P> "
rep: "P> "
cmd: "<0"
rep: "P> "
cmd: "<68"
cmd: "<68"
rep: "P> "
rep: "P> "
cmd: "<0"
cmd: "<0"
cmd: "<0"
rep: "P> "
rep: "P> "
rep: "P> "

Thanks for your help - I'll work on the issue too!

Andrew

On Fri, Dec 19, 2008 at 6:46 PM, andrew_croslanduk
<andrewcrosland@...> wrote:
> Andrew,
>
> Thanks for letting us know.
>
> The Yahoo spam filter doesn't like you for some reason!
>
> Andrew C
>
> --- In sprog-dcc@..., "Andrew Berridge"
> <andrew.berridge@...> wrote:
>>
>> Hmmm... methinks this (at least my problem) is a red herring! Please
>> don't worry - I think it's working fine - it's just my loco and my
>> track. I'm still in the very early experimental stages, and I
> couldn't
>> get a loco to work on one track. I tried just now and everything's
>> fine. One of my sections of track appears not to have full
> continuity,
>> but I've not yet soldered droppers to it. Something to do over the
>> Christmas break!
>>
>> The commands going to the SPROG look entirely correct...
>>
>> Thanks,
>>
>> Andrew
>>
>> On Tue, Dec 16, 2008 at 6:50 PM, Andrew Berridge
>> <andrew.berridge@...> wrote:
>> > Hi Andrew C,
>> >
>> > No problem at all! I think (but can't confirm as I've not
> investigated
>> > it too closely) that it's the second throttle that's opened that
>> > doesn't work.
>> >
>> > There's another problem with Decoder Pro in programming mode - if
> I
>> > try to use multiple throttles, the second one always complains
> that
>> > its address is in use by another throttle, and is therefore
> unusable.
>> > I've not investigated the Decoder Pro code yet - I want to at some
>> > stage. I'm a software developer by trade, so it does interest me!
>> >
>> > I'll try and get up into the loft this evening to confirm exactly
> what
>> > happens, and also to capture some SPROG command logs...
>> >
>> > I'm currently using Decoder Pro 2.3.6 with a SPROG I
>> >
>> > Thanks,
>> >
>> > Andrew B
>> >
>> >
>> > On Tue, Dec 16, 2008 at 5:33 PM, andrew_croslanduk
>> > <andrewcrosland@...> wrote:
>> >> Andrew,
>> >>
>> >> Sorry for the delay in your message. It got trapped as spam for
> some
>> >> reason and I didn't notice it waiting for my attention.
>> >>
>> >> If you try to control multiple locos in command station mode, do
> they
>> >> all work individually? Is it always the same one that doesn't
> work?
>> >>
>> >> Andrew C
>> >>
>> >> PS I wrote the DecoderPro code for this feature so if there is a
> bug
>> >> it's in my code.
>> >>
>> >> --- In sprog-dcc@..., "Andrew Berridge"
>> >>
>> >> <andrew.berridge@> wrote:
>> >>>
>> >>> Hi Keith,
>> >>>
>> >>> It sounds more like a decoder pro problem than a SPROG problem.
> Which
>> >>> version of Decoder Pro are you using? I have a really odd
> problem
>> >> with it
>> >>> too - it won't control more than one loco in command station
> mode -
>> >> nothing
>> >>> happens with one of them - it just won't respond! Decoder pro
>> >> doesn't crash
>> >>> on me though...
>> >>>
>> >>> I need to run in programming mode and use one throttle at a
> time.
>> >>>
>> >>> Andrew
>> >>>
>> >>> On Sun, Dec 14, 2008 at 8:47 PM, andrew_croslanduk <
>> >>> andrewcrosland@> wrote:
>> >>>
>> >>> > John,
>> >>> >
>> >>> > What do you mean by a reboot of the power supply? Turning it
> off and
>> >>> > on?
>> >>> >
>> >>> > Does turning the track power off and on from the throttle
> help at all?
>> >>> >
>> >>> > Could you open the SPROG command monitor and log the activity
> and
>> >>> > send it directly to me (use the contact e-mail on our web
> page)?
>> >>> >
>> >>> > Regards,
>> >>> >
>> >>> > Andrew Crosland
>> >>> >
>> >>> > --- In sprog-dcc@...
>> >> <sprog-dcc%40yahoogroups.co.uk>, "Keith
>> >>> > Woodbridge"
>> >>> > <keithrwoodbridge@> wrote:
>> >>> > >
>> >>> > > Hi All,
>> >>> > > I have a particular problem, I wonder if anyone can help
> please?
>> >>> > > Whereas my Sprog II works fine in Service Mode Programming,
> plus
>> >>> > the
>> >>> > > throttle routine is good. However, in Ops Mode, I can't get
>> >>> > anything to
>> >>> > > run using the throttle for more than about 5 seconds. After
> that,
>> >>> > the
>> >>> > > loco stops, Decoder Pro freezes and a re-boot of the Sprog
> Power
>> >>> > Supply
>> >>> > > is required. Because of this, I haven't even tried
> programming in
>> >>> > Ops
>> >>> > > Mode.
>> >>> > > Does anyone have the same experience as me? Incidently, I'm
> running
>> >>> > on
>> >>> > > Windows XP with USB 1 if that makes a difference.
>> >>> > > Thanks in anticipation,
>> >>> > > regards,
>> >>> > > Keith
>> >>> > > Droitwich Spa
>> >>> > >
>> >>> >
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>> [Non-text portions of this message have been removed]
>> >>>
>> >>
>> >>
>> >
>>
>
>

Ooops - not sure how that happened. No 2) in ops mode should have been:

rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "S"
rep: "S=h01C4 h0000 h00 hFC7196

P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "O 2C 3F 81 92"
rep: "P> "
cmd: "S"
rep: "S=h01C4 h0000 h00 hFD9019

P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "S"
rep: "S=h01C3 h0000 h00 hFEB0A0

P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "S"
rep: "S=h01C4 h0000 h00 hFFD20E

P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "S"
rep: "S=h01C3 h0000 h00 h00EFAF

P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "S"
rep: "S=h01C4 h0000 h00 h020CD3

P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "S"
rep: "S=h01C3 h0000 h00 h032DAD

P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "O 2C 3F AF BC"
rep: "P> "
cmd: "S"
rep: "S=h01C4 h0000 h00 h044E40

P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"
rep: "P> "
cmd: "O 2C 3F 80 93"


On Fri, Dec 19, 2008 at 9:05 PM, Andrew Berridge
<andrew.berridge@...> wrote:
> Actually - I'm not sure that it is a red herring. I set up a loco with
> a brand new decoder this afternoon. It worked perfectly in program
> mode, but not in command station mode. I even had it on the same track
> in the same location and switched between the two modes. This kind of
> thing doesn't seem to be entirely predictable, but I will try to
> figure out what causes the issue and when it occurs. Here are a couple
> of sets of outputs (by the way, I've not yet researched how the
> commands to the SPROG work - that might be the next thing I do..):
>
> 1) Working in program mode:
>
> cmd: ">1"
> rep: "P> "
> cmd: ">41"
> cmd: ">41"
> rep: "P> "
> rep: "P> "
> cmd: ">76"
> cmd: ">76"
> rep: "P> "
> rep: "P> "
> cmd: ">0"
> cmd: ">0"
> rep: "P> "
> rep: "P> "
> cmd: "<0"
> rep: "P> "
> cmd: "<68"
> cmd: "<68"
> rep: "P> "
> rep: "P> "
> cmd: "<0"
> cmd: "<0"
> cmd: "<0"
> rep: "P> "
> rep: "P> "
> rep: "P> "
>
> In operation mode:
>
> cmd: ">1"
> rep: "P> "
> cmd: ">41"
> cmd: ">41"
> rep: "P> "
> rep: "P> "
> cmd: ">76"
> cmd: ">76"
> rep: "P> "
> rep: "P> "
> cmd: ">0"
> cmd: ">0"
> rep: "P> "
> rep: "P> "
> cmd: "<0"
> rep: "P> "
> cmd: "<68"
> cmd: "<68"
> rep: "P> "
> rep: "P> "
> cmd: "<0"
> cmd: "<0"
> cmd: "<0"
> rep: "P> "
> rep: "P> "
> rep: "P> "
>
> Thanks for your help - I'll work on the issue too!
>
> Andrew
>
> On Fri, Dec 19, 2008 at 6:46 PM, andrew_croslanduk
> <andrewcrosland@...> wrote:
>> Andrew,
>>
>> Thanks for letting us know.
>>
>> The Yahoo spam filter doesn't like you for some reason!
>>
>> Andrew C
>>
>> --- In sprog-dcc@..., "Andrew Berridge"
>> <andrew.berridge@...> wrote:
>>>
>>> Hmmm... methinks this (at least my problem) is a red herring! Please
>>> don't worry - I think it's working fine - it's just my loco and my
>>> track. I'm still in the very early experimental stages, and I
>> couldn't
>>> get a loco to work on one track. I tried just now and everything's
>>> fine. One of my sections of track appears not to have full
>> continuity,
>>> but I've not yet soldered droppers to it. Something to do over the
>>> Christmas break!
>>>
>>> The commands going to the SPROG look entirely correct...
>>>
>>> Thanks,
>>>
>>> Andrew
>>>
>>> On Tue, Dec 16, 2008 at 6:50 PM, Andrew Berridge
>>> <andrew.berridge@...> wrote:
>>> > Hi Andrew C,
>>> >
>>> > No problem at all! I think (but can't confirm as I've not
>> investigated
>>> > it too closely) that it's the second throttle that's opened that
>>> > doesn't work.
>>> >
>>> > There's another problem with Decoder Pro in programming mode - if
>> I
>>> > try to use multiple throttles, the second one always complains
>> that
>>> > its address is in use by another throttle, and is therefore
>> unusable.
>>> > I've not investigated the Decoder Pro code yet - I want to at some
>>> > stage. I'm a software developer by trade, so it does interest me!
>>> >
>>> > I'll try and get up into the loft this evening to confirm exactly
>> what
>>> > happens, and also to capture some SPROG command logs...
>>> >
>>> > I'm currently using Decoder Pro 2.3.6 with a SPROG I
>>> >
>>> > Thanks,
>>> >
>>> > Andrew B
>>> >
>>> >
>>> > On Tue, Dec 16, 2008 at 5:33 PM, andrew_croslanduk
>>> > <andrewcrosland@...> wrote:
>>> >> Andrew,
>>> >>
>>> >> Sorry for the delay in your message. It got trapped as spam for
>> some
>>> >> reason and I didn't notice it waiting for my attention.
>>> >>
>>> >> If you try to control multiple locos in command station mode, do
>> they
>>> >> all work individually? Is it always the same one that doesn't
>> work?
>>> >>
>>> >> Andrew C
>>> >>
>>> >> PS I wrote the DecoderPro code for this feature so if there is a
>> bug
>>> >> it's in my code.
>>> >>
>>> >> --- In sprog-dcc@..., "Andrew Berridge"
>>> >>
>>> >> <andrew.berridge@> wrote:
>>> >>>
>>> >>> Hi Keith,
>>> >>>
>>> >>> It sounds more like a decoder pro problem than a SPROG problem.
>> Which
>>> >>> version of Decoder Pro are you using? I have a really odd
>> problem
>>> >> with it
>>> >>> too - it won't control more than one loco in command station
>> mode -
>>> >> nothing
>>> >>> happens with one of them - it just won't respond! Decoder pro
>>> >> doesn't crash
>>> >>> on me though...
>>> >>>
>>> >>> I need to run in programming mode and use one throttle at a
>> time.
>>> >>>
>>> >>> Andrew
>>> >>>
>>> >>> On Sun, Dec 14, 2008 at 8:47 PM, andrew_croslanduk <
>>> >>> andrewcrosland@> wrote:
>>> >>>
>>> >>> > John,
>>> >>> >
>>> >>> > What do you mean by a reboot of the power supply? Turning it
>> off and
>>> >>> > on?
>>> >>> >
>>> >>> > Does turning the track power off and on from the throttle
>> help at all?
>>> >>> >
>>> >>> > Could you open the SPROG command monitor and log the activity
>> and
>>> >>> > send it directly to me (use the contact e-mail on our web
>> page)?
>>> >>> >
>>> >>> > Regards,
>>> >>> >
>>> >>> > Andrew Crosland
>>> >>> >
>>> >>> > --- In sprog-dcc@...
>>> >> <sprog-dcc%40yahoogroups.co.uk>, "Keith
>>> >>> > Woodbridge"
>>> >>> > <keithrwoodbridge@> wrote:
>>> >>> > >
>>> >>> > > Hi All,
>>> >>> > > I have a particular problem, I wonder if anyone can help
>> please?
>>> >>> > > Whereas my Sprog II works fine in Service Mode Programming,
>> plus
>>> >>> > the
>>> >>> > > throttle routine is good. However, in Ops Mode, I can't get
>>> >>> > anything to
>>> >>> > > run using the throttle for more than about 5 seconds. After
>> that,
>>> >>> > the
>>> >>> > > loco stops, Decoder Pro freezes and a re-boot of the Sprog
>> Power
>>> >>> > Supply
>>> >>> > > is required. Because of this, I haven't even tried
>> programming in
>>> >>> > Ops
>>> >>> > > Mode.
>>> >>> > > Does anyone have the same experience as me? Incidently, I'm
>> running
>>> >>> > on
>>> >>> > > Windows XP with USB 1 if that makes a difference.
>>> >>> > > Thanks in anticipation,
>>> >>> > > regards,
>>> >>> > > Keith
>>> >>> > > Droitwich Spa
>>> >>> > >
>>> >>> >
>>> >>> >
>>> >>> >
>>> >>>
>>> >>>
>>> >>> [Non-text portions of this message have been removed]
>>> >>>
>>> >>
>>> >>
>>> >
>>>
>>
>>
>

Hi Andrew, etc...

How strange... I really don't know what's going on at all! Identical
setup in another loco works just fine. Same decoder, same setup. Just
don't know what's going on! I took another loco that wasn't working in
command station mode and played with it, and initially it didn't work.
After a bit it started to! Just don't know what's going on.

All decoders work perfectly in plain SPROG mode.

At one stage I suspected the capacitor "stay alive" I had fitted to
the decoders. One loco didn't appear to be working, so I disconnected
the stay alive, and it worked. Replaced the stay-alive and it still
worked fine! I disconnected the stay alive from a loco I have not had
working in command station mode, and it still didn't work, so I don't
think that's the problem.

A couple of thoughts:

1) Could the rapidly-repeating DCC packets cause a problem?
2) Is Decoder Pro correctly formatting the packets?
3) Is the SPROG good at generating packets when run in programming
mode, but not so good at generating them when in ops mode?

I've got the Decoder Pro code running in the Eclipse Java IDE and am
checking it carefully. Can't see anything particularly wrong with it.
However, I'm just wondering - why does it always send 3F as the second
argument?

I've just checked the packet output - it looks fine. The checksum is
correctly generated by Decoder Pro...

Hopefully this message won't be marked as spam!

Thanks,

Andrew B

---- cut

OK... Now I'm baffled... Sorry to keep mailing the list like this -
maybe that's why my e-mails are coming across as spam!

I haven't changed anything, and yet... Everything now works perfectly
in command mode!

Perhaps this is the intermittency rearing its head? If I could tell
what was going on I would suggest a cure!

I will continue to monitor, but if things just continue to work, I'll be happy.

Thanks,

Andrew B

On Sat, Dec 20, 2008 at 5:46 PM, Andrew Berridge
<andrew.berridge@...> wrote:
> Hi Andrew, etc...
>
> How strange... I really don't know what's going on at all! Identical
> setup in another loco works just fine. Same decoder, same setup. Just
> don't know what's going on! I took another loco that wasn't working in
> command station mode and played with it, and initially it didn't work.
> After a bit it started to! Just don't know what's going on.
>
> All decoders work perfectly in plain SPROG mode.
>
> At one stage I suspected the capacitor "stay alive" I had fitted to
> the decoders. One loco didn't appear to be working, so I disconnected
> the stay alive, and it worked. Replaced the stay-alive and it still
> worked fine! I disconnected the stay alive from a loco I have not had
> working in command station mode, and it still didn't work, so I don't
> think that's the problem.
>
> A couple of thoughts:
>
> 1) Could the rapidly-repeating DCC packets cause a problem?
> 2) Is Decoder Pro correctly formatting the packets?
> 3) Is the SPROG good at generating packets when run in programming
> mode, but not so good at generating them when in ops mode?
>
> I've got the Decoder Pro code running in the Eclipse Java IDE and am
> checking it carefully. Can't see anything particularly wrong with it.
> However, I'm just wondering - why does it always send 3F as the second
> argument?
>
> I've just checked the packet output - it looks fine. The checksum is
> correctly generated by Decoder Pro...
>
> Hopefully this message won't be marked as spam!
>
> Thanks,
>
> Andrew B
>
> ---- cut
>

Hi Kieth/Andrew C,

I have found the root of this issue! If you use the SPROG in
programming mode, and then immediately use it in command station mode,
it doesn't work properly. However, if (between swapping modes) you
power-cycle the SPROG, all works fine. It's an indeterminate problem,
but it always seems to affect one or more locos. Probably won't be the
one you were programming - just randomly seems to affect others...

Andrew - this appears to be a small issue with the SPROG firmware -
any ideas? It's had me stumped for quite a bit and I've spent ages
trying to figure out what's going on!

Thanks,

Andrew

On Sat, Dec 20, 2008 at 8:20 PM, Andrew Berridge
<andrew.berridge@...> wrote:
> OK... Now I'm baffled... Sorry to keep mailing the list like this -
> maybe that's why my e-mails are coming across as spam!
>
> I haven't changed anything, and yet... Everything now works perfectly
> in command mode!
>
> Perhaps this is the intermittency rearing its head? If I could tell
> what was going on I would suggest a cure!
>
> I will continue to monitor, but if things just continue to work, I'll be
happy.
>
> Thanks,
>
> Andrew B
>
> On Sat, Dec 20, 2008 at 5:46 PM, Andrew Berridge
> <andrew.berridge@...> wrote:
>> Hi Andrew, etc...
>>
>> How strange... I really don't know what's going on at all! Identical
>> setup in another loco works just fine. Same decoder, same setup. Just
>> don't know what's going on! I took another loco that wasn't working in
>> command station mode and played with it, and initially it didn't work.
>> After a bit it started to! Just don't know what's going on.
>>
>> All decoders work perfectly in plain SPROG mode.
>>
>> At one stage I suspected the capacitor "stay alive" I had fitted to
>> the decoders. One loco didn't appear to be working, so I disconnected
>> the stay alive, and it worked. Replaced the stay-alive and it still
>> worked fine! I disconnected the stay alive from a loco I have not had
>> working in command station mode, and it still didn't work, so I don't
>> think that's the problem.
>>
>> A couple of thoughts:
>>
>> 1) Could the rapidly-repeating DCC packets cause a problem?
>> 2) Is Decoder Pro correctly formatting the packets?
>> 3) Is the SPROG good at generating packets when run in programming
>> mode, but not so good at generating them when in ops mode?
>>
>> I've got the Decoder Pro code running in the Eclipse Java IDE and am
>> checking it carefully. Can't see anything particularly wrong with it.
>> However, I'm just wondering - why does it always send 3F as the second
>> argument?
>>
>> I've just checked the packet output - it looks fine. The checksum is
>> correctly generated by Decoder Pro...
>>
>> Hopefully this message won't be marked as spam!
>>
>> Thanks,
>>
>> Andrew B
>>
>> ---- cut
>>
>

Andrew,

Thanks for that. I don't have any ideas at the moment, but I'll
hopefully get time to look at it during the holidays.

Two questions. Does it only happen if you were using the throttle in
programming mode?

If so, does it make any difference if you turn off the track power
(using the LED icon in the throttle) before switching modes?

Andrew

--- In sprog-dcc@..., "Andrew Berridge"
<andrew.berridge@...> wrote:
>
> Hi Kieth/Andrew C,
>
> I have found the root of this issue! If you use the SPROG in
> programming mode, and then immediately use it in command station mode,
> it doesn't work properly. However, if (between swapping modes) you
> power-cycle the SPROG, all works fine. It's an indeterminate problem,
> but it always seems to affect one or more locos. Probably won't be the
> one you were programming - just randomly seems to affect others...
>
> Andrew - this appears to be a small issue with the SPROG firmware -
> any ideas? It's had me stumped for quite a bit and I've spent ages
> trying to figure out what's going on!
>
> Thanks,
>
> Andrew
>
> On Sat, Dec 20, 2008 at 8:20 PM, Andrew Berridge
> <andrew.berridge@...> wrote:
> > OK... Now I'm baffled... Sorry to keep mailing the list like this -
> > maybe that's why my e-mails are coming across as spam!
> >
> > I haven't changed anything, and yet... Everything now works perfectly
> > in command mode!
> >
> > Perhaps this is the intermittency rearing its head? If I could tell
> > what was going on I would suggest a cure!
> >
> > I will continue to monitor, but if things just continue to work,
I'll be happy.
> >
> > Thanks,
> >
> > Andrew B
> >
> > On Sat, Dec 20, 2008 at 5:46 PM, Andrew Berridge
> > <andrew.berridge@...> wrote:
> >> Hi Andrew, etc...
> >>
> >> How strange... I really don't know what's going on at all! Identical
> >> setup in another loco works just fine. Same decoder, same setup. Just
> >> don't know what's going on! I took another loco that wasn't
working in
> >> command station mode and played with it, and initially it didn't
work.
> >> After a bit it started to! Just don't know what's going on.
> >>
> >> All decoders work perfectly in plain SPROG mode.
> >>
> >> At one stage I suspected the capacitor "stay alive" I had fitted to
> >> the decoders. One loco didn't appear to be working, so I disconnected
> >> the stay alive, and it worked. Replaced the stay-alive and it still
> >> worked fine! I disconnected the stay alive from a loco I have not had
> >> working in command station mode, and it still didn't work, so I don't
> >> think that's the problem.
> >>
> >> A couple of thoughts:
> >>
> >> 1) Could the rapidly-repeating DCC packets cause a problem?
> >> 2) Is Decoder Pro correctly formatting the packets?
> >> 3) Is the SPROG good at generating packets when run in programming
> >> mode, but not so good at generating them when in ops mode?
> >>
> >> I've got the Decoder Pro code running in the Eclipse Java IDE and am
> >> checking it carefully. Can't see anything particularly wrong with it.
> >> However, I'm just wondering - why does it always send 3F as the
second
> >> argument?
> >>
> >> I've just checked the packet output - it looks fine. The checksum is
> >> correctly generated by Decoder Pro...
> >>
> >> Hopefully this message won't be marked as spam!
> >>
> >> Thanks,
> >>
> >> Andrew B
> >>
> >> ---- cut
> >>
> >
>

Andrew B,

Before switching to command station mode try using the throttle (in
programming mode) to release the loco you were running and select a
different address, any address other than the ones you want to use in
command station mode.

Keith has fixed his issue by removing XP service pack 3, so I think he
had a different issue.

Andrew C


--- In sprog-dcc@..., "Andrew Berridge"
<andrew.berridge@...> wrote:
>
> Hi Kieth/Andrew C,
>
> I have found the root of this issue! If you use the SPROG in
> programming mode, and then immediately use it in command station mode,
> it doesn't work properly. However, if (between swapping modes) you
> power-cycle the SPROG, all works fine. It's an indeterminate problem,
> but it always seems to affect one or more locos. Probably won't be the
> one you were programming - just randomly seems to affect others...
>
> Andrew - this appears to be a small issue with the SPROG firmware -
> any ideas? It's had me stumped for quite a bit and I've spent ages
> trying to figure out what's going on!
>
> Thanks,
>
> Andrew
>
> On Sat, Dec 20, 2008 at 8:20 PM, Andrew Berridge
> <andrew.berridge@...> wrote:
> > OK... Now I'm baffled... Sorry to keep mailing the list like this -
> > maybe that's why my e-mails are coming across as spam!
> >
> > I haven't changed anything, and yet... Everything now works perfectly
> > in command mode!
> >
> > Perhaps this is the intermittency rearing its head? If I could tell
> > what was going on I would suggest a cure!
> >
> > I will continue to monitor, but if things just continue to work,
I'll be happy.
> >
> > Thanks,
> >
> > Andrew B
> >
> > On Sat, Dec 20, 2008 at 5:46 PM, Andrew Berridge
> > <andrew.berridge@...> wrote:
> >> Hi Andrew, etc...
> >>
> >> How strange... I really don't know what's going on at all! Identical
> >> setup in another loco works just fine. Same decoder, same setup. Just
> >> don't know what's going on! I took another loco that wasn't
working in
> >> command station mode and played with it, and initially it didn't
work.
> >> After a bit it started to! Just don't know what's going on.
> >>
> >> All decoders work perfectly in plain SPROG mode.
> >>
> >> At one stage I suspected the capacitor "stay alive" I had fitted to
> >> the decoders. One loco didn't appear to be working, so I disconnected
> >> the stay alive, and it worked. Replaced the stay-alive and it still
> >> worked fine! I disconnected the stay alive from a loco I have not had
> >> working in command station mode, and it still didn't work, so I don't
> >> think that's the problem.
> >>
> >> A couple of thoughts:
> >>
> >> 1) Could the rapidly-repeating DCC packets cause a problem?
> >> 2) Is Decoder Pro correctly formatting the packets?
> >> 3) Is the SPROG good at generating packets when run in programming
> >> mode, but not so good at generating them when in ops mode?
> >>
> >> I've got the Decoder Pro code running in the Eclipse Java IDE and am
> >> checking it carefully. Can't see anything particularly wrong with it.
> >> However, I'm just wondering - why does it always send 3F as the
second
> >> argument?
> >>
> >> I've just checked the packet output - it looks fine. The checksum is
> >> correctly generated by Decoder Pro...
> >>
> >> Hopefully this message won't be marked as spam!
> >>
> >> Thanks,
> >>
> >> Andrew B
> >>
> >> ---- cut
> >>
> >
>

--- In sprog-dcc@..., "andrew_croslanduk"
<andrewcrosland@...> wrote:
>
> Andrew B,
>
> Before switching to command station mode try using the throttle (in
> programming mode) to release the loco you were running and select a
> different address, any address other than the ones you want to use
in
> command station mode.
>
> Keith has fixed his issue by removing XP service pack 3, so I think
he
> had a different issue.
>
> Andrew C
>
>
> --- In sprog-dcc@..., "Andrew Berridge"
> <andrew.berridge@> wrote:
> >
> > Hi Kieth/Andrew C,
> >
> > I have found the root of this issue! If you use the SPROG in
> > programming mode, and then immediately use it in command station
mode,
> > it doesn't work properly. However, if (between swapping modes) you
> > power-cycle the SPROG, all works fine. It's an indeterminate
problem,
> > but it always seems to affect one or more locos. Probably won't
be the
> > one you were programming - just randomly seems to affect others...
> >
> > Andrew - this appears to be a small issue with the SPROG
firmware -
> > any ideas? It's had me stumped for quite a bit and I've spent ages
> > trying to figure out what's going on!
> >
> > Thanks,
> >
> > Andrew
> >
Hi All,
Just an up-date of where I've arrived at - yes, cycling the Sprog
power supply between service mode and ops mode does seem to guarantee
a better chance of working correctly. Since just before Christmas,
I've tried the Sprog/Decoder Pro on Windows Me. Which, after some
time spent searching for an earlier version of Java to install on Me,
did actually work satisfactorily. I used the Sprog drivers from the
forum site as I couldn't get the ones on the Sprog web site to work.
However, I subsequently re-installed Windows XP up to SP2 and all
seems much happier now. I always did have some doubts about SP3 which
seemed to mess up my main PC also.
Anyway, question is, "Does anyone else have any experience of Windows
XP Service Pack 3 causing a problem with Sprog/Decoder Pro when it
had previously been OK with SP2?".
Happy New Year all,
regards,
Keith

Hi Andrew C,

OK - thanks for the info - I'll give it a go. I've not had a chance to
do any further investigation. Still using XP SP2 - however, I have a
different really strange problem with decoder pro on my main laptop
that doesn't appear on another. Full reinstalls of Java, etc. have no
effect!

A different issue entirely, and probably not relevant here, but it
means I've had to use a different machine. I won't upgrade to SP3 on
it!

Thanks,

Andrew B

On Sat, Jan 3, 2009 at 1:50 PM, Keith Woodbridge
<keithrwoodbridge@...> wrote:
> --- In sprog-dcc@..., "andrew_croslanduk"
>
> <andrewcrosland@...> wrote:
>>
>> Andrew B,
>>
>> Before switching to command station mode try using the throttle (in
>> programming mode) to release the loco you were running and select a
>> different address, any address other than the ones you want to use
> in
>> command station mode.
>>
>> Keith has fixed his issue by removing XP service pack 3, so I think
> he
>> had a different issue.
>>
>> Andrew C
>>
>>
>> --- In sprog-dcc@..., "Andrew Berridge"
>> <andrew.berridge@> wrote:
>> >
>> > Hi Kieth/Andrew C,
>> >
>> > I have found the root of this issue! If you use the SPROG in
>> > programming mode, and then immediately use it in command station
> mode,
>> > it doesn't work properly. However, if (between swapping modes) you
>> > power-cycle the SPROG, all works fine. It's an indeterminate
> problem,
>> > but it always seems to affect one or more locos. Probably won't
> be the
>> > one you were programming - just randomly seems to affect others...
>> >
>> > Andrew - this appears to be a small issue with the SPROG
> firmware -
>> > any ideas? It's had me stumped for quite a bit and I've spent ages
>> > trying to figure out what's going on!
>> >
>> > Thanks,
>> >
>> > Andrew
>> >
> Hi All,
> Just an up-date of where I've arrived at - yes, cycling the Sprog
> power supply between service mode and ops mode does seem to guarantee
> a better chance of working correctly. Since just before Christmas,
> I've tried the Sprog/Decoder Pro on Windows Me. Which, after some
> time spent searching for an earlier version of Java to install on Me,
> did actually work satisfactorily. I used the Sprog drivers from the
> forum site as I couldn't get the ones on the Sprog web site to work.
> However, I subsequently re-installed Windows XP up to SP2 and all
> seems much happier now. I always did have some doubts about SP3 which
> seemed to mess up my main PC also.
> Anyway, question is, "Does anyone else have any experience of Windows
> XP Service Pack 3 causing a problem with Sprog/Decoder Pro when it
> had previously been OK with SP2?".
> Happy New Year all,
> regards,
> Keith
>
>

If I can stick my 2penneth in, I can't get it to work as a throttle
full stop with one exception that I will come to.

As soon as I change to Command Station mode, the Throttles stop
working - i.e. the loco will not move, BUT, press F1 for sound and the
chip chirps away kicking out all the right notes.

Change back to normal mode and all works again as should, except I
still can't get any functions between 4 and 9 to do anything ? (on any
loco with functions that high, obviously!)

I am running Decoder Pro version  2.4 and Java is 1.6.0_11(en_US)
Oh, and Sprog 1 circuit board.

Any ideas ?

Regards

Andy Sollis

--- In sprog-dcc@..., "Andrew Berridge"
<andrew.berridge@...> wrote:
>
> Hi Andrew C,
>
> OK - thanks for the info - I'll give it a go. I've not had a chance to
> do any further investigation. Still using XP SP2 - however, I have a
> different really strange problem with decoder pro on my main laptop
> that doesn't appear on another. Full reinstalls of Java, etc. have no
> effect!
>
> A different issue entirely, and probably not relevant here, but it
> means I've had to use a different machine. I won't upgrade to SP3 on
> it!
>
> Thanks,
>
> Andrew B
>
> On Sat, Jan 3, 2009 at 1:50 PM, Keith Woodbridge
> <keithrwoodbridge@...> wrote:
> > --- In sprog-dcc@..., "andrew_croslanduk"
> >
> > <andrewcrosland@> wrote:
> >>
> >> Andrew B,
> >>
> >> Before switching to command station mode try using the throttle (in
> >> programming mode) to release the loco you were running and select a
> >> different address, any address other than the ones you want to use
> > in
> >> command station mode.
> >>
> >> Keith has fixed his issue by removing XP service pack 3, so I think
> > he
> >> had a different issue.
> >>
> >> Andrew C
> >>
> >>
> >> --- In sprog-dcc@..., "Andrew Berridge"
> >> <andrew.berridge@> wrote:
> >> >
> >> > Hi Kieth/Andrew C,
> >> >
> >> > I have found the root of this issue! If you use the SPROG in
> >> > programming mode, and then immediately use it in command station
> > mode,
> >> > it doesn't work properly. However, if (between swapping modes) you
> >> > power-cycle the SPROG, all works fine. It's an indeterminate
> > problem,
> >> > but it always seems to affect one or more locos. Probably won't
> > be the
> >> > one you were programming - just randomly seems to affect others...
> >> >
> >> > Andrew - this appears to be a small issue with the SPROG
> > firmware -
> >> > any ideas? It's had me stumped for quite a bit and I've spent ages
> >> > trying to figure out what's going on!
> >> >
> >> > Thanks,
> >> >
> >> > Andrew
> >> >
> > Hi All,
> > Just an up-date of where I've arrived at - yes, cycling the Sprog
> > power supply between service mode and ops mode does seem to guarantee
> > a better chance of working correctly. Since just before Christmas,
> > I've tried the Sprog/Decoder Pro on Windows Me. Which, after some
> > time spent searching for an earlier version of Java to install on Me,
> > did actually work satisfactorily. I used the Sprog drivers from the
> > forum site as I couldn't get the ones on the Sprog web site to work.
> > However, I subsequently re-installed Windows XP up to SP2 and all
> > seems much happier now. I always did have some doubts about SP3 which
> > seemed to mess up my main PC also.
> > Anyway, question is, "Does anyone else have any experience of Windows
> > XP Service Pack 3 causing a problem with Sprog/Decoder Pro when it
> > had previously been OK with SP2?".
> > Happy New Year all,
> > regards,
> > Keith
> >
> >
>

Hello everybody. I have recently put together a MERG SPROG kit and
then found this user group. While looking for some control software,
I was surprised to see that the rocrail program didn't support the
SPROG.

If you don't know about this program already, it is an open source
railway control program that is designed to be multiplatform - ie
runs on Linux, Mac and Windows. It supports a number of computer
interfaces like Lenz and Hornby etc.

I would just like people to know that I have registered with their
site and asked if it would be supported. The developers are German
and there was no mention of the SPROG on there, so I assumed they
had not heard of it.

http://forum.rocrail.net/viewtopic.php?t=615&sid=e76d5173596afa79db58128eb51afcd\
6

I have also registered with sourceforge and put in a feature request
for a SPROG library to support it.

http://sourceforge.net/tracker/?group_id=62652&atid=501349

The developer, Rob Versluis, has added the framework for the SPROG
to "svn4254".

If there was some more interest in this software, I'm sure they
would add a SPROG library to rocrail and we could use it.

--- In sprog-dcc@..., "twid1969@..." <twid1969@...> wrote:
>
> Hello everybody. I have recently put together a MERG SPROG kit and
> then found this user group. While looking for some control software,
> I was surprised to see that the rocrail program didn't support the
> SPROG.
[...]
> If there was some more interest in this software, I'm sure they
> would add a SPROG library to rocrail and we could use it.

Yes, I know about Rocrail, and agree that it looks to be a more
attractive layout control program than PanelPro (JMRI) to someone from
a UK/EU background.  It looks less good on decoder programming
(DecoderPro within JMRI).  RocRail on a small solid-state netbook plus
a Sprog is a potentially very low cost small automated layout
controller.
However, even with Gamepad support, there will remain the problem of
hardware throttles being a less than ideal user interface. Unless
there is a hardware (MERG?) project to build a USB throttle which
could be used (potentially) with both JMRI and RocRail ?


I suspect that any support in RocRail will, to an extent, be down to
whether Andrew Crosland wishes to spend time helping the RocRail team
with the Sprog interface into RocRail.

I would assume any interface would cover the old serial Sprogs, the
kit built MERG ones, and the ready-to-use USB examples.  I own the
latter.



- Nigel