Very strange Nart, perhaps there is something else in your software/settings that is causing the problem. Incidentally, there is no need to set CMCON = 0x07, this is the default condition of the register after all resets (POR, BOR & MCLR).

Have you tried using the bitwise and operator...

if (PORTA.F1 & PORTA.F2) run_function();

I'm not certain why the and comparison doesn't work but my reasoning is that you are trying to deduce a 1 or 0 mathematically, hence the bitwise operator.

As a side issue, which GPS module are you using? Most of them have adjustable baud rates these days.

A couple of observations; it looks like you're using FAT16 so you should use Mmc_FAT_Init(). Secondly, the logic of while (mmc_init()); is wrong, that call returns zero if the initialisation was successful. Try something like this... //Fire up SPI channel 1 at low speed... Spi1_Init_Advanced(_SPI_MA...

The main problem with the Soft_Uart functions is that there is no buffering for incoming data, the hardware Uart has a FIFO buffer which means you can read the incoming data in the right order after it has arrived. You can't do this with the Soft_Uart reads; you have to read each character before th...

Have a look at escape sequences in the Help files. To send 'hello' along with a carriage return you would type " hello\r ", where \r is the escape character for 0x0D. It's worth pointing out that there is an unwritten standard for terminating ASCII strings which uses both the carrige return and a li...

How have you declared 'output'? And what is the text that you are sending over the UART comms? It may be that 'output' is not large enough to receive the entire message or that the delimiter character (0x0D) is not being received within the 10 read attempts.

Is this a standard way of using arrays or is it MikroC specific?. The ANSI C language uses pointers extensively for all types of variables, not just arrays. MikroC adheres to the ANSI C standard so pointers are available for us to use. However, as I mentioned earlier, care needs to be taken so that...

The pointer declaration simply points to a particular memory location where the first byte of 'text' can be found, subsequent memory bytes contain the rest of the array. There is no limitation to the size of the array at this stage, however, in the ME example the array size has been controlled by th...

Try this...

Hi Velimir, this could happen for many reasons, can you post your code along with PIC details, clock speed, etc?

I agree with the Doc, you need to prioritise each stage of the program and use some kind of interrupt sequence. At the moment it seems that the UART buffer is receiving data from different parts of the program and spewing it out all together. I would split each part of the program into distinct func...

Check out the Lo, Hi, Higher and Highest operators, using these you will be able to deconstruct values between 2 and 4 bytes in length and save them as single byte chunks in your EEPROM. Remember to use the bitshift operators (<<) when you reconstruct the values after reading from memory.

In that zip folder there's an example of how to calibrate and read G. The board's outputs are analogue voltages which are proportional to G in the three planes.

do i have to initialise my transducer?

Not according to the datasheet.

one transducer is for sending pulse and one for receiving.

You only need one transducer, the echo appears on the same line as the trigger pulse (see the circuit diagram on the datasheet).