I´m working on putting here some screenshots or a video showing it. So far My arduino hardware... https://www.dropbox.com/s/rii867stp80pp5z/2013-05-09%2011.15.07.jpg
https://www.dropbox.com/s/0vpsfluq3z0kub4/2013-05-09%2012.17.46.jpg I use: fullcalendar pypdf for the printing cards on the rfid card D3js Filepicker.io, allows to take pictures to workers from the browser page!!! Tornado messaging websockets Coffeescript and of course *WEB2PY* I lied, its not under 20 lines of nodejs . Its about 53 lines. Yet, in python i would need some more.... 2013/6/10 Massimo Di Pierro <[email protected]> > Tell us more. Have some pictures or screenshots? > > > On Monday, 10 June 2013 05:21:50 UTC-5, Ramos wrote: >> >> I' not spanishhh. >> Portuguese from Portugal. >> >> I have a web2py app to control all outside workers via an RFID reader. I >> use arduino to read the card and send it via serial. Then in the >> local PC I have nodejs to read it and call a web2py service that via >> tornado sockets updates a web page. >> My web2py app is in the amazon cloud. It works so fasttttttttt just under >> 20 lines of nodejs.amazing! >> >> No dia Segunda-feira, 10 de Junho de 2013, [email protected]@gma >> **il.com <http://gmail.com> escreveu: >> >>> Thanks Jason and Antonio for your help. >>> >>> Jason, thanks for the additional tips and info. You are right is not >>> web2py related, it's just python related when it comes to having the GPIO >>> working, then again anything assembled with web2py is related to it... the >>> GPIO file contains that while loop you talked about and that's what is >>> necessary to have an event listener as mentioned earlier. Again if not >>> replicating that project we'll continue to have a "failure to communicate", >>> so I agree, it's best we leave it at that as I've also already dropped >>> web2py althogether since it won't do for me and many who like me are >>> looking for an implementation that would work with more simplicity. So I'l >>> off to other option, but I thank you again for your time and help Jason. >>> >>> About NodeJS, I believe you might be incorrect. Is not as "new" as you >>> think and is already being heavily used for commercial and critical use >>> already... one company making use of it for instance, is Google, as I've >>> been told directly by a Google employee I know. >>> >>> Anyway I am really glad Antonio passed along the info... first of all I >>> love to see more technologies reaching the pi world and empowering the pi >>> platform, and also because coincidentally I've started to get into nodejs >>> since a short while so that'll be a great learning project from me. >>> Muchisimas gracias por el enlace Antonio! :) >>> >>> Cheers! ;D >>> >>> >>> On Jun 10, 2013, at 4:21 AM, Jason (spot) Brower wrote: >>> >>> Sounds interesting. Personally my system ran with very little cpu at >>> all. There are way to make it run effeciently. >>> Node is a fun new technology, but I personally don't trust it for >>> commercial use yet. It's still at that young and fragmenting stage so the >>> technology could change to fast. :) >>> Have fun and it would be great to see what you do with the pi. >>> BR, >>> Jason >>> >>> >>> On Mon, Jun 10, 2013 at 10:54 AM, António Ramos <[email protected]>wrote: >>> >>> Sorry to disappoint you but raspberry pi go a lot better with nodejs >>> javascrcipt framework.Almost no CPU usage.... >>> >>> check this >>> http://pijs.io/ >>> >>> >>> 2013/6/10 Jason (spot) Brower <[email protected]> >>> >>> HI, >>> I'm not totally sure what the gpio file is about, but an easy way to do >>> it is to have while loop in a python file. Each time it goes through the >>> loop it can do things like check the serial line for sensor data, run any >>> automated items like turning on the lights in the evening, and read for >>> messages that where sent to the server from the internal network. I used >>> ampy back in the day: >>> https://launchpad.net/**ampy<https://launchpad.net/ampy>with that system >>> running, you can check for data from the network and send >>> it as a command to your device. It's not web2py at this point. web2py >>> only assembles the ampy messages that are clicked on and sends them to your >>> service running the the backend. >>> I'd be happy to help you there if you like. But it's not very web2py >>> related, so I think it should be off list. Time is limited for me, but we >>> could do something. :) >>> BR, >>> Jason Brower >>> >>> >>> On Thu, Jun 6, 2013 at 9:50 AM, freäk qnc <[email protected]> wrote: >>> >>> Hi Jason, >>> >>> Thanks for your reply. You're right it's a group of about 5k users, >>> although I must say that while on webiopi group with less than 150 users I >>> would get an answer on the same day, which I thought was amazing given the >>> few users and just one developer. I guess the more users the more difficult >>> to get answers as many ask and few can provide an answer. >>> >>> Regarding the verbosity of my post you may notice that my original post >>> had a mere 5 lines (well on my large screen it is at least ;D), before I >>> stated "My experience so far to give you a bit of background context..." >>> which was only a recount to give those interested in reading further, an >>> idea about what I had tried before landing on web2py, but was not to needed >>> to understand what I was asking in the prior paragraph. >>> >>> About the bump, mine didn't mean to be one (which was also about 4 lines >>> long going by my screen). In all honesty I was just thanking everyone on my >>> way out. >>> I had spent several sleepless nights digging for info and reading docs >>> to make this work and that got me nowhere. In the meantime the author of >>> the referenced instructable was nice enough to get back to me, but >>> unfortunately it was (in short) with a "sorry can't be of more help" reply. >>> So I figured it wasn't meant for me to go down the web2py path. >>> >>> I didn't look at what I was asking in terms of percentages, I thought >>> web2py on raspberry isn't much different than web2py on linux, so I thought >>> I was asking 100% about python programming in web2py, while referencing the >>> small application in the linked instructable tutorial, my bad. Anyone >>> curious or wanting to help would have only needed to install that same app >>> on a raspberrypi to replicate understand what was being asked. >>> >>> Thank you for the generic info which validate what I already >>> knew. Indeed there is the need of a "deamon" or service running on the same >>> host where web2py is installed to have a permanent listener to events >>> (whether triggered by webUI or a sensor change). In the case of the >>> referenced instructable, that'**d be the "GPIOServer.py", which once >>> launched (by rooting into the raspberry >>> >>> You received this message because you are subscribed to a topic in the >>> Google Groups "web2py-users" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/** >>> topic/web2py/IhMsvEHjmW4/**unsubscribe?hl=en<https://groups.google.com/d/topic/web2py/IhMsvEHjmW4/unsubscribe?hl=en> >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> web2py+unsubscribe@**googlegroups.com. >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "web2py-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to web2py+unsubscribe@**googlegroups.com. >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> -- > > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
