Gray69

I put a stay alive in the nose of the loco behind the front grill, there is just enough room.

I removed the  8 pin connector and placed the hardwired decoder in the space left by the connector.

Thanks Nigel, I have never had anything that uses a 6 pin decoder so was unaware of the method of operation.

I get the feeling that I am missing something obvious, but I can't think of the answer.

On the Bachmann DEMU, 150 and others, the coupling bar between coaches has 2 through power connections.

I have been fitting head and tail light kits to a Bachmann class 166. To save having to add decoders to each end I wanted to run the wires required for the lighting functions through the coupling using a Viessmann 5048 coupling, which has 2 wires. It only dawned on me once I had the coupling that there are 3 wires required, the white, yellow and blue.

So how does Bachmann operate the head and tail lighting on the trailer with only 2 connectors, and is this something that can be replicated.

I am thinking of fitting a HM7000 to my VEP. Is the sound profile available for it yet.

I hope Hornby sell the interiors for the DTC, as it could replace the ones they fouled up in the NSE version with it's solid compartment wall.

The conversation was that if there is a short on the layout that took a little time to find, if all the stay alives in the coaches and locos had been drained when the power came back on, all the current draw to recharge them would then trip the power again because of an excessive power draw.

They did say that it was mainly an issue that only really affected large layouts with long rakes of coaches, but did say that if the current trend to fit big stay alives to locomotives and rolling stock was to continue, it could cause issues on smaller layouts in the future.

Accurascale were been talked about because they had these issues when running their 37, 50, 66 and 92 locos, as well as the Mk2 and Mk5 coaches.

It was not them having a go at Accurascale, it was a discussion about the issues stay alives can cause if you have a large fleet of locos and coaches fitted with them.

I found it a very interesting and informative discussion.

I also think the prices you are charging for the Irish units are fair, and I would be willing to pay similar amounts for 455, 456, 319, SR EPB, CIG, BIG and 377 models. Also a decent 3 car 101 and 119 would be nice 😉

As for how many

455, 456, 319 and CIG in NSE, Connex and Southern. Thats 12 units to start with

2 hours ago, flockandroll said:

So I have the knowledge to change CV1 to a short address, and the knowledge to rename the loco in the app. 

Not sure if it will continue to irritate me that for instance CV1 = 66 and the name is 667, 

and CV1 = 78 and the name is 7818

 

It is easiest to use the '# Program address' setting in the CV programming section of the Z21 app to change the CV. With this you can choose 667 and 7818 without issues. Don't worry about CV1

1 hour ago, Nigelcliffe said:

 

1 - stop overthinking this stuff.    The Z21 sorts out the "loco address" and use that.   Stop worrying about CVs.

 

2 -  Addressing.    There are three types of address in a DCC decoder that people will typically encounter;  short address,  long address and Consist Address.    

a)   Short address.   Takes values from 1 to 127,  though some systems will only allow 1-99.    This is stored in CV1.  

b)   Long address.   Takes values from 1 to 10,239.   But the allowed values in systems varies, it might be 1-9999 or 100-9999 or 128-9983, or (pick different range of choice).  The values are stored across CV17 and CV18, using a moderately awkward calculation method (or easy method if you're good at binary maths!).  

c)   The decision inside a decoder to respond to the Long or Short address is set in CV29,  along with lots of other things also set in CV29.  

d)   If using an "Advanced Consist" (double/multiple heading method, and one of several ways of arranging double-heading), then the Consist Address is stored in CV19.  If CV19 is not zero, the Consist Address applies, and the loco responds to that, rather than its locomotive address.  Consist address is 1-127,  adding 128 to the address means the loco runs backwards (eg. two class 20's running nose-to-nose, one needs to run backwards to the other).    There are a few decoders which support long addresses in Consists, stored in a combination of CV19 and CV20, but this is a very small niche at present.   

 

3)  From the permitted addresses in various systems, there are certain loco addresses which should be avoided if wanting to move locos from one system to another.  Addresses 100-127 might be "long" or "short" depending on system, so best avoided.    Long addresses 0001-0099 are likely to confuse, so avoid those if your system allows them as long addresses.     And Long addresses above 9983 might not work on some systems.    

 

Tools for calculating CV29 and CV17/CV18 are on the webpage I wrote a dozen years ago:   https://www.2mm.org.uk/articles/cv29 calculator.htm

 

 

 

When you are new to DCC, it can be overwhelming

