setfirelabs.com Report : Visit Site

Technical data of the setfirelabs.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host setfirelabs.com. Currently, hosted in Germany and its service provider is APEX Trading GmbH .

HTTP Header Analysis

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

DNS

HtmlToText

setfire labs currently hacking about with: nodemcu menu skip to content home dealing with dyp-me007y tx spurious readings leave a reply the serial-output of the dyp-me007y ultrasonic range detector is pretty good when you are measuring the distance to a static object with little or no other obstacles creating ‘noise’. however, the odd spurious reading does crop in from time to time. for example: 201cm 201cm 201cm 128cm 201cm 201cm 201cm 201cm 201cm 201cm this is actual data, and the spurious 128cm makes no sense and needs to be ignored (rather than just taking an average). fortunately, @jmms-karunarathne and @mikemeinz wrote some code to correct for this here: https://www.codeproject.com/tips/813946/a-method-to-ignore-anomalies-in-an-ultrasonic-dist the code takes a group of samples and counts how many of each there are. it then picks the measurement with the highest count (the ‘mode’). in the above example, there are 9 counts of 201cm – which would be returned as the measurement. so far, so good.. however, there is a problem where all the data is rubbish. look at this actual data: 275cm 273cm 273cm 275cm 0cm 483cm 0cm 0cm 125cm 235cm 274cm 274cm 274cm 690cm 816cm 274cm 274cm 273cm 0cm 483cm 0cm 274cm 274cm 90cm 184cm 292cm 273cm 539cm 648cm 316cm this was produced by out-of-range measurements – the object was less than 28cm from the sensor. the measurement which occurred the most was 274cm and so the algorithm would return this seemingly meaningful result. an improvement to the ‘mode’ routine would be to apply a ‘confidence’ to the measurement. in my code, i take 30 readings, and require a minimum of 20 of the same to accept it as a good measurement. i try this five times over, after which the routine gives up and returns a zero indicating out-of-range. this seems to work well. except some of the time. this looks like good data: 82cm 82cm 82cm 82cm 83cm 82cm 82cm 83cm 83cm 83cm 83cm 83cm 83cm 83cm 83cm 82cm 83cm 83cm 83cm 82cm 82cm 83cm 82cm 83cm 82cm 80cm 83cm 83cm 82cm 82cm confidence was 16 returning 0cm here 83cm was only measured 16 times. this was an absolutely static measurement on the bench, however the returned value was either 82 or 83cm (ignoring the 1x 80cm!). the way to deal with this is to look at the readings +1 or -1 from the mode. if either the count of the mode, added to the count of the mode+1, or mode-1 adds up to at least the threshold, then the result is good. this entry was posted in arduino , building automation , nodemcu on february 3, 2018 by jonathan clark . dyp-me007y tx (serial output) ultrasonic sensor interfacing with arduino / nodemcu 2 replies there are two main versions of the dyp-me007y ultrasonic module ( see here to tell the difference ) – this article is about interfacing and taking readings from the serial output version. at the labs, we have been working on interfacing one of these with the nodemcu – an arduino-type device with built-in wifi. this is in order to create a water tank level sensor. the automotive ultrasonic sensor lends itself to this application in that there is no need to add waterproofing – it is already there. to interface with it we need to convert the 3.3v digital in/outs from the nodemcu to the 5v required by the dyp-me007y. if you were using a 5v arduino, you wouln’d have to do this. for us, we use a bi-directional logic level converter which is available from ebay. we bought from electro tv parts because they stock them in the uk and so shipping is fast. we are only using two of the four channels on the converter. these are for the two sides of the serial connection between the nodemcu and the dyp-me007y – rx and tx. the converter also needs 5v, 3.3v and gnd, which are all available on a pins of the nodemcu board. on the nodemcu, we then need to choose two digital pins for the serial connection, and connect these to the lv (low voltage) side of the converter. the hv side connects to the dyp-me007y rx and tx pins. it also needs 5v and gnd. for the serial connection, the pin assigned as tx on the nodemcu connects (via the converter) to the rx pin on the dyp-me007y, and rx on the nodemcu to tx on the dyp-me007y, also via the converter. that’s just how serial works! now on to the coding. we use softwareserial to assign the two digital pins as the tx and rx on the nodemcu, then we are ready to read the results from the dyp-me007y. #include <softwareserial.h> // pin assignments. tx on the arduino connects to rx on the sensor, rx to tx. #define tx_pin d3 #define rx_pin d4 softwareserial dypsensor = softwareserial(rx_pin, tx_pin); const int max_try_serial = 50; // how many cycles of 10ms to wait for before giving up on the sensor (up to 255) here you can see i am using pre-defined constants (d3/d4) for the nodemcu in the arduino dev environment. we also define how many times we will try to read the serial before giving up. this allows trapping of the situation were there is nothing coming from the dyp-me007y – like if it was not connected. now in setup, we start up the serial: void setup() { serial.begin(19200); delay(10); dypsensor.begin(9600); } // end of setup we are also starting up the serial connection to the computer it is connected to so we can see debug information. our loop looks like this: void loop() { int current_reading; current_reading = getdistance(); serial.print(current_reading); serial.println("cm"); delay(50); } ..which just calls a subroutine to read the sensor and then prints the result to serial. getdistance looks like this: int getdistance() { byte msb, lsb, checksum, checkcalc, tries = 0; int distance; // we want a 255 which is the start of the reading (not msb but saving a byte of variable storage).. while (msb != 255) { // wait for serial.. while ( not dypsensor.available() && tries < max_try_serial ) { delay(10); tries++; } if (tries == max_try_serial) { serial.println(" timed out waiting for serial."); return -1; } msb = dypsensor.read(); } // now we collect msb, lsb, checksum.. while ( not dypsensor.available() ) { delay(10); } msb = dypsensor.read(); while ( not dypsensor.available() ) { delay(10); } lsb = dypsensor.read(); while ( not dypsensor.available() ) { delay(10); } checksum = dypsensor.read(); // is the checksum ok? checkcalc = 255 + msb + lsb; if (checksum == checkcalc) { distance = msb * 256 + lsb; // round from mm to cm distance += 5; distance = distance / 10; return distance; } else { serial.println("bad checksum - ignoring reading."); return -1; } } // end of getdistance() getdistance() returns a signed integer of the distance in cm, or -1 if it returned bad data, or the serial read timed out. it works like this: keep reading until we receive a 0xff which is the start byte. now read the most significant byte (msb). read the least significant byte (lsb). read the checksum. calculate the checksum and compare to the one sent from the device. if checksum matches, it’s a good reading and so return it. if not, return -1. it makes no attempt to decide whether the sensor has actually sent a meaningful result, just that what we received matched what it sent. more of validating the results in a later article. here is the code in full: /* reads a dyp-me007y tx ultrasonic sensor and writes the distance to serial. this is the serial version of the sensor */ #include <softwareserial.h> // pin assignments. tx on the arduino connects to rx on the sensor, rx to tx. #define tx_pin d3 #define rx_pin d4 softwareserial dypsensor = softwareserial(rx_pin, tx_pin); const int max_try_serial = 50; // how many cycles of 10ms to wait for before giving up on the sensor (up to 255) void setup() { serial.begin(19200); delay(10); dypsensor.begin (9600); } // end of setup // // reads bytes from rx port and returns a reading in cm int getdistance() { byte msb, lsb, checksum, checkcalc, tries = 0; int distance; // we want a 255 which is the start of the reading (not msb but saving a byte of variable storage).. while (msb != 255) { // wait for serial.. while ( n

