Help to setup GPS connection.

[mbox]

I manage to run this code for a start

@ DEVICE HS_OSC
DEFINE    OSC 20
main:

serout2 PortC.6,32774,["To PC",$D]  ;@38400 To PC
serout2 PortB.6,84,[$1B,$45]
serout2 PortB.6,84,["To LCD"] ;@9600 To Lcd
pause 500

goto main
end

I will update my codes with the Gps, and post it here later...

regards,
mbox

[mackrackit]

That is more like it.
Start small and build your way up

[mbox]

I'm trying to add two numbers, 1st number is 140000 and the 2nd is 5377 which will give me 145377. And after getting the sum it will be divided by 60. x= (140000+ 537)/60, I think WORD can not hold much of the integers I need.
Ho do I do this in PBP?

[ScaleRobotics]

You are right, a word only goes up to 65535. If you have PBP v 2.5 or later, (and were using a PIC18 chip) you could select to use PBPL to compile, and define your large variables as LONG instead of WORD.

If you want to stick with the PIC16 series, you could use N-BIT math. http://www.picbasic.co.uk/forum/cont...153-N-Bit_MATH

By the way, it looks like you are using PM as your assembler.

@ DEVICE HS_OSC

You probably need to use MPASM for N-Bit Math to work. For that, you define your configs like this:

@ __config _HS_OSC & _WDT_OFF & _LVP_OFF & _CP_OFF

But you must comment out the configs in you C:/PBP/16F877A.INC file.

See : http://www.picbasic.co.uk/forum/cont...o-your-Program

[mbox]

Hi scalerobotics, I got my setup using Mpasm, and trying to figure out how Darrel's N-Bit_Math works, I need a sample to study its output. Try to use wozzy's code in pic16f877A

PRECISION CON 8 SYSTEM  	' 8 bytes = 64-bit   
INCLUDE "N-Bit_Math.pbp"	' Include Alexander Avtanski's Multibyte Arithmetic 
				' Assembly Library Wrapped for PBP by Darryl Taylor
				' Version:1.3 Beta (1/7/2010)
;@ DEVICE HS_OSC
@ __config _HS_OSC & _WDT_OFF & _LVP_OFF & _CP_OFF
DEFINE OSC 20			' 20 MHz Crystal Oscillator

DEFINE DEBUG_REG PORTC		' PORT C6
DEFINE DEBUG_BIT 6 			' PORT C6
DEFINE DEBUG_BAUD 57600		' BAUD 57600
DEFINE DEBUG_MODE 0 		' 1 = inverted, 0 = true


I			VAR	BYTE

AA64 		VAR BYTE[PRECISION]
BB64		VAR BYTE[PRECISION]
CC64     	VAR BYTE[PRECISION]
DD64		VAR BYTE[PRECISION]

XX64		VAR BYTE[PRECISION]
YY64		VAR BYTE[PRECISION]
ZZ64		VAR BYTE[PRECISION]

PAUSE 500 : DEBUG "   ",10,13,10,13 : PAUSE 500

MAIN:
	
	
	@  MATH_MUL  _AA64, _BB64, _XX64	; @  MATH_MUL  _A, _B, _Res ; Res = A / B - Remainder in REG_Z
	@  MATH_DIV  _CC64, _DD64, _YY64	; @  MATH_DIV  _A, _B, _Res ; Res = A / B - Remainder in REG_Z
	@  MATH_DIV  _DD64, _CC64, _ZZ64	; @  MATH_DIV  _A, _B, _Res ; Res = A / B - Remainder in REG_Z
	
	DEBUG "BYTE ORDER BYTE[7],BYTE[6],BYTE[5],BYTE[4],BYTE[3],BYTE[2],BYTE[1],BYTE[0]",10,13,10,13
	DEBUG "AA64 = " : FOR I = 7 to 0 Step -1 : DEBUG BIN8 AA64[I] : NEXT I : DEBUG 10,13
	DEBUG "BB64 = " : FOR I = 7 to 0 Step -1 : DEBUG BIN8 BB64[I] : NEXT I : DEBUG 10,13
	DEBUG "CC64 = " : FOR I = 7 to 0 Step -1 : DEBUG BIN8 CC64[I] : NEXT I : DEBUG 10,13
	DEBUG "DD64 = " : FOR I = 7 to 0 Step -1 : DEBUG BIN8 DD64[I] : NEXT I : DEBUG 10,13
	DEBUG "XX64 = " : FOR I = 7 to 0 Step -1 : DEBUG BIN8 XX64[I] : NEXT I : DEBUG 10,13
	DEBUG "YY64 = " : FOR I = 7 to 0 Step -1 : DEBUG BIN8 YY64[I] : NEXT I : DEBUG 10,13
	DEBUG "ZZ64 = " : FOR I = 7 to 0 Step -1 : DEBUG BIN8 ZZ64[I] : NEXT I : DEBUG 10,13
	DEBUG "REG_Z = " : FOR I = 7 to 0 Step -1 : DEBUG BIN8 REG_Z[I] : NEXT I : DEBUG 10,13
	DEBUG 10,13,10,13,10,13,10,13
	PAUSE 10000
