BEDEROV GmbH
Contents
1. modeInfo mode DSTAR PHY DM state rx active rcvd voice VFI 36byte rcvd data n 3byte rcvd voice VFI 36byte rcvd data n 3byte rcvd termFlag modeInfo mode DSTAR PHY DM state rx armed Figure 15 MATFST expiry procedure in DM If a received transmission is ongoing longer than the MATFST than the PHY stops the retransmission and sends a short voice warning message for indicating of MATFST expiry The PHY provides the received data to the OS anyway 3 6 8 1 Abnormal behavior The following picture shows how the MATFST expiry procedure will be performed if the received transmission stops in the time period of an ongoing voice warning message UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 41 of 52 page s BEDEROV GmbH modeInfo mode DSTAR PHY DM state rx active tx warning MATFST expired rcvd voice VFI 36byte rcvd data n 3byte rcvd voice VFI 36byte rcvd data n 3byte rcvd termFlag Voice Warning modeInfo mode DSTAR PHY DM State tx warning modeInfo mode DSTAR PHY DM state rx armed Figure 16 stopped transmission during an ongoing voice warning message UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 42 of 52 page s BEDERO2. version bytel byte70 Last 15 Bytes are the ATMEL s unique serial number of the UC3B Chip 3 5 2 SysParam Syntax SysParam parameter value Length of the command 3Byte Command name SysParam This command shows the content of any particular parameter Command ID 0x40 parameter TESDELAY TX GAIN RX inv TC DC SHIFT MATFST Length of VW bytel UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 For no commercial use only Page 18 of 52 page s BEDEROV GmbH 3 5 3 reqSysParam Syntax reqSysParam parameter Length of the command 2Byte Command name reqSysParam This command requests the information about any particular parameter Command ID Ox41 parameter TAO BLAS TX GAIN RX inv TX DC SHIFT MATFST Length of VW 3 5 4 setSysParam Syntax setSysParam parameter value Length of the command 3Byte Command name setSysParam This command allows to change any particular parameter Command ID 0x42 parameter TA DELAY TX GAIN RX inv TX DC SHIFT MATFST Length of VW bytel UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 For no commercial use only Page 19 of 52 page s BEDEROV GmbH 3 5 5 uploadVoiceWarning Syntax uploadVoiceWarning Length of VW voice message Length of the command depending on Length of VW Command name up
3. Intelligent physical layer functionality PHY Operating System functionality OS On the PHY the very time critical signal processing of incoming noisy AF signal is implemented The PHY is connected to the amateur radio equipment by the traditional and well known data Mini DIN 6 jack which many transceiver by today have The OS has a lot of purposeful components which should allow to implement many comfortable software applications with new innovative ideas UPADAR block dia ram Salzburg 02 04 2012 E E 9 3h mE D 16 384MHz PHY Physical Layer AT32UC3B1512 Z1U NOOO OOO a a e Patch Field OO Hu Win a CODEC WM8510 Q aie 12MHz jj LJ LUI A EILELEILIH ELE LI E d 4 J RS2s esse IO Expansion HSD Card Holder Operating System AT32UC3A1512 Figure 1 UPADAR block diagram UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 7 of 52 page s BEDEROV GmbH 2 2 Use cases 2 2 1 Single user operation The most common use case would be the usage of this universal platform as an end user equipment At the following figure the corresponding scenario is shown As already mentioned above the physical layer does not need any external squelch information The internal state machine observed the incoming noisy AF
4. CRC FlowCtrlCounter Real tine data Source IP Port Destination IP Port Length CRC FlowCtriCounter Real time data Source IP Port Destination IP Port Length CRC FlowCtrlCounter Real time data Figure 22 proposal for a low delay inter digipeater transmission UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 52 of 52 page s
5. L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 47 of 52 page s BEDEROV GmbH data 101011000011010001101100 35 2c 36 5 6 data 100011000111010011001100 31 2e 33 1 3 data 101011000011010010110010 35 2c 4d 5 M data 001101000010110010001100 2c 34 31 41 data 101011000111010010001100 35 2e 31 5 1 data 001101001011001000110100 2c 4d 2c M data 101011000011010001010100 35 2c 2a 5 data 101011000110110010110000 35 36 Od 56 In the presented trace the following information can be identified CSOL 19 TX Message DL3OCK DENIS H13 m GPGGA 115039 02 5230 1367 N 01319 9885 E 1 05 3 0 61 3 M 41 1 M 56 CR 4 2 2 2 Transmission of GPS data The current commercial available D STAR equipment transmits in GPS mode NOT GPS A following data using container type 3 see 4 2 1 GPGGA 210530 03 5230 1381 N 01319 9732 E 1 05 4 2 53 7 M 41 1 M 56 lt CR gt lt LF gt SGPRMC 210531 03 A 5230 1381 N 01319 9731 E 0 00 173 7 141108 1 9 E A 0C lt CR gt lt LF gt DL3OCK BN DENIS 09 lt CR gt lt LF gt GPGGA 211022 03 5230 1380 N 01319 9710 E 1 05 4 1 52 0 M 41 1 M 55 lt CR gt lt LF gt SGPRMC 211023 03 A 5230 1380 N 01319 9711 E 0 00 27 7 141108 1 9 E A 38 lt CR gt lt LF gt DL30CK BN DENIS 09 lt CR gt lt LF gt In the GPS mode the user equipment seems to retransmit the original NMEA messages coming directly form a GPS device in the ca
6. RX inv should be set to 1 TX DC SHIFT 128 127 This parameter describes the linear offset of transmitted signal It is relevant for DC coupled transmitter only MATFST Maximal allowed time for a single transmission in digipeater mode in 2sec steps The time is not limited if MATFST 0 Length of VW Number of 20ms blocks of recorded voice warning message for user information about MATFST expiry DL3OCK UPADAR Released by DL3OCK technical specification UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 16 of 52 page s BEDEROV GmbH 3 3 Command overview Comman Service Mode DSTAR PHY SUM DSTAR PHY DVR DSTAR PHY DM tx tin TX ive TX Waiting for timer dx armed EET 1D ready armed reactive armed active Ox11 tx offf tx offf 0x30 Tovd header rcvd header rcvd header rcvd voice rcvd voice 0x32 rcvd SyncFlagl lu 0x33 revd_datal rcvd data 0x34 rcvd termFlag Tovd termFlag 0x35 rcvd FrameSync rcvd FrameSync 0x40 SysParam Ox4l Teg SysParam 0x42 set SysParam Oxid set QRG 0x45 ind QRG OxDl modelnfo modelnfo modelnfo OxD3 set model set model set model OxD4 cmd exe ind cmd exe indi cmd exe ind OxEI start update OxE2 transfer update block OxES update cmplt OxEd r
7. UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 Author D Bederov For no commercial use only Page 29 of 52 page s BEDEROV GmbH 3 5 23 tx test Syntax tx test sequence Length of the command 2Byte Command name tx test This command enforces the PHY to transmit some predefined periodical signals This is very helpful for adjustment activity by connection of UPADAR to a new amateur radio equipment Command ID 0x10 sequence 1111100000 PRN9 en This test data sequences are transmitted with 9600Baud UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 30 of 52 page s BEDEROV GmbH 3 6 Procedures In this section all important procedures are presented as formal message flows 3 6 1 Power On procedure sysInfo 64byte modeInfo mode service mode state ready Figure 7 Power On procedure After the power on was switched on the PHY starts its operation After the boot process is finished the PHY sends a sysInfo with a string of 70 bytes and a modeInfo message as shown in the figure above 3 6 2 Transmitting procedure In the DSTAR PHY SUM as well in DSTAR PHY DM the transmitting procedure is executing on the same way as shown in the figure below The main work for creating the output AF signal is done by PHY so the program on the OS does not
8. a data block NOP Usually all 6 bytes are 0x66 if nothing is available for transmission This container if used must be sent always in the 1 position This means immediately after synchronization flag and use only 2 bytes in which the digital squelch code CSQL is repeated twice The remaining unused 3 bytes contains 0x66 NOTE The valid CSQL range is 1 99 dec If the desired CSQL 19 than the both byte have to be OX19had Basically the header transmitted in LSDC should be identical with the information in the DV radio frame header But if the DV radio frame is retransmitted via a digipeater the digipeater will generally change the header during the retransmission All other repetitions of header in the LSDC remains of course unchanged So we have a chance to see what the transmitter originally has set in his header UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 46 of 52 page s BEDEROV GmbH 4 2 2 Empty voice data channel If the OS does not have any voice data to transmit e g some periodical GPS transmissions it fills the voice data time slots with Voice NOPs 9e 8d 32 88 26 la 3f 61 e3 4 2 2 1 Example SyncFlag data 010000111001100010011000 c2 19 19 data 011001100110011001100110 66 66 66 fff data 101011000010010011100010 35 24 47 5 G data 00001
9. case if the receiver was switched on during an ongoing transmission and missed the regular header 4 The terminating flag is send at the end of the ongoing transmission in order to indicate a regular end of it The terminating flag consists of 1 0 1 0 1 0 1 0 32 pitt 0 0 0 1 0 0 1 1 0 1 0 1 1 1 1 0Jh68 After that approximately 20 Zeros or Ones are send The Transmitter is switched of PTT deactivation after 10 such Zero or One UP4DAR Released by DL3OCK technical specification D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 44 of 52 page s BEDEROV GmbH data time slot where n ciN each 21 n 1 th va va va vc ga wg 099 va St ug 099 p9 gt gt gt X jejquie1os jo uoriesijeniul Buques Bulquiejos eee Jeldwelos jo uoresieniu ee Bujeapojur BuroBuo s uoissiuisue juano eu JIYM erep jo ndino eoipoueg WODI Jo Bunesoed Kreyeudoud yng ejduis Duipoo EUONRNIOAUOD wywobly wuywobly uuguobiy Z 1 16poo dSAd ISAd ISAG feuoynjoauod jeuondo jauueyy eieq peeds mo7 ul gep jes 1 sepeay EuBUO ena A alee EPA EPA ei 1 od L ab L DV mode in frame structure i lo D STAR radi Figure 18 Released by DL3OCK UPADAR Spec odt c o 9 o o o 2 2 Z lt o 9 2 DL3OCK 20 06 2012 Draft 0 2 Page 45 of 52 page s For no comm
10. chance to stop the retransmission of unwanted signal This is the case if the just received header does not fulfil some particular requirements for digipeating 3 6 7 Procedure for receiving of corrupted signal in DM If a transmission does not have header information due to some reasons we are speaking about a corrupted transmission This is the case if the transmitting mobile station was not receivable due to fading or if the receiver of the repeater was just switched on In such case the PHY goes into rx active tx state by receiving of the next synchronization flag as following figure shows In comparison to the receiving procedure in DM presented in 3 6 5 where the retransmission stops if we do not make any action in time the received corrupted signal will be retransmitted while it is ongoing UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 38 of 52 page s BEDEROV GmbH modeInfo mode DSTAR PHY DM state rx active tx rcvd voice VFI 9byte rcvd data n 3byte TX DELAY 8464415 4800 gt 65ms rcvd voice VFI 9byte rcvd data n 3byte rcvd voice VFI 9byte rcvd data n 3byte rcvd voice VFI 9byte rcvd data n 3byte rcvd termFlag modeInfo mode DSTAR PHY DM State tx buffer modeInfo mode DSTAR PHY DM state rx armed Figure 13 receiving of corrupted si
11. mode independent range 0xD1 0xFF 0x00 execution_status 0x01 successful execution 0x02 command is not specified or can not be used in the current situation 0x03 syntax error 0x04 command queue of PHY was busy UP4DAR Released by DL3OCK technical specification D L3 OC K UP4DAR_Spec odt For no commercial use only Page 23 of 52 page s BEDEROV GmbH 3 5 11 tx on Syntax tx on Length of the command 1Byte Command name This command starts a regular DV transmission Command ID 3 5 12 tx off Syntax tx_off Length of the command 1Byte Command name This command stops an ongoing DV transmission on a regular way by appending of the terminating flags Command ID 3 5 13 send header Syntax send header header bytes Length of the command 40Byte Command name send header This command provides to the PHY all needed bytes for a header transmission according to D STAR protocol specification Command ID 0x20 header bytes bytel byte39 UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 24 of 52 page s BEDEROV GmbH 3 5 14 send voice Syntax send voice VFI voice bytes Length of the command depending on VFI Command name send voice This command provides to the PHY encoded bytes of 20ms speech period Command I
12. 000 Denis zu Hause lt CR gt 4 2 2 3 Hints for an advanced usage of LSDC Currently used data transmission in LSDC does not have any error protection In order to protect the transmission the UP4DAR interface tanks to the number UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 49 of 52 page s BEDEROV GmbH indication of received data block allows to design some effective data transmission frames for more efficient and robust data transmission in LSDC The following figure shows a proposal for a possible advanced usage In this figure all 10 subsequent containers in between of two sync flag are presented It is proposed to use first 3 containers on the same way the currently commercial available equipment do see 4 2 1 in order to have backward compatibility 4bit 4bit 5byte 6 byte 3x6 byte for legacy transmission 7 subsequent transmitted 2x3byte groups 44 times of BCH 7 4 encoded code words Figure 20 advanced usage of LSDC The remaining 7 containers should build the new advanced data frame For this we have to find out in further investigations which container type is not used in currently commercial available equipment in order to not alloy theirs normal operation Potentially it could be each hex number which is currently missing in 4 2 1 This container type will transmitted in each place
13. 0101110001011100010 50 47 47 PGG data 000000100010001000110010 40 44 4c DL data 110011001111001011000010 33 4f 43 30C data 101011001000001000110100 35 41 2c BA data 100011001000110010101100 31 31 35 115 data 100000101101001000000100 41 4b 20 AK data 001000101010001001110010 44 45 4e DEN data 101011000000110011001100 35 30 33 503 data 100111000111010000001100 39 2e 30 9 0 data 010000101001001011001010 42 49 53 BIS data 000001000001001010001100 20 48 31 H1 data 101011000100110000110100 35 32 2c 52 data 101011000100110011001100 35 32 33 523 data 110000101100110000000100 43 33 20 C3 data 000001000000010000000100 20 20 20 data 101011000000110001110100 35 30 2e 50 data 100011001100110001101100 31 33 36 136 SyncFlag data 010000111001100010011000 c2 19 19 data 011001100110011001100110 66 66 66 fff data 101011001110110000110100 35 37 2c 57 data 011100100011010000001100 4e 2c 30 N 0 data 101011001000110011001100 35 31 33 513 data 100011001001110001110100 31 39 2e 19 data 101011001001110000011100 35 39 38 598 data 000111001010110000110100 38 35 2c 85 data 101011001010001000110100 35 45 2c BE data 100011000011010000001100 31 2c 30 1 0 data 101011001010110000110100 35 35 2c 55 data 110011000111010000001100 33 2e 30 3 0 UPADAR Released by DL3OCK technical specification O D
14. 2 page s BEDEROV GmbH 3 5 17 rcvd header Syntax rcvd header crc result header bytes Length of the command 41Byte Command name rcvd header This command provides the received and decoded header payload Command ID 0x30 crc result 0x00 CRC was OK 0x01 bad CRC header_bytes bytel byte39 For the mapping of the header byte see STD4 shogen or 4 1 3 5 18 rcvd_voice Syntax revd_voice VFI voice bytes Length of the command depending on VFI Command name rcvd voice This command provides the received voice data Command ID 0x31 VFI 0x01 2400 1200 BC FEC See dvsi section 5 2 4 for further information In 0x02 2400 current release the voice format indicator VDF 0x20 2400 1200 BC FEC SD 2400 is not supported voice_bytes VFI 0x01 bytel byte9 VFI 0x20 bytel byte36 UP4DAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 For no commercial use only Page 27 of 52 page s BEDEROV GmbH 3 5 19 rcvd syncFlag Syntax rcvd syncFlag time correction Length of the command 2Byte Command name rcvd syncFlag This command indicates that a sync flag was received and provides the done time correction in respect to the recently received sync flag before Command ID time correction o lt tc byte lt 13 The time correction value gives a result of the measured time difference between the receiv
15. 60s DVR Timer 01 2s waiting for timer Figure 6 states of UPADAR in DSTAR PHY DVR mode UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 14 of 52 page s BEDEROV GmbH 3 1 4 1 rx armed state 3 1 4 2 rx active s ate 3 1 4 3 waiting for timer state 3 1 4 4 rx state 3 1 4 5 tx state t b d 3 1 5 APRS PHY t b d 3 1 6 PR9K6 PHY t b d UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 15 of 52 page s BEDEROV GmbH 3 2 Parameters of PHY The physical layer can be optimised to his environment by configuration of following parameters Transmitter delay time between PTT activation and transmission of information data in 8bit steps additionally to 64 mandatory bits For a D STAR voice frame this means that after activation of PTT the sequence 1 0 1 0 1 0 1 0 of length TX_DELAY 8 64 in front of FrameSync flag is transmitted 128 1 1 127 Linear factor for transmitted AF signal The maximal range of DAC is achieved if TX GAIN 127 By using of negative values of TX GAIN the output AF signal can be inverted if it is needed RX inv If the incoming AF signal is inverted due to an inverting amplifier some where in receiver or if in a IF mixer LO QRG gt RX QRG for instance
16. BEDEROV GmbH Universal platform for digital amateur radio UPADAR Draft 0 2 20 06 2012 Issued by Denis Bederov DL3OCK QTH Berlin QRL Salzburg BEDEROV GmbH 2009 2012 UP4DAR technical specification DL3OCK Draft 0 2 Author D Bederov For no commercial use only Released by DL3OCK UPADAR Spec odt Date 20 06 2012 Page 1 of 52 page s BEDEROV GmbH Contents 1 GENERAL INFORMATION issie soes ana sees anna un doos ede sesde dd ees eine ee oe see de nun see wed dees die dees nd RES SN DE se 4 A sath EE EAE E AE EEE E tuae hun eneteceta ae E T 4 EZ WAIN AUTOR S erare RR EE EE 4 A ie ee EE e eA nM O A 5 1 4 ABBREVIATIONS AND DEFINITIONS seeeee mene ee ee ee ee ee ene ee rne ree ee ee ee ee ee ee ee pret ee ee 6 2 PLATFORM OVERVIEW EE ene nnn nnnn nnn nn cerraran uasa saa sanas saa ss ana asa nasa as sans sana annua 7 2 1 HARDWARE ARCHITECTURE 2 5 deret eee lead T 2 2 MUSE CASES ves seein bet UN E A di 8 22 1 Single user operation ciega ta E end o a ERRER EREEREER 8 2 2 2 Digipeater operatiOn iui anea e vA ERA EUR PR Ges ES Ne dA daa 8 2 9 ELECTRICAL CHARACTERISTICS SE io seus e ee sta Pede ends er Pee severos ede eo edv eno Deve be aca ere E Ne GE Pe DLP Doro ee ed 9 23 1 Conhiection Ol TEX utes dese epit rac leere ade via vi eod rave o eda ea Gon ee La epe Ge ela 9 3 SPECIFICATION OF UP4DAR INTERFATCE 1 1eeeeeee ee seek kk ee ee ee ek kk ee ee ee ee kk ee ee ee ek e
17. D 0x21 VFI 2400 1200 BC FEC 2400 See dvsi section 5 2 4 for further information In current release the voice format indicator VFI 2400 1200 BC FEC is supported only voice bytes DL3OCK Author D Bederov VFI 0x01 bytel byte9 UPADAR technical specification Draft 0 2 For no commercial use only Page 25 of 52 page s Released by DL3OCK UPADAR Spec odt Date 20 06 2012 BEDEROV GmbH 3 5 15 send data Syntax send data data Length of the command 4Byte Command name send data This command provides to the PHY the data bytes of the low speed data channel for current 20ms Command ID 0x22 data bytel byte3 3 5 16 change duration Syntax change duration n Length of the command 2Byte Command name change duration This command allows to overcome the slip problem by faster or slower provision of information to send during the transmission Usage of this command in front of each SyncFlag can adjust the own transmission up to 99ppm in comparison to 4800Symbols per second Command ID 0x23 duration 2x 10 This command can be used once in between of duration 2x10 two SyncFlag Two last symbols in front of following SyncFlag will be ether extended or shorted by 10 of its regular duration UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 For no commercial use only Page 26 of 5
18. E RE Es aa GE SN ER ae ees SE ER es Re a ae ee ee ee 27 DTO TOO VOICE oe EE 27 TOTO TVd AS la EE AR EE A A A E ER 28 36 20 revd data d 28 EE A o N EE REK RA OE E 29 30 22 TOVA FLAME SA N EE OE EE EE ie 29 3 6 23 All ER 30 3 6 PROCEDURES OR OE eate OE N OE N 31 UPADAR Released by DL3OCK O D L3 OC K technical specification bied iil UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 2 of 52 page s BEDEROV GmbH 3 6 1 Power On procedure RR RR AAR ee ee enhn ee ee RR RR RA AA ee ee ee ee nsns ee ee ee ee nan at 3 6 2 Transmitting procedure RR ee Re ee ee ke ee AR ke ee ee ee Re ee ee ee ee ee ee ee anaa at 3 6 3 Aborted transmitting procedure essen nnn nennen nnn 33 3 6 4 Receiving procedure in SUM ssssssssssssssses eee nnne nennen nennen 35 3 6 5 Receiving procedure in DM ee RR RA nennen nnne nennen ee ee Re ee niin 36 3 6 6 Procedure for receiving of unwanted signal in DM sene 37 3 6 7 Procedure for receiving of corrupted signal in DM sn 38 3 6 8 MATFST expiry procedure iii ee ee ee ee ee ER RR nennen ee ee ee ee nnns nnn nnn nnns sensn ann 41 3 6 9 PHY update procedure ee RR AR Re ee Ee ee ee ee GE RR AA Re ee ee ee nennen nennen n nnn 43 4 ANNE ue HQ 44 4 1 FRAME STRUCTURE OF DV PACKET IN D STAR cccccessscccceceesecceeceeeseeececcaes
19. V GmbH 3 6 9 PHY update procedure start update rdy for update transfer update block 0 511 cmd exe ind successful execution transfer update block 0 511 cmd exe ind successful execution update cmplt sysInfo Figure 17 PHY update procedure UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 43 of 52 page s BEDEROV GmbH 4 Annex 4 1 Frame structure of DV packet in D STAR A the D STAR System has two different operation modes digital voice DV digital data DD In this document the DV mode is considered only On the following figure the structure of a typical DV radio frame is presented 1 The preamble of radio frame according shogen consists of 64 bits alternating 1 und 0 Based on the fact that conventional amateur transmitter needs more time to lock its PLL after the PTT was activated the preamble is transmitted up to 550bits and longer before the frame sync will be started 2 The frame sync is following bit pattern 1 1 1 0 1 1 0 0 1 0 1 0 0 0 0 3 The sync flag consists of following bit pattern 1 0 1 0 1 0 1 0 1 0 1 1 0 1 0 0 0 1 1 0 1 0 0 0 The sync flag is transmitted in the 1 and than in each 21 data time slot The sync flag is used in the receiver for correction of time synchronization to the transmitter as well it is used as preamble in
20. byte cmd exe ind succesful tx off cmd exe ind succesful send data 3byte cmd exe ind succesful tx stop cmd exe ind succesfull modeInfo mode state rx armed Figure 9 aborted transmitting procedure UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 34 of 52 page s BEDEROV GmbH 3 6 4 Receiving procedure in SUM modeInfo mode DSTAR PHY SUM state rx active rcvd header crc result 39byte rcvd voice VFI 36byte rcvd syncFlag time correction rcvd voice VFI 36byte rcvd data n 3byte rcvd voice VFI 36byte rcvd data n 3byte rcvd termFlag modeInfo mode DSTAR PHY SUM state rx armed Figure 10 receiving procedure in SUM UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 35 of 52 page s BEDEROV GmbH 3 6 5 Receiving procedure in DM The PHY TX instance is only introduced to give an idea how PHY will internally work This should improve understanding of timings in Digipeater mode modeInfo mode DSTAR PHY DM state rx active tx rcvd header crc result 39byte send header 39byte cmd exe ind succesfull rcvd voice VFI 36byte rcvd syncFlag time correction TX DELAY 8 64 15 4800 gt 65ms rcvd voice VFI 36byte 65ms rcvd data n 3byte 20ms rcvd vo
21. ce APRS Protocol Version 1 0 3GPP 3GPP TS 23 032 V8 0 0 2008 12 Universal Geographical Area Description GAD http www 3gpp org ftp Specs html info 23032 htm UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 5 of 52 page s BEDEROV GmbH 1 4 Abbreviations and definitions AF audio frequency APRS Automatic Position Reporting System is the trademark of Bob Bruninga WB4APR digipeater digital repeater D STAR Digital Smart Technologies for Amateur Radio DV digital voice FEC forward error protection GMSK Gaussian minimum shift keying HF high frequency LO QRG frequency of local oscillator LSB least significant byte LSDC low speed data channel NMEA National Marine Electronics Association PLL phased lock loop PTT push to talk RX QRG receiving frequency t b d to be defined UP4DAR Universal platform for digital amateur radio UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 6 of 52 page s BEDEROV GmbH 2 Platform overview 2 1 Hardware architecture The universal platform for digital amateur radio UP4DAR is a very flexible high integrated platform which allows to host many different digital communication procedures from the amateur radio area The UPADAR consists of two important parts
22. d on receiver This is mainly foreseen for transmitting of short summary during the weekly amateur radio broadcasting Rundspruch Figure 21 proposal for transport format indicator TFI 4 3 Proposals for desktop software 4 3 1 GUI t b d UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 51 of 52 page s BEDEROV GmbH 4 4 Proposal for a low delay inter digipeater transmission It is basically no matter how the connection and its protocols are designed for a inter control signalling between two digipeater updates of the routing information for instance But for a critical voice data of an ongoing transmission the link between two digipeaters should be as low delay as possible In order to achieve a low delay connection it is proposed to use UDP or UDP lite protocol which is primary designed for such issues For avoiding of requests of missing data or UDP packets coming to late the following usage of the UDP packets is proposed See the next figure sss Voice data Voice data Voice data Voice data Voice data Voice data Voice data Voice data Voice data 16 bit Source IP Port Destination IP Port Length CRC FlowCtriCounter Real tie data bum ANO UDP header UDP data Source IP Port Destination IP Port Length
23. dy for update 3 4 Command transmission order Ale messages on command interface are encapsulated in the structure lt DLE gt lt STX gt lt DLE gt lt ETX gt with the usual values as follow DLE 0x10 lt STX gt 0x02 lt ETX gt 0x03 In case that the encapsulated payload has a Byte 0x10 which is equal to lt DLE gt then this byte 0x10 should be doubled All commands as well responses are transmitted serial over the UPADAR command interface byte wise Each particular byte is transmitted with LSB first Example modeInfo mode service mode status ready is transmitted as 0x10 0x02 0xD1 0x01 0x00 0x10 0x03 For the physical transfer one of typical USART ports is used The configuration of this port is BN 1 LSB first 115200Baud 3 5 Command specification In the following section the syntax of all commands is described in detail UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 17 of 52 page s BEDEROV GmbH 3 5 1 syslnfo Syntax sysInfo version Length of the command 70Byte Command name sysInfo This command informs the OS about the version of currently used PHY software This commands is only sends immediately after PHY was powered on This command can also be sent to the PHY as request at any time to get the sysInfo Command ID 0x01
24. e e ee ER ee eke 11 3 1 STATES OF Pl Yori dan TTL TUUM T 31 1 SOIVICO MOOG aore tdi r wese aid ed Ge Ee EE GEEN EED 12 3 1 2 Single user mode DSTAR PHY ee ee ee ee ee ee ek ee AA Re ee ke ee Re ee ee ee nn RR ee ee T2 3 1 8 Digipeater mode Y DSTAR PHY ees ee ek ee AR ee ee ee RR RR RR nn 13 314 DVR mode DSTAR PHY iii ee ee ee ee ee ee ee ee ee ee ee RR AG Gee ee ee ee ee ee ee ee ee ee ee ee ee ee 14 A APRS PAY esse sees dd ed ge ee ee De Se ee oe bes ee Ge He ee ge oe ee Dee de ee ei Ee oe EE 15 316 PRIKOPH AN EE EE OO NE NEE EE RE N RE 15 93 2 PARAMETERS GE PHIY olmo 16 9 9 COMMAND OVERVIEW 6 oia 17 3 4 COMMAND TRANSMISSION ORDER ee ees sees ee ee ee ee ee ee ee ee ee ee ee ee ee ee ee ee ee ke ee ee la 17 9 9 COMMAND SPECIFICATION oe EES SE Ee ee Ge a a ra Ee ee ee RE 17 A OE EE EE ER ER N 18 3 9 2 Y 2 EE A OE N EE N eevee 18 ECCL Ec RE ER EE EO EER 19 UNE ME oa IE EE EE EE RE EE N 19 3 5 5 uploadVoiceWarning AR AA Re RA ee Re ee ee ee AA ee EEEE E A TARERE 20 3 5 6 SOU ORG Hi E E o eid sheen ew wee ga E ea ee 21 39 ME Olim zi 35 8 MOO GINO cess Em 22 NT MET Ee ER N OE EE OE ME RE a 22 3 5 10 cmd SON nirmi s c t rie debe EE EE E 23 3 09 11 TE ad EE RO RE te one da ERE aioe Ai eee 24 S042 queo RE ME OE EE i eee alas 24 3i 13 send header EE ote O ARA 24 3 39 14 send VOICE AN m 25 ES Ede EE N N EE EE OE EE EE EE N N ne 26 TOTO CUANDO AUN EE EE RE N 26 3 611 revad header ES
25. e way and does not really need to be mentioned in an extra section The only reason for this section is to give an idea how the internally command pipeline of the PHY works The assumption here is that it is going about some kind of voice mail application or transmitting of any information which was already recorded and stored In such a case the OS can provide to the PHY all the voice and LSDC data in very short time interval much shorter than the corresponding play time This data can be easily received and stored in the PHY However the real time transmitting will of course need the corresponding play time anyway If in such a scenario the OS decides whatever reasons to stop the transmission it simply sends the tx stop command to the PHY In this case the PHY immediately stops the transmission deletes the data buffer and goes in the rx armed state This procedure is shown in the following figure UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 33 of 52 page s BEDEROV GmbH PHY tx on cmd exe ind succesful send header 39byte send voice VFI 9byte cmd exe ind succesful cmd exe ind succesful send syncFlag cmd exe ind succesful send voice VFI 9byte TX DELAY 8 64 15 4800 cmd exe ind succesful cmd exe ind succesful send voice VFI 9byte send data 3
26. ed Synchronisation Flag and its ideal time point Based on this measurement it is possible to calculate the relative time frequency error between the transmitter and the receiver crystal according to the following formula error in ppm tc byte 7 84 3 5 20 rcvd data Syntax rcvd data n data Length of the command 5Byte Command name rcvd data This command provides the received data of the low speed data channel Command ID 0x33 n 1 20 Number of current received block counted since the last sync flag bytel byte3 UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 For no commercial use only Page 28 of 52 page s BEDEROV GmbH 3 5 21 rcvd termFlag Syntax rcvd termFlag Length of the command 1Byte Command name rcvd termFlag This command indicates that a termination flag was received Command ID 0x34 3 5 22 rcvd FrameSync Syntax rcvd FrameSync mean deviation x2 samples Length of the command 93Byte Command name rcvd FrameSync This command provides the analogue samples of received FrameSync Flag Des Mean value of the received signal deviation x2 0 The doubled peak deviation of the received signal calculated based on FrameSync samples bytel byte90 The frame sync flag consist of 15 symbols which are represented by 6 samples per symbol 0xoo means ground level and ox means VCC level of RX AF pin4
27. either input nor output have any trimmer so the level is controlled by software parameter see 3 2 only This should allow in the OS application software to store configuration for each particular amateur radio device So a particular profile can be loaded ad hoc by connection to different transceiver e g fixed station transceiver UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 9 of 52 page s BEDEROV GmbH built in the car or a portable transceiver Such configuration file can be also exchanged with other OMs using the same transceiver Thank to a smart switching power supply concept the voltage of the power supply for UPADAR can vary in a wide range from 4V to 20V NOTE The 5V supply is only working if input power supply is in the range 6V 20V NOTE The 8V supply is only working if input power supply is in the range 8 5V 20V UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 10 of 52 page s BEDEROV GmbH 3 Specification of UPADAR interface The PHY can be considered as a kind of a well known GMSK chip CMX589 extended with a couple of features So we can now speak about an intelligent physical layer which is closed source In order to be able to develop the software for the operating syst
28. em OS at UPADAR the physical layer should be considered as a black box with strongly defined behaviour and well known interface In this chapter the interface will be presented in detail 3 1 States of PHY After power supply is switched on the physical layer starts to boot After this very fast procedure is finished the PHY goes into service mode In the further operation also other modes are possible Each operational mode of PHY can have different states In the following figures all states are described in more detail received frameSync or syncFlag received termFlag or transmission unexpected Figure 4 states of UP4DAR in DSTAR PHY SUM mode UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 11 of 52 page s BEDEROV GmbH 3 1 1 Service mode As already mentioned the PHY goes in this state immediately after its has booted after the power was switched on In this state some parameter of PHY see 3 2 can be configured from outside via the UP4DAR interface by using of special commands described in the next sections In order to adjust the level of transmitted AF signal some test sequences can be transmitted Also the input of the PHY can be adjusted to the polarity of received AF signal 3 1 2 Single user mode DSTAR PHY This mode is basically used in the most cases together with amateur
29. ercial use only D Bederov Author BEDEROV GmbH 4 2 Description of D STAR application layer As already presented a DV radio frames transmits together with digital voice data also user data in so called low speed data channel LSDC In this section the bit mapping and organization of data in LSDC of current commercial available D STAR capable amateur radio transceiver should be discussed Based on this information a outlook for potential future extensions can be given 4 2 1 Mapping of LSDC Each 21 data time slot is used for synchronization issues The remaining subsequent received 20 data slots in between 3 bytes each of them builds 10 subsequent data containers Each data container has therefore exactly 6 bytes The 1 byte indicates how the remaining 5 bytes of this container are used Thereby the 1 hex digit means the container s type and the 2 hex digit indicates how many following bytes of remaining 5 are used The unused bytes are set to 0x66 The following table shows the known container s type Container s Number of Description used bytes 1 5 bytes of the TX Message 2 5 bytes of the TX Message 3 5 bytes of the TX Message 5 5 bytes of the TX Message This container type is used for transmission of GPS data This container type is used for transmission of the original header This container can be transmitted every time if the LSDC does not have any other data to transmit This is
30. gnal in DM UP4DAR Released by DL3OCK technical specification D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 39 of 52 page s BEDEROV GmbH 3 6 7 1 Abnormal behavior If a retransmission of a corrupted signal is not desired the OS can stop the retransmission during the transmitter power on time given by TX DELAY The PHY provides the received data to the OS anyway The following picture shows this approach modeInfo mode DSTAR PHY DM state rx active tx rcvd syncFlag time correction tx stop TX DELAY 8464 15 4800 gt 65ms modeInfo mode DSTAR PHY DM state rx active rcvd voice VFI 36byte rcvd data n 3byte rcvd termFlag modeInfo mode DSTAR PHY DM state rx armed Figure 14 stopping of retransmission of a corrupted signal in DM UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 40 of 52 page s BEDEROV GmbH 3 6 8 MATFST expiry procedure PHY TX rcvd voice VFI 36byte rcvd syncFlag time correction MATFST expired modeInfo mode DSTAR PHY DM state rx active tx warning rcvd voice VFI 36byte rcvd data n 3byte rcvd voice VFI 36byte rcvd data n 3byte Voice Warning rcvd voice VFI 36byte rcvd data n 3byte rcvd voice VFI 36byte rcvd syncFlag time correction
31. ice VFI 36byte rcvd data n 3byte rcvd termFlag 20ms modeInfo mode DSTAR PHY DM state tx buffer 20ms 14ms modeInfo mode DSTAR PHY DM state rx armed Figure 11 receiving procedure in DM UP4DAR Released by DL3OCK technical specification D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 36 of 52 page s BEDEROV GmbH 3 6 5 1 Abnormal behavior If the OS does not provide the header information for the retransmitted signal at time the PHY finishes the transmission However the PHY will still provide the received data to the OS while the current received transmission is ongoing 3 6 6 Procedure for receiving of unwanted signal in DM modeInfo mode DSTAR PHY DM state rx active tx cmd exe ind succesfull TX DELAY 8 64 15 4800 gt 65ms rcvd header crc result 39byte rcvd voice VFI 36byte rcvd syncFlag time correction modeInfo mode DSTAR PHY DM state rx active rcvd voice VFI 36byte rcvd data n 3byte rcvd voice VFI 36byte rcvd data n 3byte rcvd termFlag modeInfo mode DSTAR PHY DM state rx armed Figure 12 aborting of a unwanted retransmission in DM UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 37 of 52 page s BEDEROV GmbH With this procedure the OS has a
32. ll basic features needed to make a voice digital repeater according to D STAR see 4 A potential SysOp needs only to have a traditional analogue repeater equipment in which the receiver has a data capable AF output and the transceiver a data capable AF input see 2 2 2 In this mode the PHY has the same states like in the SUM rx armed rx active tx tx termFlag with the same meaning as it was presented above Additionally the digipeater mode DM has following states received frameSync whole buffer is sent tx buffer or syncFlag received termFlag gt transmission unexpected ux stopt MATFST expires _ Voice warning finished termFlag transmitted not at time received termFlag or transmission unexpected ends tx off or Received termFlag or transmission unexpected ends tx stop tx warning Voice warning finished termFlag transmitted Figure 5 states of UPADAR in DSTAR PHY DM mode 3 1 3 1 rx active tx state This is most native state of a repeater in which a valid data transmission is almost directly retransmitted immediately by PHY to the transmitter and in addition provided to the OS for further processing e g sending of voice data and data of low speed data channel to a gateway function for establishing of an inter repeater operation 3 1 3 2 tx buffer state In this state the PHY goes if a receiving tran
33. loadVoiceWarning This command allows to upload into PHY the voice data for a voice warning about expiry of maximal allowed time for single transmission Command ID Length of VW Number of 20ms blocks of recorded voice warning message for user information about MATFST expiry voice message DL3OCK Author D Bederov bytel byteN UP4DAR Draft 0 2 N Length of VW 9 Released by DL3OCK technical specification UP4DAR_Spec odt Date 20 06 2012 For no commercial use only Page 20 of 52 page s BEDEROV GmbH 3 5 6 set QRG Syntax set QORG rx ORG tx ORG Length of the command 9Byte Command name set ORG This command allows to set the transmission and receiving frequency of a radio part which is directly connected to the PHY Command ID 0x44 rx QRG bytel byte4 unsigned int rx QRG byte1 MSB byte4 LSB tx QRG bytel byte4 unsigned int tx QRG byte1 MSB byte4 LSB 3 5 7 ind_QRG Syntax ind ORGISet ORG resp Length of the command 2Byte Command name ind QRG This command responses if the seting of new frequences was successful or not Command ID 0x45 set_QRG_resp both QRGs set up tx ORG is out of allowed range rx QRG is out of allowed range PLL is not able to lock tx QRG PLL is not able to lock tx QRG UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 For no commercial use
34. need to take care about However it is very important to fulfil the timing requirements of a D STAR DV frame which is shown with blue arrow on the right site of the PHY instance UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 31 of 52 page s BEDEROV GmbH cmd exe ind succesful send header 39byte cmd exe ind succesful send voice VFI 9byte cmd exe ind succesful TX DELAY 8 64 15 4800 send syncFlag cmd exe ind succesful send voice VFI 9byte cmd exe ind succesful send data 3byte cmd exe ind succesful send voice VFI 9byte cmd exe ind succesful send data 3byte cmd exe ind succesful tx off cmd exe ind succesful modeInfo mode state rx armed Figure 8 transmitting procedure UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 32 of 52 page s BEDEROV GmbH 3 6 2 1 Abnormal behavior As soon the OS does not provide the next portion of needed data during the transmitting procedure at time the PHY finishes the transmission on correct way The OS will be informed by indicating of change into the corresponding state The PHY will reject all further data coming not at time 3 6 3 Aborted transmitting procedure This procedure is executed on very nativ
35. of the yellow column The remaining coloured bits are encoded with a linear cycle block code BCH 7 4 This means that each code word of the length 7 carries 4 information bits Note it is important to build the code words on the shown way in the vertical and not in the horizontal direction Therefore our new advanced data frame has 22 high protected information bytes These bytes can be used as follow The 1 byte is CRC of the remaining 21 bytes The 2 byte is so called transport format indicator TFI and of course 20 information bytes The advantage of such advanced forward error protection FEC is huge For this special proposal it means that during the transmission time of 280ms for an UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 50 of 52 page s BEDEROV GmbH advanced data frame a continuous part of 40ms allows to be corrupted in order that all information bits can be detected without any error The following table give an idea for definition of the TFI Description 20 byte of TX Message 1 part of original header 2 part of original header 1 part of position fix APRS call sign message and position fix compressed according to APRS or 3GPP 2 part of position fix APRS call sign message and position fix compressed according to APRS or 3GPP General text message to be displaye
36. only Page 21 of 52 page s BEDEROV GmbH 3 5 8 modelnfo Syntax modeInfo mode state Length of the command 3Byte Command name modeInfo This command provides the information about the current operation mode state Command ID This id is from the mode independent range OxD1 OxFF 0x00 mode service mode DSTAR PHY SUM DSTAR PHY DM DSTAR PHY DVR APRS PHY PR9K6 PHY F3E PHY ready ready is used in service mode only rx armed rx active rx tx tx termFlag rx active tx tx buffer rx active tx warning tx warning waiting for timer 3 5 9 set mode Syntax set mode mode Length of the command 2Byte Command name set mode This command enforces the PHY to change in some particular operation mode UPADAR Released by DL3OCK technical specification O D L3OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 22 of 52 page s BEDEROV GmbH Command ID OxD3 This id is from the mode independent range OxD1 OxFF 0x00 mode 0x01 service mode 0x02 DSTAR PHY SUM 0x03 DSTAR PHY DM 0x04 DSTAR PHY DVR 0x05 APRS PHY 0x06 PR9K6 PHY 0x07 F3E PHY 3 5 10 cmd_exe_ind Syntax cmd_exe_ind execution status Length of the command 2Byte Parameter Description Command name cmd exe ind This command provides the feedback about the execution of recently invoked command Command ID OxD4 This id is from the
37. radio transceiver for a direct QSO or operation via a digital repeater digipeater 3 1 2 1 rx armed slate In this state the PHY stays its most time and investigates the incoming noisy signal if there is a valid data transmission It does mean that the PHY does not need any external squelch circuit Therefore the best idea it is to open completely the squelch if available As soon a valid data transmission is detected the PHY goes to the next state 3 1 2 2 rx active state Being in this state the PHY provides to the OS the received voice data and data of low speed data channel see 4 3 1 2 3 tx state If the user want to make a digital voice transmission by activation of its PTT the OS enforces the PHY to go into the transmitting tx state Being in this state the PHY get the data to be transmitted and creates a corresponding analogue GMSK AF signal 3 1 2 4 tx termFlag state Should an ongoing transmission be finished the user simply deactivates the PTT Thereupon the OS enforces the PHY to go into the tx termFlag state in which the PHY sends the terminating flag and deactivates the HF transmitter Shortly after this the PHY changes to the rx armed state UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 12 of 52 page s BEDEROV GmbH 3 1 3 Digipeater mode DSTAR PHY In this mode the PHY of the UPADAR has a
38. rs and Here are examples of valid combinations DL3OCK DL3OCK 9 DL1AA 9 DL1A DL1A AM DL1A 99 The current commercial available D STAR radio equipment is not able to calculate the check sum within GPS information message No idea why Therefore users each time they want to use this GPS mode are enforced to use a web based tool for this http www aprs is net DPRSCalc aspx This tool computes the check sum and creates only the coloured part of the whole message which should be put to a GPS configuration menu Of course an OS software developer for UP4DAR will integrate this easy computation in the program and compute the checksum immediately after the user have changed the C1 message In my opinion there is nothing against a flexible usage of two different call signs For example for the header of the whole DV radio frame MY_CALLSIGN DL3OCK M and for the GPS information message inside the same radio frame DL3OCK 9 The other available GPS mode is so called GPS A mode The advantage of the GPS mode described above in comparison to the GPS A is the fact that the current commercial available D STAR equipment is able to visualize the position of the received station on its display However a GPS A message which is APRS very likely has a more efficient error check method which is a good known CRC and not a simple check sum CRC8082 DL30CK gt API282 DSTAR 211248h5230 13N 01319 98E 027
39. se above only GGA and RMC NMEA messages were chosen in the GPS pre configuration menu A standard NMEA GPS device protects it statements by a kind of check sum which is simply XOR addition of all bytes between and In addition to the NMEA messages a current commercial available D STAR device transmits an additional message which is needed in order to allows of the software running on the current commercial available digipeater to forward such positioning reports to the world wide amateur radio APRS network The main part of this datagram is the so called C1 message It consists of maximal 13 left aligned characters ASCII bytes plus and 2 bytes of XOR check sum of all message bytes left of The following picture give the overview about the structure of the whole information message If the C1 message plus and 2 bytes of XOR check sum is shorter than 16 bytes than it will be padded right by spaces see the example above UP4DAR Released by DL3OCK technical specification D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 48 of 52 page s BEDEROV GmbH ASAS AAA NX 8bytes y 3bytes space 16bytes lt CR gt lt LF gt Figure 19 structure of the information message in GPS mode The call sign is limited to 8 characters If it is shorter it will be left aligned and padded right by spaces The call sign may contain only alphanumerical characte
40. seceeeeaasseseeteneeeeeseesanseeees 44 4 2 Description OF D STAR APPLICATION LAYER ccccceccecececececceeeeuceeuueeeueueeeueusesuueceuausueeeueeueueuueneeeaeeees 46 42 1 Mapping OF LSDE ici ee ee ee ge ee SS ve A te SG EE n ER N Ge ee LU 46 4 2 2 Emplyvoicedalachannel uie SEER iE ida ER N EE ea ac 47 4 3 PROPOSALS FOR DESKTOP SOFTWARE ec ee ees ee ee ee ee ee ee ee ee ee ee E assai sss sais daas ee saa asas sa sanas daas ee an 51 AIR GU e A a a EEEE iia ind ds 57 4 4 PROPOSAL FOR A LOW DELAY INTER DIGIPEATER TRANSMISSION sesse ee ese ee ee ee ee ee ee ee ee ee ee ee ee ee ee ee ee ee ee ee Re ee nn 52 UPADAR Released by DL3OCK technical specification O D L3 OC K UP4DAR_Spec odt Draft 0 2 Date 20 06 2012 For no commercial use only Page 3 of 52 page s BEDEROV GmbH 1 General information Currently there is no a lot solutions on market for the new digital voice operation mode in amateur radio Especially the creating of innovation in such new and interesting area is not really easy by today The target for the development of the universal platform for digital amateur radio UPADAR is to create a very flexible platform with an open and good described interface In my opinion this is a needed pre condition for enabling of a lot software talented YLs and OMs under us to create an always growing open source project which should be open for all innovations we will have in the next future The main goal of this doc
41. signal and estimates the fact of any ongoing transmission So the best sensitivity can be achieved if the available squelch is completely open Figure 2 UPADAR as a single user equipment 2 2 2 Digipeater operation The UPADAR can be also used for creating of a digital repeater The PHY provides for this purpose some helpful feature This allows to make a repeater on very simple way by using of a minimum of external components The following figure shows how a digipeater can looks like UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 8 of 52 page s BEDEROV GmbH Gateway PC Figure 3 UPADAR as a digipeater 2 3 Electrical characteristics 2 3 1 Connection to a TRX The analog connection towards an amateur transceiver is a usual Mini DIN 6 jack that a lot of transceivers of today have The AF signal from receiver which is connected to the pin 4 should be not higher than 660mVpp On the input of the pin 4 inside is a series connection of a 4 7uF capacitance and a 11KOhm resistor The cold site of the capacitance is negative so the constant component of the input signal must be smaller than 1 3V The maximal possible output AF signal at pin 1 has 2400mVpp This output has a series capacitance of 4 7uF with a negative cold site so the input of the transmitter must be DC free N
42. smission is finished in order to send out data still buffered due to a time delay between incoming and outgoing digital signal UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 13 of 52 page s BEDEROV GmbH 3 1 3 3 rx active tx warning s ate If the maximal allowed time for a single transmission in repeater mode is configured to be limited and this time was expired during a long transmission the PHY goes in this state Here the PHY still provides received data to the OS but does not retransmit them to the AF output Instead of received signal the PHY sends a short voice warning message e g Here is DBODF The last transmission was too long or simply transmission too long The data of the voice warning message can be uploaded into the PHY during configuration procedure 3 1 3 4 tx warning state In this state the PHY goes if a too long transmission was finished during the voice warning is transmitting in order to finalize the completely voice warning message 3 1 4 DVR mode DSTAR PHY received a DV transmission without any correct header received termFlag or transmission unexpected ends received correct header received a DV transmission without any correct header received termFlag or transmission unexpected ends received correct header Max recording time
43. ument is to encourage and to enable a wide number of people interesting in digital amateur radio to develop software for the OS definition follows in the next sections desktop software for comfortable work in case a computer is connected each kind of back bone routing software for world wide interconnections e g www xreflector net and some really innovative things that there is not by today am hinting at new network services e g digital routeable voice mailboxes digipeater with special ports not for a voice communication but with special measuring functionality which should report back to the user which physical parameters would be more better to set in his hardware configuration menu etc 1 1 History Version Date Chapter Changes Reasons 29 11 09 uM DL3OCK initial version started on 04 11 2009 Rule for version number e nextinteger number for major changes e 0 1 for minor changes 1 2 Main Authors Denis Bederov DL3OCK Denis Bederov gmx de UPADAR Released by DL3OCK technical specification O D L3 OC K UPADAR Spec odt Draft 0 2 Date 20 06 2012 Author D Bederov For no commercial use only Page 4 of 52 page s BEDEROV GmbH 1 3 References STD4 http www jarl com d star shiryou STD4_3C pdf shogen http www jarl com d star shogen pdf dvsi AMBE 2020TM Vocoder Chip User s Manual Version 4 8 September 2007 http www dvsinc com products a2020 htm APRS APRS Protocol Referen
Download Pdf Manuals
Related Search