Olin Lathrop | 12 Sep 14:13 2003

Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On 16F628 in ASM

Not again! <groan>

> MIME-Version: 1.0
> Content-Type: Multipart/related; type="multipart/alternative";
>               boundary="------------Boundary-00=_JXU1QL80000000000000"
> X-Mailer: IncrediMail (2001184)
> References: <000001c37804$9fac3010$69774e3f@...>
> X-FID: PLAINTXT-NONE-0000-0000-000000000000
> X-Priority: 3
> Message-ID:  <3F606BD7.000001.02344 <at> my_computer>
> Date:         Thu, 11 Sep 2003 18:04:31 +0530
> Reply-To:     pic microcontroller discussion list
<PICLIST@...>
> Sender:       pic microcontroller discussion list
<PICLIST@...>
> From: ardhuru@... (Anand Dhuru)
> Subject: Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On
16F628 in ASM
> To:           PICLIST@...
> Precedence: list
>
> --------------Boundary-00=_JXU1QL80000000000000
> Content-Type: Text/Plain;
>   charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable

Please have mommy set up your email so that your messages aren't sent in
those "attachment" thingies.

*****************************************************************
(Continue reading)

Tim Hart | 12 Sep 14:29 2003

Re: [EE]: Simple DC Current...

Fan was not running....
Book for DVM is "missing"...somewhere around here :)

But after reading your reply and others the urge to check the fuse overwhelmed me!  DUH!

The Fuse was BAD!  Bang on forhead!

Thanks to all that replied!
Tim

>>> jan-erik.xa.soderholm@... 09/11/03 15:51 PM >>>
Tim Hart wrote:

> I'm attempting to measure the current draw of a DC fan.
> I hook up a simple panel current meter and it shows 200 ma....
> (It's a small fan) and then I hook up my supper nice DVM and
> it shows ZERO!  I changed the range, set it to auto etc.  Nothing!

Many DVMs has a separate jack for voltage vs. current.

A few control questions :

- Does the fan run with the DVM connected as described ?
- Has the DVM *ever* been able to measure current ?
- Have you lost the manual for the DVM ? :-)

Jan-Erik.

--
http://www.piclist.com hint: The PICList is archived three different
(Continue reading)

Patrick Richards | 12 Sep 14:34 2003

Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On 16F628 in ASM

Byron, thank you for your reply.  You have given me several things to
think about.  After seeing your code snippet, I have decided I should
really try to work out this whole problem myself instead of hacking up a
complete piece of code I found from Microchip.  I have started to sketch
out the problem in pseudo code.

> Here's a brain plant for you to think about later on. While assembly
is
> essential to learn, both for reading other's programs and for high
> performance computing, Having abstraction for simple projects can
really
> help.

Abstraction is something I have considered.  When I write my own code, I
usually sketch everything out in pseudo code that resembles C.  Then I
write the Assembly code a chunk at a time.  A step beyond this would be
to actually use a higher level language.  For this project, I would like
to stick to Assembly because that's the first language I have any
experience with on the PIC and it is helping me understand how the chip
actually works.  But, I will look into the languages you list on your
web page at http://www.finitesite.com/d3jsys/languages.html.  Up until
now, JAL is the only one of the three I have heard of.

>         CBLOCK   0x2C   ; CBLOCK will auto the address.
>                         ; 0x2C works for most 16F style pics.
>         display         ; Make sure to init to 0
>         ENDC

> Update  incf     display,W  ; Next display
>         andlw    0x03       ; Keep in range
(Continue reading)

Patrick Richards | 12 Sep 14:43 2003

Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On 16F628 in ASM

I took a quick look at the article and it looks like it will help with
my project.  Thanks!

As far as the number of pins, I'm not concerned.  I expect to use all 8
pins on PORTB for the 7-segment display.  I don't mind wasting the
eighth pin (I am not using the decimal point) because it makes it easier
to code.  I will use RA0-RA3 to drive the transistors for each LED
display.  Since I am using the internal RC osciallator, that that will
free up two PORTA pins.  I will use RA5 and RA6 for the Up and Down
buttons.  I will use a resistor to Vcc and a NO switch to Vss on /MCLR.
That leaves Vss and Vcc.  If I am counting correctly, that is 17 pins,
leaving RA4 unused.  This is perfect for my needs.

> Hi Pat,

> This article uses PICBASIC PRO to achieve what you want, but the
hardware
> issues are beautifully explained.

> http://www.melabs.com/resources/articles/ledart.htm

> Referring to this article, I could design a 4 digit multiplexed
display in
> my last project successfully.

> Also consider the fact that your display is going to take up 11 pins
on
> the 16F628; is that acceptable? You might want to use a larger PIC.

> Hope this helps.
(Continue reading)

Michael Rigby-Jones | 12 Sep 14:50 2003

Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On 16F628 in ASM

> -----Original Message-----
> From: Patrick Richards [SMTP:pat@...]
> Sent: Friday, September 12, 2003 1:35 PM
> To:   PICLIST@...
> Subject:      Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On
> 16F628 in ASM
>
> Has someone on this PICList posted standards for coding and commenting?
> I mean, how many tabs to indent for code and comments, what to
> capitalize, etc.
>
There are no standard "standards" as such.  Find a style that that you find
easily readable/logical and apply it consistently through out your code.