GOTO MAIN

END

I don't have any display on the hyper terminal window, My first time to encounter DEBUG command, but I think its similar to Serout2, is not it?

regards,
mbox

[mackrackit]

I'm trying to add two numbers, 1st number is 140000 and the 2nd is 5377 which will give me 145377. And after getting the sum it will be divided by 60. x= (140000+ 537)/60, I think WORD can not hold much of the integers I need.
Ho do I do this in PBP?

is this still part of the GPS project or something new?
Either way, where are the numbers coming from?

[mbox]

Yes it's part of the GPS. Google map can interpret this "11 14.5377,125 00.3560". But for my Mobile map application it can not, it reads this format "11.242295, 125.005933", I will explain my alternative solution only for th the latitude part using data "$GPRMC,115209.200,A,1114.5377,N,12500.3439,E,0.02 ,296.54,021110,,,A*65", I extract data to this format "Deg 11 Min 14 Sec 5377". Then I need 14 and 5377 to be this 145377 format (my alternative solution is to 14x10000+5377) then divide it by 60 which will give me 2422.95. I need to make it whole number so 2422.95 x 100 = 242295. Then format the data to this deg 11.242295 ans send it to PortC.6, 11 is the degree and add a "." in between. Any alternative solution would be nice.

regards,
mbox

[mackrackit]

Not quite the accuracy you want but it is close. Maybe someone else can get it closer.
This returns 2422.

    K   CON 10000           
    MINS VAR BYTE 
    SECS VAR WORD    
    MINS = 14 
    SECS = 5377
    Y   VAR WORD     
    Z   VAR WORD     'DUMMY VAR
    Z1  VAR WORD     'DUMMY VAR
    
    START:
    SECS = SECS / 10
    Z = (MINS * K)
    Z1 = DIV32 10
    Y = Z1 + SECS
    Z = (Y / 6) 
    LCDOUT $FE,1,"Z= ",DEC Z
    END

[ScaleRobotics]

Hey Mbox,

I think you are close, but your degrees calculation is a little off (if I am right about you converting minutes and seconds to degrees). I know a short cut, if you can live without decimal seconds.

Say you want to convert 11 deg 14 min and 53.77 seconds to degrees. If you can live without decimal seconds, we have 11 deg 14 min and 54 seconds. To convert to degrees.degrees:

to convert minutes to degrees

(14 * 500)/3 = 2333 (really .2333 degrees)

and now convert seconds

(54 * 50)/18 = 150 (really .015 degrees)

2333
+150
=2483

or 11.2483 degrees. This result fares well with http://www.satsig.net/degrees-minute...calculator.htm , which says the result should be 11.24827 using the seconds decimals.

So with two variables you could store the result. lon_hi would = 11 and lon_low would = 2483. If you need to turn this out the serial port, your code can also place the decimal point between them.

[mbox]

Hi everyone, thanks for the inputs appreciated it very much...I will make tests and see the results regarding the calculation part. So far I made 30 queries by sms from the device and works okay without yet the format and calculation I desire in the mcu, right now the calculation are done and formatting within the mobile codings. I'll be away for 3 days, hopefully by end of the week I can smoothen it more.

Technos: PBP 2.50 and Python for the mobile app.

regards,
mbox