kopia lustrzana https://github.com/SP8EBC/ParaTNC
new readme, schematics, partlist etc
rodzic
befdd40e66
commit
0732b2fd23
54
README
54
README
|
@ -1,19 +1,57 @@
|
|||
ParaTNC version DE00, September 10th 2019
|
||||
ParaTNC version DE06, January 5th 2020
|
||||
-----------------------------------------
|
||||
|
||||
1. INTRODUCTION
|
||||
ParaTNC is a software (hardware design coming) intended to work on STM32F100RB microcontroler and cheap STM32VLDISCOVERY
|
||||
evaluation board as an multi function APRS controler. It supports key elements of what good APRS device should have:
|
||||
ParaTNC is a hardware and a software which offers the functionality of multi function APRS controler.
|
||||
The software itself can also run on cheap STM32VLDISCOVERY board with slightly reduced functionality, but
|
||||
with costs about 10..12 euro this gives the cheapest possible standalone APRS controller.
|
||||
|
||||
ParaAPRS supports key elements of what good APRS device should have:
|
||||
-> Two directional KISS TNC (no init strings required).
|
||||
-> WIDE1-1 digipeater, with an option to limit digipeating only to SSIDs 7, 8 and 9.
|
||||
-> Weather station with support for various meteo sensors like: DS18B20 for temperature, MS5611 for pressure, LaCrosse TX20 for wind and DHT22 for humidity.
|
||||
-> Extensive telemetry with an information about the count of receved, transmitted and digipeated frames plus status of weather sensors.
|
||||
-> Support for VE.Direct serial protocol used in Victron PV charging controllers. The data about currents and voltages in the PV system are transmitted using APRS telemetry.
|
||||
|
||||
2. LICENSING
|
||||
ParaAPRS can be used as a standalone weather station controller w/o using the radio transmission. The sw
|
||||
by default sends the measuremenets values
|
||||
|
||||
2. ParaAPRS HARDWARE
|
||||
The ParaTNC software can run on STM32VLDISCOVERY board but it really shows it full potential od it's own
|
||||
dedicated hardware. This not only rub out all bodge wires required with prototype board. It gives
|
||||
few features which are hardly not possible without dedicated PCB
|
||||
a) Three different grounds separated one from the another
|
||||
-> Controller
|
||||
-> DB9 connector used to interface with a radio
|
||||
-> Wind and temperature sensor
|
||||
b) Isolated DC-DC coverter to supply sensors with an option to connect another external power supply itself
|
||||
c) A relay used as a watchdog to reset wind & temperature sensor in case that no communication will be received.
|
||||
d) RS232 serial port avaliable on Cisco style RJ45 connector
|
||||
e) PCB designed to fit into Mikrotik RB411/RB711 enclosure.
|
||||
|
||||
ParaTNC PCB could be manufactured used a set of generber files locates in ./hardware/ directory a long with schematics and
|
||||
layout renders (top and bottom layer).
|
||||
|
||||
3. CURRENT OPEN POINTS AND ISSUES RELATED TO HW & SW
|
||||
As usually every design has some flaws, less or more important. In case of ParaTNC they can be divided into two
|
||||
parts, separately for software and hardware. Firstly in case of software an end user should USE ALWAYS THE SOURCE CODE
|
||||
WITH THE NEWEST TAG marked as non-beta (like DE06). ParaTNC repository is used for daily development, so the last commit
|
||||
can even sometimes don't compile at all, or consist some major bugs.
|
||||
|
||||
Hardware workarounds for now are
|
||||
-> Missing resistor in series with base of transistor T2. External 1k must be added in series with TX line
|
||||
-> Foortprint location of R7 (RX_LVL) and R8 (TX_LVL) helipots are 'not optimal'. If 'normal' pots are to be used the vertical
|
||||
version must be chosen as flat one won't fit due to neighbouring components location.
|
||||
-> J1 power-in jack has reversed polarity (negative center)
|
||||
-> The chineese manufacturer dropped the TX20 anemometer from the production which means that a supoprt to it
|
||||
became a little bit obsoloete for new installations. Support for Davis 6410 anemometer or any another with
|
||||
pulse output for windspeed and potentiometer (resistance output) for direction is ongoing and should be
|
||||
avaliable in HW-Revision B and further SW releases.
|
||||
|
||||
4. LICENSING
|
||||
ParaTNC software and hardware are licensed under terms included to the source code in 'LICENSE' file
|
||||
|
||||
3. SUPPORTED FEATURES OD VE.Direct PROTOCOL
|
||||
5. SUPPORTED FEATURES OD VE.Direct PROTOCOL
|
||||
Most of Victron devices have a support both for binary and text serial protocol. By default the text procol (VE.Direct) is
|
||||
always enabled and a device will send from its own telegrams each couple of seconds. The communication via VE.Direct is
|
||||
avaliable through dedicated socket on the charging controller which is just 3.3V TTL levels UART, so no external ICs is
|
||||
|
@ -33,7 +71,7 @@ limitations. Only these parameters are transmitted:
|
|||
-> Charging Controller status (like current charging mode) and minimum/maximum battery current in last 10 minutes.
|
||||
-> Error Codes if any (short circuit, overheat, overvoltage on PV or battery input)
|
||||
|
||||
4. TELEMETRY
|
||||
6. TELEMETRY
|
||||
If the VE.Direct protocol suppot is disabled the ParaTNC uses telemetry packets to send internal statistics and
|
||||
general information about communication with sensors. Telemetry works in 10 minutes cycle, which means that packets are sent
|
||||
every 10 minutes and they represents a state for the time between one and another.
|
||||
|
@ -62,7 +100,7 @@ NOT AVALIABLE after the telemetry packets are sent.
|
|||
The TX20 anemometer driver has a Slew Rate Limiter which keeps out all 'spikes' in values mostly due to RF interference. if the
|
||||
difference between two consecutive measuremenets excedes hardcoded limit (9m/s) the software drops the value.
|
||||
|
||||
5. CONFIGURATION
|
||||
7. CONFIGURATION
|
||||
At this point ParaTNC is delivered in form of source code which needs to be manually compiled by the user. Most options are
|
||||
configured by #define in './include/station_config.h' and then hard-coded by the C preprocessor during compilation. An example file
|
||||
consist a lot of comments which explains what is what, but generally an user can choose there which mode should be enabled:
|
||||
|
@ -77,7 +115,7 @@ one UART in the micro. The KISS modem runs on default speed of 9600 bps. Telemet
|
|||
trasmit channels values each 10 minutes and full channel descriptions each 70 minutes.
|
||||
|
||||
|
||||
6. TOOLCHAIN AND COMPILATION
|
||||
8. TOOLCHAIN AND COMPILATION
|
||||
To build ParaTNC software 'GNU ARM Embedded Toolchain' is required. This set contains gcc-arm-none-eabi compiler,
|
||||
gdb debugger, linker, HEX generator and set of libraries. ParaTNC is developed in Xubuntu 16.04LTS using 2016q-3
|
||||
version. It shoud work fine in any newer version of the toolchain. The easies way to get everything installed
|
||||
|
|
Plik binarny nie jest wyświetlany.
Ładowanie…
Reference in New Issue