Magellan GPS 320
Magellan GPS 320 - FAQ, size: 45 KB
The RAM-SB-178-MA1 Magellan GPS 300 and Blazer 12 Series Adhesive RAM Mount is a High Strength Plastic Composite Mount with a PDA Adhesive Base and RAM Custom Plastic Cradle. The mount is designed with a RAM Snap-Link friction ball and socket system that has one adjustment point in the middle of the mount. Once the adhesive base is securely mounted, you can move the Magellan GPS 300 Series cradle to your optimum viewing position with a simple twist of the mount joint. Note: This mount does not r... Read more
Part Numbers: RAM-B-166-MA1U, RAP-SB-178-MA1
UPC: 0793442915789, 793442915789
[ Report abuse or wrong photo | Share your Magellan GPS 320 photo ]
User reviews and opinions
|tymib||6:57pm on Saturday, July 24th, 2010|
|Does not hold up After about six months of use it started using batteries even though it was turned off.|
|honza__||5:38pm on Monday, June 14th, 2010|
|My first GPS - no mapping, but great for hiking and beginners After nearly getting lost with the family last month I decided to get a GPS unit.|
|alex192||3:47pm on Wednesday, May 19th, 2010|
|My first GPS - no mapping, but great for hiking and beginners After nearly getting lost with the family last month I decided to get a GPS unit. not bad, but maps are better Liked the reception of this vs. the Garmin unit I had previously. But soon learned that maps are the way to go.|
Comments posted on www.ps2netdrivers.net are solely the views and opinions of the people posting them and do not necessarily reflect the views or opinions of us.
GPS 315/320 DATABASE FORMAT
DATA FORMAT AND TRANSFER PROTOCOL FOR MAGELLAN GPS 315 & GPS 320
January 27, 2000 revision 1.01
32, 'DWDEDVH )RUPDW
The Points Of Interest (POI) database in the Magellan GPS 315 and GPS 320 receivers is composed of 3 separate (but contiguously placed in memory) sections. These are:
Bitmaps which are used for the icons displayed on the plotter screen A header from which serves as the source for the database title (displayed on power-up) and information used by the DATASEND program (or other PC program). The actual database itself
In the following document all multi-byte values are considered to be Motorola format integers in that the most significant byte is the low memory byte. All offsets are calculated from the start of the database. For example, the first icon bitmap is at offset 0, the POI header is at offset 220.
This section contains ten 22 byte bitmaps. Each represents the icon for the corresponding category (icon at location 0 is for category 0, location 22 for category 1, etc.). The total length of the section is 220 bytes. The total space must be reserved and filled, even if less than 10 categories are loaded into the unit. Bitmaps for any categories not loaded into the unit are ignored. %LWPDS )RUPDW Each bitmap is a representation of the 13 pixel by 13 pixel icon that is displayed on the plotter screen for a POI in a given category. Thus each 22 byte representation holds 169 bits representing the icons pixels with a bit value of 1 indicates a lit (dark) pixel, while a value of 0 indicates an unlit (light) pixel. Each bitmap also contains 7 ignored bits (22 bytes = 176 bits). The displayed bitmap is constructed by turning the 22 bytes of data into a continuous bit stream from low memory to high memory with the bits in each byte arranged from LSB to MSB. This stream is then split into 13 consecutive sets of 13 bits. Each set of bits is one column of the resulting icon. Each column is constructed from bottom to top and the columns are ordered from left to right. For example the bitmap for a quartered circle () might be: 00 C08 FF 49 CWhich translates into the bit stream: Which becomes the following 13 bit sequences:
0000000000000 Labelling the sequences a through m they would be displayed as follows: 0000000000000 abcdefghijklm bit bit bit bit bit bit bit bit bit bit bit bit bit 0
The header is a string of 128 ASCII characters. With one exception the content of the header is only used by the receiver as a source of the database title that is displayed on the startup screens and as a check that the database exists. The exception is that the first three bytes of the header must contain the ASCII characters 128. This is the length of the header (in bytes) expressed as an ASCII string. The existence of a valid database is assumed if the first two bytes of the header do not have values of 255 (0xFF). The database upload process will preserve these two bytes as 0xFF (the erased state of the flash) until it receives the termination command from the PC. Thus if an upload is not completed correctly these bytes will still have the value 0xFF and the unit will completely ignore the database. The three 15 character lines displayed on the startup screens as the database title are; characters 4 through 18, 20 through 34 and 36 through 50 of the database header (first character is 0). All other information in the header is for use of the PC program. This program can get the header contents with the appropriate serial protocol command sent to the unit (see Data Transmission Protocol Specification for Magellan Products for details).
The first two bytes of the database contain the number of categories in the database. There then follow category record headers for each category the database contains. Headers need to be included only for existing categories (i.e. there need only be as many headers as specified in the above two bytes). Each header is 36 bytes long and has the following format (from low to high memory):
4 bytes specifying the number of records in the category 15 bytes containing the name to be displayed for this category (ASCII characters) 1 byte of filler (value ignored) 4 bytes specifying the offset (in bytes) of the first record in this category 4 bytes specifying the offset (in bytes) of the 1 letter index 4 bytes specifying the offset of the latitude bin list size list 4 bytes specifying the offset to the latitude bin list.
Each of the 4 referenced areas can be located anywhere in the database. In general, however, they are usually packed together in the order of their offsets in the header. 'DWDEDVH 5HFRUGV This area contains a list of all database records in this category. The list should be ordered alphabetically by POI name. Each record in the database is of a fixed length of 74 bytes. The record consists of the following fields: 15 bytes POI name (must start with uppercase letter (A-Z) or number (0-9)) 1 byte filler, value ignored 3 bytes latitude of the POI, integer in radians with LSB of 2
3 bytes longitude of the POI, integer in radians with LSB of bytes line 1 of the POI description 20 bytes line 2 of the POI description 12 bytes line 3 of the POI description
VW /HWWHU ,QGH[ This list is used for fast scrolling through the database. This is a set of 36 four byte indices into the database records for this category (0 is the first record). Each index indicates the first record whose name begins with a given character. Thus the first index indicates the first database record whose name starts with 0, the second with 1,.the thirty-sixth with Z. If there are no records whose name starts with a given letter an index value of 1 should be used.
/DWLWXGH %LQ /LVW In order to speed up searches for the nearest record to a given geographic point an index ordered by geographical latitude and longitude is needed. This is accomplished in this database through this list of record indices. This list is structured in two levels. First the world is divided into ninety 2 degree latitude bins. These bins are ordered from the south pole to the north (90 S to 88 S is bin 0, 88 N to 90 N is bin 89). All database records in a given category are sorted into a latitude bin based on their geographical location. For example a POI at latitude 33 N would be in bin 61. Within each bin the records are then ordered by longitude (from West to East). The result is one long list that has a series of indices ordering POIs from West to East. The number of records in each bin is placed in the Latitude Bin List Size List. It is permissible to have empty bins (the corresponding entry in the Latitude Bin List Size List would be 0). The unit software then uses the information in the Latitude Bin List Size List to find the start of each bins longitude list. /DWLWXGH %LQ /LVW 6L]H /LVW This is a list of 90 two byte values that specify the number of indices in each of the 90 latitude bins described under Latitude Bin List. They are ordered from southernmost to northernmost bin.
'DWDEDVH 8SORDG 3URWRFRO
Data transfer from the PC to the database flash ROM in the Magellan GPS 315 & GPS 320 receivers is done via the units serial port while the unit is in a special Database Upload Mode. In order to enter this mode the unit must either receive the appropriate command via the serial port (see Data Transmission Protocol Specification for Magellan Products for details) or via the user activating it through hidden function 98.
8VHU $FWLYDWLRQ RI 'DWDEDVH 8SORDG 0RGH
The procedure for user activation of Database Upload mode on the receiver involves the following steps: 1. Activating the menu from a NAV page via the MENU key. 2. Pressing in sequence <RIGHT ARROW> <LEFT ARROW> <RIGHT ARROW> 3. Scrolling the 00 displayed to 98 via the arrow keys 4. Pressing the ENTER key
6HULDO /LQN 3K\VLFDO 3URSHUWLHV
All communications between the PC and the GPS unit take place over a serial communication link. The unit needs to be connected to a PC COM port using an appropriate cable (available from Magellan). All communication is done via RS-232 type signals using 8 data bits, 1 start bit, 1 or 2 stop bits and no parity. There are two different versions of hardware used in the GPS 315 and GPS 320. One set, the earlier, runs the serial port at 19,200 baud. Later hardware runs the serial port at 115,200 baud. These rates are fixed and unchangeable by the user or the PC. It is the responsibility of the PC program to determine which of the two baud rates to use (either through user command or sampling the data and auto-bauding). Note that the unit will be sending out hello records (see below) at approximately a 1 Hz rate. The PC program can determine the baud rate using these characters.
There are three different types of records used in this protocol:
Single byte commands and responses sent by both the PC and the GPS unit 3 byte data packets sent from the GPS unit Variable length data records sent from the PC
6LQJOH %\WH &RPPDQGV The following list delineates the single byte commands: 0xAA This is used as a hello code. The GPS unit sends this command until it gets an OK code from the PC. It is intended to be used by the PC to identify the serial port and baud rate the unit is using. This is used as an OK code. It is sent by both the PC and the GPS receiver to indicate completion of a phase of the protocol or an operation. This is the erase command sent to the GPS unit to start the flash erase cycle. This is a waiting for record command sent by the GPS receiver to the PC. It is used to help resynchronize the protocol when an error occurs. This is a coldstart command. The PC sends this to the GPS receiver to command the receiver to erase its RAM memory and place itself in a coldstart condition. The GPS unit will only accept this command when it is awaiting a record from the PC. This is a negative acknowledgement sent from the GPS receiver if a records checksum does not match the data. This is a negative acknowledgement sent from the GPS receiver if it receives a record length greater than 1024. This is a negative acknowledgement sent from the GPS receiver if it does not receive the erase command at the proper time. This is a negative acknowledgement sent from the GPS receiver if it cannot program a records data into the flash ROM or cannot erase the specified area of the flash ROM. This terminates the protocol since it usually indicates a HW failure. If the GPS receiver sends this command it will reset itself to the start of the protocol (it will begin sending Hello codes again). This is a negative acknowledgement sent from the GPS receiver if it does not receive a complete record. This is a negative acknowledgement sent from the GPS receiver if the last character in a record is not a ] (record termination character). This is sent by the GPS receiver to indicate successful erasure of a flash ROM sector.
%\WH 'DWD 3DFNHWV 3 byte data packets sent from the GPS unit can appear at any time in the protocol (the were originally designed to return debug data during an upload). They are currently used as a positive data record programming response (see below). They consist of a start byte followed by two bytes of data that can be combined into a 16 bit value. Byte 2 Value 0x8E arbitrary arbitrary Purpose Record identifier values MSB values LSB
After the GPS unit programs the data from a record into flash it will send two of these packets to the PC. The first contains the most significant word of the address in the flash ROM at which the records first byte was programmed. The second contains the least significant word of the address. 9DULDEOH /HQJWK 'DWD 5HFRUGV The PC uses variable length data records to send data and/or addresses to the GPS unit. They are used during erasure of the flash ROM, programming of the flash ROM and termination of the transfer. In all case they share the following format: Byte 2 Value 0x5B ([) arbitrary arbitrary arbitrary last-2 last-1 last arbitrary arbitrary 0x5D (]) Purpose Record start identifier MSB of the count of words of data in record LSB of the count of words of data in record data must be an even number of bytes MSB of data checksum LSB of data checksum Record end identifier
Records can contain only an even number of data bytes. Every two data bytes are defined as a single data word. The second and third bytes of the record contain the number of these data words in the record. The number of data words must be in the range 0 to 1024. The checksum is a 16 bit word which is an exclusive-OR of all the data words in the record.
The protocol sequence to reprogram the database in a GPS 315 or GPS 320 goes through various stages as given below.
,QLWLDWLRQ Once the GPS unit is placed in Database Upload mode it will start sending hello codes (value 0xAA). The PC program should respond with an OK code (value 0x55). The GPS receiver will then send its own OK code (value 0x55). (UDVLQJ WKH IODVK 520 Erasing the flash ROM takes place next and is performed in the following sequence: 1. The PC program sends an erase command (value 0x6A) to the GPS unit. 2. The GPS receiver sends an OK code (value 0x55) back to the PC. 3. The PC program sends a record of the following format to the GPS unit Byte Value 0x5B ([) arbitrary arbitrary arbitrary arbitrary arbitrary arbitrary 0x5D (]) Purpose Record start identifier MSB of the count of words of data in record LSB of the count of words of data in record First address to erase byte 0 First address to erase byte 1 First address to erase byte 2 First address to erase byte 3 Last address to erase byte 0 (MSB) Last address to erase byte 1 Last address to erase byte 2 Last address to erase byte 3 (LSB) MSB of data checksum LSB of data checksum Record end identifier
The last address to be erased is usually the total count of bytes in the database that is to be programmed. The size of the database flash ROM requires this address to be less than 0x15FFFE. 4. The GPS receiver sends an OK code (value 0x55) back to the PC. 5. The GPS receiver then sends back a sector erased command (value 0x8E) to the PC for each sector it erases (sectors are 64Kbytes in size). 6. The GPS receiver sends back an OK code (value 0x55) when it has erased all the commanded flash ROM.
3URJUDPPLQJ WKH IODVK 520 To program the flash ROM the following exchange is undertaken enough times to transfer the entire database to the GPS receiver. 1. The PC program sends a record of data to the GPS unit. Note that care should be taken to not send a record with no data (data length 0) to the GPS unit as this will terminate the entire programming cycle. See below. This record has as its first two data words the address at which the record should be programmed. This address is generally the same as the number of bytes of database data sent previously sent to the GPS receiver. 2. The GPS receiver sends an OK code (value 0x55) to the PC. 3. The GPS receiver then programs the data and upon completion sends another OK code (value 0x55) to the PC. 4. The GPS receiver then sends two 3 byte data packets to the PC. The first contains the most significant word of the address at which the record was programmed. The second contains the least significant word of the address. The PC can use the reconstructed address to verify that the correct record was programmed. The PC can use this address to verify that a record has not been lost. This address will be the actual flash address programmed, not the address contained in the data record transmitted by the PC. The difference is that the returned address will be 0xA0000 higher. Note that such errors have been seen when the PC is heavily loaded with other applications running simultaneously with a database upload program. 7HUPLQDWLRQ To terminate the upload of the database the PC should send a record with no data words (data length of 0) to the GPS receiver. The GPS receiver will then respond with an OK code (value 0x55) and do a warm start.
The RAM-SB-178-MA1 Magellan GPS 300 and Blazer 12 Series Adhesive RAM Mount is a High Strength Plastic Composite Mount with a PDA Adhesive Base and RAM Custom Plastic Cradle. The mount is designed with a RAM Snap-Link friction ball and socket system that has one adjustment point in the middle of the mount. Once the adhesive base is securely mounted, you can move the Magellan GPS 300 Series cradle to your optimum viewing position with a simple twist of the mount joint. Note: This mount does not require any drilling for installation. Magellan GPS Mount Arm Design:The RAP-SB-192 RAM Mount High Strength Plastic Composite Assembly is a 0.5 inch diameter plastic ball and socket snap-link friction grip system with diamond plate ends. One end of the assembly connects to the back of the cradle, and the other to the diamond plate on the mount base. The snap-link friction grip system relys on the screw tightened socket to grip the solid plastic ball. This ball and socket system should only be used in a low vibration application. The mounting base consists of a 2.5 inch diameter flexible base with a RAM Mount RAM-202PSA Adhesive PSA (Pressure Sensitive Adhesive) Disk.
Nokia 6111 42PFL7762D Dmpbd45 Case R240 Alcatel 4400 CMT-AH10 Fujifilm F10 Servers Toshiba TPM Solution Disk UX-A260 AQ09ugbn MF8170C VL-tone Vl-1 Z-560 Syncmaster 540N SCH-B100 Yamaha RY30 QW1660 Dagger AK77400GN Zelda-majoras Mask Accessories RS200 KX-TG2224W SC-PM29 3 0 DCD-1500AE Beverly 500 IP1800 530SI EW650F KM-2030 Cowon V5 Doorphone VR710 GE29393 GT-C5130 42LT7 Easyshare C653 SB-80DX Lumi 246 CTK-520L DNS-722-4 Zanussi IZ12 6255I E-125 Mounter 24 Changer EMP-TW520 Toolbox Electronic Lexmark T430 Casio 4738 4000S PCG-GRT816M W 83 Cabriolet PM-930C KDL-32E5500 Nikon Scan IC-F6062 AS12hpcn X500-10Q TX-903 Digital MPA XTR-540 BW6311 Motorola H700 YZ450F-2008 SC-AK240 TE 76 CR-L26WA KDL-40HX803 MW-10 CDX-05 Review NP6330 P4VX4 Nokia 6265 Digitech S100 Ftxr50EV1B9 0 0 ESQ-1 YFZ450-2006 ML-1520 CR 250 IC-Z1A Sbig ST-4 K45SS Printer SM1102 FU-440E SV650S Handheld Gps Receiver TA-DA7000ES VGN-NR31z S 8800F Hasbro Rook KX-T7560 KIT R1 PET714 DP102L
manuel d'instructions, Guide de l'utilisateur | Manual de instrucciones, Instrucciones de uso | Bedienungsanleitung, Bedienungsanleitung | Manual de Instruções, guia do usuário | инструкция | návod na použitie, Užívateľská príručka, návod k použití | bruksanvisningen | instrukcja, podręcznik użytkownika | kullanım kılavuzu, Kullanım | kézikönyv, használati útmutató | manuale di istruzioni, istruzioni d'uso | handleiding, gebruikershandleiding
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101