Darrin:

Nice video. Good to see LocCommander in action!

r/mark

Hi Frank, One other question I have with track diagrams is whether you can draw tracks that cross other tracks such as bridges, or for different layout levels?

Cheers, Dave.

Thanks Frank.

It may be a little bug, yesterday when I shut LC the CS rebooted, has this ever happened to someone else?

Interesting to follow up this one! Strange...but the only thing that happens when LC shuts down, the TCPIP socket connection is closed. Nothing special is send to the digital system when closing the program. Thus if the CS reboots after a socket connection closure something dirty is happening at the CS end.

Until now the only digital system anomalies I faced are the memory gaps that can exist after deleting and adding new objects to the digital system. This can be seen as the object id (see in LC digital system properties page for a switch object) is not reused when adding a new object after deleting one/more.

Also from firmware > 1.1.2 for the ECoS when the screensaver mode is active, connection get lost or not possible to connect anymore. But this I can only confirm after having done some more tests.

Alessandro or Dave, do you have an opinion on how/when the conditions should be evaluated with the 'Delay' parameter in the Actions/Conditions dialog. Current implementation evaluates the conditions after the Delay timeout. This means the actions will only be executed when the conditions are forfilled after the delay timeout.

Further should the delayed actions get priority over the queued actions?
Current implementation executes the delayed actions after the timer has elapsed and the current queued actions are first all executed.

Thanks,
Frank

I use to have the signals set up with blocks when I set the layout up in analog mode.

But now I don't use any blocks, currently I just set the speed of the loc when it crosses a contact or circuit track, but I may add some blocks back in just to make sure the loc stops where I want it to. and also for the hidden yard where I don't want power to be consumed when not in use.

I'm waiting on another K83 to get my signals working, but I do have the signals set up in LocCommander. I use some signals to hold or release trains as they should work and I use other fake signals as logic control.
The only problem I have had with this is that to start the layout running all trains must be in there certain spot and all signals must be set correctly before switching to automatic mode.

Hi Darrin,

Thanks for your new report. I think I miss something in your workflow but I will ask you later for more info.


A quick respons to your "train whistle" problem without a condition to switch it off...

If the train function is not defined as "a toggle" it should stop automatically after a few seconds. Otherwise you have found a new bug in LC.[:I]



Best regards,
Frank

Yes, you could say the "Actions And Conditions" tables represent "IF THEN" statements as in common programming languages.

<u>As an example:</u>
- The layout exists of 3 blocks: B(1), B(2) and B(3). Each block has a feedback item(track occupancy detector) attached to an input of a feedback decoder (Feedback Module(1)).




<u>Scenario for slowing down a train Train(1) before a signal S(1):</u>

The train Train(1) with a speed of 140km/h enters the block B(1).

1.The train speed is set to 100 when signal S(1) is Hp0(red) and B(2) is not occupied and B(1) becomes occupied.


This extra condition "B(2) is not occupied" is necessary when the train covers/occupies both blocks B(1) and B(2) otherwise the train speed would be set simultaneous to 100 and to 50. And this would cause the train to accelarate and to slown down cyclic as long as B(1) and B(2) are occupied.



2. The train speed is set to 50 when S(1) is Hp0 and B(3) is not occupied and B(2) becomes occupied.




3. The train stops when S(1) is Hp0 and B(3) becomes occupied.



In case 3 only one condition is necessary, when the train occupies all three blocks, the actions related to block B(1), B(2) will not be executed as the conditions are not forfilled.

In this simple example all the conditions are set on each action individually.

But there is also the possibility to set one or more conditions that is valid for all the actions. And to make it complicated you can have a mix: global conditions on all actions and individual conditions set per action.

<u>How does the evaluation algo works in LC:</u>
1. First are the global conditions evaluated.
2. When the global conditions are forfilled then the individual conditions set per action are evaluated. Only when all the conditions are forfilled the action is executed.

Important an action on a controllable object is only executed once when the state of the object doesn't change in the meantime.

Example:

A turnout has 2 states: straight and derived.

Thus when a feedback item becomes occupied it will trigger only once the action on this turnout eg. set it straight. Only when another feedback item becomes occupied switching it to derived the first action can set the turnout back to straight when the feedback item is still occupied or becomes again occupied.
Thus as long as a feedback item is occupied it triggers only once an action as long as no other feedback item triggers a different state on this same object. Errors can be seen when the state of a switch object alters continuosly. For a train when speed goes up and down, or a train function is activated and deactivated continously.

