What's the equivalence in seconds for nTimeout?

Carmen Garcia · Post by **Carmen Garcia** » Sat Jun 01, 2013 2:11 pm

Hello everybody:

In ZigBee's Macro "Receive_Char" is used the input paramenter "nTimeout" that's not means seconds (time), it means how much munber of retries to check for a response...

¿Does anyone know the equivalence between this retries and the seconds between them?

Thanks you very much in advanced.

Regards

Post by **kersing** » Sat Jun 01, 2013 2:48 pm

Answer for Flowcode 5:
Each try of nTimeout is 1000 microseconds. Value 255 is a special (wait forever) value.

Carmen Garcia · Post by **Carmen Garcia** » Sat Jun 01, 2013 5:39 pm

Guau¡¡¡¡ Where was this data??

Thank you very very much¡¡

Regards

Post by **kersing** » Sat Jun 01, 2013 5:58 pm

I checked the component sources.

Carmen Garcia · Post by **Carmen Garcia** » Sat Jun 01, 2013 5:59 pm

dazz · Post by **dazz** » Sat Jun 01, 2013 6:11 pm

Hi Carmen
if you add a zigbee component right click it ,click help and its in the helpfile that pops up
Regards
Dazz

Carmen Garcia · Post by **Carmen Garcia** » Sat Jun 01, 2013 6:51 pm

Hi Dazz:

I was looking for this information throught this way and doesn't appear anything like this...My FlowCode version is 5 too.

Thanks you very much
Regards

dazz · Post by **dazz** » Sat Jun 01, 2013 7:59 pm

Hi Carmen

see attached pic ,not sure if you were looking at the correct help file
1 right click select help
2 click the 3 dots opposite help
3 line explaining ntimeout

Regards
Dazz

dazz · Post by **dazz** » Sat Jun 01, 2013 8:01 pm

kersing wrote:Answer for Flowcode 5:
Each try of nTimeout is 1000 microseconds. Value 255 is a special (wait forever) value.

Hi Jaq

I thought it was 100us as per the uart. cal file

Regards
Dazz

Carmen Garcia · Post by **Carmen Garcia** » Sat Jun 01, 2013 8:08 pm

Thanks you very much for the picture

This is the flow I followed...but the UART.cal file is the key for solve my doubt.

How do you view to this file?

Thanks you very much again.

Regards

Post by **kersing** » Sat Jun 01, 2013 8:46 pm

dazz wrote:I thought it was 100us as per the uart. cal file

Dazz,

The way I read the code is:
In the code of FC_CAL_UART_Receive there is a loop (rxStatus == UART_STATUS_LOOP) that waits 10us, increments delay1 and only if delay1 equals 100, nTimeout is decremented.
That makes 100 times 10 us = 1000 us delay for each decrement of nTimeout.

Regards,

Jac

Post by **kersing** » Sat Jun 01, 2013 8:50 pm

Carmen Garcia wrote: How do you view to this file?

Use your favorite editor to open c:\Program Files\Flowcode\v5\CAL\PIC\PIC_CAL_UART.c (for 64 bit systems it is c:\Program Files (x86)\Flowcode\v5\CAL\PIC\PIC_CAL_UART.c)

dazz · Post by **dazz** » Sat Jun 01, 2013 9:03 pm

Hi Jac
cheers i missed the loop

Regards
Dazz

Matrix user forums

What's the equivalence in seconds for nTimeout?

What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?

Re: What's the equivalence in seconds for nTimeout?