Dinamo

Posted by Frans Staal on 2017-03-03 13:08

Hallo Ulrich,

wir haben schon per E-Mail kommuniziert. Mein Vorschlag zum testen: kannst du mal die zwei TM44 einzeln ausprobieren. Also alle DIP-Schalter auf ON und dann nur eine TM44 mit dem RM-C verbinden. Was siehst du dann in DinamoConfig. Wenn wir dann wissen dass die beide Modulen an sich gut funktionieren, dann machst du die Verbindung und probierst ob die beide funktionieren.

Grusse
Frans

Posted by Leon van Perlo on 2017-03-03 14:24

Ulrich,

Have you disabled the RS485 terminators on all modules except the last TM44?
So remove the terminator jumpers on the OC32's
Switches 7&8 on all TM44's OFF except the last TM44 on the bus 7&8 ON

Best regards,
Leon

Posted by Ulrich on 2017-03-03 14:35

Hallo Frans,

leider zeigt sich das gleiche Problem auch beim Austausch des zweiten TM44-Moduls.
Die angeschlossenen Blöcke an der zweiten TM44 haben in allen Fällen Null V Spannung.

Nun habe ich das Ersatzmodul TM44 an die erste Stelle gesetzt. Dort arbeitet es normal wie das ursprünglich erste Modul!
Also liegt es offenbar nicht an den Modulen selbst. Habe außerdem alle RJ45 LAN-Kabel nochmal ausgetauscht. Dies hat aber keine Änderung gebracht. Also an den Datenkabeln liegt es offenbar auch nicht.

Was kann die Ursache sein ?

LG Ulrich

Posted by Leon van Perlo on 2017-03-03 16:02

Ulrich,

Ok, terminator settings should be ok then.
On the TM44 there is no jumper for terminator. That's done through switches 7&8. On the OC32 it's a jumper. Switch or jumper, technically is identical. It's a short or open circuit.

When you add TM44 or OC32 modules, do you reboot the RM-C, e.g. by pressing the reset switch?

Could you make a photo of your installation (wiring)?

Leon

Posted by Leon van Perlo on 2017-03-03 18:06

Ulrich,

When the RM-C starts, it will start to scan the network to find what's out there. This will take about 15 seconds, depending on the size of your system. The more modules, the faster it will go. When the RM-C has discovered how the world looks today, it will start working with that environment.

If you add something to the network, the RM-C won't see that. It knows how the world looks and that's it. When you remove a module, the RM-C will keep trying to communicate with that module, however it will automatically lower the retry-frequency in order not to disturb the throughput to the other modules.

You can see it when getting the status with DinamoConfig:

• Not Found = There is no such module found when started
• Active = Module found and communicating
• Idle = The module was there when the network was scanned, but now it's gone.
• Fault = Communicating, but the module is in Fault state

Fault: When a module that controls traffic (TM-H, TM44, UCCI, RM-x) looses communication with it's "host" (so when a TM44 looses communication with an RM-C of when the RM-C looses communication with the PC) it will automatically stop all traffic it controls and issue "Fault". It's a safety measure. The "host" has to actively reset the fault to be sure that the cause for the fault has been solved. In DinamoConfig you can simply do that by pressing "Reset Fault". There can be other causes for a Fault state (internal buffer overflows, system hardware failure, etc), but usually "Fault" is nothing severe. It just means that the system is in a kind of safety halt state.

There are 2 ways to force the RM-C to rediscover the world:

1. Reset the RM-C module
2. Disconnect all modules or switch off everything except the RM-C itself.

In case 2 above, the RM-C will realise there's nothing left worth existing for anymore and will start discovering again.

Another thing: If you change the address of any module this address does not change until you reboot the module on which you have changed the address.

It is assumed that, when you change your configuration, add modules, etc, you do that while power is off. It's a matter of logical safety to do so. Yes, I know, I'm lazy too and I usually work on systems that are live, but then remind yourself that the logic is all based upon "change settings only when power is off", so you may have to reboot modules to get it all at work.

Once your system is up and running you won't be bothered by all of this. It will simply work.

Hope this clarifies some things (and if someone want to translate in German, that would be nice )

Best regards,
Leon

Posted by Ulrich on 2017-03-04 12:32

Hallo Leon,

