02 First Journey

A Journey is a sequence of Events.
An Event is an atomic one-attribute action that a Loco or App can do:
– Turn on/off a decoder Function, e.g. F0, F1 etc.
– Drive, change driving direction
– Play built-in system sound (via iPhone or bluetooth speaker)
– Wait certain amount of time for the next Event to be executed

While creating Events manually and programming their behavior, no requests are sent to the DCC station. This is only Scheduling, thus you may create your Events first and then play the Journey, and during the playback each Event is converted to a Request being sent to DCC station.

Once you set up the connection to your Z21 DCC station you may start creating your first Journey.
This feature will also work if you’re not connected; you are still able to make a Journey and add Events being offline your DCC station. However to execute the Journey you must be connected.

From the Home screen go to “My Journeys” by tapping the icon on the bottom bar.

If it’s the first Journey, the empty “My Journeys” screen will be shown. To add a new Journey tap the “+” in the top right corner.

Then enter the name if your Journey and press “Save”.

The new Journey has been created. Initially there are no Events, so the duration is 0 seconds. The App assigns a random image but you may choose your own and edit some Jourey options by tapping “Edit”.

The Journey will enter the “Edit” mode. You can:
– Rename it
– Change the image make sure that the image you choose has similar ration to the Journey frame)
– Restore the original image
– Select it and delete it by tapping the top right trash icon.

To complete the operation press “Done” and tap the Journey to enter and start adding Events.

Once you entered your Journey, initially it’s empty. Let’s have a look at the Journey screen components:

On the very top in green: Info button, Add Event button, Edit Event list button.

In Yellow the summary of number of Locos and Events

Red shows the main part which is the Event List. Initially empty.

Blue – The player panel:
– Play Journey
– Stop Playing
– Repeat (In-app Purchase feature)
– Emergency STOP (while playing)
– Listen for incoming data
– Open Control and Record Center

We will start by manually Scheduling new Events. Tap on the “+” button at the top right.

A new Event has been added to your Journey. The Event has a mini-control panel to manage the Loco or App behaviour in a single step.

You may control the following actions:
– “Go!” – Loco Driving: Speed, Diection
– “Fn” – Function on/off
– “Speaker icon” – System sound: useful if your loco doesn’t have a sound decoder
– “Loco Address” icon, let’s keep the loco with decoder address #1 for now.

Tap “Fn” to see Functions. This panel has function numbers from 0 – Light (Bulb). Tap on the function to schedule activation.

More function numbers can be viewed by tapping “+” on the right.

As explained at the beginnning, Events are atomic i.e. an Event can manage one function at a time. To schedule another function and another Event and schedule activation of F1 (usually engine sound) in this example. Next, we can set a delay, waiting time that must elapse before moving to the next Event. This can be done by inceasing “Wait” value (increase/desrease step: 0.25s). You may press the number field and input the number from the keyboard (Integer) and adjust by pressing “+” or “-” button.

After setting a delay, let’s add another Event – driving with 50% of the speed. The speed steps are defined by default to 128 steps, so the 50% will be mapped to step 64 of a DCC decoder.
Set delay to the next Event to 10 seconds. It means that schedule the loco to run for 10 seconds before we move to the next Event.

After scheduling the Drive Event we add another Event to stop the loco; V = 0. And what is important we delay next Event by 5.5s because the loco won’t stop immiediately so we must give it ample time to stop.

When 5.5s elapse let’s turn off the light and F1 (usually engine sound). To do this, we add two “Fn” Events and tap on the selected functions twice to make it gray. The newly added Events don’t verify the entire Loco state therefore once we add a new one we have to configure it.

After finishing adding Events we can check some info about our Journey by tapping “i” icon at the top. The Summary contains
– Loco addressed being used
– Event count
– Duration rounded to full secondes.

Press “OK” to exit the Summary.

Press Play button. The App will start playing the Journey by taking each Event, trying to send requests to the DCC station. If you’re connected to the DCC station your Loco #1 will start responding to the Events. Otherwise the Journey will be dry-played only by showing which Event is being executed.

Once the Journey has been completed you will be notified.

You have completed the Tutorial for manual Journey creation and scheduling. Please have a look at the video showing the same Journey in for the Piko SmartControl set.

Please go to the next unit to learn more about controlling and recording.

Controlling and Recording Events