daveakerman.com Report : Visit Site

Technical data of the daveakerman.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host daveakerman.com. Currently, hosted in United Kingdom and its service provider is Krystal Solutions LLP .

the related websites

vitalf1.com bournesports.com revital.co.uk asot.org.uk charityfair.org.uk lichfieldhockey.co.uk bournemouth.vitalfootball.co.uk targetspace.co.uk 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called LiteSpeed containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

dave akerman dave’s world skip to content home about flight history commercial flights educational flight schedule how-to twin ssdv channels with an sdr tracking car pc tracking software sms gateway links ← older posts pi zero gps/gsm tracker and habitat gateway posted on 25/05/2018 by dave gsm-based trackers are quite rightly frowned upon for hab tracking, mainly because they only work at low altitudes (within range of a mobile phone tower, which aim the signal generally downwards). so they don’t provide tracking throughout a flight, which is a problem as then you don’t know where the payload is until it lands. if you’re lucky. there are 2 problems here – one is that gsm coverage isn’t 100%, and the other is that the popular gsm trackers don’t seem to like high altitudes. i don’t know if they get confused, or they don’t like the cold, but i’ve tried these things several times and only had one work once. a gsm/gps tracker that actually works would be useful though, as a backup to a main tracker. having had little success with commercial offerings, i thought i’d make one. i found a model that uses the sim868 gsm/gps module, plus supporting electronics on a pi zero hat. so that plus a pi zero and suitable power supply would make a fairly small backup tracker, and maybe even one that works. the device supports gsm (calls, texts) and gprs (2g, i.e. slow data). it also has a gps receiver. it seemed attractive to use gprs to provide internet access (via ppp), but that would lock out the single serial port thus making gps unavailable. so i decided to just send sms from the device instead, using a script that gets the gps position, then builds and sends an sms containing that position. i wrote this in python using the pygsm library, which makes things very easy (generally no need to mess around with at commands). pygsm doesn’t know about the sim868 gps functions however, but it was simple to add those. so my test script requests and parses the gps position, then formulates a text message and ends it to my mobile phone: it would also be useful to have the balloon position automatically uploaded to the live map, so i decided to have the device send a second sms but this time to a gateway based at home. this gateway is another pi with a usb 3g modem attached. i used the same library, but a different script to poll for new messages, determine whether an incoming message is of the correct format, and if so build a ukhas telemetry sentence, finally uploading it to habhub for the live map: update: software now uploaded to github: https://github.com/daveake/gsmtracker note: not tested in flight yet so i don’t know if the software and/or hardware chosen will work or not, so user beware!! posted in weather balloon | leave a comment pi zero w streaming dashcam posted on 01/04/2018 by dave tidying my office a few days ago, i came across some car reversing monitors that i used to use as cheap pi displays for use in the chase car, to show the distance and direction to the payload; these days i use the official pi touchscreen as it’s a lot better for that application. one of the monitors is a flip-up model, and i wondered how much space there was inside. i use the pi zero a lot for balloon trackers, as it’s small and light compared to other pi models, but perhaps one could fit one inside the base to make a smart dashcam – one that can stream my balloon chases to youtube as well as record to sd. about the same time, michael horne (author of the excellent pi pod blog ), posted a picture of a similar-looking model on twitter, asking how to power it from 5v. that’s the opposite of what i wanted to do (power the pi zero from the 5v rail inside the monitor) but i felt i might be able to help so i opened up my unit to find where the 5v could be tapped. as it turned out, michael’s unit had a very different pcb to mine, but the seed was sewn so i decided to start building my dashcam. pi zero to monitor first job was to connect the the display to a pi zero w (w because i want to be able to stream the camera video). this requires the 5v and gnd lines on the gpio pins, plus the composite video output pin, to be wired to their counterparts in the monitor. once i’d used the correct video pin this worked without issue! i don’t know how much spare current capacity the display has on the 5v rail, but it dropped slightly from 5v to 4.9v which is ok. the pi zero booted and ran continuously overnight with no issues and with nothing on the display pcb getting hot. i connected the pi zero to my lan via a usb lan adapter, ssh’d to it, then set the video aspect ratio to match the monitor (16:9). sdtv_aspect=3 the full set of options is: i also updated/upgraded raspbian, and set up the wifi. ffmpeg next steps were to enable and connect the camera, and to install ffmpeg, which is what i use to stream to youtube. i used these instructions to install the library: cd /usr/src git clone git://git.videolan.org/x264 cd x264 ./configure --host=arm-unknown-linux-gnueabi --enable-static --disable-opencl make sudo make install and then ffmpeg. this takes several hours to build, so it’s a good time to find something else to do! cd /usr/src git clone git://source.ffmpeg.org/ffmpeg.git cd ffmpeg/ sudo ./configure --arch=armel --target-os=linux --enable-gpl --enable-libx264 --enable-nonfree make aspect ratio i then tested the video streaming to youtube with a command like this: raspivid -o - -t 0 -w 640 -h 360 -fps 25 -b 500000 -g 50 | ffmpeg -re -ar 44100 -ac 2 -acodec pcm_s16le -f s16le -ac 2 -i /dev/zero -f h264 -i - -vcodec copy -acodec aac -ab 128k -g 50 -strict experimental -f flv rtmp://a.rtmp.youtube.com/live2/<stream id> which worked to youtube, however the preview displayed on the monitor was distorted. i thought that this was to do with raspbian not correctly applying the screen resolution, but no matter what i did to fix that (specifying the resolution explicitly in config.txt, or specifying the preview window dimensions) fixed it. eventually i concluded that the issue was within raspivid, and then i soon found a very relevant forum post , which explained how to modify raspivid: git clone https://github.com/raspberrypi/userland.git cd userland ./buildme then add these lines near line 116 of raspipreview.c: param.set |= mmal_display_set_noaspect; param.noaspect= mmal_true; then rebuild. after following these steps, the problem was gone! assembly with the base plate removed, i threaded the flat camera cable up through the back of the base, behind the support that goes up to the top of the display, connected the camera and fixed it in position with sugru: i then added a piece of black duct tape covered the cable to stop it snagging and make it look tidy. wiring the pi zero has 3 wires connected – 5v, 0v and video, which on my monitor go to a convenient electrolytic capacitor and the back of a pcb socket. finally, a switch is mounted near the front of the monitor’s base, and connected to a gpio pin and gnd: everything was then insulated with duct tape before screwing on the metal base. script i wanted the dashcam to work in one of 2 modes – to record as a dashcam normally would, and to also live stream to youtube (via the wifi connection to a phone or myfi device, for example). so i wrote a small script that switches modes according to the position of a switch connected to a gpio pin. on startup, or when the switch position changes, the script runs the appropriate shell command for that mode. for regular dashcam recording, that’s a simple raspivid command; for streaming it pipes the raspivid output through ffmpeg (see command above). at present i’m not recording the video, so i need to do that using rotating file names, over-writing old files before the sd card fills up, and recording at a high resolution but streaming at a lower resolution. results posted in weather balloon | 2 comments how to choose a tracker posted on 25/02/2018 by dave i sometimes receive emails asking which hab tracker is be

