Moderator: Benj
Hi I am following this thread with great interest.Benj wrote:Here is a picture of the prototype E-block.
If you copy a part of program to other program...variables are not copied with them, you have to declare the variables to make the code in act.I do not know If I have to create them myself or not.
variable that has dot in front actually local variable which means the variable only usable to a particular macro. If you are inside any macro and go to variable declaration window and on the right side of the window you will see different option...Ports,Globals,macroname(here you will see variable; if you declare variable here it will be local variable and that can be used as dot in that macro...not need to declare by dot), Macro, Numeric, Textual.I tried to but flowcode does not allow a variable name with a dot in front.
If you want to replace the local variable with different name you can but you have to change in code..you can also use global variable sometime in place of local variable.Can I replace them with any name I want to or is there something special about them?
Yes, you are right. That's not available in project explorer.I do not understand why it does not show locals on the Project explorer.
Return variable is something automatically defined if you declare return type non-void while macro is declaring. That is done by Ben when he made the code..But if you want to copy simple_cap_touch macro you can declare that in main macro and while creating the new macro you will see in the bottom of the window there is an option return type. If you select "No return type" you will not get ".Return" variable as local variable in the macro. But if you select BYTE/INT or any type you want..you will be able to use that in your macro.How do you get the variable .Return between Sample_Cap_Touch and Parameters?
You will see in the Sample_Cap_Touch macro..at the end. Ben uses .return and it gets some value. so when you call "Sample_Cap_Touch" macro from main function you have to put some variable where Sample_Cap_Touch will return it's return value...in this case "State" is that variable.I see the Sample_Cap_Touch Macro ends with leaving a value in the variable .Return. The main program uses the variable State.
As I mentioned above the macro will return the return variable value to state variable and that is done in c code..you don't need to worryHow does it get a value state from return?
I think this should work fine as long as the +VREF is not enabled. All you should have to do is change the ADC component connection to AN2.AN2 is where i put the pull up resistor from vss. Is this a problem? I see this pin is also for vref+
This really needs to be based on your clock frequency. Using the RC conversion method was a bit too slow on my hardware and Fosc/2 was generating good results. Have a play around and see what setting provides you with the accuracy your after.Also I see that the ADC channel is set to FOSC/2 is that not a bit fast? Or does it not matter for capacitive touch?
There is a specific bug for doing this in v5.5, as I say making the DSP stuff more optimized has broken my cap touch demo file.Is the problem I have due to a bug in Flowcode 5.5 or is there something wrong wit connecting the 1K pull up resistor to AN2
Code: Select all
adcon0 = adcon0 | 0x04; //begin next conversionCode: Select all
*tris_reg = old_tris | tris_mask;
adcon0 = (0x01 | (Conv_Speed << 6)) | (Channel << 3); //turn ADC on
delay_us(T_Charge); //wait the acquisition time
adcon0 = adcon0 | 0x04; //begin next conversion
}
MX_UINT16 FC_CAL_Sample_ADC (MX_UINT8 Sample_Mode)
{
MX_UINT16 iRetVal;
while (adcon0 & 0x04);
if (Sample_Mode)Code: Select all
*tris_reg = old_tris | tris_mask;
adcon0 = (0x01 | (Conv_Speed << 6)) | (Channel << 3); //turn ADC on
delay_us(T_Charge); //wait the acquisition time
}
MX_UINT16 FC_CAL_Sample_ADC (MX_UINT8 Sample_Mode)
{
MX_UINT16 iRetVal;
adcon0 = adcon0 | 0x04; //begin next conversion
while (adcon0 & 0x04);
if (Sample_Mode)
Yes you can change the ADC read type to int this should still work well.Do not use filled ground planes underneath electrodes area — In case a ground plane is needed, make sure it is not filled. If the plane underneath the electrode is completely (100%) filled, the total capacitive coupling from the ground plane is much higher than the one created by a finger, adding a large offset to the capacitive measurement. It makes the detection of a valid finger touch more difficult.
Code: Select all
#define MX_ADC_TYPE_26Code: Select all
MX_ADC_TYPE_26Code: Select all
16F1822, 16F1823, 16F1824, 16F1825, 16F1828, 16F1829