Jump to content
 

Smasher2009

Members
  • Posts

    12
  • Joined

  • Last visited

Smasher2009's Achievements

4

Reputation

  1. Hi Have you looked on YouTube there is a video by Rudysmodelrailway 03 for how to connect the DR5000 to the Z21 app. It’s what I used to get connected. Rudy has done 5 videos on how to set up the controller and are quite useful. Dave
  2. Hi In the DR5000 software before you load up TC if you drive a train over the block does the detect go active. So in the Loconet T section there are all the detection addresses, and as the train crosses the block a little tick should appear. I have the first address set as 130 for example. Then In TC I assume you have the DCC system connected via loconet via the usb and com port as you can drive the train. In the block you have drawn add a sensor and in the sensor properties select the loconet system with the single address, I think it’s the last on the list, there you add the address, so for me it’s 130. Hit ok and that should be it. If you’re still not sure I’ll try to add some pictures when I’m back. D
  3. I’ve had a test with a DR4088LN and DR4088 and they do work with Traincontroller using the two controller technique, Loconet on com 6 and XpressNet on com 7. I had to program the DR4088LN using the button on the side and selecting a point for the first address as per the instruction, I did say there were 32 detectors as I’ve got 2 on the loconet, I’m not sure if this is right. I did find that in the DR5000 software I had to go into the S88 section to set the detection to momentary, there are options for latching etc. But I didn’t set the address in the S88 section, this had me foxed for a while and made the loconet section show error. Once fixed in the loconet section of the software I could see the detection when I connected the common to #1. In TC I added a simple detector and in the properties selected loconet as Uhlenbrock single address, as the rest needed address and detector. Put in the single address for #1 and when connected again the detector in TC turned red. It took me about 20mins of experimenting but it looks like it’s working. Hope this helps.
  4. Hi, I’ve just migrated my Lenz system to a DR5000 v1.5 using the Expressnet connection through the usb to Traincontroller v9. After a bit of trial and error and a bit of help from DR I’ve got it working. I thought I’d share how it was done as I’ve not found it anywhere so far. I have a LV101, LZ100, LV102 and LH100, first mistake was I needed an DR5039 in order to connect the CDE outputs from the Lenz system to the DR5000. Once bought the LH100 could connect to the Expressnet connector on the DR5000, and I could drive the trains on the track. Once the DR5000 was connected to the laptop using win8 it was registered as com4 ok. In Traincontroller I connected to the Expressnet through a Lenz USB as com 7. In the DR5000 I’d enabled the tick for Expressnet. Next up all the points were firing the wrong way, in the DR5000 config again in Expressnet there is a tick box to reverse the point directions. I didn’t tick any other boxes. For detection I use Lenz LR101’s and LDT units via the RS bus, this was wired into the DR5000, and in the config for the RS connection I ticked the “enable RS bus scanning” and “LDT timing” and “report all contacts after power on” Now the interesting part, I have a first feedback module at 39, and Traincontroller was showing empty blocks as occupied, after a bit of fiddling with a single test block I found that on the RS setting in the DR5000 the “first contact in feed-back space” was default to 64. I set this to 0 and suddenly everything worked. It took me ages to twig this. I’ve found that the DR5000 is a bit more sensitive to noise in the RS cabling but this was resolved by splitting out the LDT’s from the LR101’s and running in new cables. I also changed as many joints as I could to solder joints. So far after half an hour of running all’s well, I’ve not got the Ethernet connection going yet but I think that’s a pc issue and can wait for another day! I hope this helps anyone who has the same issues.
  5. Yes it's jet A just for RR, in the past there used to be two trains a week, but now things have got a lot more efficient.
  6. No, that wasn't me, I came to investigate on my bike while you were waiting to get through the gate to get the tanks.
  7. I thought it was unusual to see one of you guys on the phone next to the engine this dinner.
  8. Are the timings for sinfin about the same as the 56 is usually waiting to get into the fuel farm about half 12, which is good for me as it's lunch? By the way top pictures.
  9. Cracking pictures. I came and had a look at dinner while you were parked up waiting to collect the tanks. Where you stopped meant a decent view of the engine for a change, last week it was hiding down the line in the trees.
×
×
  • Create New...