Loading...
 

Dinamo

Forum List Topic List

[ prev topic ]  

Reboot of TM44

Posted by Ulrich on 2018-10-02 23:17 Germany

Hallo Leon,

i have change two TM44-Modules from an elder trainsystem to a greater configured system with four additional new TM44-Modules. The four new modules are exactly recognized with the correct DIP-Switch-Settings.
But the elder TM44-Modules couldn't identify in the status-screen of the DinamoConfig 1.30A.
How can I reboot the elder TM44-Modules? Where can I find the TM44-Handbook?
For your information I added the configuration of the new trainsystem with the DIP-Switch-Settings of the six TM44-Modules and a screenshot of the status in the DinamoConfig.
I hope you can help me!
With friendly greetings
Ulrich

Block- und Belegtmelder-Belegung Alenabahn TM44.xlsx (76.00 Kb)
Reads: 0
Link

Posted by Frans Staal on 2018-10-03 14:53 Netherlands

Hallo Ulrich,

the manual of the TM44 can be found on the Dinamo website,www.vpeb.nl. A link "Ondersteuning" on the right hand size of top of the screen will show a new page, then select Documents Dinamo. There you find the manuals, also in German. In the manual the Firmware update is described on page 24.

Greetz
Frans

Link
Posted by Ulrich on 2018-10-04 18:45 Germany

