开云体育

Hi,

I have been running transponding on my layout since about 2009 and have made changes to the scripts I use as JMRI has new releases.

I run two scripts, Transponding_Startup and Transponding. ?The first displays on the panel where locos are located at the startup of a run. ?It use MemoryVariables in the 6xxx range to store the loco address. ?The second displays the location of locos that are run during the normal running of the layout. ?It records the location of the locos using MemoryVariables in the 3xxx range. I use the script locostartup.py to run all locos at zero speed for 3 seconds to find the initial location block for each loco.

With JMRI 4.18 the Transponding_Startup.py script senses a loco at the correct location, but when the loco moves to another block the initial block location is removed. ?This should not happen as I have #ed out the 'departure' portion of the script. ?Further more if there are two locos in a block when one moves out to another transponding block both entries are disappear. ?If the loco returns to the original block both entries reappear. ?I can also follow this in the MemoryVariables table of JMRI Tools.

The files I use are:
Transponding_Startup_7_2-2020.py
Transponding_7_2_2020
Locostartup.py

The first two scripts have been added to Files, see Transponding.

Any help or advise would be appreciated.

Regards
Peter

Peter,

? ? What JMRI version were you using before downloading ver 4.18?

Roger

Hi Roger,

I think it was JMRI 4.16 and the Console told me that jmri.InstanceManager.reportManagerInsatnce had been depreciated. (At least I think that was the term used so say the comand was no loner valid).

?Unfortunately I had this current problems for about three weeks as I have also added two BXPA1's to the layout for additional tracks so it has taken a while and a number of upgrades of JMRI to get to where I am at. ?At the moment I have removed the track feeds from the BXPA1's just in was they were causing the problem - but no change.

The two scripts I use are identical except the Startup one has the 'departure' lines #ed out and uses the IM6xx to display the locos identity on the panel. ?The Transponding.py script uses the IM3xxx to display the loco identities on the panel. ?Both appear to run correctly until locos get moved between block when the startup.py one loses the location.

I have place a screen shot of the Panelpro panel in the Files Folder under Transponding.

Regards
Peter

Roger,

More testing with only one loco. Loco appears in block as should when started. Loco moves across non-transponding block loco identity retained in bock one, ie script does not action a ‘departure’.

When loco moves into a new transponding block it registers the loco address BUT also removes it from the block it was first registered in. This should not happen (and did not with my earlier script)

I know it is an anomoly but I could see know way to locate a loco that is not active other than to run the full roster at zero speed at startup and this have3 a list on screen of where all locos are.

So how does the new script manage to delete an entry that has was present when the loco moves into a transponding new block?

Regards
Peter
New Zealand

On Thu, Feb 13, 2020 at 12:03 PM, Peter Rushworth wrote:

Hi Roger,

Apologies for errors in my email,?the 3rd para should read:

I know it is an anomaly but I could not see a way to locate a loco that is not active other than to run the full roster at zero speed at startup and have a list on screen of where all locos are at the start of a session.

Regards
Peter