EzCoder VERSION-INFO.TXT file for the RC1000 and RC1000V repeater controllers 1/17/05 JM The RC1000 and RC1000V controllers produced by Micro Computer Concepts have undergone numerous firmware updates over the years. While most of the programming codes have remained the same from the early versions, certain functions have changed and require that different parameters be used in order for the EzCoder program to properly set the codes on the controller. This file will attempt to point out the various changes that are known to exist between various versions of the controller. In no way is this file the complete and ultimate guide on this issue-- but is a 'best effort' made by perusing the documentation on a half dozen units ranging from firmware version 2.20 (June 1992) to version 4.7 (November 2000). Where documentation on a specific firmware revision is available, there is a custom data file provided for use with EzCoder that reflects the commands available to work with that version of the firmware. Currently, data files are available to cover versions 2.20, 4.3, 4.4, 4.7 . If you have documentation for a version not listed and are willing to donate a copy 'for the cause', please let us know and we can include it here for the benefit of all EzCoder users. The data file for EzCoder is a standard text file using comma delimited fields. The file extension was changed to 'TX1' just to make it easier for users of EzCoder to see valid controller data files when they were browsing with the 'FILE OPEN' command-- and not have to wade through a bunch of regular text files in the display. You should open the RC1000V.TX1 file and take a look at how the data is arranged. It is fairly easy to accommodate the firmware revisions of the RC1000's by making minor text changes to the file and then saving it appropriately. The data fields in the 'TX1' data files are seperated by commas and are arranged as follows: The first field (up to the first comma) is the index number of the command. This corresponds to which button the command will appear on and only has to do with its location on the screen of the EzCoder and EzControl programs. The second field (between the first and second commas) is the text that is to display on the description for the command. If this text is 'ZZZA' then that command does not appear on screen. The third field (between the second and third commas) is the four digit programming code that MCC has specified to program the access code for that command. The fourth field (between the third and fourth commas) is the desired command code to access a command. If you are looking at the default or 'original' files, you will see that most of these just contain A,D,*, or # as nothing is programmed into most fields from the factory. Once you view a configured data file it is this fourth field that will contain all your personalized command codes. The fifth field (between the fourth and fifth commas) is a number denoting the length of the code that is required in that position. The sixth field (between the fifth and sixth commas) is the required first character for the command code. If this character is shown as a '9' then there is no checking of the first character done by EzCoder. The seventh field (between the sixth and seventh commas) is the text to be displayed by the tool tips that pop up if your mouse hovers above the command field on the screen for more than a second. Please note that for record numbers 80-99 (that is, if the first field number is 80 to 99 inclusive) the text that is written in the data file is used to display in various ancillary positions of the EzCoder program and will not normally need to be changed to reflect variations in the RC1000 firmware. Record number 85 contains the CWID programmed callsign information. Record numbers above 100 contain the autodial information. The EzCoder was written to accommodate the version 4.4 firmware that had provisions for 95 autodials. If your firmware does not have that many autodials available the extra functions will not work-- even though they may show up on screen. Please also note that if you are switching between default files you will need to exit the program and restart it for all the proper command windows to be open as they should. This quirk will be repaired in forthcoming releases, but it is the reality with the current beta release 0.1.1 . The program was written not expecting to find its use dealing with multiple versions of the MCC RC1000 firmware during a single programming session. FIRMWARE REVISION NOTES: v2.20 (pre RC1000V) 1992 vintage. This version had the ability to select between internal CWID's and an external ID unit of the repeater owners installation. The digital voice ID unit may have been an option back when this unit was first sold, I'm not certain. When the external ID function was enabled a TTL output would strobe low for 3 seconds to trigger the device (perhaps an old broadcast cartridge tape player, etc). It was hard coded that the ## command would trigger the external tape device. The CWID was setup so you could force a CWID with the #9 command (also hard-wired). There was no 911 enable/disable. There were no autodials. No 'PL override', DTMF access, 'PL control' mode, and the autopatch timeout was different as was the method to program repeater status into the CWID. The remote base TX enable was hardcoded to toggle between enabled/disabled with the '*#' code. V2.5? This version is mostly similar to the 2.20 firmware but adds in the ability to disable 911 calls, adds the DMTF access mode, a PL override mode, and the ability to disable the timeout timer. v3.0? This version adds the autodials to the patch. It also is the first version to lack 'tape' support. It adds a duplex autopatch mode and a reverse patch signal. It is the first firmware to allow the 'PL control' mode where a PL tone is required to access control functions. Additionally a special 'remote base beep' is available to signal the remote base is turned on. v4.4 and V4.3 This version adds the ability to program the remote base transmit enable code, the forced CWID code, and the forced voice ID code. It also allows you to program the 'patch outside line digit' for those who use a PBX telephone system that requires a number other than '9' to get an outside line. V4.7 The ability to use extra * command functions in place of the # functions is added (sadly, not implemented at all in EzCoder!). This is where you could use a *XX instead of a #X for what had previously been restricted to just #X two digit command codes.