How I reprogrammed a Micron MR603 receiver

Recently, I needed to reprogram a Micron MR603 receiver so it could be used to trigger all the sound effects on a Micron Mini Sound module (MSND01). As this module uses the same firmware as MyLocoSound modules, this reprogramming would also be appropriate for these.

 The sound module has seven functions triggered by inputs on seven pads (or screw terminals):

• F1 - Whistle
• F2 - Bell 
• F3 - "All aboard" (or guard's whistle)
• F4 - Safety valve
• F5 - Brake pump 
• F6 - Injector / Coal shovelling
• F7 - Chuff cam

 The receiver was going to be used with a Micron Tx22X transmitter .....

.... which has two two-way switches and two push-buttons for triggering outputs from the receiver, ....

• S1 A - sends Channel 3 high
• S1 B - sends Channel 3 low
• S2 - sends Channel 4 low
• S3 C - sends Channel 7 high
• S4 D - sends Channel 7 low
• Bind button - sends Channel 5 low

 .... thus allowing all six of the additional sounds on the Micron or MyLocoSound modules to be triggered.

The Micron MR603 has ten output pads which, as delivered, provide the following outputs:

• P1 - Front light / LED2
• P2 - Rear light
• P3 - 0v - 3.3v when Channel 3 is low
• P4 - 0v - 3.3v when Channel 3 is high
• P5 - 0v - 3.3v when Channel 5 is low
• P6 - 3.3v - 0v when Channel 5 is low
• A - Front light
• B - Rear light
• C - 0v - 3.3v when Channel 5 is low
• D - 0v - Toggle 3.3v/0v when Channel 5 is low

The Micron Mini sound card inputs (and the MyLocoSound inputs) are trigged when they are connected to 0v and so, to make use of all the features, I needed to change some of the outputs from the pads to give 0v when the channels used by the buttons and switches on the Tx22X went high or low.

So, I decided to reprogram the receiver's output pads as follows:

• P1 - Unchanged (i.e. Front light)
• P2 - Unchanged (i.e. Rear light - not used)
• P3 - 0v when Channel 3 is low (i.e. when S1 A is clicked on the Tx)
• P4 - 0v when Channel 3 is high (i.e. when S1 B is clicked on the Tx)
• P5 - 0v when Channel 4 is low (i.e. when S2 on the Tx is pressed)
• P6 - Unchanged (i.e. 0v when Channel 5 is low (i.e. the bind button is pressed on the Tx))
• A - Unchanged (i.e. Front light - not used)
• B - Unchanged (i.e. Rear light - not used)
• C - 0v when Channel 7 is low (i.e. when S3 C is clicked on the Tx)
• D - 0v when Channel 7 is high (i.e. when S3 D is clicked on the Tx)

 

 Working out the reprogramming code sequence

To determine the code needed to make these changes, the programming chart for the MR603 receiver on the Micron website was consulted.

This is probably the part of the process which most people find confusing, so I will try to describe how it works as clearly as I can.

 Let's take the changes needed for P3 as an example. The pad needs to be reprogrammed so that it provides a 0v output when the receiver detects that Channel 3 has gone low.

So, working our way across the section of the table shown above:

• The first value we need to note down is 3 which tells the receiver we want to reprogram an on/off feature
• Moving to the next column, we need to tell the receiver we want to reprogram pad 3. So 3 is our next value to be noted.
• Moving to the third column, we want the output from the pad to be momentary - i.e. we only want the output to happen while the button or switch on the transmitters is being pressed or clicked. As soon as the button is released the output from the pad will revert to whatever it was doing when the receiver was switched on. So, our next value is 1.
• The fourth column, specifies the Channel we will be using. In this case it is Channel 3 and so 3 is the next value to be noted.
• The final column specifies what sort of output we want dependent on the state of the selected Channel. We want the output to start high (on) but switch to low (off) when the Channel goes low. So, we want this value to be 4 (i.e. When Channel 3 goes low, turn off the pad (i.e. it has 0v output))

So, the reprogramming code we need for this change is - 3, 3, 1, 3, 4

 Let's skip to the last output in our list, Pad D. This needs to provide a 0v output when Channel 7 goes high.

• Again, our first value is 3, indicating we want to reprogram an on/off setting
• This time we want to reprogram Pad D - so we note down our next value as 10
• Again, we want the output to be momentary, and so our third value is 1
• We are using Channel 7, so our next value will be 7
• And finally, as we want a 0v output when Channel 7 goes high, the value we need is 6

 The coding for this change is therefore: 3, 10, 1, 7, 6 

 

So, on this basis, the codes needed for each of the pads which need to be reprogrammed are:

P3 - 3, 3, 1, 3, 4 (for 0v when Channel 3 is low) 

P4 - 3, 4, 1, 3, 6 (for 0v when Channel 3 is high)

P5 - 3, 5, 1, 4, 4 (for 0v when Channel 4 is low)

C - 3, 9, 1, 7, 4 (for 0v when Channel 7 is low)

D - 3, 10, 1, 7, 6 (for 0v when Channel 7 is high)

 

Putting the receiver into programming mode 

To actually make these changes, we firstly need to make sure the MR603 receiver has been bound to a transmitter which has a reversing switch (i.e. which can give a high and low output on Channel 3). In the Micron range, this would include:

• Either of the Micron Tx20v2 transmitters
• The Micron Tx21v2
• Any of the Micron Tx22 transmitters
• Either of the Micron Tx24 transmitters

To put the receiver into reprogramming mode, the transmitter and receiver must be switched on. After a few seconds, the morse code for SOS (dot, dot, dot, dash, dash, dash, dot, dot, dot) has to be tapped out on the bind button. The dots must be less than a second in duration and the dashes more than a second but less than five seconds. The pauses between dots and dashes must be less than 5 seconds.

When the receiver has entered programming mode, its LED will flash once every second (referred to as 1-flash)

 

 Reprogramming

We can now start the reprogramming process.

Taking our first set of values needed to reprogram Pad 3 (i.e. 3, 3, 1, 3, 4), we need to change that initial 1-flash to a 3-flash (i.e. three one second flashes, followed by a pause). To increment the number of flashes, the reversing switch on the transmitter need to be moved to the "reverse" or "down" position and then returned to the mid-position. Clicking it once will increase the flash-count by one. Clicking it again will increase the flash-count by another one. Thus, the LED should now be flashing three times before a pause. This is the value we need for the first code in our list (i.e. telling the receiver that we want to reprogram an on/off setting). To tell the receiver to "accept" that value, we move the reversing switch to "forward" or "up".

The LED will now start flashing once per second. We need to it flash three times, so we increment the number of flashes twice (by clicking the reverse switch twice in the "reverse" or "down" direction). Once it has reached 3-flash (three flashes then pausing), we "accept" this by clicking the reverse switch "forward" or "up". This tells the receiver we want to reprogram Pad 3.

LED should now flash 1-flash again (because Pad 3 is already set for momentary on/off). So we just click the reverse switch forward or up to accept this value.

The LED should now start flashing 3-flash, as P3 is already set to respond to Channel 3. So click the reverse switch to forward or up to accept this.

Finally, the LED should now start flashing 1-flash as the default for P3 is to give a 3.3v output (i.e. go high) when Channel 3 goes low. We need to change this to start high and go low when Ch3 goes low, so we need to change this value to 4-flash by incrementing the flashes by three reverse or down clicks and then accepting the 4-flash by clicking forward or up.

If you accidentally increment the number of flashes by too many, then keep incrementing until the LED reverts to 1-flash, then increment to the desired value.

 After entering the final value in our list, the LED should stop flashing and revert to solidly on.

To program another pad, we need to re-enter programming mode with the SOS morse code sequence on the bind button.

All that might sound a bit daunting but, once you've done it a couple of times, it is really easy - albeit slightly tedious.

Here's proof that all that effort is worthwhile.

 

Deltang or RC Trains transmitters

Deltang or RC Trains receivers with reversing switches can also be used to reprogram Micron receivers provided they will bind with the receiver. Some of the very early Deltang receivers are unable to bind with Micron receivers and will need their transmitter boards replacing to enable them to do so. This is a job which can be done by Andy at Micron or by Phil at RC Trains. Alternative, if you are handy with a soldering-iron, it is a relatively straightforward job you can do yourself, once you have purchased the Micron transmitter module.

 

 

How I reprogrammed a Deltang Rx102 with a Prog3

Introduction

The Deltang Rx102 receiver can be reprogrammed to change the default servo outputs from the pins to on/off outputs. This means that......

• LEDs connected to the receiver can be turned on and off remotely by a transmitter, 
• other devices can be operated through a relay 
• or sound effects on sound cards can be triggered 

 ....... by pressing buttons, flicking switches or wiggling joysticks on your transmitter.

In my case, I wanted to reprogram my Rx102 so that it could be used to trigger the additional sound effects on a MyLocoSound steam soundcard, including as the whistle and safety valve.

Most sound cards which have additional sound effects (eg the MTroniks DigiSound, the Dallee and the Phoenix sound cards) require their inputs to be connected to 0v to trigger these additional sounds (see How to interface sound cards with Deltang receivers). Some receivers, such as the Deltang Rx65b are already programmed to provide 0v outputs for sound triggers, but the Rx102 does not. However, with a Deltang Prog3, reprogramming the outputs of the Rx102 is relatively easy.

Before ploughing through the instructions set out below, I would suggest you watch the video which I have made, demonstrating the process. It should, hopefully, make what follows a lot more understandable.

Contents

1. Preparations
2. Binding the receiver to the Prog3
3. Programming the Prog3
4. Transmitting the instructions from the Prog3 to the receiver
5. Checking
6. Conclusion

1. Preparations

 i. Deciding what you want to do

The first job is to decide what you want the outputs from the receiver to do. You can change any of the outputs to give:

• Servo outputs
• On/Off outputs
• Auto directional lighting outputs

The default outputs from the signal pins on the receiver are:

Pin 1 - Servo output in response to Channel 1 on the transmitter
Pin 2 - Servo output in response to Channel 4 on the transmitter
Pin 3 - Servo output in response to Channel 3 on the transmitter
Pin 4 - Servo output in response to Channel 2 on the transmitter
Pin 5 - Servo output in response to Channel 5 on the transmitter
Pin 6 - Auto directional lighting (forward)
Pin 7 - Auto directional lighting (reverse)
Pin 8 - Servo output in response to Channel 4 on the transmitter (Pin 8 is located on the side of the receiver)

So, any pin on the receiver can be reprogrammed to respond to any Channel in any way you choose.

I decided that I wanted my receiver to be reprogrammed to give:

• 0v on Pin 5 when Channel 5 went low (ie when the Bind Button on my Deltang transmitter was pressed)
• 0v on Pin 4 when Channel 3 went high (ie when the Direction Switch on my Deltang transmitter was clicked in reverse)
• 0v on Pin 3 when Channel 3 went low (ie when the Direction Switch on my Deltang transmitter was clicked forward)

 My next task was to consult the programming chart for the Rx102 on the Deltang website to discover what codes needed to be sent to the Rx102 to effect the changes I wanted.

ii. Consulting the programming chart

At first sight, the chart on the website can look a bit daunting. However, it actually makes a lot of sense when you work out how the various columns map on to the things you want to change on the receiver.

The part of the chart which was of interest to me was the second row (shown in bold):

2. PROGRAMMING OPTIONS:

Level 1	Level 2 Output number	Level 3 Output type	Level 4 Channel number	Level 5 Other choices	Information
1 flash	1-8 flash = P1-8	1 flash = Servo	1-7 flash = Channel 1-7		(eg: 1,2,1,4 = P2, Servo, Ch4)
1 flash	1-8 flash = P1-8	2 flash = On/Off led	1-7 flash = Channel 1-7	1 flash = ON when Ch is low 2 flash = ON when Ch is mid 3 flash = ON when Ch is high 4 flash = OFF when Ch is low 5 flash = OFF when Ch is mid 6 flash = OFF when Ch is high	Off in other positions (eg: 1,3,2,5,1 = P3, On/Off, Ch5 Low ON) On in other positions (6 options from v110-3)

The first column just tells the receiver the menu from which we are selecting our instructions. For the Rx102 there is just this one menu (for the Rx65b there are 13 different menus). The first code number is therefore 1.

The second column determines which output pin we want to change. I decided to start off by changing Pin 5 as I wanted to use this to trigger the whistle sound effect when the bind button on the transmitter is pressed. So, the next number I needed in my list of instructions for the receiver was 5 (ie pin 5)

The next column tells the receiver what action you want it to perform on the chosen pin. I wanted the on/off option (rather than controlling a servo or have directional lighting) and so my next instruction code for the receiver was 2.

The fourth column determines which Channel the pin on the receiver will respond to. In my case, I was wanting Pin 5 to respond to Channel 5 (ie the Bind Button) and so my fourth instruction was 5.

The fifth column tells the receiver how it must respond when receiving a signal on the chosen channel. In my case, I wanted the pin to give 0v when the Bind Button was pressed. Pressing the Bind Button on the transmitter makes Channel 5 go low - so I needed to use instruction 4 (ie turn OFF the output from Pin 5 when the signal from the transmitter on Channel 5 goes low).

iii Working out the codes I needed to send to the receiver

This gave me the following series of codes for the receiver:

1, 5, 2, 5, 4

ie:

• 1= Menu 1
• 5 = Pin 5
• 2 = On/Off
• 5 = Channel 5
• 4 = 0v when the channel goes low

For my the other changes I wanted to make to the receiver, the codes are:

 1, 4, 2, 3, 6

ie

• 1 = Menu 1
• 4 = Pin 4
• 2 = On/Off
• 3 = Channel 3 (Direction switch)
• 6 = 0v when the channel goes high (ie when the direction switch is in reverse)

..... and

 1, 3, 2, 3, 4

ie

• 1 = Menu 1
• 3 = Pin 3
• 2 = On/Off
• 3 = Channel 3 (Direction switch)
• 4 = 0v when the channel goes low (ie when the direction switch is forward)

You might need to take a little while to grasp the logic of this - particularly how the values in the fifth column relate to the response you want to get when a button, switch or joystick is operated on the transmitter. Just remember, that moving a joystick, flicking a switch or pressing a button will make a particular channel go high or low (or higher or lower if it is a proportional control).

2. Binding the receiver to the Prog 3

The Prog3 is very much a stripped down transmitter and so the bind process is similar to any transmitter.

The first job is to put the receiver into bind mode. I had an earlier version of the Rx102 which requires a manual approach to putting the receiver into Bind Mode.

1. The receiver was turned off.
2. The large (black) bind plug was connected to signal pins 5 and 7

3. The receiver was turned on
4. The LED on the receiver flashed rapidly showing it was in Bind Mode
5. The Bind Plug was removed

NOTE: If you have one of the later Rx102s (marked Rx102(AB)) then it will go into Bind Mode automatically. Make sure the transmitter and Prog3 are turned off. Turn on the receiver and wait ten seconds. The receiver should go into Bind Mode (ie the LED on the receiver should flash rapidly).

To put the Prog3 into Bind Mode, I:

1. Held the Bind Button on the Prog3 down
2. Turned on the Prog3 (with the button still held down)
3. Released the Bind Button
4. The LED on the Prog3 and the LED on the Rx102 flashed once a second
5. When the LEDs stopped flashing the bind process was completed.
6. The LED on the Rx102 started flashing three times, then pause, three times, etc to show it was communicating with the Prog3

NOTE: Sometimes the bind process doesn't work first time. If so, turn off the receiver and the Prog3 and try the process again, moving the receiver and Prog3 to a different orientation. Also make sure there are no other transmitters on close by.

I then turned off the Rx102 to make sure I didn't accidentally reprogram it before I was ready.

3. Programming the Prog3

The Prog3 needed to be programmed with the first of the codes shown above (ie 1, 5, 2, 5, 4)

The first five pins on the Prog3 represent the five columns (or Levels) on the programming chart. So, I needed to change the values on each of the pins to those needed to reprogram the Rx102.

The 'values' on each pin are shown as a series of flashes of the LED on the Prog3.

• 1-flash means the value on that pin is 1, 
• 2-flash means it's 2, 
• 3-flash means it's 3,
• and so on........

 To change the values on each pin, we use the Bind Plugs which come with the Prog3. The Large Black Bind Plug increases the number of flashes on the pin it's connected to. The Small Red Bind Plug decreases the number of flashes on the pin.

When a Prog3 is delivered new, the values on each pin are 1, and so the Large Black Bind Plug is needed to increase them.

To check the value on Pin 1, I connected the Large Black Bind Plug to Signal Pin 1 and Negative Pin 1.

The LED started by flashing once, then pausing, showing the pin had the expected value of 1. I quickly removed the Bind Plug so it wouldn't increase to 2. (If it had, I would have used the Red Bind Plug to reduce it - the Red Bind Plug is connected to Signal Pin 1 and Positive Pin 1 (ie the middle pin)).

To change the value on Pin 2, I connected the Large Black Bind Plug to Signal Pin 2 and Negative Pin 2.

The LED gave 1-flash when it was connected, it then repeated 1-flash and went on to 2-flash, repeated, then 3-flash, repeat, 4-flash, repeat, then 5-flash. At this point I removed the Bind Plug and the LED repeated its 5-flash before going out. This showed the value on Pin 2 was now 5, as required.

I repeated the process of putting the Large Black Bind on Pin 3 until it showed 2-flash. Then Pin 4 until it showed 5-flash and finally Pin 5 until it showed 4-flash.

To 'fix' these values, the Bind Button was pressed on the Prog3.

The Prog3 was now ready to transmit the information to the Rx102.

4. Transmitting the information from the Prog3 to the Rx102

I first checked that the transmitter to which the Rx102 had been bound was off. It's not essential, but it is advisable so that nothing untoward happens.

The Rx102 was switched on and I waited until it started flashing three times, pause, three times etc, to show it was in communication with the Prog3.

I then pressed the Bind Button on the Prog3 and the LED on the Rx102 flashed rapidly to show it was receiving the information.

I released the Bind Button and the LED on the Rx102 returned to 3-flash.

The programming was now completed.

I turned off the Rx102 to make sure the new instructions were processed and also turned off the Prog3

5. Checking

To make sure all was well, I wanted to check that the instructions had been correctly transmitted and also that they were giving the output I was expecting.

I turned on the transmitter to which the Rx102 had previously been bound (in my case a Tx20) and then turned on the Rx102.

Once the LED on the Rx102 was glowing steadily, showing it had 'found' the Tx20, I connected an LED to Pin 5 of the Rx102. I had wired up an LED to a servo plug, the white lead (yellow on other servo leads) to the +ve leg of the LED and the black lead (brown on other servo leads) to the -ve leg of the LED. There is no need to connect a resistor in series with the LED as the Rx102 outputs are buffered with suitable resistors. The middle red lead was left unconnected.

When initially connected, the LED glowed, showing it was receiving 3.2v from the receiver (ie the output from Pin 5 was on).

I then pressed the Bind Button on the Tx20 and the LED went out - showing the output from Pin 5 was dropping to 0v. As expected.

I then reprogrammed the other two pins in the same way

Conclusion

The ability to reprogram the outputs of the Rx102 makes them even more versatile. There is no need for additional circuitry connected to the output pins for switching on lighting or accessories or triggering sound effects.

NOTE: The switched outputs are non-latching and so some sort of circuitry will be needed if the switch on the transmitter is also momentary. A latching flip-flop module such as this (£3 each on eBay) can be connected to the pin to provide a latching output.

See - How I created latching on/off outputs from a Deltang Rx102 receiver or see How I used a latching flip flop switch with reed switches for lighting circuits in my coaches)