In the OP, it seemed that flockandroll was initially confused by the fact that after they had programmed a long address into the decoder, then when reading CV1, they got an address of 3. This was obviously not what they were expecting. This then starts a rabbit hole of confusion into long and short addresses

If you are new to DCC, thinking CV1 will give you the loco address is an easy mistake to make.

I know that programming DCC can be as simple or as difficult as you make it 😀

but thank you for the explanation, as I like to be able to understand how it works

On 03/01/2024 at 13:41, flockandroll said:

I am new to DCC, this could be my second newbie error. I wanted to change the loco address from the default 3' to the actual (builder's) number of the loco, 3716.

Watching a couple of YouTube videos, I went into the vehicles part of the phone app, added the loco and picture, changed its number to 3716. But now in steering, no function keys are displayed, just speed and direction and a picture, on the right. The left side of the screen where the functions used to be displayed is now blank.

So I thought,  "Oh, I need to reprogram the decoder on the program track. So switch over the connector on the back of the Z21, put the loco back on the track, read CV1 and it is set to 3. So I change it, I wanted 3716, but I settle for 37 for now, as 3716 is a long address, and sticking to a short address is easier for now. Reread the CV, and yes, CV1 is now 37.

Back to vehicles, basic information and change loco address fro 3716 to 37.

Loco off track. Change over green plug to main track loco back on track. Select loco in steering, still no function keys visible.   

I can control speed and direction, but no functions (that is to say, firebox flicker and sounds). I have added loco to the WLANmaus, and I can control the speed and direction only. Before I started changing the address, I could control sounds and turn firebox flicker on and off. The loco is a Rapido Hunslet 16in Alex with factory fitted sound decoder.

 

How can I get the functions back please?

 

 

As this question threw up a couple of queries in my mind, I thought I would look at my settings. I then got really confused over what CV1 shows.

I always change a loco CV with the '# Program address' setting in the CV programming section of the Z21 app. I always use a long address as I find it easier. Checking CV1 on a loco that had a long address showed a result of 3. After having a play with the address, it appears to me that CV1 only shows the correct address if you use a short address. If you then change your short address to a long address, CV1 seems to read whatever the last short address was. Hopefully an expert will come along soon an explain this.

Using short or long address doesn't really seem to matter, just use an address that you will remember.

When you setup a loco in the WLANmaus with an address of say 3716, when you operate the controls, it will just send the command to any loco with that address. The functions are not stored on the WLANmaus, so when you press a function key, all it does is send the signal to the decoder to operate that function.

On 03/01/2024 at 17:27, jaym481 said:

If you added the functions under one address they won't transfer to the new address when you change it. You have to manually add them again. It's one aspect of the Z21 that I wish could be managed better.

You don't need to manually add them again.

Once you have set up a loco with functions and pictures etc, If you change the address of a loco, you can simply change the 'Loco address' in the Vehicles page to whatever the new address is. It keeps all the other settings.

5 hours ago, adb968008 said:

One of the pictures in those samples is the old NSE release , not stagecoach… 

 

 

url kink from Hornbys website.

now i’m seeing it painted i’m not sure what I think about blacked out compartment windows ?

 

I don't know what the model in NSE livery is, but the original model has the motor at the other end of the coach, not at the brake van end.

3 hours ago, PieGuyRob said:

Has anyone else seen Sam's Trains review of these wagons? Ok, I don't own any yet, but, I wasn't happy with his review. I tend to buy stuff he gives a bad review to. Are the points he raises true?

So you won't be buying any of these then. He is very positive about the wagon

1 hour ago, McC said:

 

Indeed over 100 positive reviews from real customers https://www.accurascale.com/en-eu/collections/fna-d-new-generation-nuclear-flask-carrier

There is nothing in Sam's video that is not mentioned in the real customer reviews.

Short of sending the decoder back to Zimo, they advised me that there was nothing else that could be done to update the decoder.

On 21/06/2023 at 17:15, SteveM666 said:

Run an autocalibrate routine on CV149, that will programme the decoder to ‘match’ your motor. Also, turn the volume slide down, it may help.

Thanks for the info on CV149

Stage 1 made no difference. Tinkering with CV150-152 in stage 2 made it a little better, and I did not understand stage 3 at all so I gave up.

The only way to make the sound better on the 73 is to turn it off.

1 hour ago, meatloaf said:

