disconnect fixes it. I'm assuming that the socket is fixed, meaning
that when something connects to 45678 (as I have it set), that 45678
isn't redirected to another open socket (like the TCPIP server
symbol), leaving 45678 open for a later connection. Then when the
iPad disconnects, the processor doesn't properly release and needs to
be told to release. Just like to understand...
Thanks, Heath
On Jul 25, 1:06 am, Jarrod Bell <jar...@guilink.com> wrote:
> iViewer sends a heartbeat MSG every 3 seconds so it will only detect
> inactivity if the app is not actually connected. Do you have the
> 'activity timeout' signal connected up as per the demo program?
>
> Jarrod
>
> Sent from my iPhone
>
> On 25/07/2010, at 11:37 AM, Heath Volmer <hvol...@gmail.com> wrote:
>
>
>
> > And I forgot to mention that it doesn't behave any different at 15
> > seconds. I see no activity in Toolbox when I put the iPad to sleep,
> > and for minutes after. The iPad is unresponsive.
>
> > On Jul 24, 7:23 pm, Heath Volmer <hvol...@gmail.com> wrote:
> >> No sure why those messages are posting before I finished typing....
>
> >> I have 60 in the timeout. Does that mean that it should kill the
> >> socket after 60 seconds of inactivity? I see the demo has 15. I'm a
> >> little confused about the operation here. With it set at 15, will
> >> the
> >> socket disconnect every time it sits idle for 15 seconds, even if the
> >> user is still browsing, say?
>
> >> Thanks, Heath
>
> >> On Jul 24, 7:20 pm, Heath Volmer <hvol...@gmail.com> wrote:
>
> >>> I'm following you. I had 60 in the timeou
>
> >>> On Jul 23, 5:30 pm, Jarrod Bell <jar...@guilink.com> wrote:
>
> >>>> Make sure that the Crestron processor is detecting the
> >>>> disconnection
> >>>> when the device goes to sleep (this generally takes about 30
> >>>> seconds
> >>>> after the device goes to sleep before the wifi is disabled). The
> >>>> main
> >>>> issue is Crestron does not always detect the disconnection, and
> >>>> therefor hogs the socket and doesnt let iViewer reconnect. This is
> >>>> where the 'activity timeout' logic in our demo SIMPL program comes
> >>>> into play. This allows you to manually force the socket to close
> >>>> after
> >>>> a period of inactivity (length defined in the module parameters).
> >>>> Please follow the example in our latest demo program as to an
> >>>> example
> >>>> of how to do this.http://code.google.com/p/commandfusion/
>
> >>>> Jarrod
>
> >>>> On Jul 24, 8:26 am, Heath Volmer <hvol...@gmail.com> wrote:
>
> >>>>> Having trouble with connection. The iPad goes to sleep and
> >>>>> sometimes
> >>>>> when we turn it back on it doesn't make connection with the
> >>>>> control
> >>>>> system. It took about a minute the last time and previously
> >>>>> I've had
> >>>>> to restart the processor. What might I look for?
>
> >>>>> Thanks, Heath
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "CommandFusion" group.
> > To post to this group, send email to commandfusion@googlegroups.com.
> > To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com
> > .
> > For more options, visit this group athttp://groups.google.com/group/commandfusion?hl=en
> > .
--
You received this message because you are subscribed to the Google Groups "CommandFusion" group.
To post to this group, send email to commandfusion@googlegroups.com.
To unsubscribe from this group, send email to commandfusion+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.


Comments
0 comments to "Re: Losing connection"
Post a Comment