How I reprogrammed a Deltang Rx102 with a Prog4 module to operate a MyLocoSound sound card

Preamble

Although I have previously written a post about reprogramming the Rx102 receiver (see How I reprogrammed a Deltang Rx102), things have changed a little since then and so I felt it was time I replaced that post with a more fully detailed, up to date version.

I wanted to reprogram an Rx102 receiver so that I could use spare pins to trigger the effects on a MyLocoSound sound card. The MyLocoSound card (like most sound cards) need a 0v signal to trigger additional effects. The default outputs from the Rx102 are either for servos (on Pins 1 to 5) or for directional lighting (on Pins 6 and 7). As I wanted to use my Deltang Tx22 transmitter to trigger the effects, I wanted to use the Bind Button (Channel 5) and the Direction switch (Channel 3) as sound effect triggers. For more information on interfacing the MyLocoSound card with Deltang receivers see How to interface Deltang receivers with sound cards - MyLocoSound

The outputs could just as easily be reprogrammed to provide 3.2v positive outputs to power LEDs eg for interior lighting (see below). There is no need to include a load resistor when wiring up LEDs to the signal pins of the Rx102 as the receiver outputs include appropriate resistors.

Contents

• The Prog4 Programma module
• Installing the software (on a Windows 10 PC)
• Setting up CoolTerm
• Binding the receiver to the Prog4
• Creating the text files
• Sending the text files to the receiver
• Checking

