OK Mark..
Here is what I am talking about.
This is a prototype offer I got to make. And I am sure about the pay too.
I will post a schema once you finalized the PIC to be used.
I will make the test circuit, you have to code the chip. Code needs to be via PM, But I will post the schema here, and the rest can be discussed openly.
What it is will be left anonymous for the time being. I believe it will be a hit.
Circuit details.
Circuit will evolve as it progresses.
The circuit consists of a PIC μC controller preferably with USB hardware for the near future.
It should have display. It can be a LCD or 7 segs, can use which ever is easier to work with.
Input is through 3 push buttons, which will be used daily. So we call this the 3 user inputs
The circuit will work this way :
When u press an input the program should identify which one from the three is pressed. Next it should prohibit the use of the other two inputs which ever that is from using for at least 10 seconds. After this delay the program should be ready to scan the keys again.
Next is the press indication and can be stored in a memory in three registers.
3 registers are for each switch. The register is updated respectively for consequent inputs. The register should store it in a non volatile memory for power failure reasons.
The register will be counting the number of presses the three inputs are giving through out a time span of 1 month or longer if necessary.
The count can be from 0 to 9999 counts.
So in short the memory will have a graph or table of the number of times the user input has been pressed for a month or two.
This count needs not to be displayed for the users.
After the end of the month, a person in charge will be noting down the counts for whatever reason he needs it.
He should be able to scan through the three input tables and should be able to see the count hit each user input has gone through. It should display the initiated date to the current date he is checking. Only he can reset the count registers after noting down the ended month details.
To display the count details a 20 character by 2 row LCD can be used or 7 segs, which ever is easier.
The person in charge controls will be hidden inside a locked console together with display. What is available will only be the three user inputs.
You can determine how many keys the in charge will need to scan through the tables and reset it. A numeric keypad is preferable to pass code lock it prohibiting the use of unauthorized access to the tables completely. This will increase security.
The USB interface is necessary if further advancement to display the chart in a PC program. But this can be done much later.
One more important to note about the user keys is that they will be placed at around 20 to 40 feet away. So use of minimum no. wires going to the users is needed. Something like 2 line input for multiple keys, the voltage divider method.
And yes a led out to indicate the key press needs to go to the user pad as an indication for the button pressed together with a buzzer.
So I believe I will be going for the cat5 or 6 cable for the user pad. I need ur thought on this.
Further more this thread is open for discussion on how to go about it.
Here is what I am talking about.
This is a prototype offer I got to make. And I am sure about the pay too.
I will post a schema once you finalized the PIC to be used.
I will make the test circuit, you have to code the chip. Code needs to be via PM, But I will post the schema here, and the rest can be discussed openly.
What it is will be left anonymous for the time being. I believe it will be a hit.
Circuit details.
Circuit will evolve as it progresses.
The circuit consists of a PIC μC controller preferably with USB hardware for the near future.
It should have display. It can be a LCD or 7 segs, can use which ever is easier to work with.
Input is through 3 push buttons, which will be used daily. So we call this the 3 user inputs
The circuit will work this way :
When u press an input the program should identify which one from the three is pressed. Next it should prohibit the use of the other two inputs which ever that is from using for at least 10 seconds. After this delay the program should be ready to scan the keys again.
Next is the press indication and can be stored in a memory in three registers.
3 registers are for each switch. The register is updated respectively for consequent inputs. The register should store it in a non volatile memory for power failure reasons.
The register will be counting the number of presses the three inputs are giving through out a time span of 1 month or longer if necessary.
The count can be from 0 to 9999 counts.
So in short the memory will have a graph or table of the number of times the user input has been pressed for a month or two.
This count needs not to be displayed for the users.
After the end of the month, a person in charge will be noting down the counts for whatever reason he needs it.
He should be able to scan through the three input tables and should be able to see the count hit each user input has gone through. It should display the initiated date to the current date he is checking. Only he can reset the count registers after noting down the ended month details.
To display the count details a 20 character by 2 row LCD can be used or 7 segs, which ever is easier.
The person in charge controls will be hidden inside a locked console together with display. What is available will only be the three user inputs.
You can determine how many keys the in charge will need to scan through the tables and reset it. A numeric keypad is preferable to pass code lock it prohibiting the use of unauthorized access to the tables completely. This will increase security.
The USB interface is necessary if further advancement to display the chart in a PC program. But this can be done much later.
One more important to note about the user keys is that they will be placed at around 20 to 40 feet away. So use of minimum no. wires going to the users is needed. Something like 2 line input for multiple keys, the voltage divider method.
And yes a led out to indicate the key press needs to go to the user pad as an indication for the button pressed together with a buzzer.
So I believe I will be going for the cat5 or 6 cable for the user pad. I need ur thought on this.
Further more this thread is open for discussion on how to go about it.
Last edited: