QSI knowledge?

[Johnreese]

I have a Walthers Proto E8 loco with QSI decoder and speakers. I have it programmed on JMRI and went to "reset" the decoder to
factory settings, but am finding I don't know how to control the basic speed. I get a reading saying "programmer
error" and it is "speaking with my controller (360)" What does that mean? Anyone?
JRP

 

[TheXModelRailroader]

I don't know much about DCC, but here is some tips Copilot (a Ai engine) gave...Best of luck.

Quick Answer: The “programmer error” message combined with “speaking with my controller (360)” is JMRI telling you that the QSI decoder is using its verbal feedback feature (literally speaking through the loco’s speaker) while JMRI is trying to program it. This “talk-back” can confuse JMRI’s programmer, leading to error messages. It doesn’t mean the decoder is broken—it’s just how QSI decoders behave when reset and reprogrammed.

What’s Happening​

• QSI “Talk Back” Feature: QSI decoders are unique in that they announce CV changes and programming feedback audibly. When you reset the decoder, it often says things like “reset complete” or “controller 360.” JMRI interprets this as unusual feedback and throws a “programmer error”.
• JMRI Error Codes: JMRI’s “programmer error” usually means the command station is busy or doesn’t understand the request. In your case, the audible feedback from the QSI decoder is interfering with JMRI’s normal CV read/write process.
• Factory Reset Effect: After a reset, QSI decoders often revert to default speed tables and CVs. That’s why you’re finding it hard to control basic speed—the decoder is back to its default motor control settings, which may feel different than what you had programmed before.

How to Fix or Work Around It​

• Use Ops Mode (Programming on the Main): QSI decoders often behave better when programmed in Ops Mode rather than on the service track. This avoids some of the “programmer error” issues.
• Disable Verbal Feedback Temporarily: Some QSI decoders allow you to turn off the “talk-back” feature via CV settings. Doing so can make JMRI programming smoother.
• Check Electrical Contact: Ensure the loco is making solid contact on the programming track. Poor contact can also trigger “programmer error” messages.
• Reprogram Speed CVs: After reset, you’ll need to re-enter your preferred speed settings. Start with CV2 (start voltage), CV5 (top voltage), and CV6 (mid voltage). These control the basic speed curve.

Practical Next Steps​

1. Put the loco on the programming track and confirm it responds after reset.
2. Try programming CV2, CV5, and CV6 in Ops Mode.
3. If JMRI still throws errors, consider disabling the QSI verbal feedback (check your decoder manual for the CV that controls this).
4. Once basic speed control is restored, you can fine-tune momentum and speed tables again.

In short: Your E8 isn’t broken—the “speaking with my controller (360)” is just the QSI decoder’s quirky way of acknowledging commands. JMRI interprets that as an error, but you can bypass it by using Ops Mode and reprogramming your speed CVs.

Would you like me to walk you step-by-step through setting CV2, CV5, and CV6 on your QSI decoder in JMRI so you can get the loco running smoothly again?

 

[Johnreese]

I don't know much about DCC, but here is some tips Copilot (a Ai engine) gave...Best of luck.

Quick Answer: The “programmer error” message combined with “speaking with my controller (360)” is JMRI telling you that the QSI decoder is using its verbal feedback feature (literally speaking through the loco’s speaker) while JMRI is trying to program it. This “talk-back” can confuse JMRI’s programmer, leading to error messages. It doesn’t mean the decoder is broken—it’s just how QSI decoders behave when reset and reprogrammed.

What’s Happening​

• QSI “Talk Back” Feature: QSI decoders are unique in that they announce CV changes and programming feedback audibly. When you reset the decoder, it often says things like “reset complete” or “controller 360.” JMRI interprets this as unusual feedback and throws a “programmer error”.
• JMRI Error Codes: JMRI’s “programmer error” usually means the command station is busy or doesn’t understand the request. In your case, the audible feedback from the QSI decoder is interfering with JMRI’s normal CV read/write process.
• Factory Reset Effect: After a reset, QSI decoders often revert to default speed tables and CVs. That’s why you’re finding it hard to control basic speed—the decoder is back to its default motor control settings, which may feel different than what you had programmed before.

How to Fix or Work Around It​

