With so many emails on this list I worry it was lost in the action.
Was a clear enough?
I just need to run a thread or something inthe background so that I
can keep the robot heart ticking while the user decides on an action.
BR,
Jason Brower

On Dec 17, 11:44 am, encompass <[email protected]> wrote:
> Therobotdoes some cool stuff that has never been done before.  I
> just can tell you because of business rules. It is a very expensive
> commercial device.  When it is released, I will inform everyone here.
> Well, I have one app right now. This seems to be the biggest issue:
> I send data to therobotand I get a response in a second or two if
> the movement happened successfully.  I need that data but should I
> really while loop until I get the response?  That would slow down the
> response in the webUI.
> I also get a heartbeat ever second or more.  I need to send responses
> that I have successfully read the hardbeat. It should be automatically
> done outside of the gui.
> It's pretty crazy, but the web interface opens a huge door of
> opportunity for thisrobot.  I am using pySerial for communication.
> So in other words, I have 2 parts that I know I need.
> One for the web application, GUI, database of information, commands torobot
> Two is the loop of logic (I call it the "Logical Loop of Love") It
> contains checks of the data coming in from therobotand a list of
> movement/init commands that are going to be sent to therobot.  It
> also handles the hardbeat and certain things like timeouts and other
> information.  I was thinking of creating a thread of the Logic Loop
> and then accessing and retrieving data from that, but don't know if
> that is even possible or the best way.  Others tell me twisted is the
> way to go, but I would like to stay with as much web2py as possible.
> Regards,
> Jason
>
> On Dec 17, 9:24 am, mdipierro <[email protected]> wrote:
>
> > I am not sure I understand but sounds very cool. What does therobot.
>
> > I may be mistaken but if I understand you have two web apps. One talks
> > to therobotand one talks to you. Your question is how do they
> > exchange information? My advice is merge the two apps into one app
> > with two controllers (one for you and one for therobot), the use
> > cache.ram to store information that needs to be passed between them.
>
> > On Dec 17, 12:51 am, encompass <[email protected]> wrote:
>
> > > I am creating arobotinterface in web2py.
> > > I am making great progress as I can send commands and other what not
> > > to therobotand make it do it's thang, but I find problems in
> > > monitoring signals from the device.
> > > Therobotsends "heartbeat" requests about ever 5 seconds, if it doesn
> > > get a response from the computer that it is also alive, then it will
> > > panic and start sending requests ever .5 second until it gets a
> > > response.
> > > Should I create another web application that connects with this web
> > > application that simply response through serial to keep things alive?
> > > I think I am close with this approach:
> > > I have create a loop sequence that checks the states of the machine,
> > > depending on what the machine is doing and what responses it gets it
> > > changes it's status.  The next time it goes through the loop it
> > > updates itself.  This is very nice, as it can quickly handle the
> > > requests.  Is there a way to run that, and then my webapp and probe
> > > that states or change states of variables in that loop to make things
> > > happen in therobot?  Sounds crazy, but by doing this I can create a
> > > universal interface for myrobotand run myrobotwith a cellphone,
> > > webtablet or anything with an internet connection.
> > > Best Regards,
> > > Jason Brower

--

You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en.


Reply via email to