I'm a little desperate and it seems to me that it is a stony way to get success with the Dinanmo system!
I have follow all your advice above and in the DinamoConfig Status all modules are right and active.
Before I have corrigated all adresses in the iTrain and then connect to the RM-C and the other modules with reset.
But the occupied-contacts from the second TM44 with block-no 3, 5a, 6 and 7 cannot be activated.
I attache the file of my iTrain-configuration.
How can I reboot the modules, specially the second TM44 ?
Where can I download the handbook of the DinamoConfig (I hope I could get in english), Ican't found it here in DinamoUsers.

LG Ulrich

Posted by Ulrich on 2017-03-07 17:51

Dear Leo, dear Frans,

in addition to the steps of my former postings, I have try the following steps:
1) I change the TM44-Modul on the second position against my third module and make all the same procedures as disribed from Leon. But the result is the same: no occupied-contacts from the blocks of the TM44-modul can be acctivated
2) than I switch only the second TM44-modul to the RM-C and that all DIP-Switches of this single modul in ON-positon and make al necessary steps as above.
If I test the occupied-contacts in sequence from block 3, 5a, 6, 7 of this modul, than the occupied-contacts of the first TM44-modul with block 1, 2,5b and 4 response in this sequence.
What does this mean? Are the information of the first postioned TM44-modul stored in RM-C, although I have make all necessary steps, as dicsribed from Leon?

I hope you can solve my ongoing problem!

It seems, that no other users from germnay join to this forum.
Could you give me hints about modelbaarners who use Dinamosystems with iTrain for märklin spoor z in analog modus in germany, specially in the region of "nordrhein-westfalen" ? It would help me to change experience with them.

Thank you for your help.

Friendly greetings
Ulrich

Posted by Geert on 2017-03-07 20:11

Hello Ulrich,

With interest I did read your "struck-ling" with Dinamo and iTrain. By myself I'm also driving with Märklin Z, Dinamo and iTrain, so hopefully I can give you some hints.

The reason that the occupied-contacts reacting if it is the first TM-44 is because of the Dip-switch setting. The occupied-contacts of number 1 are exactly the same as number 2 except the change of the dip-switch. So 0.1 is identical to 1.1.

When you make your second TM-44 as he has to react as number 1 it is number 1.

What you can do is the change the dip-switches for your second TM-44 to number 2 in Dinamo settings :

Dip1 = On Dip2= Off Dip3=On Dip4=On Dip5=On and Dip6=Off

Than you need to fill in in iTrain the corresponding numbers of that TM-44
So the first Block is 8 for Dinamo and 2.1 for iTrain with occupier 1 = 2.0 etc.

After changing the TM-44 in Dinamo you have to change it also in iTrain. Every card number has its unique blocks and occupiers.

In iTrain you can set by the second tab "Wijzig on Dutch perhaps Change in English on German = Bearbeiten" at the last field "Voorkeuren= Voreinstellungen" that you want to split up your Blocks in Standard or 4 or 8 Blocks. If you change it you will see that iTrain gives corresponding numbers as to your TM-44 cards.

To be sure you can check in Dinamoconfig after changing dip-switches if the TM-44 is on the right position.

It looks that you work already with the omrekenen TM-44 xls sheet from Frans, so if you take the original you found the numbers for block and occupier.

I hope it helps you a bit.

Greetings,

Geert

Posted by Leon van Perlo on 2017-03-07 22:26

Ulrich,

Changing the address to module number 2.0 may work, but it should not be necessary. I cannot follow exactly what you do and therefore cannot see what's wrong in your case.
Remind that detectors on module 0.1 are in the range 64..79, detectors on 1.0 are in 128..143, detectors on 1.1 are in 192..207 etc. So there are only 16 detectors per TM44, but they are in blocks of 64 ...
You may download and install JdinamoCC3. It's a program for cars, but it allows you to show the feedbacks, also from TM44's. It may help you to see what's going on.

Best regards,
Leon

Posted by Geert on 2017-03-08 12:52

Ulrich,

Just tested on my own layout (anlage) .

Put TM-44 1 and 2 dip-switches in the positions for 0.0 and 0.1 and did a check of the occupiers.

I made some printscreens in Dinamo config and iTrain so it helps you ; )

Most important for you to check is the Occupier Monitor. If you put in a lok in a block the occupier has to light up.

For me it was for the second TM-44 ( 0.1) Block 2.1 , 2.2 , 2.3 , 2.4 with corresponding occupiers.

Greetings,

Geert