test -----Mensagem original----- De: Automatic digest processor Para: Recipients of PICLIST digests Data: S‡bado, 1 de Agosto de 1998 01:11 Assunto: PICLIST Digest - 30 Jul 1998 to 31 Jul 1998 >There are 78 messages totalling 2582 lines in this issue. > >Topics of the day: > > 1. low cost pid retmocontroler (2) > 2. 16C63 Runs at 5.25V not at 5.2 0or 5.00V > 3. CNC, pics, Autocad and hpgl (3) > 4. 17Cxxx serial programming (2) > 5. POR bit? (2) > 6. Other Micro's for high end stuff (2) > 7. how to decode Motorola MC145026 remote controler protocol > 8. how to decode motorola MC145026 remote controler protocol > 9. Help for tato programmer > 10. OT: Book with Bresenham and shading/refl./radiosity algorythms ? (3) > 11. Upper and Lower Case 7 Seg Characters (2) > 12. 16 bit square root > 13. [OT] English name (8) > 14. [OT] SCR failures (4) > 15. PICLIST Digest - 29 Jul 1998 to 30 Jul 1998 > 16. A PIC start! > 17. Book with Bresenham and shading/refl./radiosity algorythms ? > 18. Reply: [OT]: Book with Bresenham and shading/refl./radiosity algorythms ? > 19. FW: Book with Bresenham and shading/refl./radiosity algorythms ? > 20. C compilers for the PIC17C752 Chip... which one is best? (2) > 21. Designing for dollars entries, where? (2) > 22. Reply: [OT]: Book with Bresenham and shading/refl./radiosity > algorythms ? > 23. OT: Book with Bresenham and shading/refl./radiosity > algorythms ? > 24. Confirmation of Receipt (13) > 25. On T: Is there a FM/MFM implementation for PICs that is in the PD ? > 26. let me out! (5) > 27. OT : Verilog > 28. Off-Topic? Maybe... (was: "Re: Reply: [OT]: Book with Bresenham and > shading/refl./radiosity algorythms ?" > 29. Autoconfirmations to piclist > 30. (Fwd) Confirmation of Receipt > 31. MPlab 3.99 and 12C508 (2) > 32. [OT] Missing girl > 33. Cannot write information from RCREG to Element in Array... (MCC17) (3) > 34. OT : MOS-FET's > 35. > 36. Robots information. (2) > 37. www.scenix.com > >---------------------------------------------------------------------- > >Date: Fri, 31 Jul 1998 09:37:44 +0400 >From: Romeo Dimitrov >Subject: low cost pid retmocontroler > >hi all > >I'm new in pics .can anybody help me where can I find a project (or >ideas , or help , or something) for a low cost PID termocontroller. > > R. Dimitrov > vop@botev.ttm.bg > >------------------------------ > >Date: Fri, 31 Jul 1998 04:13:42 +0100 >From: Leon Heller >Subject: Re: 16C63 Runs at 5.25V not at 5.2 0or 5.00V > >In message , Paul Gaastra > writes >>Hello. >> >>I have a circuit with a 16C63 -04I/SO which works when powered by >>5.25V but at 5.20V it continually runs part of the code and restarts >>continually. At 5.00V nothing happens. Any ideas why it doesn't >>want to work at lower voltages? >> >>Is this an example of it not being programmed "hard enough"? I >>programmed it using an Advantech LabTool-48 programmer which doesn't >>use the serial programming technique (what it does use I don't know). >> >>I have a 3.6864MHz crystal with 22pF caps to ground. > >Have you tried using a different crystal? I've just been reading some >Motorola applications info about crystals for use with some oftheir PLL >synthesiser chips, and they mention a possible problem, with the >oscillator only working over a limited voltage range with crystals that >aren't properly specified. > >Leon >-- >Leon Heller: leon@lfheller.demon.co.uk http://www.lfheller.demon.co.uk >Amateur Radio Callsign G1HSM Tel: +44 (0) 118 947 1424 >See http://www.lfheller.demon.co.uk/dds.htm for details of a simple AD9850 >DDS system. See " "/diy_dsp.htm for a simple DIY DSP ADSP-2104 system. > >------------------------------ > >Date: Fri, 31 Jul 1998 04:43:40 +0100 >From: Leon Heller >Subject: Re: CNC, pics, Autocad and hpgl > >In message <3.0.5.32.19980730173751.00a3d930@hotmail.com>, Brian Gracia > writes >>Good Day All, >> >>I was wondering if any one had built a CNC machine and used Autocad or an >>Autocad generated file to run it. I know that this is hpgl. Does anyone >>have any info on such subjects. I am looking at two in some old issues of >>Microcomputer Journal. >> >>What I want to do is write an hpgl file to some eeprom and put it into a >>pic circuit to control a cnc machine with x,y & Z axis. Basically just >>plug-n-go programming. >> >>Any leads/help would be appreciated. >> >>Thanks Guys, >> >>Brian > > >CNC software for the PC is available from one or two suppliers. They >take in an HPGL file and control stepper motors driven from the printer >port. I don't think a PIC is suitable for this. > >Leon >-- >Leon Heller: leon@lfheller.demon.co.uk http://www.lfheller.demon.co.uk >Amateur Radio Callsign G1HSM Tel: +44 (0) 118 947 1424 >See http://www.lfheller.demon.co.uk/dds.htm for details of a simple AD9850 >DDS system. See " "/diy_dsp.htm for a simple DIY DSP ADSP-2104 system. > >------------------------------ > >Date: Fri, 31 Jul 1998 17:11:24 +1000 >From: Jim Robertson >Subject: Re: 17Cxxx serial programming > >At 14:12 30/07/98 +0200, you wrote: >>Hello everyone, >>has anybody information about (experience with) the software part of >>getting a program into the PIC 17 via in-circuit serial programming? >> >>-Do I need a terminal program (e.g.in BASIC) on the PC ?- Or does the >>internal PIC-BootROM start an initialisation sequence on the PC (in either >>a MICROCHIP program or a simple terminal program) and show a message? >> >>I appreciate any comment and help. >> >> Andreas Dante > >Andreas, > >You need a programmer and software designed for the 17C75x parts. The >17C75x parts use Async serial I/O and not RS232 so a terminal program is of >no use. Also the 17C75x boot code does not drive a programming menu (like, >say, the DS5000.) Programming it is more like programming a serial EEPROM >or any of the 16Cxx parts. You need some intelligence to generate external >signals and timings etc. > >The PICSTART PLUS will program the 17C75x parts in the ISP mode. > >I am waiting on sample 17Cxxx parts so I can test my 17Cxxx upgrades for >the PICSTART 16B and 16C. > >Jim > > > >>-------------------------------------------------------------------------- - >--- >>my e-mail addresses: >> A.Dante@City.ac.uk >> dante@snoopy.e-technik.uni-dortmund.de >> >>-------------------------------------------------------------------------- - >--- >> >-------------------------------------------------------- >Jim Robertson >NEWFOUND ELECTRONICS >Email: newfound@pipeline.com.au >http://www.pipeline.com.au/users/newfound >-------------------------------------------------------- > >------------------------------ > >Date: Fri, 31 Jul 1998 09:10:00 +0200 >From: "Dr. Imre Bartfai" >Subject: Re: POR bit? > >Hi all, > >excuse you all, it was the manual wrong. On a particular side states, that >PCON register should have the address 8Eh generally. It is not true. On >the particular memory map one can see, that PCON is 8Eh only for >16C72/73/74. However, for the 16C710/711 (in my case) the address is 87h. >It is silly from Microchip as before the particular registers have all >their constant address. > >POR does not detect MCLR; it detects really Power-on-Reset. So, after I >corrected my program, I can distinguish between Power-on and other type of >resets (e. g. MCLR). It is very fine as I collect some data beginning from >power-up, and I will show this data if the user ties MCLR to ground. >The following code snippet can show it: > > ... > JNB POR,:POR ; if not set, then POR > ... ; process collected data here > BTFSS POR ; only for cleanlyness >:POR BSF POR ; now WE set POR to mark it for the future > ... > >Remember, that POR EQU PCON.1 and it resides in the bank#1, so RP0 is >to be set. > >Thanks once again who wanted to help me. > >Imre > > > >On Thu, 30 Jul 1998, Peter L. Peres wrote: > >> POR detects MCLR which is always asserted at power-up. If you assert MCLR, >> POR will be cleared. More exactly, there is no such thing as a power on >> without a MCLR assertion. It will not be cleared if the reset occurs due >> to a watchdog timeout f. example. >> >> Peter >> >> > >------------------------------ > >Date: Fri, 31 Jul 1998 10:17:54 +0200 >From: Tjaart van der Walt >Subject: Other Micro's for high end stuff > >We've decided against Mchip for high-end apps, and >are looking around for other good micro's. We will >probably keep using the 16C77 for low-end products. >The 17CXXX pricing and functionality sucks when >compared to other 16 bit devices. > >We've done a few projects on the Motorola 916, but >the lead times are hurting too much, even though we >pay almost the same for the flash versions of the 916 >than what the 17C756 would go for. > >I am very impressed by the Fujitsu 16 bit devices. >Has anyone on the list ever used them? We are about >to spend big money on the tools, so I would like some >unbiased opinion. > >BTW the pricing is really good. The MB90F583A has >3 (real) UARTS, two more programmable serial ports, >8 X 8bit A/D's, 128k Flash (5V), 6k RAM, 3 X 16 bit >timers, 2 X D/A, a programmable pulse generator and >a partridge in a pear tree. It runs off 1.8 to 3V. >They go for around $16 each. > >-- >Friendly Regards > >Tjaart van der Walt >mailto:tjaart@wasp.co.za > >|--------------------------------------------------| >| WASP International | >|R&D Engineer : GSM peripheral services development| >|--------------------------------------------------| >|SMS mailto: tjaart@sms.wasp.co.za (160 chars max)| >| http://www.wasp.co.za/~tjaart/index.html | >|Voice: +27-(0)11-622-8686 Fax: +27-(0)11-622-8973| >| WGS-84 : 26=B010.52'S 28=B006.19'E | >|--------------------------------------------------| > >------------------------------ > >Date: Fri, 31 Jul 1998 10:26:29 +0100 >From: Stefan Sczekalla-Waldschmidt >Subject: Re: how to decode Motorola MC145026 remote controler protocol > >Hello Martin >Martin McCormick schrieb: > >> Stefan Sczekalla-Waldschmidt writes: >> >Thats the thing I' like to control. My approach to decode is "look for >> >Edges" in the signal and messure the distance between. Would have been nice >> to see > how somebody >else has done this. >> >> This method gives you a time measurement between transitions, >> all right, and that is valuable. It can trip you up so be careful. >> When I was trying to decode the Manchester-style output of a HP28 >> printer port, I did this very thing and it did not work at all. >> >> The signaling protocol was such that a 0 was represented by a >> half-bit period of no carrier followed by a half-bit period of >> carrier. When there is a 0 to one transition, one reads two half-bits >> of carrier back to back as ones are represented by a half-bit of >> carrier followed by half of a bit of no carrier. What actually >> happened, was that sometimes there would be a tiny glitch back to no >> carrier between the two half-bits and other times, there was either no >> glitch or the detector ran the two half-bits together effectively >> filling them in to make a long 1-bit carrier period. >> >> I found all that out by measuring the time as is described >> above and then discovering that there were hardly ever any carrier >> bursts that were two half-bits long, but there were lots of times in >> which there was a half-bit on time followed by a return to 0 that was >> sometimes as brief as one or two CPU cycles and then another >> half-bit. The thing to do is to reliably detect the start of a frame >> and then wait, in this case, a quarter of a bit length before reading >> the detector again. The idea is to read in the middle of a bit and >> not on an edge because that's where the signal is most likely to be >> unstable. This is how UARTS do their thing and in the case of the >> HP28, this lets the detector glitch between bits all it wants and >> nothing bad happens. > >I hope to be in a luckier position because the source of my signal to >decode is wired, and has a very low output resistance.Viewing them with a >storing-scope ( dont know correct english term for it ) the signals looked >quite >precisely timed. So I `m hopeful, things you mentioned above wont happen to me >... >also I 4ll do a little filtering on the signal with an RC set. > >Detecting the start of frame and then doing it the uarts way was my first idea >but this will take to much time Signal is abt. 38.4 kHz. I also have to do some > >tests to the data because I cant be sure about the type. > >The application is an decoder for model railroad loco and ther can be differnt >kind >of transmition protocols on the same track. > >Kind regards. > > Stefan > >------------------------------ > >Date: Fri, 31 Jul 1998 11:55:35 +0100 >From: Keith Doxey >Subject: Re: how to decode motorola MC145026 remote controler protocol > >Hi Stefan, > >I have been looking at the same idea as I already use the MC145026/7 in a >Video switcher I made about 4 years ago. > >Get hold of the datasheet. It contains details of the code format with timings. > >Hope that helps > >Keith > >-----Original Message----- >From: Stefan Sczekalla-Waldschmidt [SMTP:ssw@OIKOSSW.DE] >Sent: Tuesday, July 28, 1998 1:23 PM >To: PICLIST@MITVMA.MIT.EDU >Subject: how to decode motorola MC145026 remote controler protocol > >Hi, > >Has somebody tried to write or written a decoder for Motorola remote >controle >ic type MC 145026. > >I need code to implement something like an MC 145027 with additional >functions. >16C84 preferred, but all hints and tips are welcome. > >kind regards > > Stefan Sczkalla-Waldschmidt > >------------------------------ > >Date: Fri, 31 Jul 1998 13:15:58 +0200 >From: Michel Mermin >Subject: Help for tato programmer > >Good day >I have build the Tato programmer on the PCB found at the same url but when >i try to write i n the chip the first project of D Tait , i've got >the follow message >Write error on mem 0 >I'm a beginners with the pic, so can somebody help me >thank > >mermin.michel@hol.fr > >------------------------------ > >Date: Fri, 31 Jul 1998 13:21:10 +0000 >From: "Peter L. Peres" >Subject: OT: Book with Bresenham and shading/refl./radiosity algorythms ? > >Hello, > > I am looking for a book that covers the $SUBJ in some detail (at least >code snippets), for lines, arcs, circles, and ellipses (Bresenham or >faster) and has some discussion on light reflection/refraction modelling >with special attention for efficient (i.e. fast) implementations. > > If you know such books, please report, if possible including year of >publishing and printing house, or ISBN. Private email is ok. > >thanks, > > Peter > >------------------------------ > >Date: Fri, 31 Jul 1998 13:01:32 +0000 >From: "Peter L. Peres" >Subject: Re: POR bit? > >Sorry, I oopsed. I had assumed that you were talking about TO and PD, and >i was really tired. I'll censor my postings much better from now on ;) > >Peter > >------------------------------ > >Date: Fri, 31 Jul 1998 08:15:46 -0400 >From: Lou Calkins >Subject: Re: Upper and Lower Case 7 Seg Characters > >>About twenty years ago, TI came up with a character set for using a seven >>segment display which is actually a lot better for most characters. Using >>it, the examples above become: >> >>> _ _ _ >>> _||_| _ |_ |_ _ >>>|_|| || ||_||_ | >>> >>> _ _ _ _ _ _ _ >>> |_||_||_ _ | |_| _ |_ | | _ | |_| >>>|_|| | |_ | |_ | | _||_ |_|| ||_ _| >> >>Which is only marginally better and still requires the user to understand >>the character set (Note what happened to "s" so that it can be >>differentiated with "5"). Other problem characters include "K", "M", "N", >>"Q", "T", "V", "W", "X" and "Z". >> > >There are some inconsistancies here. You say that the S needs to be >different from the numeral 5, but yet the G in the first example uses the >same segments as the numeral 6 (and your O uses the same segments as the >numeral 0). Why not let the S be the same segments as the 5? Unless you >are displaying amateur radio call signs, there probably would not be a problem. > >I just finished a project where I needed to have a number representing >seconds displayed. I used a space and S (same as 5) at the end, and I did >not have room for SEC. I will admit it looks a little wierd when displaying >5 seconds (looks like 5 5). The space helps it to looks a little better, so >context does help. > >The most difficult one I had to do was a project with thermocouples where I >needed to show types J, K, T and E. No problem with type E, but J looked >like a hockey stick (not bad) and T was the lowercase t that is often seen, >but for type K I needed to spell out CAy. I will admit this really looks >stupid, but what is the alternative? > >Do you know where TI has published the character set they came up with? I >would really like to see it. Please let me know if a URL might be available >for the set. Thanks! > >Lou > >------------------------------ > >Date: Fri, 31 Jul 1998 15:16:09 +0300 >From: juha tuomi >Subject: 16 bit square root > >Thanks to all for helping me about sqrt routine. > >Juha > >------------------------------ > >Date: Fri, 31 Jul 1998 14:48:38 +0000 >From: Nuno Pedrosa >Subject: [OT] English name > >What do you call "{"? > >Brackets are "[", right? >Thanx. >-- > .^. _,^,_ /\ >___( | )_____ Nuno Filipe Freitas Pedrosa __________ o(`} | , __/\/ /__ > /*\\|//*\ SIEMENS S.A. Portugal (]| /' \ \/\ > \(\\V//)/ mailto:Nuno.Pedrosa@oen.siemens.de (]|`% (") \/\ \ > ` -=- ' Tel. :00351-1-4242454 (") /`/ / /\/ >__B//|\\P___________________________________________\' / `/______\/____ > `-' "Try and leave this world a little better than you found it..." > >------------------------------ > >Date: Fri, 31 Jul 1998 08:59:13 +0000 >From: Lawrence Lile >Subject: [OT] SCR failures > > * This message contains the file 'nt5esch.gif', which has been > * uuencoded. If you are using Pegasus Mail, then you can use > * the browser's eXtract function to lift the original contents > * out to a file, otherwise you will have to extract the message > * and uudecode it manually. > >