HI Rinus,

Well, it may takes a bit of time to answer accurately to all your questions.

I won't be online tomorrow, but I'll try to add more answers later. So, for a quick answer:
1) Menu file/analyze/analyze
2) It is advised to use the route generator when all your blocks are defined. The route generator computes all links between available blocks. So if later you add more blocks, then the route generator should be run again to add missing routes. I must confess that when I used the generator in the past, sometimes not all new routes weren't generated and/or some parameters I added previously to the old routes were reset. But, you must experiment new versions of Rocrail as a new generator has been rewritten recently...
3) This one is easy : when you draw straight sections, you may choose "straight, or "direction", or "both direction". The "direction" implies a straight section with a direction arrow, which indicates the direction of traffic. Of course "both direction" means the section is bidirectional. By default, if you don't tell any direction, the section is bidirectional. So, if you have unidirectional traffic is some sections, it is mandatory to use the direction arrow. Depending of these directions the amount of routes generated is not obviously the same. In Rocrail, each route is unidirectional, so if you have bi-directional sections twice the amount of routes must be generated.

Let's have a simple example: a single oval and a station with two parallel tracks delimited by a couple of switches: B100 is station lane 1, direction from right to left (put a direction arrow in Block B100), B200 is station lane 2, direction from left to right (put a direction arrow in Block B200), B300 is the single lane representing the rest of the oval (either put a double-arrow somewhere in the oval -more for understanding, or don't put it as it is the default).

The routes generated are : B100->B300 (counter clockwise), B300->B100 (counter clockwise), B200->B300 (clockwise) and B300->B200 (clockwise). NO routes are generated for B300->B100 clockwise, as the direction arrow in B100 prevents it. Same rule apply (NO route) for B300->B200 counter clockwise due to the direction arrow in B200.
See my post #336 in Trossingen https://www.marklin-user...ossingen.aspx#post389397 for the synoptic with direction arrows, which describes which blocks are unidirectional or bidirectional.
4) go there: http://rocrail.net/software/rocrail-snapshot/ and load the version corresponding to your OS.
5) As a quick answer I'd say it's an old explanation. As the generator will provides automatically all links between blocks, this sentence seems to me to be a bit obsolete.

Hope you'll find some answers to your questions.
In case you need it, i can provide you my configuration for "Trossingen" (only 2 xml files, not so big)

Cheers
FAbrice

Hi Fabrice,

Outstanding! iIve been reading your replies and they help me a lot. Will implement them next weekend.

One other question. As you might know Im using Uhlenbrock Lissy as sensors. Ive got them working. they detact a train and the specific sensor shows up in Rocview and Rocrail server. there is hwoever one problem: the sensor on rocview turns red at occupation (which is good) but does not automaticaly turn to normal again after the sensor is free.

Do you know how to arange this?

Rinus

Hi Fabrice,

Do you have to asign al individual track pieces to a block?



Rinus

Hi all,

Spent most of the weekend reworking my rocrail plan.

Reworked the blocks ... adressed the level conectors ... updated rocrail ... reworked the entire plan on efficiency ...

Unfortunately in the proces I did some damage to the plan (copy and paste) so I lost quite a few configs for the sensors and switches.

So I need to re-configurate some sensors, switches, signals before I can do the auto generate routes.

Here are the results...







Some questions that remain:
If a block is to short for a train to stop, do you specify that with the option "wait - no"?
In case of linking a signal to a block, does one enter the signal at the end of a block or before the block begins?

Rinus

Hi fabrice,

Thank you again!

When I ran the track analyzer yesterday evening the only issues that occured where signals and switches with no adress (no motorola adress but port, bus, adress... ). I'll fix that this weekend and the try to auto generate some routes.

Regarding the signalling I see it the same way. However I noticed that sometimes it is seen the other way around: signal at block start guarding the entry of a block. Signal at block end however is more logical practical.

Concerning the block definition I now try to define every track between two switches as a block. Perhaps it would be an option not to do that and let rocrail sort this herself?

One new question: Whats your set up in stations? How do you define that certain trains stop and wait for lets say a minute? With the 'wait' function?

Rinus

Hi all,

tried to go automatic mode today, but the first attempt failed ...

This is what happend:
1. i positioned a train on the track near the sensor fo the 'in' event of a block
2. registered the train to the block and the block turned red
3. pressed auto mode button in rocview
4. double clicked on the occupied block for 'start'
5. I saw in rocview that a reservation for a route was made (yellow path to next block)
6. after several moments the train went off ( )
7. passed the next block and kept un running .....

During this brief moment I noticed that once the train had left the firt block nothing happenend in rocview. Not even when the next block was reached. The initial block remained occupied.

Very strange especially since in hand mode the occupancy of blocks changed as expected.

Any idea what I did wrong??

BTW i also experienced some problems with the server which I posted on the rocrail forum. I did not start up any more.

Rinus

Hi fabrice,

Thank you for your response. I've also posted in the RR forum. Last night I really want to solve this.

I'll have a closer look at the set-up of the (Lissy) sensors. I think I did something wrong there.

Allthough the sensors detect the train (seen in the server info) this information seems not to result in a action/status change of the blocks.

I'll keep u posted.

Rinus

I know. Uploaded the wrong xml