Actions
Forum Thread Details
  • Replies 3 replies
  • Subscribers 316 subscribers
  • Views 295 views
  • Users 0 members are here
Related

Software / Server stack for browser based controls

Former Member

Hey all!

 

I've prototyped a ruby on rails application to manage machine processes

 

basically a user logs in, creates a new protocol, the application saves it to the database and then the user is able to run those established protocols.

 

The machine layer recieves binary protocols from the rails server at the microcontroller and the MC controls the actual physical movements within the robot system.

 

Is there anyone here whos worked with a stack like this, and can comment on the benefits and shortfalls of this system?

Parents

  • Hi Carl,

     

    Could you share more information, such as your design and code so we can take a look at it to see its potential for other implementations?

     

    Thanks

    DAB

  • in reply to DAB

    DAB,

     

    http://i.imgur.com/dYRCM.jpg

     

    here is the general breakdown,  for the first iteration I think using my existing arduino mega is about as simple as it gets.

     

    Hookup the individual pumps to the mega viola.

     

    between:

    browser  <  ruby on rails  >  server

    server <  Active Record  > DB

    server < simple binary protocol > Arduino

    arduino <  wires  > syringe pumps

     

     

    I think that sums it up pretty well image

     

    basically " where will this break ?"

  • in reply to Former Member

    Hi Carl,

     

    To find out where it will break, you need to set up a test to see how fast your can run messages from the Arduino to the server and from the server to both the DB and the UI.  Once you characterise your current capability, you can then look to see if your application can live within those limits or do you need to upgrade one or more of your system components to increase your throughput.

     

    From what I see, as long as you have a low response need, say seconds, you should be alright.  But I still recommend you build a stressing test to see where your weaknesses are.

     

    DAB

Reply
  • in reply to Former Member

    Hi Carl,

     

    To find out where it will break, you need to set up a test to see how fast your can run messages from the Arduino to the server and from the server to both the DB and the UI.  Once you characterise your current capability, you can then look to see if your application can live within those limits or do you need to upgrade one or more of your system components to increase your throughput.

     

    From what I see, as long as you have a low response need, say seconds, you should be alright.  But I still recommend you build a stressing test to see where your weaknesses are.

     

    DAB

Children
No Data