• Content Count

  • Joined

  • Last visited

1 Follower

About StuxNet

  • Rank
    Elite member

Profile Information

  • Gender
    Not Telling
  • Location
    Minnesota, USA
  • Interests
    Python, Ruby, SBC's, SOC's, Basketball, Raspi Cheesecakes, API's and IPA's. Not necessarily in that order.

Recent Profile Visitors

2114 profile views
  1. pcdoodle. That name rings a bell to a local comp rep shop. You local to mn? I could def teach you a thing or two. Hit me up if interested.
  2. The script I gave you was a very loose example and it includes things I was using for my specific project. Things that you don't necessarily need to use for your own. trigPin in this situation is just an 'empty' pin that I use as an LED trigger. If temperature is above X, turn on LED. If temp below X, turn LED off. If you just want a temp and humidity readout, remove every function, set pins how you'd like and just print tempOut() Then go here: Or here: Or here: https://ww
  3. Got this same wrapper, as well as others to work on an NPiNeo and an OPiZ recently (defining outside ) but you're right it's prolly redundant. I got it working using this wrapper (forked/updated within 1 year opposed to 2yr on the one u link to) and the following script. What happens when you print(instance) after it's defined? from pyA20.gpio import gpio from pyA20.gpio import port import dht import time import datetime # initialize GPIO temPin = port.PG11 trigPin = port.PG7 gpio.init() gpio.setcfg(trigPin, gpi
  4. You have a problem with the dht22 working. You never specify what the problem actually is. What's the error code you're getting? Ima go ahead and take a wild guess that you don't initiate a configuration for that port. put the following after gpio.init() PIN2 =gpio.setcfg(PIN2, gpio.OUTPUT)
  5. Which is easier to say? Every post previous, or run this? Attached is a bash script that will install and make various dtbo/dts edits automagically in order to install and interface with ds18b20 Thermometer connected to a NPiNeo running Armbian 5.69. I've also attached an image for how the module needs to be physically connected (using 10k resistor between 1 wire and PWR). If you do not have a physical 10k resistor you may use the internal pullup to do so (do not use on long connections?) This is done by adding param_w1_pin_int_pullup 1 on a newline after param_w1_pin=PG11 in the /boot/a
  6. You guys are awesome. I love you but I also hate you. That is a joke btw. Remember, threads/emails are not ideal communication. When you finalize a thread, maybe wrap it all up in a single coherent, command by command tutorial? Just spent the last hour trying to hodge podge the meaning of this thread + this All I needed to know is that param_w1_pin=PG11 shoulda been on a seperate line while a simple dump of the full amrbianEnv.txt woulda sufficed... verbosity=1 logo=disabled console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=armbian-add-overlay
  7. Which Armbian kernel and version? When this happens to me, I typically just revert to a previous version that has the support and/or features I'm looking for. I would recommend doing the same, in addition to making an image of SD card (if you've spent a good deal of time setting it up) before updating to the latest kernel. This is one fix. Without booting up my own device with latest version, and taking your word for it that it's not available in armbian-config menu. It's likely because the armbian-config is being worked on, and you will not be able to enable specifically through a
  8. For when the link goes dead and for those looking to buy on the english version of Aliexpress. FFC FPC Ribbon cable 0.5mm pitch 24 pin 24PIN Front Length 250mm Width 12.5mm Ribbon Flex Cable
  9. I've gotten higher than 1A ratings from a USB port (usb 3.0) before and absolutely gotten less than 1A from a similarly rated 'ac/dc module' Can never go wrong with getting an appropriate, reliable setup. In my experience, FriendlyArm boards are no where near as fickle (power wise) than OPi boards. I can boot any of them from just about any power source I connect them to. For this reason I prefer the Neo. OPiZ's are absolutely a different case. For me, they rarely work just from USB, unless I use a specific, good quality cable. Forget compiling/installing more robust libraries. I can't
  10. The actual better ending to this story is not a post of the working camera but actually the underlying issue in the first place. I'm not a newb but I also don't know every schema of every board I own. Does the cable connect N/E/S/W on OPi/NPi/RPi/BPi? Perhaps include a picture of the correct orientation of the connected camera's ribbon cable? No one seems to ever talk about that. Not going to spend the next 4 hours yakshaving the cam across 6+ boards, 3 OS's in an attempt to port, decipher posts and problem solve. Multiply every attempt by 3 because I wonder "is the camera actu
  11. @Larry Bank hit up this guy >>> <<< He has very similar projects to what your working on, ie: universal SBC's wrappers, except mainly for screens. He has one repo "OPi.GPIO" that aims to accomplish something similar to ArmbianIO project but is limited to OPi as you can imagine. He has recent commits that suggest branching out into NanoPi (Duo) territory though. I talked to him awhile back, pretty cool dude but seems pretty busy and the OPi.GPIO isn't his main focus. In any case this is all to say, without looking at your source and knowi
  12. Yea I get that. Totally understandable. In some situations, especially bigger companies, you would want to go with a more professional solution like you describe. Of course people forget to stamp, isn't that going to be an issue regardless of the device though? I don't think you need to be a mathematician, to do a timeclock. Let a spreadsheet do that for you. All that aside, as a whole SBC's represent (to me) the option and freedom to do without those kinds of proprietary (usually expensive) devices that offer zero control. On top of doing without the service fees and support. At the end
  13. Welp. It currently works for...more than a couple employees and has been tested using various means/devices for months. I could go into more detail but your opinion does not apply to my specific circumstance. Regardless, thanks for the criticism. (seriously) In my experience every 'small business' solution to this has been to simply, not have a time clock. Again, I could go into details but I'm not the trend that every local business owner I've met, has set. I don't know what you mean by terribly complicated but I beg to differ. Let OPiZ offer RFID interface to a Gsheet. Let Gsheet
  14. Wanted to automate payroll. Needed to be as simple/easy on the eyes as possible for your run of the mill user. General functionality is that it makes digital timecards for every employee action/swipe of an RFID tag. Every swipe also punches a Google Sheet based on company department, by utilizing regex to find column associated with employee name, then the row based on today's date. It then punches current military time to corresponding clock in/out offset. The timecard math is all done using the Google spreadsheet functions to discern overtime, total hours, etc... More will be included lat
  15. Not exactly sure what you mean by some of your post but "sometimes it does it gets stuck and then he turn off" Sounds like a power issue. OPiZeros commonly 'halt' when big power/usage demands are put on the SBC. How are you powering the OPi? I've successfully installed both xvfb and wkhtmltopdf on an OPiZ, so... xhtml2pdf and weasyprint might be some alternatives to look into. Depending on the unspecified language/methods you're using for wkhtmltopdf.