The Prog4 Programma module

 The Prog4 (like the Prog1, Prog2 and Prog3) is a modified Rx102 receiver. The most significant difference is that the Prog4 has a rather prominent push button mounted on one side. This is the bind button (on the other Prog modules, it is also used for transmitting the programming instructions).

The Prog4 needs to be connected a computer with an RS232/USB (CH340) cable.

I got mine via eBay by searching for PL2303TA TTL to RS232 Converter Serial Cable
. The first one I purchased failed to work (not sure why) but the second one (and a third) worked well so it might be worth persevering if things do not work out OK the first time you try.

When it arrived, I connected the lead to the Prog4:

• Black lead to the Bottom Pin 7
• Red lead to Middle Pin 7
• Green lead to Upper Pin 7
• White lead to Upper Pin 6

Installing the software (on a Windows 10 PC)

Before installing the software, I needed to download and install a driver for the interface cable. This was downloaded from https://serialio.com/drivers-and-set-up-usb-rs-232-adapter-in-windows. As indicated on the web page, once the .EXE file was downloaded and saved, I had to install it 'as an administrator'. I right-clicked on the saved file and selected 'Run as administrator'.

Once that was installed I downloaded CoolTerm from http://freeware.the-meiers.org/ . The zipped file needed to be extracted which I did by right-clicking and selecting Extract all.

 I dragged the resultant folder on to my desktop so that I would know where to find it in future (the program does not install to the programs list in the Windows menu).

