Can it do both?

Certain functions should only go to the lead loco (horn, bell, etc), but others should go to all (braking, dynamics, Drive Hold in LocSounds).  I guess if I could only have one, I'd want it to go to all.

Scott Chatfield 

Consisting

I'm a NCE user and one thing I like about their consisting is the ability to access either end of the consist as the control point. I'm guessing your current cab would do the same thing. As far as control of all units in a consist I would say horn bell in the loco number being controlled . Dynamics in all units in consist along with drive hold and braking . Lighting should be controlled only in the controlled loco .The majority of my consists are already put together before an op session using cv19. Can your handset handle cv 19 in it's initial offering ?---  Ken 

Thanks for the feedback

Scott, we've been having a debate about how we would determine which functions would only go to the lead loco (which is not necessarily the one in the front when moving). In the US, it seems F1 and F2 are more or less standardized. But not in Europe. So that means we would probably need to allow you to specify which functions would stay with the lead only on a function-by-function basis.

Ken, if you're using CV-19 advanced consisting, the consist address is in the encoders, so there is no impact on how our throttle works. Our in-throttle consisting is really more of a light-weight consist model rather than a permanent (or semi-permanent consist). So when you ask if we can handle CV-19, are you asking if we can operate it (yes we can), or if we can setup, break down, or modify a CV-19 consist from the throttle (not at the moment).

As a layout owner...

... who hopes to host op sessions someday, I prefer throttles that cannot affect CV19 consisting. That's my job, using JMRI. 

Having a throttle that can set up temporary consists is interesting - I had not known that Engine Driver had that capability. I can use that.

Agree with Jeff

One of the common annoyances we have with the Engine Driver app is guys accidentally making consists when all they want to do is address an engine.  Granted, these are fellows that only operate now and then.   But if there were a way to lock out throttle based consisting, I'd do it in a New York Minute.

gs

Ease of in-throttle consists

Thanks Jeff and gs.

We intentionally made creating a consist a little more difficult so you certainly won't end up creating one by accident. Here are the steps we currently have for creating a consist:

• Press the menu button
• Select 4 Consisting and press Enter
• Select 1 Add Loco to Consist and press Enter
• Select the loco

There are a couple more steps, having to do with allowing you to change the direction of the loco in the consist, but that gives you and idea. With the phone apps, it's a lot easier to create a consist and you certainly can end up creating one by accident.

Contrast this with how you select a loco in our throttle:

• Press the select loco button
• Select a loco

You can see that they're in completely different parts of the UI.

@gsinos, does that address your concerns?

Anyone using in-throttle consists?

Are others using the in-throttle consisting features in Engine Driver or the WiThrottle iPhone app? I'm curious about when you would use this feature. The most obvious, to me, at least, is for helpers if you don't have a separate operator for helpers. But I'm curious if there are other cases when people use this feature.

@johnsocha - that looks good.

@johnsocha - that looks good. Thanks, gs