URL analysis for setfirelabs.com

http://www.setfirelabs.com/2018/02
http://www.setfirelabs.com/wifi/eight-pointers-to-help-you-fix-your-sonos-for-big-buildings
http://www.setfirelabs.com/tag/cr200
http://www.setfirelabs.com/building-automation/dyp-me007y-ultrasonic-distance-sensor-pwm-or-serial#respond
http://www.setfirelabs.com/wp-content/uploads/2014/11/screen-shot-2014-11-07-at-10.59.42.png
http://www.setfirelabs.com/tag/unifi
http://www.setfirelabs.com/tag/sonos
http://www.setfirelabs.com/wifi/ubiquiti-unifi-repair
http://www.setfirelabs.com/freedomotic/freedomotic-logging-for-development-and-debugging-part-2
http://www.setfirelabs.com/tag/syslog
http://www.setfirelabs.com/comments/feed
http://www.setfirelabs.com/category/freedomotic
http://www.setfirelabs.com/tag/ubiquiti
http://www.setfirelabs.com/page/2
http://www.setfirelabs.com/feed
ebay.co.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: SETFIRELABS.COM
Registry Domain ID: 1834238397_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.meshdigital.com
Registrar URL: http://www.domainbox.com
Updated Date: 2017-04-23T00:00:00Z
Creation Date: 2013-11-05T00:00:00Z
Registrar Registration Expiration Date: 2018-11-05T00:00:00Z
Registrar: WEBFUSION LIMITED
Registrar IANA ID: 1515
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.8779770099
Reseller: 123Reg/Webfusion
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Jonathan Clark
Registrant Organization: Setfire Media
Registrant Street: 5-6 Gregson Rd
Registrant Street: Reddish
Registrant City: Stockport
Registrant State/Province: Cheshire
Registrant Postal Code: SK4 3GN
Registrant Country: GB
Registrant Phone: +44.1619685970
Registrant Phone Ext:
Registrant Fax Ext:
Registrant Email: [email protected]
Registry Admin ID:
Admin Name: Jonathan
Admin Organization: Setfire Media
Admin Street: 5-6 Gregson Rd
Admin Street: Reddish
Admin City: Stockport
Admin State/Province: Cheshire
Admin Postal Code: SK4 3GN
Admin Country: GB
Admin Phone: +44.1619685970
Admin Phone Ext:
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID:
Tech Name: Webfusion Limited
Tech Organization: Webfusion Limited
Tech Street: 5 Roundwood Avenue
Tech City: Stockley Park
Tech State/Province: Uxbridge
Tech Postal Code: UB11 1FF
Tech Country: GB
Tech Phone: +44.8712309525
Tech Phone Ext:
Tech Fax Ext:
Tech Email: [email protected]
Name Server: ns.123-reg.co.uk
Name Server: ns2.123-reg.co.uk
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2017-07-10T17:35:40Z <<<

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


The Data in this WHOIS database is provided
for information purposes only, and is designed to assist persons in
obtaining information related to domain name registration records.
It's accuracy is not guaranteed. By submitting a
WHOIS query, you agree that you will 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(spam);
or (2) enable high volume, automated, electronic processes that
apply to this WHOIS or any of its related systems. The provider of
this WHOIS reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by this policy.

LACK OF A DOMAIN RECORD IN THE WHOIS DATABASE DOES
NOT INDICATE DOMAIN AVAILABILITY.

  REGISTRAR 123-REG LIMITED

  REFERRER http://www.meshdigital.com

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =setfirelabs.com

  PORT 43

  SERVER whois.123-reg.co.uk

  ARGS setfirelabs.com

  PORT 43

  TYPE domain

DOMAIN

  NAME setfirelabs.com

NSERVER

  NS.123-REG.CO.UK 212.67.202.2

  NS2.123-REG.CO.UK 62.138.132.21

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

  CHANGED 2017-04-23

  CREATED 2013-11-05

  EXPIRES 2018-11-05

  REGISTERED yes

Mistakes

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