Alessandro I hope this explains better the actions and conditions concept implemented in LC. In later versions I would like to simplify this process but you can also use the route concept but this is less powerfull.

With the "Actions and Conditions" concept you are programming yourself a part in LC.

Best regards,
Frank

Hi Darrin,

I'm happy that you are enjoying it more and more.

Yes, it can give a real kick when you see everything running automatically. Especially when defining yourself the 'actions and conditions' you are adding intelligence to the system.
Thus, if it fails don't blame the system.
I must agree LC is a computer program thus bugs are still there...and it runs on Windows. Plus the hardware factor, although the 6051 is pretty good!
But, keep in mind to limit the actions you want to get through the system.

For later versions I would like to improve automatic control so that the system can react/interact on actions taken by the operator.
But to accomplisch this I have to implement mathimatical models regarding networks.
But, there are some heavy math brains in this forum I hope that can help me out in this complex world of networks. Michael?

But still a lot of work in different parts of the program (GUI, data exchange with the digital systems(ECoS/CS), automatic control, etc.)

BTW. thank you for putting your layout files on the web. But, it is hard to follow the actions and conditions even for me.
Under the installation folder of LC in the subfolder DemoLayouts, you can find the layout files representing my model railroad in LC.

Best regards,
Frank

Hi,

The lastest version 1.0.0.14 can be downloaded.

Hopefully...I have corrected the issue that was introduced in LC's previous version regarding reading out feedbacker decoders (S88).

<u>IMPORTANT REMARK when using LC on the Windows Vista platform:</u>

As LC was orignally developed under the Windows XP platform file compability is automatically done when installing and running LC on the Windows Vista platform.

It is important to know that the Catalog.dbl file is no longer written under the C:\Program Files\LocCommander\ [default folder] but under the folder:
C:\Users\username\AppData\Local\VirtualStore\Program Files\LocCommander.

When uninstalling LC a backup of this catalog file is written under:
C:\Users\username\AppData\Roaming\LocCommander

In a next release the user will be able to indicate himself the folder where this catalog file is placed on the system.
A default folder will be defined according the standard Windows file policy.

Best regards,
Frank

Frank, Its pretty hard going - I got it to work once but have no Idea how - .

Frank, It is step 1 that is the stumbling block.


1. Import the feedback decoders from the digital system (click on digital system in Tree View, connect and go to Import tabpage in properties page dialog)

This works.
Notes:
1) Under Digital System you must also select Central Station
2) The "Connect" button is on the "Connection" TAB
3) The Import button is on the "Import" sub-tab which itself is under the "Object Management" tab


or add manually feedback module objects (S88) to a layout.

This did not work
Notes: the "IDs" under the "Digital System" tab started from 1,2,3 etc if added manually - These IDs cannot be changed!!!!. The imported ones (that worked) had 101,102 .....

Hi,

I have put a MS powerpoint presentation "Object Management with the digital systems(ECoS/CS) in LC" on http://fvri.forumco.com/topic.asp?TOPIC_ID=11

Best regards,
Frank

Points 1, 2 a and b: ok, I will verify and try to fix...

