HtmlToText
disk91.com – technology blog technology, hardware, security, hacking (diy), iot skip to content home news technology hardware systems middleware programming networks sigfox iot sigfox lessons who am i contact me privacy policy ← older posts getting started with gnuradio & scapy by paul posted on 16 october 2018 gnuradio is an open-source software for making software defined radio. it can be used to model a radio transmission or the process a real radio communication. scapy is a python tool set able to interact with gnuradio. basically gnuradio will receive an signal from a sdr key and process it to get a digital sequence. scapy will process this sequence and potentially generate a new sequence to be process by gnuradio to be transmitted. there are plenty of example of gnuradio/scappy usage to hack, simulate, learn many radio protocols like wifi, gsm, bluetooth… i want to play a little with sigfox also so that’s why i started to investigate on this tool. as this tool is a bit complicated, this post details the key element having helped me to getting started with this tool. continue reading → share : twitter facebook google linkedin pinterest tumblr print posted in networks | tagged gnuradio , hackrf , rf868 , sigfox | leave a comment review laird sentrius lorawan gateway by paul posted on 13 september 2018 after having tested different lorawan gateway like kerlink ifemtocell , thethingsgateway and kerlink wirnet , in the past two years, i was looking for a new low cost indoor gateway for deploying thethingsnetwork (the global crowd-sourced lorawan network) in my city. gateway are not all easy to shop, kerlink at first. as one of my ifemtocell has burned into the hell this summer with no reason after only 3 months powered-on i was not looking for the same. thethingsgateway has different semiconductor provider reseller but myne suffer of certain instabilities actually and i need to reboot on regular basis. so that’s the reason of this new try. let’s see how to setup on ttn. continue reading → share : twitter facebook google linkedin pinterest tumblr print posted in lora | tagged iot , lorawan | 2 comments stm32 and low power mode by paul posted on 12 september 2018 stm32 arm mcu are proposing different low power mode for saving energy when running iot on battery. some basic example of low power are delivered with the sdk as part of cubemx solution but these example are not really complete, not well documented and in my point of view difficult to use in a fresh new project. basically my current feeling with stm32 is these guy are pretty good to write thesis on how to do magic stuff with the mcu, writing hundreds of pdf pages about really detailed stuff but they are really bad for providing some line of code to illustrate this valuable content with something practicable you can use on the go. so after spending a week working on a working and understood example of low power code, i’ll share with you the result of this work… continue reading → share : twitter facebook google linkedin pinterest tumblr print posted in hardware | tagged arm , lowpower , stm32 | leave a comment stm32 and arduino, working with a custom board by paul posted on 4 september 2018 arduino is supporting stm32 platform and after following the installation steps , you can easily work with the st-microelectronics development kit. in the real life you need to create a specific setup once your prototype is transformed into a custom board. this setup redefines the pin mapping, the target mcu and needs to refine the firmware transfer method as you will use and external stlink programmer. in this post we are going to see the different step for doing this. continue reading → share : twitter facebook google linkedin pinterest tumblr print posted in hardware , iot | tagged arduino , iot , stm32 | leave a comment arduino for stm32 by paul posted on 2 september 2018 in a previous post i explained how to getting started with stm32 with classical eclipse or keil environments. these environments are very cool for starting from scratch in designing firmware. that said, you have to recreate a lot of basic functions and libraries to create your firmware. on the other hand, the arduino community is proposing a lot a existing libraries and a development framework with a large number of supported features. the stm32 community looks active and that’s a good way to quickly create advanced firmware. that said there is different point blocking in my point of view for using arduino as a professional environment: outside of the core libs and some nice one, most of the lib are badly written the official editor is a mess if you manage more than 3 files… writing libraries with official editor is… “impossible” for this reason, in this tuto, i’ll use visual code studio to see if the 2 last point can be solved. regarding the first point, there is nothing better than using well coded libraries and rewrite (and share) the badly written one. continue reading → share : twitter facebook google linkedin pinterest tumblr print posted in hardware | tagged arduino , arm , stm32 | leave a comment getting started with arduino mkrwan1300 & lorawan ttn by paul posted on 30 august 2018 after making some post on arduino mkrfox1200 , here i come with the first steps to use mkrwan1300 board to send your first frame on ttn and also how to use them for discovering the ttn coverage around. mkrwan1300 board is a lorawan arduino board based on the murata cmwx1zzabz module. this module is capable for lorawan in europe (868mhz), na (915mhz) asia (923mhz) …. it is also capable for sigfox in both zone (but actually not with this board as much as i know). producing 14db emission and capable for 20db emission for fcc zone. the price of the arduino board is about 40€ and it is largely available on internet. in this post we are going to see how to make the first steps with this board and create a device to map the ttn network coverage with and without a gps. continue reading → share : twitter facebook google linkedin pinterest tumblr print posted in lora | tagged arduino , lorawan , thethingsnetwork | leave a comment how to get some sigfox subscriptions ? by paul posted on 24 august 2018 this is a frequent question i received from many hackers or companies: how can i get a sigfox subscription for my iot device? we need to start saying a sigfox subscription is a right to have its device data to be proceeded for a year. in the lpwa technology there is no sim cards or any physical things attached to the subscription. you buy a device from a semiconductor company, when this device is compatible with sigfox you have an id attached to this device. this id is uniq and used to identify the device on the sigfox network. so once you have a subscription, you attach this subscription to this device id then you will be able to access your device data from the sigfox backend. that’s clarified we can address the question of this post: what are the way to access a subscription? continue reading → share : twitter facebook google linkedin pinterest tumblr print posted in sigfox | tagged lpwa , sigfox | leave a comment enhanced sigfox api services by paul posted on 13 august 2018 since i’m using sigfox backend there are a lot of operations i’m regularly manually doing. thanks to the sigfox api , it is possible to automate these manual operations to gain in productivity and save time. the most consuming operation were for me to manage the device type because each of them have multiple callback and every callback uses many parameters. the callback replication is for me a recurrent operation when adding a new contract, when creating a new version of application, when instancing for dev, prod… it’s also a complex operation when you have to ask a third party ( like a client ) to configure a device-type for connecting to your service. as a consequence these operations are the first one i’ve automated thanks to the sigfox api. i’ve decided to publish this usefull
Informations Whois
Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;
Domain Name: DISK91.COM
Registry Domain ID: 98159866_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.ovh.com
Registrar URL: http://www.ovh.com
Updated Date: 2015-04-19T16:44:20Z
Creation Date: 2003-05-21T12:42:59Z
Registry Expiry Date: 2018-05-21T12:42:59Z
Registrar: OVH
Registrar IANA ID: 433
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS12.OVH.NET
Name Server: NS12.OVH.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-09-01T08:12:56Z <<<
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 OVH
SERVERS
SERVER com.whois-servers.net
ARGS domain =disk91.com
PORT 43
TYPE domain
RegrInfo
DOMAIN
NAME disk91.com
CHANGED 2015-04-19
CREATED 2003-05-21
STATUS
clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
NSERVER
DNS12.OVH.NET 213.251.188.131
NS12.OVH.NET 213.251.128.131
REGISTERED yes
Go to top