Hallo Frans, I have the elder TM44-Modules updatet with the TM44-Firmware 1.2.
These two TM44 are then correct recognized in the DinamConfig under adress 0.0 and 0.1. But if I add the other four TM44 in the network and reset the RM-C then only the four TM44 are correct recognized under adress 1.0 , 1.1, 2.0 and 2.1 but not the two elder TM44 on the adress 0.0 and 0.1. (s.a. the added Block-Configuration which contains also the DIP-Switch-Configuration of the 6 TM44--Network
What goes wrong?
I asume, that I have to update the firmware on each of the 6 TM44-Modules seperately (not in the network-connection) only between the RM-C and the TM44-Module which has to be updated!?

I hope you can give me the right hint for solving this network-problem!

Greatings Ulrich

Block- und Belegtmelder-Belegung Alenabahn TM44.xlsx (76.00 Kb)
Link



Posted by Ulrich on 2018-10-04 21:44 Germany

Hallo Frans,
I have tried to update all 6 TM44 seperately with the AVRootloader. Until to the TM44-Modul No. 4 it goes well and all four TM 44 with the adress 0.0, 0.1, 1.0 and 1.1 are correctly recognized in the DinamoConfig.
But the TM44-Modules on position 2.0 and 2.1 couldn't be updated with the AVRootloader. If I try to connect the device than pop up the error-message: no device found, although I did all steps to update as before with the other TM44-Modules.
What is the reason?
I hope you have a good advice!

Greatings Ulrich

Link

Posted by Frans Staal on 2018-10-05 00:12 Netherlands

Hallo Ulrich,

please let me know the position of the dip/switches of all TM44. Or make a picture where the switches can be seen.

grusse
Frans

Link

Posted by Leon van Perlo on 2018-10-05 09:33 Netherlands

Ullrich,

When updating modules in a larger system, apparently modules react on some bootloader sequences while they should not and even could not in theory.
If that happens, the best option is to connect only the module you are updating, or, if that is not practical, keep all modules in reset by the jumper, except the one you are updating.

If it does not work immediately after an update, it is recommended to power off and power on your entire system at least once, to be sure no module is hanging in bootloader mode.

Link
Posted by Ulrich on 2018-10-05 10:26 Germany

Dear Leon.

the problem is, that the last two TM44-Modules (under adress 2.0 and 2.1) cannot see the device in the AVRootloader if I press the "connect to device"-button.
But these two TM44-Modules work right in the last four TM44-Network (under adress 1.0, 1.1, 2.0 and 2.1).
The second problem is, that the AVRootloader doesn't work as described during updating the other TM44-Modules, because after pressing the "connect to device"-button and when all LED's blink in the correct manner, I take off the RESET-jumper, but in the AVRootloader-window there is no "connected" notified and I can see no device-info.
The AVRootloader has the revisions-nummber: 6.0.0.0

What may be the reason?

Greatings Ulrich

Link

Posted by Leon van Perlo on 2018-10-05 20:54 Netherlands

Hi Ulrich,

I understand modules 2.0 and 2.1 work correctly in the Dinamo network but cannot be updated by the bootloader. Note that the suggestion to keep all modules in reset also applies to the OC32's, even if you don't want to update these. Of course it would be wise to find the reason for the bootloader issue and solve it, but on the other hand, for now, if the modules work and have the correct firmware there is no reason to update, so I would postpone that issue.
I understand modules 0.0 and 0.1 have been updated but do not communicate.

Neither Frans nor I can see from a distance what is the problem. My first suspect would be power supply or network cabling. I suggest to start with checking that the modules themselves are all ok by connecting them one by one to the RM-C, preferrably by using the same network cable so you know that cannot be the problem.

Best regards,
Leon

Link

Posted by Ulrich on 2018-10-11 20:07 Germany

Hallo Leon. hallo Frans,

now I have found the "rabbit" (in german " Karnickel"). The RJ45-cabl between TM 44-module 1.1. and 2.0 was not right.
But the problem with the AVRootloader is the same for updating the firmware of the OC32-modules. I have installed the AVRootloader again. But if I pressing the "connect to device"-button and when all LED's blink in the correct manner, I take off the RESET-jumper, but in the AVRootloader-window there is no "connected" notified and I can see no device-info. The led's on the OC32-module on fourth position didn't stay on after reset the jumper. I have made a separate connection with a wire-ended RS 485 to the RM-C/1of the 3-pol-plug, but it doesn't work.
What I have I to do, to solve this problem?

Another question for configuration the devices in the OC32 is for the device declutcher, which needs only one aspect with an impuls. In the device-galerie I didn't find a proper solution. Which configuration-parameter have I to adjust in the OC32Config?

I hope you can give me some advices!

Greatings Ulrich

Link
Posted by Ulrich on 2018-10-12 15:07 Germany

Hallo, I must corrigate my last information as follow:

But the problem with the AVRootloader is the same for updating the firmware of the OC32-modules. I have installed the AVRootloader again. I have made a separate connection with a wire-ended RS 485 to the RM-C/1of the 3-pol-plug. Then set my RM-C/1 in transparent- and boot-mode. The RM-C/1 works correctly as described. I press the "connect to device"-button and all LED's blink in the correct manner. I take off the RESET-jumper and the green and orange led's are on. After the hint "device is connected" I can see the correct device-info with the version-no and so on. But if I "disconnect the device-button" the led's on the OC32-module no 3 didn't stay on and after reseting all connection and start DinamoConfig the OC32 # 3 is not found.
What I have I to do, to solve this problem?
Greatings Ulrich

Link

Posted by Leon van Perlo on 2018-10-12 16:47 Netherlands

Ullrich,

Have you rebooted the RM-C to get it out of bootloader mode? Have you restored all connections?
Best just reboot your entire system if something behaves strange.

Best regards, Leon

Link
Posted by Ulrich on 2018-10-12 22:51 Germany

Hallo Leon,
the solution of the above mentioned problem was, that I have follow the chapter 13.1 in the OC32-handbook on page 64 bis 65. I set the two jumpers reset and No-Init on K6 as described and than the OC32 #3 could be recognized in the DinamoConfig.
Now my basic-construction and device-configuration of the "Alenabahn" in Märklin Spoor Z is built up. I have added a photo of this spoorbahn.
So I hope I can begin with the finetuning of all functions in iTrain.
The only problem is to get a right configuration of the "Blocksignal" and "Einfahrsignal" in the german OC32Devices DE 20130305 and for the impuls-configuration of the declutcher as mentioned in the further blog.
Thank you for your advices.
Best regards Ulrich

Basisausführung Alenabahn.jpg (41.18 Kb)
Link

Posted by Leon van Perlo on 2018-10-13 00:51 Netherlands

Hi Ulrich,

Ok, so apparently you had programmed an infinite loop in the OC32. Then this was already the case before you started the bootloader. Reprogramming the firmware will never erase the configuration.
It is unclear to me what you mean by problem is to get a right configuration of the Blocksignal and Einfahrsignal. There is a large amount of ready-made definitions in the German DD, including output-saving alternatives and including the ones you mention.

Best regards,
Leon

Link

 
Dutch (Nederlands, nl)English British (British English, en-uk)German (Deutsch, de)