36
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + − − '''*'''see below Line 17:
Line 15: − + + + + + + + Line 28:
Line 32: − + − + −
no edit summary
The [http://www.micro-node.com/thin-m1.shtml Micro-Node Radio Thin Client Module (RTCM)] is the commercial version of the VOTER. It uses surface mount parts (SMT), but is functionally equivalent to the original VOTER.
The [http://www.micro-node.com/thin-m1.shtml Micro-Node Radio Thin Client Module (RTCM)] is the commercial version of the VOTER. It uses surface mount parts (SMT), but is functionally equivalent to the original VOTER.
In general, the two terms (RTCM/VOTER) are used interchangeably, as they operate the same, and use the same firmware'''*'''.
In general, the two terms (RTCM/VOTER) are used interchangeably, as they operate the same, and use the same firmware (mostly, see below).
This page will highlight some of the operational concerns, quirks, bugs, and other items of interest that relate to these interfaces. Much of the information has been gleaned off the AllStar mail list, comes from personal experience, or comes from notes in the firmware source code.
This page will highlight some of the operational concerns, quirks, bugs, and other items of interest that relate to these interfaces. Much of the information has been gleaned off the AllStar mail list, comes from personal experience, or comes from notes in the firmware source code.
The VOTER uses a dsPIC33FJ128GP802 and the RTCM uses a dsPIC33FJ128GP804.
The VOTER uses a dsPIC33FJ128GP802 and the RTCM uses a dsPIC33FJ128GP804.
Current firmware (.cry file) is available here: https://github.com/AllStarLink/voter/tree/master/board-firmware
There are '''two parts''' to the firmware, a bootloader, and then the actual firmware file. The bootloader starts when power is applied, and allows you to talk to the dsPIC and load new firmware files over ethernet. If the bootloader is not intercepted by the loading tool, it will continue to boot the current firmware file.
All new boards will need to have the bootloader installed first, followed by a firmware file. You '''can''' load a firmware file directly (.hex) in to the dsPIC, but then you will not have any of the bootloader remote loading features.
The current bootloader (.cof file) is available here: https://github.com/AllStarLink/voter/tree/master/voter-bootloader (the -smt file is for the RTCM). It needs to be loaded with a PICKit programmer.
Current firmware (.cry file) is available here: https://github.com/AllStarLink/voter/tree/master/board-firmware . They are loaded with the EBLEX C30 Programmer.
There are multiple "flavors" of firmware available. See below for further explanation of what all the options mean.
There are multiple "flavors" of firmware available. See below for further explanation of what all the options mean.
==Compiling Environment==
==Compiling Environment==
If you look in the votersystem.pdf, you will find a procedure to modify and load the bootloader in to the dsPIC of a VOTER board.
If you look in the [https://github.com/AllStarLink/voter/blob/master/votersystem.pdf votersystem.pdf], you will find a procedure to modify and load the bootloader in to the dsPIC of a VOTER board.
Unfortunately, there is an important step missing in that procedure, which is covered below.
Unfortunately, there is an important step '''missing''' in that procedure, which is covered below.
In addition, the old links for the MPLAB software are dead, so let's update this info and get you going.
In addition, the old links for the MPLAB software are dead, so let's update this info and get you going.
Currently (Feb 2017), you can get the required software from:
Currently (Feb 2017), you can get the required software from:
http://www.microchip.com/development-tools/downloads-archive
http://www.microchip.com/development-tools/downloads-archive