Watch variables in Oshonsoft showing 0x000 not 0x00?

[camerart]

Hi,
I'm pretty sure that in watch variables, where it shows e,g, (0x000), this means 0x00, but can anyone clarify please?
Camerart

 

[Nigel Goodwin]

Hi,
I'm pretty sure that in watch variables, where it shows e,g, (0x000), this means 0x00, but can anyone clarify please?
Camerart

They are exactly the same thing, as is 0x0 - the reason for allocating three nibbles is to allow 12 bit values (so presumably low-end PIC's? - mid-range are 14 bit, so would need four nibbles).

 

[camerart]

They are exactly the same thing, as is 0x0 - the reason for allocating three nibbles is to allow 12 bit values (so presumably low-end PIC's? - mid-range are 14 bit, so would need four nibbles).

Hi N,
Ok, understood, thanks.
C

 

[Ian Rogers]

Another reason for the three nibbles ( or three characters ) is that when using hex notations "0x0" some compilers do not like the first char to be non numeric so "0xB8" is written "0x0B8" for clarity.

 

[camerart]

Hi,
Thanks.
The extra '0' led me to believe that it was 16 BIT.
C.

 

[Ian Rogers]

0x00000000000000 is still zero. LOL as Nige said 0x000 is 12 bit ( 12 bit command set on pics )

 

[Nigel Goodwin]

Hi,
Thanks.
The extra '0' led me to believe that it was 16 BIT.
C.

Each nibble is 4 bits, so three nibbles is 12 bits - four nibbles is 16 bits, etc.