Setting up CoolTerm

Before starting up the program, I inserted the USB lead into a USB socket. The driver had installed successfully (I had rebooted the computer to make sure) and so there were no error messages. The LED on the Prog4 came on to show it was connected.

In the CoolTerm folder on the desktop were a couple more folders and the CoolTerm.exe file. I doubled clicked this to start up the program.

The program loaded OK and the LED on the Prog4 started flashing 3 times, then pause, three times, etc. (ie 3-flash) to show the software was communicating with it.

Before using the software, I needed to set it up for the Prog4. Clicking on the Options Button ......

.......... took me to the Options screen.

On my computer and with my USB socket, the Prog4 was showing up as COM3. You might need to click on the 'Re-Scan Serial Ports' button to get your Prog4 to show up. If it doesn't you might need to try another USB socket (or buy another lead - see above). Your USB lead/Prog4 might show up on a different port (it was COM7 on my old laptop).

The settings needed to be changed to those above, ie:

• Baud rate = 115200
• Data bits = 8
• Parity = Even
• Stop Bits = 1
• XON check box ticked

I also clicked on the 'Receive' settings and ticked the Ignore receive signal errors check box.

The program was now ready to send information to the Rx102

Binding the receiver to the Prog4

Before the programming info could be sent to the Rx102, the receiver needed to be bound to the Prog4. The receiver was put into Bind Mode by connecting the black bind plug (supplied with the receiver) across signal Pins 5 and 7 (ie the uppermost row) and turning on the receiver.

The LED on the receiver started flashing rapidly showing it was in Bind Mode and so I removed the bind plug.

I removed the Prog4's USB plug from the computer and then, holding down the bind button on the Prog4, I re-inserted the USB plug - this puts the Prog4 into Bind Mode.

I removed my thumb from the bind button and the LEDs on the Prog4 and the Rx102 flashed once a second in unison and then after a few seconds they both started flashing three times and pausing, three flashes, pause, etc. The Prog4 and the Rx102 were now bound together (Note: if the Rx102 had previously been bound to a transmitter such as the Tx22, it will not forget that bind).

The Prog4 was now ready to reprogram the receiver.

Creating the text files

The easiest way to reprogram a receiver with the Prog4 is to create a series of text files with the instructions for the receiver. I wanted to set up my Rx102 so that I could use the bind button and direction switch on my Tx22 transmitter to trigger sound effects on a MyLocoSound sound card. The Bind Button sends Channel 5 low when it is pressed and the Direction Switch sends Channel 3 high or low depending on which way it is switched.

To discover what instructions need to be sent to the receiver, I consulted the table for the Rx102 on the Deltang website. (click on the image to enlarge it).

This table showed that the codes needed to reprogram pin 5 on the receiver were:

1,5,2,5,4

• 1 = menu one
• 5 = Pin 5
• 2 = on/off
• 5 = Channel 5
• 4 = Off when the channel is Low

In other words, when the Bind Button is pressed on the transmitter (sending Channel 5 low), the receiver will turn off the output from Pin5 (ie the output from Pin5 will become 0v)

The codes for the Direction Switch were:

1,3,2,3,6

ie. The output from Pin3 will become 0v when the Direction Switch is flicked in reverse (ie sends Channel 3 high).

And.......

1,4,2,3,4

The output from Pin4 will become 0v when the Direction Switch is flicked forward (ie sends Channel 3 low).

I used Notepad on my computer to create the text files (if you can't find it, type Notepad into the search box on the bottom left of the screen and press return). NOTE: Although you can save text files from MS Word, the files include all sorts of additional gobbledegook which could confuse the Prog4.

The text file for the Bind Button instructions........

The text file for the Reverse Direction Switch ......

and the text file for the Forward Direction Switch......

 Each text file was saved (in a folder inside the CoolTerm folder) so they could be used later.

Sending the text files to the receiver

 With the receiver bound to the Prog4 and the Prog4 communicating with the computer through CoolTerm, I was now ready to send the instructions to the Rx102.

I needed to unplug the USB lead and re-insert it because the Prog4 had gone to sleep. It switches off after 5 minutes if nothing is happening.

The first job was to open the connection between CoolTerm and the Prog4. I clicked on the Connect button.

Once connected, I then clicked on the Connection menu and selected Send Textfile...

I navigated to the folder where I had stored the text files and then clicked on the first of them and clicked the Open button.

The information in the text file was sent from the computer to the Prog4 and then on to the Rx102.

The other two text files were also sent in the same way. I got a series of messages in the CoolTerm window to show the files had been transmitted OK

Note: these messages do not always appear straight away, even though the files have been transmitted successfully. The best way to find out if they have worked is to check the receiver (as below).

The receiver was turned off (to save the changes).

Checking

 To check that the receiver had been programmed correctly, I wired-up an LED to a servo plug. There is no need to include a resistor with the LED as the Rx102 includes load resistors in the circuitry for the output pins. The black lead from the servo plug was connected to the negative leg of the LED and the white (or yellow) lead was connected to the positive leg of the LED. The middle (red) lead from the plug was left unconnected.

The receiver was bound to the Tx22. The LED was connected in turn to Pins 3, 4 and 5 and the relevant button or switch operated on the transmitter. When first connected, the LED glowed steadily but when the switch or button was operated on the Tx the LED was extinguished showing the output was going from 3.2v to 0v.

I will attempt to make a video showing this process but it will have to be a combination of screen captures and live action and so it might take a while to figure out the best way to achieve this. In the meantime, I hope the information above is useful.

Progress Report 71

Introduction

We don't seem to have had much of a summer in terms of fine weather - and it also seems that when the weather was good I was elsewhere. We spent a long weekend, for example, in Yorkshire where I drove a steam loco on the Elsecar Heritage Railway as part of my birthday present.

However, I have managed to complete some projects and engage in a few operating sessions since my previous Progress Report, and also hosted a visit from another of my Antipodean friends.

Permanent Way

Apart from ongoing maintenance, the only significant development in the Permanent Way Dept has been to iron out a hump in the track just outside Bulkeley station. 

Many moons ago, when I first built the railway, I constructed a wall from breeze blocks and bricks to support Bulkeley station. I wasn't entirely sure at that time where the tracks would run and it turned out that the wall cut across the track leading from Bulkeley down towards Bickerton. Over the years, the trackbed at Bulkeley has dropped by around 1.5" but, of course, the wall has remained the same height. Last week, I decided this hump also had to go and so the brickwork on top of the wall was attacked with a cold chisel and angle grinder.

Once the hump had been eliminated, a layer of concrete was put down to smooth out some of the irregularities in the underlying blockwork. I find this is easier than lifting the blocks, tamping down the soil and relaying the blocks - only to find they will sometimes sink again as the soil settles.

Most of the stock had little problem negotiating the hump previously, but occasionally a wagon might become derailed passing over the point leading to the Copper Mine branch. Time will tell if this has solved this particular problem.

Lineside

 Refreshment Room

To fill a gap on the approach to the station building at Beeston Market, I decided to construct a small refreshment room, based on a building which used to stand beside the overbridge below Beeston & Tarporley Station on the Crewe to Chester mainline railway between the two world wars.

Using dimensions derived from the photo, plus a modicum of modellers' licence, I drew up a sketch plan and constructed the building primarily from plasticard.

It is still awaiting interior detailing and needs to be sited on the vacant plot beside the station at Beeston Market, but I am pleased with the result so far. For more information on the build see How I constructed the Refreshment Room.

Water mill

Another vacant plot on the railway is in the process of being occupied. For a while, I have been planning to construct a water mill to sit beside the stream near Peckforton (eg see Progress Report 41). Over the past couple of months, this building has slowly been taking shape.

The first stage was to remodel the stream to create a mill stream (see How I revamped part of the stream). Once that had been done, the area between the stream and the mill siding was landscaped.

 
Meanwhile, the building itself was slowly taking shape. I used PVC foamboard for the main structure - a new material for me and one with which I am most impressed.

The building and its location are taking shape - more work is required on detailing and a sluice gate needs to be constructed to control the flow of water under the wheel.

[Awaiting photo]

For more information see How I constructed the mill - pending

Operation

Market Day

A few minor operating sessions have taken place since the past progress report and one full scale operating session. In this session, I imagined it was Market Day and so extra trains were laid on to accommodate the increase in passenger numbers and the additional livestock and farming related traffic.

The Up Market Day Mixed passing the Copper Mine hauled by Bagnall 0-4-2T No. 11 Bunbury

Down Special Market Day Goods approaching Beeston Castle with Beyer Peacock(ish) 0-4-0T No. 12 Tiverton

The Up special goods returning passing the River Gowy

The Down Market Day Mixed arriving at Bickerton

The scheduled midday Up passenger arriving at Beeston Market

The Up pickup goods approaching Beeston Castle with Black Hawthorn 0-4-0T No. 14 Burwardsley

A short video showing some of the Market Day Train movements

Visitor from New Zealand

During one of my operating days, I was ably assisted by Andy Murray (the other Andy Murray) from New Zealand who was over on a family visit. He took charge of the pickup goods, carrying out shunting duties as it passed up and down the line.

Many thanks to Andy for his company and his patience.

Post Script

I received a request from a fellow modeller for assistance in setting up his MyLocoSound steam sound card - particularly regarding the settings for getting a loco to coast when slowing down. I felt the easiest way to demonstrate this was to make a video.

This video now also features on the MyLocoSound website.

I am hoping to take delivery shortly of the latest version of the MLS soundcard which incorporates brake squeal when the loco comes to a halt.

<< Go to Progress Report 70