URL analysis for daveakerman.com

http://www.daveakerman.com/?p=1639
http://www.daveakerman.com/?p=2011
http://www.daveakerman.com/?p=1232
http://www.daveakerman.com/?p=1440
http://www.daveakerman.com/?p=2019
http://www.daveakerman.com/?p=952
http://www.daveakerman.com/?p=2254
http://www.daveakerman.com/?p=2257
http://www.daveakerman.com/?p=2324#respond
http://www.daveakerman.com/?paged=2
http://www.daveakerman.com/?p=1362
http://www.daveakerman.com/?p=310
http://www.daveakerman.com/?p=2156
http://www.daveakerman.com/?p=1732
http://www.daveakerman.com/?p=1536
recantha.co.uk
amazon.co.uk
engineer2you.blogspot.co.uk
caltekservices.co.uk
ukhas.org.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: DAVEAKERMAN.COM
Registry Domain ID: 1636630067_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2017-03-04T22:41:33Z
Creation Date: 2011-01-24T10:50:32Z
Registry Expiry Date: 2018-01-24T10:50:32Z
Registrar: eNom, Inc.
Registrar IANA ID: 48
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.KRYSTAL.CO.UK
Name Server: NS2.KRYSTAL.CO.UK
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-08-22T18:51:37Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR eNom, Inc.

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =daveakerman.com

  PORT 43

  TYPE domain

DOMAIN

  NAME daveakerman.com

  CHANGED 2017-03-04

  CREATED 2011-01-24

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  NS1.KRYSTAL.CO.UK 77.72.0.11

  NS2.KRYSTAL.CO.UK 139.162.230.184

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .