sunrunner4kr

I accidentally touched 2 connections together on a Viessmann 4414 while moving the decoder box, and now the green LED is permanently on XD Has anyone don’t something similar before, and know if it’s fixable?

I had the same thinking. But Z21 doesn’t have a warning/distance signal object. I set the DR4018 to be address 80 - so in theory 80-88 So instead, I added a simple on/off signal...and yes, the main signal switches red and green at address 80 I then added a 3 aspect signal, and set to 82 & 83, which I’m assuming correspond to OUT3 & OUT4 and the lights aren’t changing at all.

Hi all, couldn’t find a topic in the forum already that helps my current predicament. Hoping someone out there has some experience with connecting signals to DR4018 units. I’m worried my wiring is incorrect, as I’m not getting the required behaviour. I have a Z21 system (with the beginnings of iTrain control). I have a DR4018 to control one DB Main Signal with Distance signal from Viessmann 4414 Based on a thread from another forum: - https://www.1zu160.net/scripte/forum/forum_show.php?id=1098276 I’ve programmed the DR4018 to CV47 value of preset 8 for DB Main Signal, and then programmed the the first two signal groups separately, CV131 (1-4) as value 2 DB_HP, and CV132 (5-8) as value 4 DB_VR. My understanding is that the whole DR4018 has to be set to one CV47 preset. But having the CV132 set to DB_VR treats it as a Distance signal for the Main signal. I’ve attached a diagram of my wiring. I’ve connected both Main Signal wires up to the first Output, and then both sets of green and yellow for the distance signal for outputs 3 and 4. Both signals share a diode to the common connection. I’m hoping there’s something obvious straight away t everyone, and I’m being stupid. I’m struggling to get iTrain to control the lights correctly, and I want to rule out my wiring before I get stuck in iTrain troubleshooting. Thanks in advance for any help!

Great to know I can mix it up a little :)

Yeah....I'm now considering itrain Vs Train Controller XD

So, here’s my setup so far. It’s all working as planned. Loco shows in any block on the layout with that block address. So...the only bit I don’t like, is that for a stretch of rail, you can either: - Show one piece of that track with the block occupancy Show the occupancy at the beginning and end of that block section Or, have the occupancy object on every section of that length of track That latter option means you can see for any section of horizontal/vertical track what is occupying it. However, it’s a lot more work to set up! AND for a section of track, would show the loco image several times... Seems a bit clunky to me. Would be better if the app let you set the beginning and end of a block section, and then it highlights all that track with occupancy. The app, also doesn’t let you add the occupancy object diagonally...which is really stupid. So you have to manipulate the layout to be horizontal or vertical when you want to show track occupancy...

I just found this useful link. So will give it a try. http://adventuresinzscale.blogspot.com/2018/02/setting-railcom-feedback-inside-of-z21.html?m=1

Hi all, Has anyone got any experience setting up track occupancy using the Z21 app? There’s a ‘response module’ object in the app layout, but I’m unsure how to use it. Do I need one of these objects for each block? Or need it instead of all track on the layout where there is block detection? Or at the beginning and end of a block? I couldn’t find any guidance from the Z21 manual or their online video tutorials. I’m using a DR5088RC digidetect. Thanks in advance for any help! Simon

Thanks David! Will check it out

oooh that's really useful, thanks. I was struggling on the Google searches trying to work out what coach versions they had

Ah nice! I have similar express coaches at the moment, and focusing on DB Baureihe 23 too. Aiming around 1950/60s

Hi all Anyone running a DB/DRG Class 23? I'm looking for inspiration for coaches to run with this engine, which epoch (assuming III), any specific lines/services. Any regional differences etc... Thanks all! Simon

I had to sleep on it. I moved the cabling over to use the decoder frog control. And now everything works perfectly. Both points and both frogs. So now I have one I've the motors controlling a frog, and he decoder controlling the other. Maybe it's just a faulty motor. But from now on, think I'll just use the decoder frogs for peace of mind. Thanks everyone for all your kind help!!

So, I've switched over the cables now on the RH point as well, for the LH frog. The frog is now, no longer switching polarity. Maybe this was the problem all along...and why I was getting so confused. LH point, controlling RH frog is fully working now I've switched cables. Wonder if anything else could be wrong... Before I rip it out and assume the point motor is dud.. Guess I could try switching the frog on the decoder instead as suggested.

Right.... It's because the frog on the left is now out of sync. Z21 app matching physical config. But frog is wrong polarity...

Did a bit more testing. I'm not sure there is continuity, but the multimeter was making a strange pulsating noise when connecting any of the other rails to the bottom rail. In any configuration. It seems to come and go. Sometimes it's doing it all the time. Sometimes nothing. I wonder if it's a loose cable or something

Wow, thanks for all the help!! I've swapped the black and red cables over and that point and frog are now correct! I'm getting successful movement in every direction now but one. The plot thickens... Now I'm getting continuity over my top and bottom rail, when I am directing bottom left to bottom right. Which seems strange. So now, in this configuration, basically everything is red :/ both outside rails and the frogs. The frogs are correct as they are now effectively the top rail in this configuration. But why the bottom rail has continuity when it's wired separately to black and works as black in the other configurations....

@mikeg I'm using two turnouts back to front in the app btw, not the double switch unit

Thanks both. @mikeg do you mean y points in the app? @Ray H sorry, it was hard to explain. The frog polarity is wrong every time I throw it. Always the opposite it needs to be. Like it's back to front. And like I tried to explain, in the Z21 app it makes sense. The polarity and direction matches what it should be. It's just that physically it's pointing the opposite direction. If I change the Z21 app switch to match the way it's pointing physically, then the app always matches physically. But the polarity is then always wrong, alternating to the opposite of what it should be.

Hi all, I have a Peco code 55 double switch wired up. I'm having problems with one of the frog polarities and hoping someone could help! I have a Z21 setup, with PM1 motors connected to ads2sx. All rails connecting to double slip are insulated. My right point (wired to left frog) is working fine, which when I set in Z1, switches and sets the opposing frog polarity correctly. My left point (wired to right frog) when set in Z21, is switching and setting the opposing frog polarity correctly in line with what Z21 thinks it is, but physically it's set to the wrong direction. I've tried swapping the signal on Z1 for the point, so physically it matches the Z1, but then polarity of the frog is wrong. I've tried switching the connectors to the ads2sx around, and still the same problem. I've tried manually moving the point, but it just remembers and sets it wrong again. It's really frustrating, as i'm sure there must be something wired wrong, but i've wired it the same as the opposing motor/frog which is working correctly. So, in the picture below when for the configuration when the tracks should be directed top left, to top right. I've highlighted what polarity the tracks are when physically it is set to move the engine in the yellow highlighted direction. On the Z21, when the app is set to the picture on the left, the polarity is correct, but physically it's pointing bottom right. And when the app is set to the picture on the right, it's physically correct, but polarity the opposite. Any help much appreciated! Thanks Simon

That's great to know! Thank you

Ok...I was being an absolute buffoon. In all my troubleshooting and re-wiring, I re-wired the solenoid to the LED connectors, not the solenoid connectors... It's now working. Thanks for the help!! And yes, I'm equally dissatisfied with the wiring. The decoder has really small connectors, that the 30/0.2 wiring will not fit in! Although following advice, I'm using the 30/0.2 wiring for the solenoids. The decoder manual also suggests NOT to tin the wiring etc...so I'm unsure if using some form of fixed connector for the wiring would be better

Hello everyone, I'm hoping someone can give me some advice on troubleshooting my seep motor problem. I have a Z21, with a Digikeijs booster powering a DCC bus. I have an ADS4SX decoder connected, and powered by this bus. I then have a Gaugemaster PM1 seep motor wired up to the decoder 30/0.2; wired to my track DCC bus for power 16/0.2; and frog wired to point frog 30/0.2. I've used the ADS4SX decoder Set option and the Z21 to program the turnout. When I select the turnout in the Z21 app, I can hear the ADS4SX click, but the motor doesn't budge. I tried switching the bus wiring on the PM1 from A to B, and no change. I also enabled the Z21 addressing setting for the address offset. Does anyone have any ideas what could be wrong, or how I can troubleshoot where the problem could be? Oh, the ADS4SX also makes quite a bit of a hummin noise. I assume that is normal with all the capacitors. Many thanks in advance Simon