• Use Ops Mode (Programming on the Main): QSI decoders often behave better when programmed in Ops Mode rather than on the service track. This avoids some of the “programmer error” issues.
• Disable Verbal Feedback Temporarily: Some QSI decoders allow you to turn off the “talk-back” feature via CV settings. Doing so can make JMRI programming smoother.
• Check Electrical Contact: Ensure the loco is making solid contact on the programming track. Poor contact can also trigger “programmer error” messages.
• Reprogram Speed CVs: After reset, you’ll need to re-enter your preferred speed settings. Start with CV2 (start voltage), CV5 (top voltage), and CV6 (mid voltage). These control the basic speed curve.

Practical Next Steps​

1. Put the loco on the programming track and confirm it responds after reset.
2. Try programming CV2, CV5, and CV6 in Ops Mode.
3. If JMRI still throws errors, consider disabling the QSI verbal feedback (check your decoder manual for the CV that controls this).
4. Once basic speed control is restored, you can fine-tune momentum and speed tables again.

In short: Your E8 isn’t broken—the “speaking with my controller (360)” is just the QSI decoder’s quirky way of acknowledging commands. JMRI interprets that as an error, but you can bypass it by using Ops Mode and reprogramming your speed CVs.

Would you like me to walk you step-by-step through setting CV2, CV5, and CV6 on your QSI decoder in JMRI so you can get the loco running smoothly again?

es, I would appreciate it if you could walk me thru setting CV2, 5, and 6 on my QSI decoder using JMRI.

Thank you.

JRP

 

[TheXModelRailroader]

Yes, I would appreciate it if you could walk me thru setting CV2, 5, and 6 on my QSI decoder using JMRI.

Thank you.

JRP

That wasn't me actually.
Ai will always have more info like that. You can go to https://copilot.microsoft.com/ yourself and ask the first question, that way it can walk you through it all. But here is the further response it gave me after your next question.
If you need more help I can keep forwarding your questions for you. Just let me know.

Copilot Ai: Perfect — let’s walk through this step by step so you can get your Walthers Proto E8 with the QSI decoder running smoothly again. We’ll focus on the three key CVs that control basic speed:

• CV2 (Start Voltage): Determines how much voltage is applied when you first crack the throttle open.
• CV5 (Top Voltage): Sets the maximum speed.
• CV6 (Mid Voltage): Defines the midpoint of the speed curve, shaping how the loco accelerates between start and top speed.

Step-by-Step in JMRI​

1. Open JMRI DecoderPro​

• Launch DecoderPro and select your E8 locomotive from your roster.
• Make sure the loco is on powered track (preferably the main track if service track programming is giving errors).

2. Switch to Ops Mode (Programming on the Main)​

• In the Programmer window, look for the option to program in Ops Mode.
• This avoids the “programmer error” issue you saw earlier because QSI decoders often don’t play nicely with service track programming.

3. Locate the CVs​

• In the programmer tabs, go to Motor Control or Basic Speed Control (the exact tab name depends on your JMRI version).
• You should see fields for Start Voltage (CV2), Mid Voltage (CV6), and Top Voltage (CV5).

4. Enter Values​

Here’s a good baseline to start with:

• CV2 (Start Voltage): Try 2 or 3. This ensures the loco moves at speed step 1 without stalling.
• CV6 (Mid Voltage): Try 15. This gives a smooth ramp-up in the middle of the throttle.
• CV5 (Top Voltage): Try 30. This caps the loco’s top speed at a realistic level.

(Note: QSI decoders often use a wider CV range than some other brands, so you may need to experiment. The idea is to balance smooth starts with a realistic top speed.)

5. Write the CVs​

• Click Write Changes on Sheet (or Write CVs) in JMRI.
• The loco may “talk back” (literally announce the change). That’s normal for QSI.
• If you get a programmer error, don’t worry — as long as the loco responds on the track, the CVs are likely written.

6. Test on the Track​

• Put the loco on the mainline and slowly advance the throttle.
• Check that it starts smoothly, accelerates evenly, and doesn’t rocket unrealistically at full throttle.
• If it feels off, adjust CV2, CV5, and CV6 again until you’re happy.

Fine-Tuning Tips​

• If the loco still hesitates at startup → raise CV2 slightly.
• If mid-speed feels sluggish → increase CV6.
• If top speed is too fast → lower CV5.
• Once you’re happy, you can explore momentum (CV3 acceleration, CV4 deceleration) for more realistic operation.