Re: [ti-chronos-development] Keeping the acess point on for long periods of time?

[Paolo Dev]

In the accelerometer code there is a timeout of 60 minutes after that it will switch off.

You can just increase it or modify the condition check in the interrupt code.

If you cannot manage drop me an email.

Sent from my iPad

On 8 Aug 2012, at 21:55, Mathieu Granzotto <origina...@gmail.com> wrote:

I'm using the default firmware that comes with CCC to read accelerometer data with a python script. Problem is, the watch turns off the acess point off after a random time (1h~3h).

 

Anyone have a fix for that?

 

I'm thinking about soft-reseting the clock every once in a while, but since I don't know where this behaviour comes from, I'm not so confident this will work.

 

Thanks!

 

--
You received this message because you are subscribed to the Google Groups "TI Chronos Development" group.
To view this discussion on the web visit https://groups.google.com/d/msg/ti-chronos-development-/-/PceAeiwtVJYJ.
To post to this group, send email to ti-chronos-...@googlegroups.com.
To unsubscribe from this group, send email to ti-chronos-develo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ti-chronos-development-?hl=en.

[Mathieu Granzotto]

I was trying to modify acceleromer.c, but I realized that is the wrong file.

 

The RF code is in rfsimpliciti.c, where it sets the timeout ( in start_simpliciti_tx_only() ).

The timer check is in timer.c ( TIMER0_A0_ISR() ), but the problem is that I can't modify this code on a limited CCS.

I could loop around the simpliciti code, but is there a way to compile the unrestricted version?

 

Thanks for the attention!

 

Quinta-feira, 9 de Agosto de 2012 16:00:20 UTC-7, epokh escreveu:

In the accelerometer code there is a timeout of 60 minutes after that it will switch off.

You can just increase it or modify the condition check in the interrupt code.

If you cannot manage drop me an email.

Sent from my iPad

On 8 Aug 2012, at 21:55, Mathieu Granzotto <origina...@gmail.com> wrote:

I'm using the default firmware that comes with CCC to read accelerometer data with a python script. Problem is, the watch turns off the acess point off after a random time (1h~3h).

 

Anyone have a fix for that?

 

I'm thinking about soft-reseting the clock every once in a while, but since I don't know where this behaviour comes from, I'm not so confident this will work.

 

Thanks!

 

--
You received this message because you are subscribed to the Google Groups "TI Chronos Development" group.
To view this discussion on the web visit https://groups.google.com/d/msg/ti-chronos-development-/-/PceAeiwtVJYJ.
To post to this group, send email to ti-chronos-...@googlegroups.com.

To unsubscribe from this group, send email to ti-chronos-development-+unsub...@googlegroups.com.