your pk2 device list file is out of date, there are many more k22 chips supported .
your pk2 device list file is out of date, there are many more k22 chips supported .
Warning I'm not a teacher
ooops i dint know.
i tried many times to check if there is a newer version and didnt find any that 2.61 with the devicefile 1.61.
I will check again. thanks for the update really i didnt know it.
First of all i need to Apologize for my absent.
Now :
1. Didnt find and Update for pickit2. Not a problem because i will think to use the following PICs and i see that pickit2 at the moment supports it.
2. As far as the pic16f88 is limited in ram i need to step up and use a better microcontroller. Im Looking at the PIC18F4550 or PIC18F2550.
3.The project as i have it in mind need to have an SD in order to store the Data from GPS Nmea.
I found out that only a microcontroller with 48mhz supports something like that. Apart from that i have a question.
May i use the same speed for All the peripherals SD, Ulcd, GPS? Or do i need to specify different one for each module?
May i use 48mhz for processor speed and use low speed baudrate to communicate for Serial?
Could You help me and clarity what i need for each GPS, SD, Ulcd?
So i need to communicate Serial with GPS module and then i need to store the raw Nmea Data to SD and display what i need from the Nmea protocols to display.
Last edited by astanapane; - 20th June 2018 at 15:49.
The file "PK2Devicefile.dat" have not edited the microcontroller type. Use DEVICE EDITOR software from here https://sites.google.com/site/pk2devicefileeditor/ and here is the Device ID PIC's
where did you find that , its not what I understand the case to be. are you confusing usb support for sd card support ?The project as i have it in mind need to have an SD in order to store the Data from GPS Nmea.
I found out that only a microcontroller with 48mhz supports something like that
unless you specify what spi rate the sd card supports and what sd card system you intend to use [sdfs3 ? fat16? fat 32?] along withMay i use the same speed for All the peripherals SD, Ulcd, GPS? Or do i need to specify different one for each module?
the baud rate used for the serial I/f's and your osc speed it would be guesswork only.
not really you need to supply a lot more infoCould You help me and clarity what i need for each GPS, SD, Ulcd?
compared to PIC18F4550 or PIC18F2550 a pic 18f26k22 has two times the flash memory , sram ,spi ports, eusarts has more timers and can run at 64 MHz . I think it would be a good fiti need to communicate Serial with GPS module and then i need to store the raw Nmea Data to SD and display what i need from the Nmea protocols to display
for that sort of project
Last edited by richard; - 21st June 2018 at 01:49.
Warning I'm not a teacher
Oops well i'm wrong, base on the following and FAT16 it is not necessary.The project as i have it in mind need to have an SD in order to store the Data from GPS Nmea.
I found out that only a microcontroller with 48mhz supports something like that
where did you find that , its not what I understand the case to be. are you confusing usb support for sd card support ?
http://melabs.com/samples/PBP-mixed/sdfs3.htm
I was confused with this link as they specify high MCU speed for FAT32
http://www.picbasic.co.uk/forum/showthread.php?t=18370
Regarding Serial speed baudrate:May i use the same speed for All the peripherals SD, Ulcd, GPS? Or do i need to specify different one for each module?
unless you specify what spi rate the sd card supports and what sd card system you intend to use [sdfs3 ? fat16? fat 32?] along with
the baud rate used for the serial I/f's and your osc speed it would be guesswork only.
1) For GPS, i have tried to send the "right" command for increase the baudrate, with no sucess....it seems that the GPS receives the command but does not like it :P.
2) ulcd seems to work with higher baud rate, but i need to configure the delay times for each command. I havent really understand how to increase the baudrate corresponding to delays. The ulcd needs some delay time to accept the command and display it properly. Is it right?
3) SD card with FAT 16 (when i reach that point we will discuss further). At the moment it is clear that up to 2GB fat 16 is required and is not necessary high MCU speed. But i will try to get the maximum from the PIC.
I understand that im not clear, as i really wont have the knowledge to explain it. Actually im confused with MCU speed, which is the speed that PIC running each command and calculate each command, with the speed of the communication ports.Could You help me and clarity what i need for each GPS, SD, Ulcd?
not really you need to supply a lot more info
I guess that a higher MCU speed is better in order to calculate faster the information from the peripherals. I know my questions are too basic, and believe me i start reading all these stuff in order to understand better. I feel that you cannot help me i i dont understand these basic processes of the PIC.
So i started to read about MCU speed, clock and counter.
i need to communicate Serial with GPS module and then i need to store the raw Nmea Data to SD and display what i need from the Nmea protocols to display.
compared to PIC18F4550 or PIC18F2550 a pic 18f26k22 has two times the flash memory , sram ,spi ports, eusarts has more timers and can run at 64 MHz . I think it would be a good fit
for that sort of project
Really appreciate your advice....PIC18LF26K22 or PIC18LF4550 fits to my project better because i would like to use a single 3.7V Lipo battery not more than 800-1000mha. The Final circuit will have:
1. PIC18LF26K22 or PIC18LF4550
2. GPS module for all the info....Date, Time, Speed, Coordinates etc.
3. SD for storage the raw NMEA Data
4. A display only for the on the go use. For battery saving, a ulcd will not be used normally. SD will keep the info.
Many thanks once again.
I would like to apologize for "breaking" the original TOPIC. Is it possible an Admin to move all the discussion i have started from POST #66, in a NEW thread? Thanks.....
Last edited by astanapane; - 21st June 2018 at 07:45.
the data sheet for the module should resolve that issue1) For GPS, i have tried to send the "right" command for increase the baudrate, with no sucess....it seems that the GPS receives the command but does not like it :P.
the ulcd data sheet should give you that information2) ulcd seems to work with higher baud rate, but i need to configure the delay times for each command. I havent really understand how to increase the baudrate corresponding to delays. The ulcd needs some delay time to accept the command and display it properly. Is it right?
since sd cards use spi [a synchronous data transfer method] cpu osc speed is largely irrelevant as long as it not too fast for the card/mssp combination3) SD card with FAT 16 (when i reach that point we will discuss further). At the moment it is clear that up to 2GB fat 16 is required and is not necessary high MCU speed. But i will try to get the maximum from the PIC.
when you use the mssp module there are several spi clock options.
a PIC18LF4550 is in my opinion not a good choice , the project calls for a chip with two eusarts.
I agree, as I have said from the start what you are asking has no relevance to maidenhead in any way shape or formI would like to apologize for "breaking" the original TOPIC. Is it possible an Admin to move all the discussion i have started from POST #66, in a NEW thread? Thanks.....
Warning I'm not a teacher
Hi Richard,
thanks once again for your time and help. You are right regarding the 18LF4550. It is not for my application.
Some modules requires you to send a checksum at the end of the command. Here for a NEO-6M GPS Module:
Do you really need to change the baud rate? If you are just logging then 9600 is more than enough.Code:'Turn off RMC - Recommended minimum specific GPS/Transit data hserout2 ["$PUBX,40,RMC,0,0,0,0,0,0*47", 13, 10] pause 500 'Turn off GSA - GPS DOP and active satellites hserout2 ["$PUBX,40,GSA,0,0,0,0,0,0*4E", 13, 10] pause 500 'Turn off GSV - GPS Satellites in view hserout2 ["$PUBX,40,GSV,0,0,0,0,0,0*59", 13, 10] pause 500 'Turn off GLL - Geographic position, latitude / longitude hserout2 ["$PUBX,40,GLL,0,0,0,0,0,0*5C", 13, 10] pause 500 'Turn on ZDA hserout2 ["$PUBX,40,ZDA,0,1,0,0,0,0*45", 13, 10] pause 500
FYI, here is my source for most of the NMEA sequences: http://aprs.gids.nl/nmea/
Yep, thanks a lot.....i've seen all that, for my case i have the MKT 3333 and 3339 module. Which have the following
The problem is that it does not work for some reason.Code:'serout2 gps_rx,84, ["$PMTK314,0,1,1,1,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0*0D",13,10] 'serout2 gps_rx,84, ["$PMTK251,57600*2C",13,10] ' baudrate, check MTK manual configuration 'serout2 gps_rx,84, ["$PMTK220,200*2C",13,10] ' 200(millisecond)=0.2(sec)-->1/0.2 pps=5 Hz
I think i need to use the HSEROUT2 instead of SEROUT2. I'm confused at this point.
I get online help for checksum from this site
http://www.hhhh.org/wiml/proj/nmeaxor.html
Bookmarks