As I couldn't get the component to transmit - I modified my code above to the 12f1840 (**** actually 12LF1840 - you might need to change this).

This gave:

LabNation_Screenshot73.png

Note that one slight oddity - because the transmit is interrupt driven (and doesn't wait for completion at the ...

I've just attempted to test a 'transmit' with a PIC12F1840 (actually a 12LF1840 which is the low voltage version) - however I get a compilation error using the component:

12f1840.c: myisr()
977: FCM_::Timer_Event();
^ (195) expression syntax
1017: }
^ (350) unused label "FCM_" (from line 0 ...

Hi Enrique,

I've not had time to work on this either - but I've just received some PICs including a few of the types mentioned above and might get a chance to depend a little time over the next week.

It would be better to get the component fixed - but i was hoping to get something working - at ...

Thanks Steve,

I must have hit the toggle by mistake sometime... Been running like it for weeks too

It might be a configuration setting - but I've noticed that properties seems to get the variable name displayed rather than the description...

... The modified component code imports glcd_ssd1963 (parallel) and is using this for the read & write routines (and others).

So modifying this would be one way to go.

Alternatively - as a test - write a tiny component or program to test the display. This doesn't need to be very large - it needs ...

I tested this - I modified your component (slightly - gave it a new GUID changed the name) and compiled to SSD_TEST - then compiled the test program having modified it to use the new component and removed the old component. The new component moved to development - with name SSD_TEST

Have no way of ...

This might give a solution:


#include <math.h>
#include <stdio.h>

int main()
{
int a, b;

// Using typecasting for
// integer result
a = (int)(pow(5, 2) + 1e-9);
b = round(pow(5,2));
printf("%d \n%d", a, b);

return 0;
}



Which looks to give the correct result on both cases (from ...

It might be because it uses floating point...

pow(2, flt_fromi(FCL_I));

- not sure why it doesn't also do flt_fromi(2)?

However - it shouldn't make it so wrong ?

Wrote my own integer

Just spent a while chasing a bug in my code - but it turns out 'pow' returns an incorrect value.

It actually returns the result - 1 (except for pow(2, 0) and pow(2, 1))

The attached demonstrates this behaviour (on an Arduino - other devices may differ?):


2**0 = 1
2**1 = 2
2**2 = 3
2**3 = 7
2**4 ...