Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
11/19/11 16:19
Modified:
  11/19/11 16:23

Read: times


 
#184809 - Well
Responding to: ???'s previous message
Because I built a big library of modules to the PICs and dsPICs over the years, it will be much faster for me to use a previously built and debuged DS1307 RTC module say to integrate into other projects.
Also it was easy and cheap to get pic products in our part of the world. very few people used other types.
One strange incident with PIC is I designed 7 clocks that display date and time for a local pharmatical research company which should be synchronized.
I made one master clock and 6 slaves, the master clock displays date and time and sends this data using RS-485 to the rest of the clocks to display.
I used PIC16F77 chips in each clock at 19200BPS.
the clocks worked perfectly for 2 years then only the master clock worked, which means communication error. I replaced the master clock with a new board and other clocks still wouldn't accept the incomming data. After looking carefully into serial port it turned out if I inserted 1msec delay after each character sent the other displays will work fine and accept the data. Why did the code work for 2 years then stop? I'm sure its not my fault but the PICs have a mind of their own!
Mahmood

List of 25 messages in thread
TopicAuthorDate
NXP Promises ARM Cortex-M0 in DIL Package!            01/01/70 00:00      
   Amazing! I thought DIL was DEAD.            01/01/70 00:00      
      Me too!            01/01/70 00:00      
   Hmm..            01/01/70 00:00      
      maybe            01/01/70 00:00      
         dsPIC is a waste of time            01/01/70 00:00      
            We Await The Results...            01/01/70 00:00      
            Which one(s)?            01/01/70 00:00      
               two            01/01/70 00:00      
            Why so long?            01/01/70 00:00      
               Well            01/01/70 00:00      
                  Two years            01/01/70 00:00      
                     Answers            01/01/70 00:00      
                        But what delays did you try before original release?            01/01/70 00:00      
                        shorter delays            01/01/70 00:00      
                           good thinking            01/01/70 00:00      
                           Can't get the error            01/01/70 00:00      
                              What changed?            01/01/70 00:00      
                     Seems a little harsh            01/01/70 00:00      
                        Never blame manufacturer without proofs            01/01/70 00:00      
                           Proven Product Syndrome            01/01/70 00:00      
                           My response ...            01/01/70 00:00      
                              No Offense            01/01/70 00:00      
                                 What I Do and Not Do            01/01/70 00:00      
   NXP are mistaken            01/01/70 00:00      

Back to Subject List