From vk4tec at hotmail.com Fri Aug 6 00:12:35 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Fri, 6 Aug 2004 10:12:35 +1000 Subject: [picsig] test Message-ID: From vk4tec at hotmail.com Sun Aug 8 00:44:56 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Sun, 8 Aug 2004 10:44:56 +1000 Subject: [picsig] GPSiiLCD Plus (Project Update) Message-ID: Howdy, Project Update I developed a PIC based GPS to LCD display, and then I thought, why not through a TinyTrak in there with it .... Now I have a cool GPS display and APRS all in the one box. (GPS Display plus car tracking tone generator) www.tech-software.net (GPSiiLCD Plus link) Feedback welcome Cheers Andy vk4tec From vk4tec at hotmail.com Sat Aug 7 23:30:19 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Sun, 8 Aug 2004 09:30:19 +1000 Subject: [picsig] GPSiiLCD Plus (Project Update) Message-ID: Howdy, Project Update I developed a PIC based GPS to LCD display, and then I thought, why not through a TinyTrak in there with it .... Now I have a cool GPS display and APRS all in the one box. (GPS Display plus car tracking tone generator) www.tech-software.net (GPSiiLCD Plus link) Feedback welcome Cheers Andy vk4tec From vk4tec at hotmail.com Wed Aug 11 19:00:22 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Thu, 12 Aug 2004 05:00:22 +1000 Subject: [picsig] Unusual terminal behaviour Message-ID: Howdy, NMEA Parse. looking at the field after the ",N," Wonder is someone has seen this before ? Using hyperterminal, I send this $GPVTG,300,T,001,M,000.0,N,0A01.E,K*7E and I get this out "SPD 0A01" I send this $GPVTG,300,T,001,M,000.0,N,0001.E,K*7E and I get this out "SPD 00-1" It is almost as if hyperterminal is seeing any two consecutive zeros after the ,N, and following with a "-" Is this a particular ASCII case ? Hook it up to the GPS and all is fine. Maybe I should try another terminal package ? Cheers Andy vk4tec From vk4tec at hotmail.com Thu Aug 12 06:36:36 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Thu, 12 Aug 2004 16:36:36 +1000 Subject: [picsig] EMI Help Message-ID: Ok I built a GPSiiLCD display. works fine on the bench throw it in the car , drive off down the road works for about 5 kms random characters start to creep in. then the whole thing just gets worse - until it unusable - grabage all over the screen even ran it on battery and 12volts from the car . the project is in a plastic case any body had probs with hamhuds and EMI ? i have grounded the shield from the gps to the unit maybe i can try some caps across the bus lines ? Any body an expert on EMI ? Cheers Andy VK4TEC From archer at eskimo.com Thu Aug 12 16:16:14 2004 From: archer at eskimo.com (Curt, WE7U) Date: Thu, 12 Aug 2004 09:16:14 -0700 (PDT) Subject: [picsig] EMI Help In-Reply-To: References: Message-ID: On Thu, 12 Aug 2004, Andrew Rich wrote: > Ok I built a GPSiiLCD display. works fine on the bench > throw it in the car , drive off down the road > works for about 5 kms > random characters start to creep in. > then the whole thing just gets worse - until it unusable - grabage all over > the screen > even ran it on battery and 12volts from the car . > the project is in a plastic case > any body had probs with hamhuds and EMI ? > i have grounded the shield from the gps to the unit > maybe i can try some caps across the bus lines ? > Any body an expert on EMI ? More than likely you're getting horrible stuff coming in on the power wiring. Mobile platforms (forklifts, cars, trucks, boats) throw some pretty nasty stuff at you. -- Curt, WE7U http://www.eskimo.com/~archer "Lotto: A tax on people who are bad at math." -- unknown "Windows: Microsoft's tax on computer illiterates." -- WE7U "The world DOES revolve around me: I picked the coordinate system!" From vk4tec at hotmail.com Thu Aug 12 21:17:55 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Fri, 13 Aug 2004 07:17:55 +1000 Subject: [picsig] RE: EMI Help Message-ID: Thanks to those who replied. To show you what I have setup, i have included a photo http://www.tech-software.net/139_3905.JPG and the schematic. http://www.tech-software.net/nmea6.jpg Ideas ? Plan of attack 1. Wrap aluminium foil 2. Metal case 3. More caps 4. Shorter bus run to LCD 5. Try another GPS 6. Put CRO across the BUS rails with the car running in the driveway From jprouland at comcast.net Thu Aug 12 22:05:33 2004 From: jprouland at comcast.net (J.P. Rouland) Date: Thu, 12 Aug 2004 15:05:33 -0700 Subject: [picsig] RE: EMI Help In-Reply-To: References: Message-ID: <411BE9AD.1050807@comcast.net> Before you go too far, here are a few suggestions: 1) Check your grounds: bring the LCD's ground to the PIC's ground, not the general ground (i.e. as close to the PIC as possible): the LCD needs signals from the PIC. It interprets these signals using its own ground pin as reference, so you want it to be as close to the PIC's own ground as possible. 2) Watch for transients from the car battery: I wouldn't mind seeing a small choke in series with the 12V input to the regulator. On the regulator's input side, be sure to have 1 or 2 0.1uF ceramic capacitors, in parallel with a bigger (10uF, up to 100uF) electrolytic cap. The ceramic cap takes care of "ignition"-type transients. The lytic covers longer, deeper perturbations, like solenoid dumps ( starter, fan, windshield motors, etc..) that CAN momentarily bring the 12V input to ZERO, even, at times, NEGATIVE! 3) Finally, it is KNOWN that the GPS leads often act as an HF/VHF antenna, bringing unexpected signals to the PIC's inputs, and the PIC doesn't like it. Normally, a few ferrite beads on the GPS leads, just before the connection onto the TT3, seem to solve the problem. 4) Foil: good and simple, as a test, BUT, to be "real", you have to be SURE the foil is in GOOD CONTACT with the ground wire on the 12V input. A "floating" shield doesn't protect much!!! Again, you want the GPS, TT3 ( or your PIC), and the display to talk together, meaning they must be using the SAME ground reference, protected from outside influences by the overall shield, itself referenced ( i.e. connected) to the ground wire from the battery, close to the box to protect. 4)The LCD, normally, doesn't use much current, and should have some capacitance on its own board. Still, adding 10uF on the TT3 board ( sorry: your PIC board), close to where the power goes out towards LCD, may not be a bad idea. Good luck, and keep us posted on the results: I dealt a lot -professionnally- with these kind of issues, but still learn new tricks everyday!!! No one-size-fits-all solution in this field! J.P. Rouland NQ6T Andrew Rich wrote: > Thanks to those who replied. > > To show you what I have setup, i have included a photo > > http://www.tech-software.net/139_3905.JPG > > and the schematic. > > http://www.tech-software.net/nmea6.jpg > > Ideas ? > > Plan of attack > > 1. Wrap aluminium foil > 2. Metal case > 3. More caps > 4. Shorter bus run to LCD > 5. Try another GPS > 6. Put CRO across the BUS rails with the car running in the driveway > > > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > From jeff at aerodata.net Thu Aug 12 22:16:37 2004 From: jeff at aerodata.net (Jeff King) Date: Thu, 12 Aug 2004 18:16:37 -0400 Subject: [picsig] RE: EMI Help In-Reply-To: <411BE9AD.1050807@comcast.net> Message-ID: <2004812181637.318335@DARLA> If it is already not there, add a blocking diode on the power from the car to the unit. As JP said, the automotive bus can actually go negative, and that would discharge the input cap if the blocking diode was not there. The alpha of the PIC-E was experiencing similar problems, and I believe this suggestion solved many of them in a automotive environment. On Thu, 12 Aug 2004 15:05:33 -0700, J.P. Rouland wrote: >Before you go too far, here are a few suggestions: 1) Check your >grounds: bring the LCD's ground to the PIC's ground, not the general >ground (i.e. as close to the PIC as possible): the LCD needs signals >from the PIC. It interprets these signals using its own ground pin >as reference, so you want it to be as close to the PIC's own ground >as possible. 2) Watch for transients from the car battery: I >wouldn't mind seeing a small choke in series with the 12V input to >the regulator. On the regulator's input side, be sure to have 1 or 2 >0.1uF ceramic capacitors, in parallel with a bigger (10uF, up to >100uF) electrolytic cap. The ceramic cap takes care of "ignition"- >type transients. The lytic covers longer, deeper perturbations, like >solenoid dumps ( starter, fan, windshield motors, etc..) that CAN >momentarily bring the 12V input to ZERO, even, at times, NEGATIVE! >3) Finally, it is KNOWN that the GPS leads often act as an HF/VHF >antenna, bringing unexpected signals to the PIC's inputs, and the >PIC doesn't like it. Normally, a few ferrite beads on the GPS leads, >just before the connection onto the TT3, seem to solve the problem. >4) Foil: good and simple, as a test, BUT, to be "real", you have to >be SURE the foil is in GOOD CONTACT with the ground wire on the 12V >input. A "floating" shield doesn't protect much!!! Again, you want >the GPS, TT3 ( or your PIC), and the display to talk together, >meaning they must be using the SAME ground reference, protected from >outside influences by the overall shield, itself referenced ( i.e. >connected) to the ground wire from the battery, close to the box to >protect. 4)The LCD, normally, doesn't use much current, and should >have some capacitance on its own board. Still, adding 10uF on the >TT3 board ( sorry: your PIC board), close to where the power goes >out towards LCD, may not be a bad idea. Good luck, and keep us >posted on the results: I dealt a lot -professionnally- with these >kind of issues, but still learn new tricks everyday!!! No one-size- >fits-all solution in this field! J.P. Rouland NQ6T > >Andrew Rich wrote: > >>Thanks to those who replied. >> >>To show you what I have setup, i have included a photo >> >>http://www.tech-software.net/139_3905.JPG >> >>and the schematic. >> >>http://www.tech-software.net/nmea6.jpg >> >>Ideas ? >> >>Plan of attack >> >>1. Wrap aluminium foil 2. Metal case 3. More caps 4. Shorter bus >>run to LCD 5. Try another GPS 6. Put CRO across the BUS rails with >>the car running in the driveway >> >> >> >> >>_______________________________________________ picsig mailing list >>picsig at lists.tapr.org https://lists.tapr.org/cgi- >>bin/mailman/listinfo/picsig >> > > > >_______________________________________________ picsig mailing list >picsig at lists.tapr.org https://lists.tapr.org/cgi- >bin/mailman/listinfo/picsig From vk4tec at hotmail.com Thu Aug 12 22:24:04 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Fri, 13 Aug 2004 08:24:04 +1000 Subject: [picsig] RE: EMI Help References: <2004812181637.318335@DARLA> Message-ID: I do not believe the power supply is the problem at all. 9volt battery and 12 volts from the car ------same thing ----- Original Message ----- From: "Jeff King" To: "TAPR PIC Mailing List" Sent: Friday, August 13, 2004 8:16 AM Subject: Re: [picsig] RE: EMI Help If it is already not there, add a blocking diode on the power from the car to the unit. As JP said, the automotive bus can actually go negative, and that would discharge the input cap if the blocking diode was not there. The alpha of the PIC-E was experiencing similar problems, and I believe this suggestion solved many of them in a automotive environment. On Thu, 12 Aug 2004 15:05:33 -0700, J.P. Rouland wrote: >Before you go too far, here are a few suggestions: 1) Check your >grounds: bring the LCD's ground to the PIC's ground, not the general >ground (i.e. as close to the PIC as possible): the LCD needs signals >from the PIC. It interprets these signals using its own ground pin >as reference, so you want it to be as close to the PIC's own ground >as possible. 2) Watch for transients from the car battery: I >wouldn't mind seeing a small choke in series with the 12V input to >the regulator. On the regulator's input side, be sure to have 1 or 2 >0.1uF ceramic capacitors, in parallel with a bigger (10uF, up to >100uF) electrolytic cap. The ceramic cap takes care of "ignition"- >type transients. The lytic covers longer, deeper perturbations, like >solenoid dumps ( starter, fan, windshield motors, etc..) that CAN >momentarily bring the 12V input to ZERO, even, at times, NEGATIVE! >3) Finally, it is KNOWN that the GPS leads often act as an HF/VHF >antenna, bringing unexpected signals to the PIC's inputs, and the >PIC doesn't like it. Normally, a few ferrite beads on the GPS leads, >just before the connection onto the TT3, seem to solve the problem. >4) Foil: good and simple, as a test, BUT, to be "real", you have to >be SURE the foil is in GOOD CONTACT with the ground wire on the 12V >input. A "floating" shield doesn't protect much!!! Again, you want >the GPS, TT3 ( or your PIC), and the display to talk together, >meaning they must be using the SAME ground reference, protected from >outside influences by the overall shield, itself referenced ( i.e. >connected) to the ground wire from the battery, close to the box to >protect. 4)The LCD, normally, doesn't use much current, and should >have some capacitance on its own board. Still, adding 10uF on the >TT3 board ( sorry: your PIC board), close to where the power goes >out towards LCD, may not be a bad idea. Good luck, and keep us >posted on the results: I dealt a lot -professionnally- with these >kind of issues, but still learn new tricks everyday!!! No one-size- >fits-all solution in this field! J.P. Rouland NQ6T > >Andrew Rich wrote: > >>Thanks to those who replied. >> >>To show you what I have setup, i have included a photo >> >>http://www.tech-software.net/139_3905.JPG >> >>and the schematic. >> >>http://www.tech-software.net/nmea6.jpg >> >>Ideas ? >> >>Plan of attack >> >>1. Wrap aluminium foil 2. Metal case 3. More caps 4. Shorter bus >>run to LCD 5. Try another GPS 6. Put CRO across the BUS rails with >>the car running in the driveway >> >> >> >> >>_______________________________________________ picsig mailing list >>picsig at lists.tapr.org https://lists.tapr.org/cgi- >>bin/mailman/listinfo/picsig >> > > > >_______________________________________________ picsig mailing list >picsig at lists.tapr.org https://lists.tapr.org/cgi- >bin/mailman/listinfo/picsig _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From vk4tec at hotmail.com Thu Aug 12 22:28:51 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Fri, 13 Aug 2004 08:28:51 +1000 Subject: [picsig] RE: EMI Help References: <411BE9AD.1050807@comcast.net> Message-ID: Thanks. 1. Same thing happens on 9volt battery 2. GND's are fine 3. I had garbage before, and added 10uF across reg, fixed it inside 4. I have already got the braid of the GPS cable to deck I am going to slow down the switching rate on the data bus It is cranked up flat out Cheers ----- Original Message ----- From: "J.P. Rouland" To: "Andrew Rich" ; "TAPR PIC Mailing List" Sent: Friday, August 13, 2004 8:05 AM Subject: Re: [picsig] RE: EMI Help Before you go too far, here are a few suggestions: 1) Check your grounds: bring the LCD's ground to the PIC's ground, not the general ground (i.e. as close to the PIC as possible): the LCD needs signals from the PIC. It interprets these signals using its own ground pin as reference, so you want it to be as close to the PIC's own ground as possible. 2) Watch for transients from the car battery: I wouldn't mind seeing a small choke in series with the 12V input to the regulator. On the regulator's input side, be sure to have 1 or 2 0.1uF ceramic capacitors, in parallel with a bigger (10uF, up to 100uF) electrolytic cap. The ceramic cap takes care of "ignition"-type transients. The lytic covers longer, deeper perturbations, like solenoid dumps ( starter, fan, windshield motors, etc..) that CAN momentarily bring the 12V input to ZERO, even, at times, NEGATIVE! 3) Finally, it is KNOWN that the GPS leads often act as an HF/VHF antenna, bringing unexpected signals to the PIC's inputs, and the PIC doesn't like it. Normally, a few ferrite beads on the GPS leads, just before the connection onto the TT3, seem to solve the problem. 4) Foil: good and simple, as a test, BUT, to be "real", you have to be SURE the foil is in GOOD CONTACT with the ground wire on the 12V input. A "floating" shield doesn't protect much!!! Again, you want the GPS, TT3 ( or your PIC), and the display to talk together, meaning they must be using the SAME ground reference, protected from outside influences by the overall shield, itself referenced ( i.e. connected) to the ground wire from the battery, close to the box to protect. 4)The LCD, normally, doesn't use much current, and should have some capacitance on its own board. Still, adding 10uF on the TT3 board sorry: your PIC board), close to where the power goes out towards LCD, may not be a bad idea. Good luck, and keep us posted on the results: I dealt a lot -professionnally- with these kind of issues, but still learn new tricks everyday!!! No one-size-fits-all solution in this field! J.P. Rouland NQ6T Andrew Rich wrote: > Thanks to those who replied. > > To show you what I have setup, i have included a photo > > http://www.tech-software.net/139_3905.JPG > > and the schematic. > > http://www.tech-software.net/nmea6.jpg > > Ideas ? > > Plan of attack > > 1. Wrap aluminium foil > 2. Metal case > 3. More caps > 4. Shorter bus run to LCD > 5. Try another GPS > 6. Put CRO across the BUS rails with the car running in the driveway > > > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > From vk4tec at hotmail.com Fri Aug 13 04:52:09 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Fri, 13 Aug 2004 14:52:09 +1000 Subject: [picsig] RE: EMI Help References: <2004812181637.318335@DARLA> Message-ID: Thanks to all that helped. Here is what I did :- 1. Shortened the LCD data bus lead by half 2. Changed the code so there are less interrupts (less chance of glitches) 3. Added a 0.1uF across the Vin and Vout (I already had 10uF on Vin and V out) 4. Added a 0.1uF across the GPS in data line 5. Wound the input voltage leads in a ferrite bead. 6. Moved the caps closer to the voltage regulator Now I am up against thermal stress. I turned up the heater in the car and the regulator started to give up. Bring the temperature back again and all is well. What is the best way to get from car volts (14Volts) down to something acceptable for a 5 volt regulator ? Most of the problem from running off the car is heat dissapation. Getting from 14Volts down to 7ish volts. Voltage divider ? Cheers Andy VK4TEC ----- Original Message ----- From: "Jeff King" To: "TAPR PIC Mailing List" Sent: Friday, August 13, 2004 8:16 AM Subject: Re: [picsig] RE: EMI Help If it is already not there, add a blocking diode on the power from the car to the unit. As JP said, the automotive bus can actually go negative, and that would discharge the input cap if the blocking diode was not there. The alpha of the PIC-E was experiencing similar problems, and I believe this suggestion solved many of them in a automotive environment. On Thu, 12 Aug 2004 15:05:33 -0700, J.P. Rouland wrote: >Before you go too far, here are a few suggestions: 1) Check your >grounds: bring the LCD's ground to the PIC's ground, not the general >ground (i.e. as close to the PIC as possible): the LCD needs signals >from the PIC. It interprets these signals using its own ground pin >as reference, so you want it to be as close to the PIC's own ground >as possible. 2) Watch for transients from the car battery: I >wouldn't mind seeing a small choke in series with the 12V input to >the regulator. On the regulator's input side, be sure to have 1 or 2 >0.1uF ceramic capacitors, in parallel with a bigger (10uF, up to >100uF) electrolytic cap. The ceramic cap takes care of "ignition"- >type transients. The lytic covers longer, deeper perturbations, like >solenoid dumps ( starter, fan, windshield motors, etc..) that CAN >momentarily bring the 12V input to ZERO, even, at times, NEGATIVE! >3) Finally, it is KNOWN that the GPS leads often act as an HF/VHF >antenna, bringing unexpected signals to the PIC's inputs, and the >PIC doesn't like it. Normally, a few ferrite beads on the GPS leads, >just before the connection onto the TT3, seem to solve the problem. >4) Foil: good and simple, as a test, BUT, to be "real", you have to >be SURE the foil is in GOOD CONTACT with the ground wire on the 12V >input. A "floating" shield doesn't protect much!!! Again, you want >the GPS, TT3 ( or your PIC), and the display to talk together, >meaning they must be using the SAME ground reference, protected from >outside influences by the overall shield, itself referenced ( i.e. >connected) to the ground wire from the battery, close to the box to >protect. 4)The LCD, normally, doesn't use much current, and should >have some capacitance on its own board. Still, adding 10uF on the >TT3 board ( sorry: your PIC board), close to where the power goes >out towards LCD, may not be a bad idea. Good luck, and keep us >posted on the results: I dealt a lot -professionnally- with these >kind of issues, but still learn new tricks everyday!!! No one-size- >fits-all solution in this field! J.P. Rouland NQ6T > >Andrew Rich wrote: > >>Thanks to those who replied. >> >>To show you what I have setup, i have included a photo >> >>http://www.tech-software.net/139_3905.JPG >> >>and the schematic. >> >>http://www.tech-software.net/nmea6.jpg >> >>Ideas ? >> >>Plan of attack >> >>1. Wrap aluminium foil 2. Metal case 3. More caps 4. Shorter bus >>run to LCD 5. Try another GPS 6. Put CRO across the BUS rails with >>the car running in the driveway >> >> >> >> >>_______________________________________________ picsig mailing list >>picsig at lists.tapr.org https://lists.tapr.org/cgi- >>bin/mailman/listinfo/picsig >> > > > >_______________________________________________ picsig mailing list >picsig at lists.tapr.org https://lists.tapr.org/cgi- >bin/mailman/listinfo/picsig _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From vk4tec at hotmail.com Fri Aug 13 04:49:53 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Fri, 13 Aug 2004 14:49:53 +1000 Subject: [picsig] Re: EMI Help (fixed) Message-ID: Thanks to all that helped. Here is what I did :- 1. Shortened the LCD data bus lead by half 2. Changed the code so there are less interrupts (less chance of glitches) 3. Added a 0.1uF across the Vin and Vout (I already had 10uF on Vin and V out) 4. Added a 0.1uF across the GPS in data line 5. Wound the input voltage leads in a ferrite bead. 6. Moved the caps closer to the voltage regulator Now I am up against thermal stress. I turned up the heater in the car and the regulator started to give up. Bring the temperature back again and all is well. What is the best way to get from car volts (14Volts) down to something acceptable for a 5 volt regulator ? Most of the problem from running off the car is heat dissapation. Getting from 14Volts down to 7ish volts. Voltage divider ? Cheers Andy VK4TEC From vk4tec at hotmail.com Fri Aug 13 17:04:46 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Sat, 14 Aug 2004 03:04:46 +1000 Subject: [picsig] GPSiiLCD DC Power Supply Message-ID: Scott that is a multimeter in line ...177 mAH actually It gets so hot you can not touch it. (no heat sink) When you turn the backlight off the LCD, the current drops and the heat goes. What I found was that when I reduced the voltage to 7 Volts on the input, the reg runs really cool. But when you up the voltage in the car, the reg has to loose the extra volts somehow. I have drawn up the buck reg cct. My friend builds PIC's for a living, and he has just discovered em too. http://www.tech-software.net/gpsiilcd.php LM2576. I have updated my cct diagram, with the planned changes. My mate says they run very cool. I am interested in a more correct solution. And that seems the way. I really hate stressing electronics. They need all the margin you can give them . hi hi One thing that I think really helped me, was disabling the serial rx routines when you don't need them. They really only increas the risk of interference to other parts of the code. Being interrupt driven. When I first had the cct running on the bench, the 7805 would run away with no caps, then adding 10uF helped alot. Then it was not until the cct hit the harsher power and heat environ, that the cct displayed different affects from volts, EMI and heat stress. All good stuff. Some off that stuff they taught at UNI is sinking in hi hi I have a CRO coming soon, which I have never had before, and the car is just downstairs. What I would like to do is probe the voltage regulator and make notes before I move onto the buck step down reg. Cheers Gents and Ladies From isomk at airmail.net Fri Aug 13 23:05:45 2004 From: isomk at airmail.net (isomk at airmail.net) Date: Fri, 13 Aug 2004 18:05:45 -0500 (CDT) Subject: [picsig] GPSiiLCD DC Power Supply In-Reply-To: References: Message-ID: <1115.4.226.24.147.1092438345.squirrel@webmail.airmail.net> I run my PIC-E off a 5v fixed linear regulator that is being feed from a 723 adj linear regulator that brings the 12.6-14.2 down to 9v. I may be wasting power but it works great and I think it helps to keep noise out of the PIC-E Not most attractive way to do it... but works. Of course, a string of series 1N4001s could be used to drop the voltage down some too... poor mans regulator. lets see who can do it the cheapest... KD5AIA > Scott that is a multimeter in line ...177 mAH actually > It gets so hot you can not touch it. (no heat sink) > When you turn the backlight off the LCD, the current drops and the heat > goes. > What I found was that when I reduced the voltage to 7 Volts on the input, > the reg runs really cool. > But when you up the voltage in the car, the reg has to loose the extra > volts > somehow. From vk4tec at hotmail.com Sat Aug 14 08:35:30 2004 From: vk4tec at hotmail.com (Andrew Rich) Date: Sat, 14 Aug 2004 18:35:30 +1000 Subject: [picsig] Telemetry question Message-ID: If I want to send RS232 data across a voice channel, what is stopping me using MX614 ? No checksum, not interested, no flags, no ax25 not interested, just wanna send data. Comments ? From mailist at san.rr.com Mon Aug 16 06:37:38 2004 From: mailist at san.rr.com (Barry Gershenfeld) Date: Sun, 15 Aug 2004 23:37:38 -0700 Subject: [picsig] GPSiiLCD DC Power Supply In-Reply-To: Message-ID: <4.2.0.58.20040815213435.01d1a100@postoffice.worldnet.att.net> >multimeter in line ...177 mAH actually >It gets so hot you can not touch it. (no heat sink) To go from 14 volts to 5 volts requires you drop 9 volts, and at 177 mA that means 1.6 watts. And it doesn't matter how you do it or where you do it. A resistor, a regulator, a string of diodes, all have to shed 1.6 watts somehow. Putting a resistor (or another regulator) ahead of the 7805 just divides the heat between the two devices. That is valid if that is how you want to do it. Having a heat sink can also work for you. The temperature of the device is going to be related to how little a space you try to keep that 1.6 watts in. Even a small heat sink will be cooler than just the regulator by itself. >When you turn the backlight off the LCD, the current drops and the heat goes. You mentioned that backlight as the big contributor to current draw. You might consider taking the backlight off the main supply and running it on its own supply. You still would burn the power but maybe your concern is only to keep the other regulator cool. The light doesn't demand much in the way of regulation, either. I'm assuming the light is independent of the display. Every one I've seen is. Lastly, this commentary assumes a resistive device to drop the voltage, which all the above mentioned are. If you do it with a switching supply, you can get very good efficiency and little heat. But that's another story, one you may be about to embark on as you have mentioned the buck regulator. What I talked about could spare you from going that route. Barry From dvanhorn at dvanhorn.org Thu Aug 19 02:33:46 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Wed, 18 Aug 2004 21:33:46 -0500 Subject: [picsig] Something a bit off the wall In-Reply-To: References: Message-ID: <6.1.2.0.2.20040818212547.040d6010@mail.dvanhorn.org> I just got a box of NKK Smartswitches, through one of the fellows on the piclist, and I've written an example application for the AVR (sorry, no pics here) that implements graphics and text (limited) with color changing, and smooth roll and scan. IS15ANCP4CF is the part number of the switches I have, red/green backlight, 40 x 24 lcd. http://www.dvanhorn.org/AvrSoftware/ is where the code lives, and http://www.nkksmartswitch.com/ is the link to find out about the switches. I have not yet located a disti for them, and I understand the singles pricing is somewhat high.. But they are WAY cool! From vk4tec at tech-software.net Thu Aug 19 20:17:10 2004 From: vk4tec at tech-software.net (Andrew Rich) Date: Fri, 20 Aug 2004 06:17:10 +1000 Subject: [picsig] test Message-ID: From vk4tec at tech-software.net Mon Aug 23 09:39:55 2004 From: vk4tec at tech-software.net (Andrew Rich) Date: Mon, 23 Aug 2004 19:39:55 +1000 Subject: [picsig] APRS tone encode question Message-ID: I threw the tinytrak audio onto a CRO and compared it to a sine wave from a sig gen. How come a DAC ladder network of 4 resistors only produces 8 steps ? Should it not end up being 16 steps ? 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 image http://www.tech-software.net/139_3935.JPG From dvanhorn at dvanhorn.org Mon Aug 23 14:06:49 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Mon, 23 Aug 2004 09:06:49 -0500 Subject: [picsig] APRS tone encode question In-Reply-To: References: Message-ID: <6.1.2.0.2.20040823090355.044adec0@mail.dvanhorn.org> At 04:39 AM 8/23/2004, Andrew Rich wrote: >I threw the tinytrak audio onto a CRO and compared it to a sine wave from a >sig gen. > >How come a DAC ladder network of 4 resistors only produces 8 steps ? > >Should it not end up being 16 steps ? The hardware does, but obviously the software dosen't. You would have to deal with the timer int twice as frequently, and that may have become a problem, especially in a PIC. From vk4tec at tech-software.net Mon Aug 23 20:46:16 2004 From: vk4tec at tech-software.net (Andrew Rich) Date: Tue, 24 Aug 2004 06:46:16 +1000 Subject: [picsig] RE: [aprssig] APRS tone encode question In-Reply-To: <000201c4893d$68669460$0a01a8c0@home.miller.org> Message-ID: Scott how do you get this waveform ? RC ? -----Original Message----- From: Scott Miller [mailto:scott at 3xf.com]On Behalf Of scott at opentrac.org Sent: Tuesday, 24 August 2004 4:17 AM To: vk4tec at tech-software.net; 'TAPR APRS Mailing List'; 'TAPR PIC Development Special Interest Group' Subject: RE: [aprssig] APRS tone encode question Yeah, I'd expect 16 levels. Haven't had a chance to look at my TT3 to see what it's actually doing. Here's a snapshot of an OpenTracker's output. Steps aren't really visible on this 'scope... http://n1vg.net/opentracker/images/waveform.jpg The OpenTracker uses PWM for D/A. In AFSK mode it uses 4 bits resolution, and in BPSK mode it's 8. Works pretty well. I'll have to do a comparison of the output waveforms of the TT3, OpenTracker, and MX614 sometime. For audio stuff, Yoshimasa Electronic's RAL package is great. It's got a nice oscilloscope and FFT analyzer display, plus a signal generator and assorted other features. Scott N1VG -----Original Message----- From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Andrew Rich Sent: Monday, August 23, 2004 2:40 AM To: TAPR APRS Special Interest Group; TAPR PIC Development Special Interest Group Subject: [aprssig] APRS tone encode question I threw the tinytrak audio onto a CRO and compared it to a sine wave from a sig gen. How come a DAC ladder network of 4 resistors only produces 8 steps ? Should it not end up being 16 steps ? 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101 1110 1111 image http://www.tech-software.net/139_3935.JPG _______________________________________________ aprssig mailing list aprssig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig From jtowler at xtra.co.nz Mon Aug 23 21:36:16 2004 From: jtowler at xtra.co.nz (jtowler) Date: Tue, 24 Aug 2004 09:36:16 +1200 Subject: [picsig] RE: [aprssig] APRS tone encode question In-Reply-To: Message-ID: <001901c48959$39009290$0264a8c0@AFOX> Guys, Interesting that the original picture of the 3 bit resistor waveform and the MX614 waveform both look sin-wave in shape, but that last one from OpenTracker looks much more like a triangle shape. Very sharp looking peaks. Real question: How well does each decode on typical receive units? Just interested ... Not really too important ... Just interacting to pass the time ... Regards, Jim, ZL1TYF > -----Original Message----- > From: picsig-bounces at lists.tapr.org > [mailto:picsig-bounces at lists.tapr.org] On Behalf Of Andrew Rich > Sent: Tuesday, 24 August 2004 8:46 a.m. > To: scott at opentrac.org; 'TAPR APRS Mailing List'; 'TAPR PIC > Development Special Interest Group' > Subject: [picsig] RE: [aprssig] APRS tone encode question > > > Scott how do you get this waveform ? RC ? > > > -----Original Message----- > From: Scott Miller [mailto:scott at 3xf.com]On Behalf Of > scott at opentrac.org > Sent: Tuesday, 24 August 2004 4:17 AM > To: vk4tec at tech-software.net; 'TAPR APRS Mailing List'; 'TAPR PIC > Development Special Interest Group' > Subject: RE: [aprssig] APRS tone encode question > > > Yeah, I'd expect 16 levels. Haven't had a chance to look at > my TT3 to see > what it's actually doing. > > Here's a snapshot of an OpenTracker's output. Steps aren't > really visible > on this 'scope... > > http://n1vg.net/opentracker/images/waveform.jpg > > The OpenTracker uses PWM for D/A. In AFSK mode it uses 4 > bits resolution, > and in BPSK mode it's 8. Works pretty well. I'll have to do > a comparison > of the output waveforms of the TT3, OpenTracker, and MX614 > sometime. For > audio stuff, Yoshimasa Electronic's RAL package is great. > It's got a nice > oscilloscope and FFT analyzer display, plus a signal > generator and assorted > other features. > > Scott > N1VG > > -----Original Message----- > From: aprssig-bounces at lists.tapr.org > [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Andrew Rich > Sent: Monday, August 23, 2004 2:40 AM > To: TAPR APRS Special Interest Group; TAPR PIC Development Special > Interest Group > Subject: [aprssig] APRS tone encode question > > > I threw the tinytrak audio onto a CRO and compared it to a > sine wave from a > sig gen. > > How come a DAC ladder network of 4 resistors only produces 8 steps ? > > Should it not end up being 16 steps ? > > 0000 > 0001 > 0010 > 0011 > 0100 > 0101 > 0110 > 0111 > 1000 > 1001 > 1010 > 1011 > 1100 > 1101 > 1110 > 1111 > > image > > http://www.tech-software.net/139_3935.JPG > > > _______________________________________________ > aprssig mailing list > aprssig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig > > > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > From dvanhorn at dvanhorn.org Mon Aug 23 22:14:58 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Mon, 23 Aug 2004 17:14:58 -0500 Subject: [picsig] RE: [aprssig] APRS tone encode question In-Reply-To: <001901c48959$39009290$0264a8c0@AFOX> References: <001901c48959$39009290$0264a8c0@AFOX> Message-ID: <6.1.2.0.2.20040823171340.04989ec0@mail.dvanhorn.org> At 04:36 PM 8/23/2004, jtowler wrote: >Guys, > >Interesting that the original picture of the 3 bit resistor waveform and the >MX614 waveform both look sin-wave in shape, but that last one from >OpenTracker looks much more like a triangle shape. Very sharp looking peaks. If the DAC resistors aren't sized properly, then you end up with a triangle. It just has more harmonic content that way. From dvanhorn at dvanhorn.org Tue Aug 24 04:41:09 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Mon, 23 Aug 2004 23:41:09 -0500 Subject: [picsig] RE: [aprssig] APRS tone encode question In-Reply-To: <6.1.2.0.2.20040823171340.04989ec0@mail.dvanhorn.org> References: <001901c48959$39009290$0264a8c0@AFOX> <6.1.2.0.2.20040823171340.04989ec0@mail.dvanhorn.org> Message-ID: <6.1.2.0.2.20040823233915.04bc0648@mail.dvanhorn.org> At 05:14 PM 8/23/2004, Dave VanHorn wrote: >At 04:36 PM 8/23/2004, jtowler wrote: > >>Guys, >> >>Interesting that the original picture of the 3 bit resistor waveform and the >>MX614 waveform both look sin-wave in shape, but that last one from >>OpenTracker looks much more like a triangle shape. Very sharp looking peaks. > >If the DAC resistors aren't sized properly, then you end up with a triangle. >It just has more harmonic content that way. The other way to hose that up, is using equal time intervals for each step. Sounds like this is what they did. The frequency is right, but it's got more harmonic content than it should. Normally, you'd have a lookup table that sets the duration of each step, and of course you only need a quarter of a sine wave, since you can mirror and invert it to get the other three quadrants. From jprouland at comcast.net Tue Aug 24 05:40:35 2004 From: jprouland at comcast.net (J.P. Rouland) Date: Mon, 23 Aug 2004 22:40:35 -0700 Subject: [picsig] RE: [aprssig] APRS tone encode question In-Reply-To: <6.1.2.0.2.20040823233915.04bc0648@mail.dvanhorn.org> References: <001901c48959$39009290$0264a8c0@AFOX> <6.1.2.0.2.20040823171340.04989ec0@mail.dvanhorn.org> <6.1.2.0.2.20040823233915.04bc0648@mail.dvanhorn.org> Message-ID: <412AD4D3.9040803@comcast.net> Dave, The most common way is to use equal times ( simpler on the micro), and size the resistors.... "non-linear DAC".... J.P. NQ6T Dave VanHorn wrote: > At 05:14 PM 8/23/2004, Dave VanHorn wrote: > > >>At 04:36 PM 8/23/2004, jtowler wrote: >> >> >>>Guys, >>> >>>Interesting that the original picture of the 3 bit resistor waveform and the >>>MX614 waveform both look sin-wave in shape, but that last one from >>>OpenTracker looks much more like a triangle shape. Very sharp looking peaks. >> >>If the DAC resistors aren't sized properly, then you end up with a triangle. >>It just has more harmonic content that way. > > > The other way to hose that up, is using equal time intervals for each step. > Sounds like this is what they did. > The frequency is right, but it's got more harmonic content than it should. > Normally, you'd have a lookup table that sets the duration of each step, and of course you only need a quarter of a sine wave, since you can mirror and invert it to get the other three quadrants. > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > From VE3STI at rac.ca Wed Aug 25 19:17:44 2004 From: VE3STI at rac.ca (David Beach) Date: Wed, 25 Aug 2004 15:17:44 -0400 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD Message-ID: I am toying with the idea of my first real 'from the ground up' PIC programming project. It's not a ham project but I'm not sure who else to ask and it uses concepts also used by people here. I have a boat with a Flo-Scan meter that reads fuel flow in litres/hour. I also have a Garmin GPS that can spew out the usual speed data, etc., over RS-232. For about $280 USD, I can get the meter modified at the factory to also read mileage but I thought it might be an interesting exercise to try a separate readout. A separate readout could also display other GPS info. I can see 4 major 'modules' of code. First, I need to receive and parse the output of the GPS for speed data, then I need to receive and interpret the output of the fuel flow sensor (I think it is a pulsed output proportional to flow but I haven't figured this out for sure. The transducer is a proprietary one made by Flo-Scan.), then, a bunch of arithmetic calculations need to be done and, finally, output the fuel consumption info to a 'Hitachi standard' 16x2 LCD display. Rather than re-inventing the wheel, I was wondering if anyone knew of 'blocks of code' that are available (public domain or whatever) for receiving/parsing GPS data and ouputting data to an LCD display. Any suggestions as to where such might be available? The other modules I presume I will need to do from scratch - unless someone else has tried reading from a Flo-Scan sensor! If there are free/cheap higher level language compilers, I would be tempted to use one rather than assembler. I presume almost any 18 pin PIC will do as none of this sounds particularly complicated or specialized. I have a few 16F628As and a couple of 16F88s hanging around. This will be an 'over the winter' project for next year's boating. Any comments would be welcome! (Maybe 'just buy the modification from the factory!') David Beach VE3STI From jprouland at comcast.net Wed Aug 25 19:34:53 2004 From: jprouland at comcast.net (J.P. Rouland) Date: Wed, 25 Aug 2004 12:34:53 -0700 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: References: Message-ID: <412CE9DD.4010202@comcast.net> If possible, use more than 16x2 display. Look at 16x4's , 20x2's, and all the surplus ones (Alltronics.com, mpja.com, etc..). They all "program almost the same", and the readability would be MUCH improved. Price difference is small. Some guys on this list have worked on the GPS part.. but will they share their code? We shall wait for the answers.... J.P. NQ6T David Beach wrote: > I am toying with the idea of my first real 'from the ground up' PIC > programming project. It's not a ham project but I'm not sure who else to ask > and it uses concepts also used by people here. > > I have a boat with a Flo-Scan meter that reads fuel flow in litres/hour. I > also have a Garmin GPS that can spew out the usual speed data, etc., over > RS-232. For about $280 USD, I can get the meter modified at the factory to > also read mileage but I thought it might be an interesting exercise to try a > separate readout. A separate readout could also display other GPS info. > > I can see 4 major 'modules' of code. First, I need to receive and parse the > output of the GPS for speed data, then I need to receive and interpret the > output of the fuel flow sensor (I think it is a pulsed output proportional > to flow but I haven't figured this out for sure. The transducer is a > proprietary one made by Flo-Scan.), then, a bunch of arithmetic calculations > need to be done and, finally, output the fuel consumption info to a 'Hitachi > standard' 16x2 LCD display. > > Rather than re-inventing the wheel, I was wondering if anyone knew of > 'blocks of code' that are available (public domain or whatever) for > receiving/parsing GPS data and ouputting data to an LCD display. Any > suggestions as to where such might be available? The other modules I presume > I will need to do from scratch - unless someone else has tried reading from > a Flo-Scan sensor! > > If there are free/cheap higher level language compilers, I would be tempted > to use one rather than assembler. > > I presume almost any 18 pin PIC will do as none of this sounds particularly > complicated or specialized. I have a few 16F628As and a couple of 16F88s > hanging around. > > This will be an 'over the winter' project for next year's boating. Any > comments would be welcome! (Maybe 'just buy the modification from the > factory!') > > David Beach > VE3STI > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > From dvanhorn at dvanhorn.org Wed Aug 25 19:37:40 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Wed, 25 Aug 2004 14:37:40 -0500 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: References: Message-ID: <6.1.2.0.2.20040825143513.04aa6560@mail.dvanhorn.org> > >I can see 4 major 'modules' of code. First, I need to receive and parse the >output of the GPS for speed data, then I need to receive and interpret the >output of the fuel flow sensor (I think it is a pulsed output proportional >to flow but I haven't figured this out for sure. The transducer is a >proprietary one made by Flo-Scan.), then, a bunch of arithmetic calculations >need to be done and, finally, output the fuel consumption info to a 'Hitachi >standard' 16x2 LCD display. You'll likely need a timer if it's a pulsed output, or a counter and read it off every so often. You can get clock time from the GPS. >Rather than re-inventing the wheel, I was wondering if anyone knew of >'blocks of code' that are available (public domain or whatever) for >receiving/parsing GPS data and ouputting data to an LCD display. Any >suggestions as to where such might be available? The other modules I presume >I will need to do from scratch - unless someone else has tried reading from >a Flo-Scan sensor! If you can get a spec, then it's not a big problem, unless the electrical interface is really nasty. >If there are free/cheap higher level language compilers, I would be tempted >to use one rather than assembler. Wimp :) >I presume almost any 18 pin PIC will do as none of this sounds particularly >complicated or specialized. I have a few 16F628As and a couple of 16F88s >hanging around. It would be easiest, if you used one with a hardware UART. You'll find LCD code on the MIT piclist I'm sure. From hshk at ix.netcom.com Wed Aug 25 19:33:11 2004 From: hshk at ix.netcom.com (HSHK) Date: Wed, 25 Aug 2004 15:33:11 -0400 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: <412CE9DD.4010202@comcast.net> References: <412CE9DD.4010202@comcast.net> Message-ID: <200408251533110332.0060DAE9@mail.nacs.net> I have some 16 x 4 LCD display that use the HD4470. Email me directly... Bill KA8VIT ka8vit at ix.netcom.com *********** REPLY SEPARATOR *********** On 8/25/2004 at 12:34 PM J.P. Rouland wrote: >If possible, use more than 16x2 display. >Look at 16x4's , 20x2's, and all the surplus ones (Alltronics.com, >mpja.com, etc..). They all "program almost the same", and the >readability would be MUCH improved. Price difference is small. >Some guys on this list have worked on the GPS part.. but will they share >their code? We shall wait for the answers.... >J.P. NQ6T > >David Beach wrote: > >> I am toying with the idea of my first real 'from the ground up' PIC >> programming project. It's not a ham project but I'm not sure who else to >ask >> and it uses concepts also used by people here. >> >> I have a boat with a Flo-Scan meter that reads fuel flow in litres/hour. >I >> also have a Garmin GPS that can spew out the usual speed data, etc., over >> RS-232. For about $280 USD, I can get the meter modified at the factory >to >> also read mileage but I thought it might be an interesting exercise to >try a >> separate readout. A separate readout could also display other GPS info. >> >> I can see 4 major 'modules' of code. First, I need to receive and parse >the >> output of the GPS for speed data, then I need to receive and interpret >the >> output of the fuel flow sensor (I think it is a pulsed output >proportional >> to flow but I haven't figured this out for sure. The transducer is a >> proprietary one made by Flo-Scan.), then, a bunch of arithmetic >calculations >> need to be done and, finally, output the fuel consumption info to a >'Hitachi >> standard' 16x2 LCD display. >> >> Rather than re-inventing the wheel, I was wondering if anyone knew of >> 'blocks of code' that are available (public domain or whatever) for >> receiving/parsing GPS data and ouputting data to an LCD display. Any >> suggestions as to where such might be available? The other modules I >presume >> I will need to do from scratch - unless someone else has tried reading >from >> a Flo-Scan sensor! >> >> If there are free/cheap higher level language compilers, I would be >tempted >> to use one rather than assembler. >> >> I presume almost any 18 pin PIC will do as none of this sounds >particularly >> complicated or specialized. I have a few 16F628As and a couple of 16F88s >> hanging around. >> >> This will be an 'over the winter' project for next year's boating. Any >> comments would be welcome! (Maybe 'just buy the modification from the >> factory!') >> >> David Beach >> VE3STI >> >> >> _______________________________________________ >> picsig mailing list >> picsig at lists.tapr.org >> https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig >> > > > >_______________________________________________ >picsig mailing list >picsig at lists.tapr.org >https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From dvanhorn at dvanhorn.org Wed Aug 25 19:43:58 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Wed, 25 Aug 2004 14:43:58 -0500 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: <200408251533110332.0060DAE9@mail.nacs.net> References: <412CE9DD.4010202@comcast.net> <200408251533110332.0060DAE9@mail.nacs.net> Message-ID: <6.1.2.0.2.20040825144118.044c5ec0@mail.dvanhorn.org> At 02:33 PM 8/25/2004, HSHK wrote: >I have some 16 x 4 LCD display that use the HD4470. One thing to watch when using someone else's code: The LCD interface timing is important, and there are a number of time delays, that probably all depend on the processor clock speed. If you are a little too tight, you'll likely get a blank display. Also, their code may not have met the spec sheet, but may have worked on their displays. I've seen this a number of times, where code was borrowed. It can be very frustrating when it "Used to work".. I would definitely get the display working first, as that will help you get the rest working. From hshk at ix.netcom.com Wed Aug 25 19:47:44 2004 From: hshk at ix.netcom.com (HSHK) Date: Wed, 25 Aug 2004 15:47:44 -0400 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: <6.1.2.0.2.20040825144118.044c5ec0@mail.dvanhorn.org> References: <412CE9DD.4010202@comcast.net> <200408251533110332.0060DAE9@mail.nacs.net> <6.1.2.0.2.20040825144118.044c5ec0@mail.dvanhorn.org> Message-ID: <200408251547440498.0067D0F7@mail.nacs.net> No timing is necessary.... there is a busy line that you can poll... The are the actual displays.... I also have some 8051 assembler and 'C' code to operate them. Very simple stuff. Bill KA8VIT *********** REPLY SEPARATOR *********** On 8/25/2004 at 2:43 PM Dave VanHorn wrote: >At 02:33 PM 8/25/2004, HSHK wrote: > >>I have some 16 x 4 LCD display that use the HD4470. > >One thing to watch when using someone else's code: >The LCD interface timing is important, and there are a number of time >delays, that probably all depend on the processor clock speed. If you are >a little too tight, you'll likely get a blank display. Also, their code >may not have met the spec sheet, but may have worked on their displays. > >I've seen this a number of times, where code was borrowed. >It can be very frustrating when it "Used to work".. > >I would definitely get the display working first, as that will help you >get the rest working. > > >_______________________________________________ >picsig mailing list >picsig at lists.tapr.org >https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From jj at aprsworld.net Wed Aug 25 20:00:08 2004 From: jj at aprsworld.net (James Jefferson) Date: Wed, 25 Aug 2004 15:00:08 -0500 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: References: Message-ID: <200408251500.08854.jj@aprsworld.net> > Rather than re-inventing the wheel, I was wondering if anyone knew of > 'blocks of code' that are available (public domain or whatever) for > receiving/parsing GPS data and ouputting data to an LCD display. Any > suggestions as to where such might be available? The other modules I > presume I will need to do from scratch - unless someone else has tried > reading from a Flo-Scan sensor! Below is the C code to run a HD7780 LCD in 4-bit mode. As Dave warned, it works for me, but it may not work for you. I've used it with the PIC16F628 with internal oscillator, but some friends of mine used it with a 16f877a at 20 MHz. > If there are free/cheap higher level language compilers, I would be tempted > to use one rather than assembler. I would recommend CCS's PCM C. I think it's about $125 at this point. > I presume almost any 18 pin PIC will do as none of this sounds particularly > complicated or specialized. I have a few 16F628As and a couple of 16F88s > hanging around. Both are good chips. /* * LCD interface example * This code will interface to a standard LCD controller * like the Hitachi HD44780. It uses it in 4 bit mode, with * the hardware connected as follows (the standard 14 pin * LCD connector is used): * * Copywrite Craig Lee 1998 * modified by James Jefferson Jarvis to work with CCS c * */ #define lcd_cursor(x) lcd_write(((x)&0x7F)|0x80) #define LINE1 0x00 /* position of line1 */ #define LINE2 0x40 /* position of line2 */ #define LCD_RS PIN_A0 // Register select #define LCD_RW PIN_A1 #define LCD_EN PIN_A2 // Enable #define LCD_D4 PIN_A3 // Data bits #define LCD_D5 PIN_A4 // Data bits #define LCD_D6 PIN_A6 // Data bits #define LCD_D7 PIN_A7 // Data bits void LCD_STROBE(void) { output_high(LCD_EN); output_low(LCD_EN); } /* write a byte to the LCD in 4 bit mode */ void lcd_write(unsigned char c) { output_bit(LCD_D7,c & 0x80); output_bit(LCD_D6,c & 0x40); output_bit(LCD_D5,c & 0x20); output_bit(LCD_D4,c & 0x10); LCD_STROBE(); output_bit(LCD_D7,c & 0x08); output_bit(LCD_D6,c & 0x04); output_bit(LCD_D5,c & 0x02); output_bit(LCD_D4,c & 0x01); LCD_STROBE(); delay_us(40); } /* * Clear and home the LCD */ void lcd_clear(void) { output_low(LCD_RS); lcd_write(0x1); delay_ms(2); } /* write one character to the LCD */ void lcd_putch(unsigned char c) { output_high(LCD_RS); lcd_write(c); } /* * Go to the specified position */ void lcd_goto(unsigned char pos) { output_low(LCD_RS); lcd_write(0x80 + pos); } /* initialise the LCD - put into 4 bit mode */ void lcd_init(void) { /* step 1 */ delay_ms(15);// power on delay /* step 2 */ output_low(LCD_RS); output_low(LCD_RW); output_low(LCD_D7); output_low(LCD_D6); output_high(LCD_D5); output_high(LCD_D4); /* step 3 */ LCD_STROBE(); delay_ms(5); /* step 4 and 5 */ LCD_STROBE(); // init! delay_us(100); /* step 6 */ LCD_STROBE(); // init! delay_ms(5); output_low(LCD_D4); LCD_STROBE(); delay_us(40); lcd_write(0x28);// 4 bit mode, 1/16 duty, 5x8 font, 2lines lcd_write(0x0C);// display on lcd_write(0x06);// entry mode advance cursor lcd_write(0x01);// clear display and reset cursor } From dvanhorn at dvanhorn.org Wed Aug 25 20:15:59 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Wed, 25 Aug 2004 15:15:59 -0500 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: <200408251547440498.0067D0F7@mail.nacs.net> References: <412CE9DD.4010202@comcast.net> <200408251533110332.0060DAE9@mail.nacs.net> <6.1.2.0.2.20040825144118.044c5ec0@mail.dvanhorn.org> <200408251547440498.0067D0F7@mail.nacs.net> Message-ID: <6.1.2.0.2.20040825151324.020c8378@mail.dvanhorn.org> At 02:47 PM 8/25/2004, HSHK wrote: >No timing is necessary.... there is a busy line that you can poll... > >The are the actual displays.... Some don't implement the busy flag properly, and there are still timing requirements for setup and hold times that you have to respect.. Ignore them, and you MAY get lucky. I'm not sure where I'm going to use it, but I just finished interface code for the NKK Smartswitches, with pictures and ASCII text, and roll and pan, as well as color sliding. The display is 24 x 40 pixels, a little small, but then again, it's in the end of a pushbutton. From vk4tec at tech-software.net Wed Aug 25 20:30:29 2004 From: vk4tec at tech-software.net (Andrew Rich) Date: Thu, 26 Aug 2004 06:30:29 +1000 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: <200408251500.08854.jj@aprsworld.net> Message-ID: Be carefull not to enable interrupts while writting to LCD. I got rid of all of my GPS to LCD problems by disabling GIE while writing to LCD www.tech-software.net -----Original Message----- From: picsig-bounces at lists.tapr.org [mailto:picsig-bounces at lists.tapr.org]On Behalf Of James Jefferson Sent: Thursday, 26 August 2004 6:00 AM To: TAPR PIC Mailing List Subject: Re: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD > Rather than re-inventing the wheel, I was wondering if anyone knew of > 'blocks of code' that are available (public domain or whatever) for > receiving/parsing GPS data and ouputting data to an LCD display. Any > suggestions as to where such might be available? The other modules I > presume I will need to do from scratch - unless someone else has tried > reading from a Flo-Scan sensor! Below is the C code to run a HD7780 LCD in 4-bit mode. As Dave warned, it works for me, but it may not work for you. I've used it with the PIC16F628 with internal oscillator, but some friends of mine used it with a 16f877a at 20 MHz. > If there are free/cheap higher level language compilers, I would be tempted > to use one rather than assembler. I would recommend CCS's PCM C. I think it's about $125 at this point. > I presume almost any 18 pin PIC will do as none of this sounds particularly > complicated or specialized. I have a few 16F628As and a couple of 16F88s > hanging around. Both are good chips. /* * LCD interface example * This code will interface to a standard LCD controller * like the Hitachi HD44780. It uses it in 4 bit mode, with * the hardware connected as follows (the standard 14 pin * LCD connector is used): * * Copywrite Craig Lee 1998 * modified by James Jefferson Jarvis to work with CCS c * */ #define lcd_cursor(x) lcd_write(((x)&0x7F)|0x80) #define LINE1 0x00 /* position of line1 */ #define LINE2 0x40 /* position of line2 */ #define LCD_RS PIN_A0 // Register select #define LCD_RW PIN_A1 #define LCD_EN PIN_A2 // Enable #define LCD_D4 PIN_A3 // Data bits #define LCD_D5 PIN_A4 // Data bits #define LCD_D6 PIN_A6 // Data bits #define LCD_D7 PIN_A7 // Data bits void LCD_STROBE(void) { output_high(LCD_EN); output_low(LCD_EN); } /* write a byte to the LCD in 4 bit mode */ void lcd_write(unsigned char c) { output_bit(LCD_D7,c & 0x80); output_bit(LCD_D6,c & 0x40); output_bit(LCD_D5,c & 0x20); output_bit(LCD_D4,c & 0x10); LCD_STROBE(); output_bit(LCD_D7,c & 0x08); output_bit(LCD_D6,c & 0x04); output_bit(LCD_D5,c & 0x02); output_bit(LCD_D4,c & 0x01); LCD_STROBE(); delay_us(40); } /* * Clear and home the LCD */ void lcd_clear(void) { output_low(LCD_RS); lcd_write(0x1); delay_ms(2); } /* write one character to the LCD */ void lcd_putch(unsigned char c) { output_high(LCD_RS); lcd_write(c); } /* * Go to the specified position */ void lcd_goto(unsigned char pos) { output_low(LCD_RS); lcd_write(0x80 + pos); } /* initialise the LCD - put into 4 bit mode */ void lcd_init(void) { /* step 1 */ delay_ms(15);// power on delay /* step 2 */ output_low(LCD_RS); output_low(LCD_RW); output_low(LCD_D7); output_low(LCD_D6); output_high(LCD_D5); output_high(LCD_D4); /* step 3 */ LCD_STROBE(); delay_ms(5); /* step 4 and 5 */ LCD_STROBE(); // init! delay_us(100); /* step 6 */ LCD_STROBE(); // init! delay_ms(5); output_low(LCD_D4); LCD_STROBE(); delay_us(40); lcd_write(0x28);// 4 bit mode, 1/16 duty, 5x8 font, 2lines lcd_write(0x0C);// display on lcd_write(0x06);// entry mode advance cursor lcd_write(0x01);// clear display and reset cursor } _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From vk4tec at tech-software.net Wed Aug 25 20:32:17 2004 From: vk4tec at tech-software.net (Andrew Rich) Date: Thu, 26 Aug 2004 06:32:17 +1000 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: Message-ID: The longest you have to wait is 4ms so I pushed mine out to 5 ms delays between anything and never had a problem with the LCD _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From vk4tec at tech-software.net Wed Aug 25 20:32:54 2004 From: vk4tec at tech-software.net (Andrew Rich) Date: Thu, 26 Aug 2004 06:32:54 +1000 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: <412CE9DD.4010202@comcast.net> Message-ID: www.futurelec.com Bought a 20x4 for the price of a 16x2 www.tech-software.net -----Original Message----- From: picsig-bounces at lists.tapr.org [mailto:picsig-bounces at lists.tapr.org]On Behalf Of J.P. Rouland Sent: Thursday, 26 August 2004 5:35 AM To: TAPR PIC Mailing List Subject: Re: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD If possible, use more than 16x2 display. Look at 16x4's , 20x2's, and all the surplus ones (Alltronics.com, mpja.com, etc..). They all "program almost the same", and the readability would be MUCH improved. Price difference is small. Some guys on this list have worked on the GPS part.. but will they share their code? We shall wait for the answers.... J.P. NQ6T David Beach wrote: > I am toying with the idea of my first real 'from the ground up' PIC > programming project. It's not a ham project but I'm not sure who else to ask > and it uses concepts also used by people here. > > I have a boat with a Flo-Scan meter that reads fuel flow in litres/hour. I > also have a Garmin GPS that can spew out the usual speed data, etc., over > RS-232. For about $280 USD, I can get the meter modified at the factory to > also read mileage but I thought it might be an interesting exercise to try a > separate readout. A separate readout could also display other GPS info. > > I can see 4 major 'modules' of code. First, I need to receive and parse the > output of the GPS for speed data, then I need to receive and interpret the > output of the fuel flow sensor (I think it is a pulsed output proportional > to flow but I haven't figured this out for sure. The transducer is a > proprietary one made by Flo-Scan.), then, a bunch of arithmetic calculations > need to be done and, finally, output the fuel consumption info to a 'Hitachi > standard' 16x2 LCD display. > > Rather than re-inventing the wheel, I was wondering if anyone knew of > 'blocks of code' that are available (public domain or whatever) for > receiving/parsing GPS data and ouputting data to an LCD display. Any > suggestions as to where such might be available? The other modules I presume > I will need to do from scratch - unless someone else has tried reading from > a Flo-Scan sensor! > > If there are free/cheap higher level language compilers, I would be tempted > to use one rather than assembler. > > I presume almost any 18 pin PIC will do as none of this sounds particularly > complicated or specialized. I have a few 16F628As and a couple of 16F88s > hanging around. > > This will be an 'over the winter' project for next year's boating. Any > comments would be welcome! (Maybe 'just buy the modification from the > factory!') > > David Beach > VE3STI > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From dvanhorn at dvanhorn.org Wed Aug 25 20:34:23 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Wed, 25 Aug 2004 15:34:23 -0500 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: References: <200408251500.08854.jj@aprsworld.net> Message-ID: <6.1.2.0.2.20040825153257.04432ec0@mail.dvanhorn.org> At 03:30 PM 8/25/2004, Andrew Rich wrote: >Be carefull not to enable interrupts while writting to LCD. > >I got rid of all of my GPS to LCD problems by disabling GIE while writing to LCD Hmm.. Shouldn't be any problems there, all the timing delays are X => spec, so if you get an int and take longer than normal, it shouldn't be a problem. Last time I did 44780 code, I had tons of interrupts happening, with no problems. From vk4tec at tech-software.net Wed Aug 25 20:37:00 2004 From: vk4tec at tech-software.net (Andrew Rich) Date: Thu, 26 Aug 2004 06:37:00 +1000 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: Message-ID: http://www.futurlec.com sorry -----Original Message----- From: picsig-bounces at lists.tapr.org [mailto:picsig-bounces at lists.tapr.org]On Behalf Of Andrew Rich Sent: Thursday, 26 August 2004 6:33 AM To: TAPR PIC Mailing List Subject: RE: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD www.futurelec.com Bought a 20x4 for the price of a 16x2 www.tech-software.net -----Original Message----- From: picsig-bounces at lists.tapr.org [mailto:picsig-bounces at lists.tapr.org]On Behalf Of J.P. Rouland Sent: Thursday, 26 August 2004 5:35 AM To: TAPR PIC Mailing List Subject: Re: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD If possible, use more than 16x2 display. Look at 16x4's , 20x2's, and all the surplus ones (Alltronics.com, mpja.com, etc..). They all "program almost the same", and the readability would be MUCH improved. Price difference is small. Some guys on this list have worked on the GPS part.. but will they share their code? We shall wait for the answers.... J.P. NQ6T David Beach wrote: > I am toying with the idea of my first real 'from the ground up' PIC > programming project. It's not a ham project but I'm not sure who else to ask > and it uses concepts also used by people here. > > I have a boat with a Flo-Scan meter that reads fuel flow in litres/hour. I > also have a Garmin GPS that can spew out the usual speed data, etc., over > RS-232. For about $280 USD, I can get the meter modified at the factory to > also read mileage but I thought it might be an interesting exercise to try a > separate readout. A separate readout could also display other GPS info. > > I can see 4 major 'modules' of code. First, I need to receive and parse the > output of the GPS for speed data, then I need to receive and interpret the > output of the fuel flow sensor (I think it is a pulsed output proportional > to flow but I haven't figured this out for sure. The transducer is a > proprietary one made by Flo-Scan.), then, a bunch of arithmetic calculations > need to be done and, finally, output the fuel consumption info to a 'Hitachi > standard' 16x2 LCD display. > > Rather than re-inventing the wheel, I was wondering if anyone knew of > 'blocks of code' that are available (public domain or whatever) for > receiving/parsing GPS data and ouputting data to an LCD display. Any > suggestions as to where such might be available? The other modules I presume > I will need to do from scratch - unless someone else has tried reading from > a Flo-Scan sensor! > > If there are free/cheap higher level language compilers, I would be tempted > to use one rather than assembler. > > I presume almost any 18 pin PIC will do as none of this sounds particularly > complicated or specialized. I have a few 16F628As and a couple of 16F88s > hanging around. > > This will be an 'over the winter' project for next year's boating. Any > comments would be welcome! (Maybe 'just buy the modification from the > factory!') > > David Beach > VE3STI > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From vk4tec at tech-software.net Wed Aug 25 20:43:45 2004 From: vk4tec at tech-software.net (Andrew Rich) Date: Thu, 26 Aug 2004 06:43:45 +1000 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: Message-ID: Where can I get MX614 from ? -----Original Message----- From: picsig-bounces at lists.tapr.org [mailto:picsig-bounces at lists.tapr.org]On Behalf Of Andrew Rich Sent: Thursday, 26 August 2004 6:33 AM To: TAPR PIC Mailing List Subject: RE: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD www.futurelec.com Bought a 20x4 for the price of a 16x2 www.tech-software.net -----Original Message----- From: picsig-bounces at lists.tapr.org [mailto:picsig-bounces at lists.tapr.org]On Behalf Of J.P. Rouland Sent: Thursday, 26 August 2004 5:35 AM To: TAPR PIC Mailing List Subject: Re: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD If possible, use more than 16x2 display. Look at 16x4's , 20x2's, and all the surplus ones (Alltronics.com, mpja.com, etc..). They all "program almost the same", and the readability would be MUCH improved. Price difference is small. Some guys on this list have worked on the GPS part.. but will they share their code? We shall wait for the answers.... J.P. NQ6T David Beach wrote: > I am toying with the idea of my first real 'from the ground up' PIC > programming project. It's not a ham project but I'm not sure who else to ask > and it uses concepts also used by people here. > > I have a boat with a Flo-Scan meter that reads fuel flow in litres/hour. I > also have a Garmin GPS that can spew out the usual speed data, etc., over > RS-232. For about $280 USD, I can get the meter modified at the factory to > also read mileage but I thought it might be an interesting exercise to try a > separate readout. A separate readout could also display other GPS info. > > I can see 4 major 'modules' of code. First, I need to receive and parse the > output of the GPS for speed data, then I need to receive and interpret the > output of the fuel flow sensor (I think it is a pulsed output proportional > to flow but I haven't figured this out for sure. The transducer is a > proprietary one made by Flo-Scan.), then, a bunch of arithmetic calculations > need to be done and, finally, output the fuel consumption info to a 'Hitachi > standard' 16x2 LCD display. > > Rather than re-inventing the wheel, I was wondering if anyone knew of > 'blocks of code' that are available (public domain or whatever) for > receiving/parsing GPS data and ouputting data to an LCD display. Any > suggestions as to where such might be available? The other modules I presume > I will need to do from scratch - unless someone else has tried reading from > a Flo-Scan sensor! > > If there are free/cheap higher level language compilers, I would be tempted > to use one rather than assembler. > > I presume almost any 18 pin PIC will do as none of this sounds particularly > complicated or specialized. I have a few 16F628As and a couple of 16F88s > hanging around. > > This will be an 'over the winter' project for next year's boating. Any > comments would be welcome! (Maybe 'just buy the modification from the > factory!') > > David Beach > VE3STI > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From dvanhorn at dvanhorn.org Wed Aug 25 20:49:23 2004 From: dvanhorn at dvanhorn.org (Dave VanHorn) Date: Wed, 25 Aug 2004 15:49:23 -0500 Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: References: Message-ID: <6.1.2.0.2.20040825154551.04538ec0@mail.dvanhorn.org> At 03:32 PM 8/25/2004, Andrew Rich wrote: >The longest you have to wait is 4ms so I pushed mine out to 5 ms delays >between anything and never had a problem >with the LCD Yeow. That's one solution, but I'd hate to waste that much time. From jeff at aerodata.net Wed Aug 25 21:57:58 2004 From: jeff at aerodata.net (jeff at aerodata.net) Date: Wed, 25 Aug 2004 16:57:58 -0500 (CDT) Subject: [picsig] Sl. OT: GPS + fuel flow -> mileage LCD In-Reply-To: References: Message-ID: <2593.64.9.221.44.1093471078.squirrel@www.aerodata.net> You got alot of responses on the LCD, but none I could see on the GPS parsing. Here is a good place to start for that: ftp://ftp.tapr.org/software_lib/picsig/software/ as many of the PIC-E projects used GPS on them, there are examples of doing it both in C (CCS PCM) as well as MicroChip assembler. And my 0.02 on the LCD, if this is a one off project, take a look at these two items: http://www.matrixorbital.com http://www.seetron.com/ Of the two, I have used the Matrix Orbital ones, mostly because besides RS-232 serial, it also supported I2C. Good luck -Jeff wb8wka > I am toying with the idea of my first real 'from the ground up' PIC > programming project. It's not a ham project but I'm not sure who else to > ask > and it uses concepts also used by people here. > > I have a boat with a Flo-Scan meter that reads fuel flow in litres/hour. I > also have a Garmin GPS that can spew out the usual speed data, etc., over > RS-232. For about $280 USD, I can get the meter modified at the factory to > also read mileage but I thought it might be an interesting exercise to try > a > separate readout. A separate readout could also display other GPS info. > > I can see 4 major 'modules' of code. First, I need to receive and parse > the > output of the GPS for speed data, then I need to receive and interpret the > output of the fuel flow sensor (I think it is a pulsed output proportional > to flow but I haven't figured this out for sure. The transducer is a > proprietary one made by Flo-Scan.), then, a bunch of arithmetic > calculations > need to be done and, finally, output the fuel consumption info to a > 'Hitachi > standard' 16x2 LCD display. > > Rather than re-inventing the wheel, I was wondering if anyone knew of > 'blocks of code' that are available (public domain or whatever) for > receiving/parsing GPS data and ouputting data to an LCD display. Any > suggestions as to where such might be available? The other modules I > presume > I will need to do from scratch - unless someone else has tried reading > from > a Flo-Scan sensor! > > If there are free/cheap higher level language compilers, I would be > tempted > to use one rather than assembler. > > I presume almost any 18 pin PIC will do as none of this sounds > particularly > complicated or specialized. I have a few 16F628As and a couple of 16F88s > hanging around. > > This will be an 'over the winter' project for next year's boating. Any > comments would be welcome! (Maybe 'just buy the modification from the > factory!') > > David Beach > VE3STI > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > From VE3STI at rac.ca Wed Aug 25 23:20:30 2004 From: VE3STI at rac.ca (David Beach) Date: Wed, 25 Aug 2004 19:20:30 -0400 Subject: [picsig] Fuel Consumption Project - Thanks! Message-ID: Wow! I have had a flood of suggestions from the list. Thanks guys! I am looking forward to more as more of the listers read their mail. Every time I read the list, I learn something from you guys... David VE3STI From hjmhs at yahoo.com.ar Wed Aug 25 23:55:06 2004 From: hjmhs at yahoo.com.ar (=?iso-8859-1?Q?Hugo_M=FCller_\=28HJM\=29?=) Date: Wed, 25 Aug 2004 20:55:06 -0300 Subject: [picsig] [OT] How can suspend reception of messages or cancel temporaly? References: Message-ID: <078401c48b00$665a6ec0$6400a8c0@ineptium> Hi guy: sorry by this OT but How can suspend reception of messages or cancel temporaly? Thanks Hugo ----- Original Message ----- From: "David Beach" To: "TAPR PIC Mailing List" Sent: Wednesday, August 25, 2004 8:20 PM Subject: [picsig] Fuel Consumption Project - Thanks! Wow! I have had a flood of suggestions from the list. Thanks guys! I am looking forward to more as more of the listers read their mail. Every time I read the list, I learn something from you guys... David VE3STI _______________________________________________ picsig mailing list picsig at lists.tapr.org https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig From jra at febo.com Thu Aug 26 01:18:48 2004 From: jra at febo.com (John Ackermann N8UR) Date: Wed, 25 Aug 2004 21:18:48 -0400 Subject: [picsig] [OT] How can suspend reception of messages or cancel temporaly? In-Reply-To: <078401c48b00$665a6ec0$6400a8c0@ineptium> References: <078401c48b00$665a6ec0$6400a8c0@ineptium> Message-ID: <412D3A78.60409@febo.com> Go to the list web interface (https://lists.tapr.org/mailman/listinfo/picsig) and after logging in you can set your list options to hold off on sending messages. 73, John N8UR ---- Hugo M?ller (HJM) wrote: > Hi guy: > sorry by this OT but > How can suspend reception of messages or cancel temporaly? > Thanks > > Hugo > > ----- Original Message ----- > From: "David Beach" > To: "TAPR PIC Mailing List" > Sent: Wednesday, August 25, 2004 8:20 PM > Subject: [picsig] Fuel Consumption Project - Thanks! > > > Wow! I have had a flood of suggestions from the list. Thanks guys! I am > looking forward to more as more of the listers read their mail. > > Every time I read the list, I learn something from you guys... > > David > VE3STI > > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > > _______________________________________________ > picsig mailing list > picsig at lists.tapr.org > https://lists.tapr.org/cgi-bin/mailman/listinfo/picsig > >