Most people use 3 or 4 space tabs, and many people get upset if you use
actual tabs instead of converting them to spaces, as it screws up the
formatting when using an editor with different tab stops.  Personaly I find
using real tabs significantly speeds up editing, especialy when formatting
tables etc. and converting them to real spaces for others convienience is a
click away in the editor I use.(ultraedit).

Mike

=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
(Continue reading)

Olin Lathrop | 12 Sep 14:47 2003

Re: [PIC]: Err 154 from qqq_intr.aspic.

> While configuring the QQQ_INTR.ASPIC part, I get the
> error below. It's not clear to me if I have done
> something wrong (not impossible !), or if it's something
> else. Anyway, what should I be looking for ?
>
> Jan-Erik.
>
> From the .LST file :
> (I have cut down the comments a bit)
>
>
>       00090 ;
>       00091 ;   This state is private to the interrupt...
>       00092 ;   be accessible regardless of the current...
>       00093 ;
> Error[154]  : Each object file section must be contiguous
>               (section .udata_shr)
>       00094          UDATA_SHR
> 0000  00095 W_SAVE   RES     1   ;saved W during interrupt,...
>       00096

I just tried a bare 12F629 project and the INTR module assembled fine,
after stripping out the UART stuff of course.

The assembler is complaining that you tried to define two separate
UDATA_SHR sections in the same source module, which is definitely a no-no.
I'm guessing you added some of your own variables immediately above the
code you showed.  It probably defined a UDATA_SHR section, and the
assembler complains when it hits the second definition.  It looks like the
UDATA_SHR in my template is a holdover from before I had the DEFRAM macro.
(Continue reading)

Russell McMahon | 12 Sep 14:52 2003
Picon

Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On 16F628 in ASM

From: "Anand Dhuru" <ardhuru@...>
Subject: Re: [PICLIST] [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On
16F628 in ASM

Anand,

I'm posting this response on list as well as sending it to you directly as
it may be useful to others.

You may not realise the last 6 posts that you have made to the list (since
August 3rd inclusive) have had a blank message body, with your reply
included as an attachment, plus a bonus file IMSTP.GIF attached. This makes
the messages hard for most people to read (have to open the attachment with
attendant wondering about viruses) and the GIF is just added rubbish. I
think IMSTP.GIF is added by the Netscape browser.

In the PICList records that I have currently to hand (which go back to early
June), prior to the 6 problem posts,  you made about 25 posts with text
showing in the email body as usual. Something happened at the start of
August.
I'd guess that you changed your email program or settings in early August
and that this has caused the problems.

I don't know if you are able to change the way emails are being sent to the
list but I'm sure it would be appreciated by everyone if you could.

regards

            Russell McMahon

(Continue reading)

Bob Ammerman | 12 Sep 00:34 2003
Picon

Re: [PIC]:Manchester Lookup table

The OP  is just sending normal ASYNC over the air.

He is encoding bits within a byte in a pseudo-Manchester scheme to ensure
long term 0:1 ratio is 50% on the  wire to keep the data slicer happy.

The user is depending on  the receiver recognizing the start bit correctly,
which is problematic at best. I have written a document on piclist.com
(http://www.piclist.com/techref/microchip/ammermansync.htm) that outlines
how you can use a specially formatted preamble to assure byte
synchronization. Hopefully this prefix won't confuse the data slicer too
much trouble.

Bob Ammerman
RAm Systems

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@... with SET PICList DIGEST in the body

Alan B. Pearce | 12 Sep 15:03 2003
Picon
Picon

Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On 16F628 in ASM

>You may not realise the last 6 posts that you have made to the list (since
>August 3rd inclusive) have had a blank message body, with your reply
>included as an attachment, plus a bonus file IMSTP.GIF attached. This makes
>the messages hard for most people to read (have to open the attachment with
>attendant wondering about viruses) and the GIF is just added rubbish. I
>think IMSTP.GIF is added by the Netscape browser.

This was brought up when he first posted, and someone else pointed out the
problem is the Mickeysoft products do not work correctly according to the
standards when handling this type of message. You can find a discussion
about it if you go back to around the time of the first message, and follow
the subject lines.

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@... with SET PICList DIGEST in the body

Olin Lathrop | 12 Sep 15:02 2003

Re: [PIC]: 4-Digit Counter Multiplexing 7-Segment LEDs On 16F628 in ASM

> Has someone on this PICList posted standards for coding and commenting?
> I mean, how many tabs to indent for code and comments, what to
> capitalize, etc.

Ha, ha.  Posting standards isn't the problem, getting others to follow
them is.  Everyone naturally has their own idea of how things should be
indented, capitalized, etc.  As for commenting, it's a struggle just to
get people to do it at all.  (Although I've noticed even Andrew Warren has
recently started commenting the code snippets he posts.  Thanks, Andy.
Maybe there is hope.)

For whatever it's worth, I put labels in column 1 (the assembler requires
that), opcodes in column 10, operands starting in column 18, and end of
line comments starting in column 30.  I sometimes receive code from other
places, and it's usually a mess (why else would someone hire a consultant
to "fix" it?).  For my sanity, I've created a program called ASPIC_FIX
that fixes arbitrary messy alignment to the above values.  It also
eliminates tabs and only uses hard spaces for formatting in the output
file.  ASPIC_FIX is part of my PIC development environment, which you can
download for free.  See http://www.embedinc.com/pic.

As for capitalization, I write everything lower case because something is
a lot quicker to type if you don't have to keep hitting CAPS LOCK or
holding down the SHIFT key.

*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
(Continue reading)


Gmane