Point 2 c: Fetching info after something has changed in the digital system can easily be done by calling the 'Fetch' action in the 'Object Management' tabpage Properties Pages dialog of the digital system. [See also the ppt in the link: "Object Management with the digital systems(ECoS/CS) in LC" on http://fvri.forumco.com/topic.asp?TOPIC_ID=11].
This action can only be done when connected!

Thus, no need to disconnect and reconnect again. But it can be used for this purpose.

Also important to know is the use of this "level" setting in the 'Fetch' tabpage ('Object Management' tabpage in Properties Pages dialog of the digital system).
In the digital system it is possible to specify 3 names for a switch object. This level setting refers to the one of the 3 names that will be used as name for the switch object in LC.

I know there is still some work to do regarding this object management with the digital systems. Especially the 'import' gives me some headaches.

Thank you very much for this test work and the error report!

Best regards,
Frank

Hi Caillin,

Here I have some references to the:
1. P50 protocol(RS232-communication):
http://www.tams-online.de/htmls...asyControl/interface.txt

http://www.uhlenbrock.com/3/4/0...CD68948-002.apd/P50X.zip

2. PCInterface protocol ASCII (TCP/IP communication):
http://users.telenet.be/loccomm...sPcInterfaceProtocol.pdf

Best regards,
Frank

Excelent - Thank you both for your replys - I think I will try the emulator first - If it does what I want then there will be no need to build fancy circuits

Caillin

Caillin.

Not sure from you comments if you already have LISSY in operation. If you do then I am not sure I would reinvent the wheel.

Augmenting it with a loconet capable interface like locobuffer using JMRI should offer any advanced logic that you require.

Hi,

Recently, I have released version 1.0.0.16 of LC.
To download please go to : http://users.telenet.be/loccommander/DownloadsPage.html

Main issues regarding this version:

- Improved 'automatic run mode' for the digital systems CS/ECoS.
Use of events to trigger actions instead of the 'readout loop' for the feedback decoders (S88 modules).

- A 'route' object can be used to define actions (see 'Actions and Conditions' dialog).

- User definable 'Speed conditions' when defining conditions (see 'Actions and Conditions' dialog).

- Bug fixes regarding the 'Train Control Dialog'.


As an illustration of how LC controls my model railroad in 'automatic run mode' please play this movie:
http://users.telenet.be/loccomm...s/LCAutomaticControl.exe

In the movie you will see how track occupancy changes in the layout, how train speed changes in the 'Train control dialogs' and how some turnouts and signals are triggered.

In another movie I show how to define actions and conditions/rules in LC. Starting from defining a feedback module(Eg. S88) and an occupancy detector in the layout until adding actions and conditions via the 'Actions and Conditions' dialog.
http://users.telenet.be/loccomm...ActionsAndConditions.exe


Thanks to very valuable/useful feedback of Alessandro(alias Frankie) and Darrin I'm able and will continue to improve LC.

Object management between LC and the digital systems ECoS/CS still needs more improvements.[:I]

Feature and bug reports can be reported in http://fvri.forumco.com or here of course!

Further... ESU has announced that they will release in the near future a new version of the PC interface protocol...

Best regards,
Frank

Has the emulator worked as you expected, then?
I mean a booster and the emulator are sufficient to control the layout with LocCommander?

Frank: I have not had much time to play recently, but I have my CS hooked up via Cat-5 cable to a PC running LC, latest version. I have run into a problem. I downloaded the information from the CS to LC, and every time I try to operate anything on an MFX Lok LC bounces back to "edit mode" from operational mode. I can control non-MFX trains, and solenoid devices, but try one thing with an MFX Lok and it's all over. Is there a fix, what is going on, can I work around this? Thanks.--MM

Hi Michael,

Yes, indeed strange... Alessandro(frankie) uses a mix of trains and so far no problems but of coarse there could always be one data item causing problems. The fact it switches immediately to 'Edit mode' is very strange this could only be when a connection is broken with digital system or an illegal command was send to the digital system.

Anyway I need to investigate this.
Is it possible to send me your Catalog.dbl file, in the Properties tabpage of the Properties Page dialog of the Catalog object(click on Catalog in the TreeView) you can see where your Catalog.dbl file is located on disk.

For me it is the only way to see what data is really imported from CS into LC catalog database file regarding this loc.

Maybe also the layout file(.lo)!

BTW. what is the firmware version of CS?

Thanks.
Best regards,
Frank

No, the firmware should not be an issue when it is &gt;=2.0.4 (for CS I think):

Ok, I appreciate this a lot!

Thanks.
Frank

Alessadro and Frank: I am a Computer Science professor, and I have produced a widely used piece of mathematical software. So I definitely understand that even when code works well for most of the user base, weird thing pop up. This is VERY USEFUL SOFTWARE, it just has bugs, which is what all software always has. I like LC a lot, and I hope that I can help make it better by collaborating with the developer. In fact, I think, up to the point that Frank cannot cope with our comments, Frank is probably happy to see people using LC and reporting back with bug reports.--MM

There is a forum just for LC at least I wil not be alone therehttp://fvri.forumco.com/default.asp

OK, I will go to the forum.

BTW: I will post the information for you, but I am running LC version 1.0.0.15, my CS is hardware v1.2, firmware v2.0.4, and protocol v0.1. I will create a web page for you to see the files you need at:

www.cs.fsu.edu/~mascagni/Loccommander

Thanks.--MM