The class 73 im having trouble with. Updated the decoder to begin with. Failed first time but was fine 2nd time. The 73 sound profile has so far installed twice, but getting no sound or movement. Takes a good deal longer to install as well. Now trying for a 3rd time but with the power bank removed. The decoder does work as i quickly checked it before linking it to the app and it chuffed away merrily.

 

EDIT :  Failed again. So then ive decided to try a different profile as im sure ive read somewhere that the 73 profile is problematic. Tried the deltic and the and the 08 sound and both installed first time. I do however seem to have a broken speaker as its all crackly and the sound breaks up.

 

Just left it installing the 73 profile for the 4th time. EDIT : .... And failed for a 4th time!

The 73 sound file took nearly 3 times longer to download than anything else I tried. Is the phone staying on and connected the whole time, as on one attempt I made, the phone went into standby and interrupted the download.

I would not bother with the 73 as it doesn't sound anything like it. The engine idle sound will drive you potty very quickly as it seems like a very short sound clip on continuous repeat. Under acceleration, it doesn't give the distinctive thumping noise, just a whining noise and the horn options don't give you the basic 2 tone, instead you get a stupid attempt at a tune.

I replaced a Zimo MX600 in a Hornby 73 with the 8 pin HM7000 sound decoder, and after waiting for the Android app, I really wish I hadn't bothered.

The loco has turned from smooth and quiet to jerky and loud.

The quality of the sounds are a joke. I am really wondering if a 73 was recorded as it doesn't sound anything like one

I know it is half the price of a Zimo or ESU, but it is definitely not value for money.

I haven't been that impressed by the service from West Hill Wagon Works. I purchased a few packs of couplings from them on eBay and a number of them broke when fitting them. When I contacted them I got a reply asking what had broken. I replied telling them and that is the last I heard. All other communication has gone unanswered.

On 18/05/2023 at 21:12, RFS said:

 

I have an MX623R decoder and flashed it to level 40.2 only last week using the Z21 Maintenance Tool on my PC.

 

One thing I have found is that the update process seems to be very sensitive. I originally had a siding on the layout switchable between normal operation and Z21 programming track. But the update of firmware this way was very hit and miss. In the end had to have a dedicated piece of track very close to the Z21. 

Was it the latest version, 40.20 that you updated to, or just updated to an older version 40.2

23 minutes ago, Vecchio said:

Just one timid question - what is the change in the software of the MX623? is it essential? 

I have a couple of these decoders which work fine, so I do not see the reason for an update. 

 

Best regards

 

Vecchio

 

(Vecchio uses mainly Zimo decoders, owns MXTAPS and MXULFA, control is Z21)

The decoder seems to work fine, but the issue points to the fact that there is something not right with it.

Whether it is a hardware or software issue, it could cause a premature failure and possibly cause damage to the loco it is in.

I wish to add my thanks to the Alton Model Centre.

They were very helpful in trying to sort out an issue with a Zimo decoder. The added bonus was a ride on the Mid Hants Railway whilst they were working on the decoder.

The decoder has now been on 3 different MXULFA at 3 different locations including 2 Zimo dealers, so I think track/power/etc can be ruled out. It has been run on track and on the Zimo MXTAP

When run, the procedure recommended by Zimo showed that the update had finished against a nice green background. Sadly, it had not updated the firmware.

I will contact Zimo again to see if they have any more ideas, or whether it is a case of sending it back to them to look at.

I have heard back from Zimo.

They advise that I use the Zimo Firmware Flasher program from a PC connected to the MXULFA. The drivers needed to connect it to a PC are in the 'USBFlash drive software' file and the latest version of the ZSP package, which contains the firmware flashing program are both on the website 

When you run the Zimo Firmware Flasher Program you should make a check mark at programming without any acknowledgement to force the update.

WARNING, I have spoken to somebody who said that this could brick the decoder, so run at your own risk,

On 21/05/2023 at 17:22, grimbo007 said:

how did you contact Zimo i have sent emails but no reply any help would be appreciated, and what did they tell you you can do with the MXULFA to hopefully update the decoder.

thanks

I used this address, and got a very prompt reply.

service@zimo.at

I will contact them again to find out the procedure.

13 hours ago, Lemmy282 said:

Which is where I came in. I have the MXULFA and it wont update MX623's. In the end I gave up with my attempts.

 

Nigel L

It is worth contacting Zimo, as they told me there is something else you can do with the MXULFA to hopefully update the decoder.

It is worth also downloading the latest  40.20 firmware package again from the website. There was apparently an issue with it and it was rereleased at the beginning of May.