Get ticks

[MJ]

Hi chaps, I'm new to CCS and am getting congrats with the built in functions.

How does the get-ticks() and set_ticks() functions work and how is it related to the timer ticks and the size of the bits in te timer setup. Does it process overflows etc or does it simply return the relevant timer value. I've looked at the manual but am a little confused.

[Ttelmah]

It returns a timer count, based on the size of timer counter you have specified
in the #USE TIMER setup. This is explained in the #USE TIMER manual entry.
It is a 'ticker', based on a hardware timer, rather than the timer itself.
The default if you don't specify a BITS= value in the #USE, is a 32bit value.

[MJ]

Thanks, the manual still doesn't clearly explain how the function works. I tested it with the ICD and understand how it functions now.

[jeremiah]

[MJ]

wow, are you normally this condescending to new users? Not everyone is a pro coder using CCS. The functions don't explain how the tick timer is incremented and updated.

[Ttelmah]

Actually they do.
The point is you have to read all the parts together. So #USE TiIMER, says:

This directive creates a tick timer using one of the PIC's timers. The tick
timer is initialized to zero at program start. This directive also creates the
define TICKS_PER_SECOND as a floating point number, which specifies that
number of ticks that will occur in one second.

So it is saying that this uses a PIC timer.

You then have:

TICK=xx - Sets the desired time for 1 tick. xx can be used with
ns(nanoseconds), us (microseconds), ms (milliseconds), or s (seconds). If
the desired tick time can't be achieved it will set the time to closest
achievable time and will generate a warning specifying the exact tick time.
The default value is 1us.

So it is using a PIC timer, and it sets the rate it advances as close as
possible to what you ask, or tells you what it has used.

This is common throughout coding, that you must look at the other sections
referenced by what you are looking at. The references are there for a good
reason.
Also, generally look at the examples. These are really 'part' of the manual.

[MJ]

Thanks, that's a really good explanation. I know how the PIC works, I have been using them for decades in assembly and basic compilers. It doesn't specifically state how it is physically incremented by the function or how the function works; it was my understanding or confusion at the time that I struggled with. In any case, the documentation in comparison to other compilers is quite challenging to interpret, especially if you are not a C coder, but I understand that this is not a fault of the compiler and over the last few months I have learnt CCS very well, it still differs from other compilers in that it is heavily function based where the compiler does pretty much everything and this is new for me.

It was also not easy to read the examples at the time as I did not fully understand the C syntax, and the fact that CCS uses its own non-ANSI functions, etc.

I now understand how it works and have come to like the compiler libraries. As a newbie to CCS, having not used C but fully understanding the MCU architectures, it's quite a learning curve to one, learn C, and, secondly, get to grips with a new compiler that is heavily function-based rather than having to generate libraries yourself.

I was going to post two new SSD1306 libraries. One that is even more compact than the one you provided using a smaller font table and a math zoom function for font, with very little Ram using Page memory writes for speed and a second that is double buffered with bitmap, sprite manipulation for battery, wifi symbols, animation that are a breeze to create and manipulate from ROM, external memory or USB, curves, circles, lines, boxes, and text that runs at >300FPS (little overclocking as I was forced to 12M SPI from the USB HW). I don't think I'll bother now.

Appreciate the explanation

[temtronic]

One of the reasons I bought PCM ( V2.453 ish..) WAS the extensive 'libraries' or 'functions'. Didn't know squat about 'C' ,so having them allowed for fast progress.
Another nice thing is that you can dump the listing and SEE all the machine code the compiler generates. In most cases it's very efficient at doing 'stuff'.
Going from Assembler to C was a challenge but using CCS's examples really helped !
Can the documentation be better ? Of course,but with 100s of functions, 1,000s of PICs, you'd have to employee a team of 10-12 JUST to keep up with the new peripherals and features today's PICs have !
I suggest you do post your programs in the 'code library'. Maybe you've got a clever bit of code others can use.

[jeremiah]