In the past few years I’ve been getting into IOT. You may have seen tweets or blog about the Tech-Turkey project I’ve been working on or flame throwing pumpkins at Halloween. I’ve learned and used Arduinos, Raspberry Pi’s, and Particle Photons and Electrons. It has been fun to learn more and get into the connected world… the internet of things!
I’ve been keeping ServoCity in business and even recently worked to get a custom PCB created. Every step of the way I’ve been learning different things and realizing just how much more there is to learn. Recently I’ve started learning more about Splunk.
What is Splunk If you don’t already know what Splunk is, Splunk is a software company based in San Francisco that produces software for searching, monitoring, and analyzing machine generated big data via a web style interface. Splunk’s software helps organizations with operational intelligence, log management, application management, enterprise security and compliance.
Side note: In my first exploration into Splunk I wrote a blog about using Splunk with DNN that may interest you.
Particle & SplunkDNN is a web application, but what if I wanted to get data from an IOT device? That’s when we call on Particle. If you’re not familiar with Particle, it makes it really easy to bring real world objects online. Particle is one of my favorite IOT platforms. It makes awesome microcontrollers, provides a nice IDE, has awesome documentation, and a great community. Connecting to Particle’s cloud is straight forward and even southerners can do it! See my presentation at our user group on DNN & Particle.
If you’re not familiar with Splunk, it makes it really easy to pull in data (machine data) and make sense of it. I’m talking about parsing vast amounts of data, creating visualizations and/or alerts and making it simple to understand. Even southerners can use it too!
Both Particle and Splunk are industry leaders and have some really big names behind their companies and as clients of their companies.
So why not bring Particle & Splunk together?
Reading Temperature with ParticleTo use the awesomeness that both solutions bring us we’ll first need to read the temperature and post it to a webservice. Here again, Particle makes this easy. I used a basic temperature reader in a bread board layout for this experiment.
Then, in Particle’s IDE I used the basic tutorial level code to read an analog value and post it to a Particle cloud variable. Cloud variables are accessible via web services. That is, I can make a GET request and parse the JSON object to get the data. Epic.
Now we were cooking with oil! The next step was to get this data into Splunk.
Getting Particle’s RESTful Data Into SplunkGetting RESTful data into Splunk is really straightforward thanks to Splunk’s extensibility. Splunk has an extensions gallery that can be found on the Apps and Ad-Ons sections of the Splunk website. I tell you this because ultimately, I followed a blog by Damien Dallimore on getting REST data into Splunk which used a modular input extension and that was all it took. I simply completed the required fields in the Splunk REST Modular Input as shown below.
After clicking save, the data from my Particle temperature reader was showing up in Splunk!
Creating Dashboards from the Particle DataOnce data shows up in Splunk you can literally perform any search query you want on the data and create/configure dashboards, panels, reports, alerts and more. Splunk is very powerful in this regard and scale to infinity. However, for this scenario I just wanted log the temperature over time from one device, as well as the temperature’s highest, lowest, and average. Splunk, again, made this very simple.
After clicking on the “result” field I created some visualizations and voila! Out popped some neat dashboards showing all my data in a way that’s easy to understand.
If you are like me, you kind of want to see things in action. So for those of you like me who are visual learners, here’s a quick video of the solution in action.
An IOT Combination That’s Hard to Beat!As you can see, both solutions are awesome and the opportunities are endless. Consider the possibilities here… Particle is easy to deploy and post data to the net and Splunk can easily connect, suck in data, and bring instant insights. The more data you give to Splunk the more knowledge you’re going to have. Splunk can handle this at scale too… I mean massive scale. Why not connect thousands of devices and pump all the data into Splunk and tune it to your liking! I believe that’s what they refer to as operational intelligence 😊 Now my mind is spinning with possibilities. Is yours?
I’ve recently been researching Splunk and have been impressed with its power, flexibility, and ease of use. This blog is not intended to be a step-by-step tutorial, but rather is aimed to show some initial findings, overview one way to integrate Splunk with DNN, and paint the picture of some potential use cases.
So What is Splunk?
If you don’t already know what Splunk is, Splunk is a software company based in San Francisco that produces software for searching, monitoring, and analyzing machine generated big data via a web style interface. Splunk’s software helps organizations with operational intelligence, log management, application management, enterprise security and compliance.
Installing Splunk was simple and after clicking around a little while it was evident that Splunk is an intuitive software. From a UI standpoint, it makes logical sense and the flow is easy to understand. And it didn’t take long to see and understand how powerful it is.
As you may imagine, I began to wonder if and how I could integrate Splunk with DNN.
DNN + Splunk: One Way to Connect the Two
One of Splunk’s powerful features is that it can literally suck in all types, styles, and formats of data. This data can be machine data, log files, or even data from a REST API. There are several mechanisms for getting data into Splunk, but for this scenario, DNN’s web API implementation makes this an easy fit. On the DNN side, a developer can easily create a custom module using web services to expose any DNN data on an endpoint, which Splunk can then access. If you’d like to go the custom module route, check out my other blog series on module development. However, I did not write a custom module to test the integration.
For my initial investigation into Splunk I chose to use DNN Sharp’s API Endpoint module as it allows easy configuration of end points. Splunk is architected to consume any type of data and then it makes that data extremely easy to search, create visualizations and/or alerts with. These searches, visualizations, and alerts can be very basic or very complex in nature.
Another thing to note is that Splunk is architected to do this at scale and can easily parse enormous amounts of data. For example, every time you drink from a Coca-Cola “Freestyle” machine at a fast food restaurant, the data from your drink selection is logged and Splunk helps analyze the data, denote trends, and sends alerts. So yes, those Coke machines (all across the world) are connected IOT devices and Coke is a Splunk customer. See how Coke is using Splunk in the Splunk Conf 2014 Keynote replay session. Imagine how much data that is on a global scaled --> Splunk is helping Coke make sense of it.
Side note: Check out the blog I wrote on using Particle & Splunk to monitor temperature
So, my first goal was simple: see if I could get data from DNN into Splunk.
Sticking along the thought process of “data logs” I figured why not expose the DNN event log on an endpoint and see what I could make happen. Obviously, the event log may not be the best use case as site administrators can clear logs or processes to automatically clear logs sometimes exist. However, for this initial test it is a good candidate. To get the event log data on an end point I used the DNN Sharp API Endpoint module to make a SQL query on the event log view and return it as JSON.
With the event log now sitting out there as JSON on a DNN end point now all I needed to do was get it into Splunk…
Getting REST Data Into Splunk
The Splunk side of this configuration only took a few minutes to configure and keep in mind I’m no Splunk guru (read, it’s easy!). Splunk is similar to DNN in that it’s extensible. Splunk extensions can be found on the Apps and Ad-Ons sections of the Splunk website. I tell you this because ultimately, I followed a blog by Damien Dallimore on getting REST data into Splunk which used a modular input extension and that was all it took. I simply completed the required fields in the Splunk REST Modular Input as shown below.
I chose to poll the data every 60 seconds. With this information inputted I clicked save and returned to the Data Inputs screen of Splunk and chose my newly created data source.
BOOM! I was seeing DNN event log info in Splunk!
Searching, Visualizations, & Alerts in Splunk
With data in Splunk now I needed to proceed to using Splunk to make sense of the data. Splunk’s searching functionality makes it very easy to search for, well... anything you'd like. I’m not yet knowledgeable enough to fully explain all the capabilities, but what I can easily see is that you can select your data source, click on keywords, add them to the source's search criteria and set your desired timeframe for the search. It’s feels as if you have a Google search bar and all your searches are performed on your data source and intellisense & syntax highlighting for your search are provided too!
Once you have a search returning data you can then create visualizations or alerts. And yes, there are tons of visualizations provided by Splunk. These visualizations can be saved as reports or live as “panels” that reside on dashboards. Dashboards can have as many panels as you want and you can have multiple dashboards if you like. Also, you can easily embed these panels into DNN or any other location by clicking the “convert to HTML” link that each panel has. Being able to display this info anywhere you like is a neat feature. Are your mental light bulbs turning on yet?
So, I created a few visualizations based on event log data that was available. I created a number-based-visualization to show a large number that represented a count of 404 errors, a line graph showing the number of failed logins, and a chart showing the 404’s over time. So, in just minutes Splunk was already helping me understand that I have some issues going on with one of my sites. I believe one reason for the 404's is that I've renamed some pages that I think bots are targeting trying to register. Anyways, I've got work to do... don't judge!
Opening Up Possibilities
Now you may be looking at this and thinking to yourself, yeah this is neat, but I could create a custom module to make something similar to this happen. And you would be correct, but keep in mind the potential use cases, flexibility, and scalability of Splunk in comparison to a custom module. You could easily have all your customers as data sources and create dashboards to help you (and your customers) quickly understand what’s going on with your customer's applications. You could also do data mashups of data from a DNN website/web app, some IOT device out in space, and any other data source you can think of to provide valuable insight. And again, Splunk has no problem doing this with massive amounts of data.
With just a little research into Splunk it didn’t take long to get my mind spinning with all the possibilities within DNN and beyond. Think about your current DNN use cases, requirements of your customers, and the exploding IOT market and you’ll soon see the light.
Here are some ideas I had right off the bat:
As you can see the power and flexibility Splunk provides is really nice. I believe Splunk could be a game-changer especially for those with large amounts of data to parse, anybody in the IOT space, and much more. I hope this blog has provided you with an introductory glimpse into some of the capabilities of Splunk and even got you thinking of potential ways to integrate Splunk into your applications or customer's environments. I am still learning about it and hope you will too. I know that I'm just scratching the surface here in my initial findings.
Find out more about Splunk at http://www.Splunk.com
I need to start out by saying that I’ve been inspired to do all this by some great guys in the Charlotte area and they are Dan Thyer, Mike Linnen, and Jay Ziobrowski… thanks for the motivation guys! I am either copying something creative I’ve seen them do or trying to imitate their passion, talent, and drive for Halloween and/or IOT projects. One day I hope to be as sharp and creative as they are.
Halloween & IOT
In 2016 I made a flame throwing pumpkin (copy-catting one of Dan’s inventions) and let’s just say some of the parents weren’t too keen on fire being near their kids and I also didn’t make any fans on the community’s HOA! Though, we all must start somewhere. In 2017 I went the safer route and made the AirGhost which is very similar to this year’s project.
The IOT Clown
This year I have created an IOT Clown. I did some testing and iterating on various ideas and concepts and there’s just no way to get around it… the thrust of compressed air brings a startling surprise and the best part is that it’s safe. We have tons of young kids in our neighborhood and moving a skeleton bone (which I debated in this early prototype) could likely hit someone, cause a toddler to fall, or trip someone up which could potentially lead to a spill on the concrete sidewalk. I don’t want to injure anyone or have some local parents mad at me, so I reverted to the compressed air, but then added a few more movements and changed the medium from a ghost to a clown.
Here’s a quick video of the end-product prototype just to show you where we’re heading… I’m going to dress it up a little more by Halloween, but you’ll get the gist.
Here are the main components I’m using for this project:
Here’s a video “talk-through” of the mechanical parts and power supplies being used.
Let’s Talk About Particle
The Particle platform is awesome! Check out this video of the Particle platform to learn more. I am admittedly a little bit behind all of Particle’s new innovations. I still need to learn about their Mesh and Argon solutions. Even though I’m not 100% up to speed I know you can do tons of creative stuff with the particle platform, their multiple IOT devices, and their integrated IDE. Since I’m using the Particle photon, we’ll start with it.
The Particle photon is a small IOT (internet of things) device that makes it easy to bring real world objects online. Particle makes it easy to setup the device and to connect to Wifi via a mobile app. If you want to know more about initially connecting and getting up and running with Particle they have some of the best documentation I’ve seen check out the doc, tutorials, and guides.
For this project all I really want to do is to move 3 servos… one for the head to spin, one for the head to roll, and one to push the handle on the air compressor. To do that we need to use the components I listed above + Particle’s platform + some code. I’ve listed out the components and just introduced the photon… now let’s look at some code.
Let’s Look at Some Code!
Particle’s platform is awesome, but we need some code to make things happen! I could easily copy and paste code here, but that wouldn’t help you understand the “why” and “how” behind some of the concepts. I hope to help you connect some dots here and as such I’ve cut a video walking through how I’m doing some of this stuff. The video shows code and includes videos of the device in action.
To all you senior devs… yes, the code shown in the video could be much better. I have not refactored anything yet, so the code is not nearly as efficient as it could be. And yes, I showed my handy Particle access token in the video… no worries though, by the time you read this I’ve already recycled it and created a new one.
Here are some relevant links:
So, with some disclaimers down and links shared let’s talk through the code some…
If you take the sum of all the info presented here that is how I’m making this happen!
And We Wait on Halloween!
Halloween is just about a week away at this point. If you have any questions or issues filling the gaps in this high-level tutorial, please reach out and ask your question. I plan on trying to video some of the fun at Halloween and posting any interesting reactions here just below this section… so stay tuned!
The Halloween Video
Check out some of the reactions we got from kids and a few adults!
Once you choose a font you can click to the “Type Tester” section to see how any specific words you type will look in your selected font. You can easily increase or decrease the font with the slider and you can also view how the font looks in various browsers on the “Browser Samples” tab as shown in the screenshot below.
Typekit uses “kits” to organize fonts for usage by designers. It’s really easy to create a new kit. Simply hover the kit section and click “Add New Kit”. As you can see from the screenshot below, I've created a kit for each site on which I use custom fonts. You can see how to add a new kit in the below screenshot.
Now that the "kit" is ready I need to add some fonts to it. Once you decide on a font you simply hover over the font and click “Add to Kit” and the font will be added to the kit for which you are currently viewing as denoted in the below image.
After you add a font to a kit you can go into the "kit editor" to further customize. Once you’re inside the kit editor you can customize various settings and styles that make the custom fonts appear on your site. You can simply add the CSS selectors that you’re using on your site & they will then render showing the custom font that you've just selected in Typekit. Notice in the below screenshot where I'm adding " .ANewSelector " class in Typekit's editor.
If you wanted to access specific weights & styles via your skin.css file you can click on the “Using weights & fonts in your CSS” option which will give you the below screen allowing you to copy the CSS necessary for your specific font & weight.
Now if you did click the “Copy CSS” option you would end up with some CSS that resembled the below:
font-family: "atrament-web",sans-serif; font-style: normal; font-weight: 400;
Once you click publish you will be ready to go. I should also mention that if you want to develop or test out styles locally you can also enter “localhost” in your kit editor settings and that will make your local sites work with the new custom fonts.
If you were concerned about how your styles would display on mobile devices you can click into the "Mobile Settings" section of the Typekit editor as seen in the below screenshot.
Now to make all of this active we need to click the big green “Publish” button at the bottom right hand corner of the kit editor screen which you can see in the below screenshot.
Then in my HTML Module I simply referenced the CSS classes that I specified earlier in the Typekit selectors area.
And that's all it takes to get everything lined up. You can see an example of the redesigned home page (running locally) using the custom font “Atrament web” that I selected earlier.
Typekit makes it extremely easy to use custom fonts in your site. If you’re a Creative Cloud member you should check it out. I hope this blog has been helpful to you with integrating custom fonts in your DotNetNuke sites.
Have you ever seen a small pixel in your Pulsar Thermal optic’s screen that you wish wouldn’t stick out like a sore thumb? If you fire your gun a lot these pixels-that-need-repair occasionally occur, but fear not, Pulsar has anticipated this and provided a way to resolve it. I had one on my screen for a few months before I investigated it and the good news is that it’s simple to correct!
A “defective pixel” is a pixel within your viewfinder or screen that is “degraded”, sticks out, and won’t go away even after your scope calibrates. I’ve owned a Pulsar Trail XP-50 for over 2 years and in this time, I’ve only had 2 defective pixels. Though, when it does happen, over time it will bother you enough to want to know how to fix it.
Here’s a screenshot of one of my defective pixels while in “White-Hot” mode
In this screenshot, the defective pixel may not seem like a big deal, but when you’re hunting and looking through the viewfinder it can become distracting to your eye over time, especially if it’s near the crosshairs. While hunting with the defective pixel shown in the screenshot above there were several times I panned the horizon and mistook the small white dot for being an animal that was a great distance out.
The first thing to do if you notice a defective pixel or something that doesn’t look correct in your viewfinder is to calibrate the optic. If you haven’t changed any settings on your scope then your Pulsar thermal optic will automatically calibrate every so often to ensure what you’re seeing is accurate, clear, and crisp. Calibrating the optic makes the clicking sound that you may have grown accustomed to hearing by now if you own a thermal optic.
These calibrations can be forced by pressing the power button in the Trail models. If my screen ever gets hazy or I notice something not sharp in the viewfinder I simply calibrate the scope. With all that said, the first thing to do if you notice a defective pixel is to force a calibration because generally that will fix it.
If calibrating the optic doesn’t resolve the issue then repair the defective pixel by going to one of the last menu options in the menu system, the “Defective Pixel Repair” option.
Once you choose this option it’s simple. The system presents you with a pixel selector and provides you with the ability to move the X & Y coordinates. This task feels very similar to sighting in the scope.
Just move the X & Y coordinates until you are right on top of the defective pixel. As you update the values for the X & Y coordinates the pixel selector will move across the screen as shown below. The pixel selector surrounded by the box is like the Picture-In-Picture feature and is a magnified (zoomed in) version of the pixel selector.
The goal is to move the defective pixel selector on top of (or as close as possible to being on top of) the defective pixel.
Once you have the defective pixel lined up you then need to hit the record button, yes, the record button. The system will repair the pixel and respond with an “OK” message.
Note: You can also use the remote control to do this as shown in this video by Michael Bennett
And that’s all there is to it! Note that depending on your unique situation, it may take repairing multiple pixels to get the screen back to the desired state. In one of the previous defective pixel scenarios, I had to repair 2 pixels before it was back clear, and the pixel was no longer bothering me.
I also made a quick video walking through this process. You can see the video below:
I hope you found this content helpful. If so, leave me a comment below.
We’ve hunted in the WeHuntSC.com Predator Challenge for 7 years. We’ve hunted hard and have yielded minimal results other than being frustrated. Lately we’ve heard a lot of people telling us how effective they have been with hunting coyotes with night vision. This year we aimed to reduce frustration and get more coyotes on the ground by upgrading to a night vision setup. This journey would lead to many lessons learned, which I’ll share in the below blog entry.
After doing some research it seems most hunters are using AR’s for their choice of weapon when coyote hunting. The AR model frees hunters from having to manually chamber another shell as this is done by the gun. This allows more rapid fire at targets which is beneficial when hoping to shoot multiple coyotes … if you can get multiple to come in.
I’d recently heard about Anderson Arms having a unique AR setup. Anderson uses a nanotechnology called RF-85 on their guns that makes it to where you never have to oil the gun. It’s pretty sweet technology. I went with the Anderson Arms AM15 optic ready. If you haven’t checked it out, head on over to https://www.andersonrifles.com.
With the gun selection done it was time to move on to the scope. This meant I had to learn about night vision. It seems in the night vision world there are 2 routes one can go – infrared or thermal. I’m sure you can get into religious debates about the advantages & disadvantages of each, but in the end I chose thermal. Once I decided on thermal I needed to pick out a brand. I had previously purchased a FLIR monocular for spotting scope which I use for tracking wounded animals and ensuring I’m not spooking deer on my way in or out of the woods. It’s very handy, but not very clear. I wanted to try a different brand to see if it was any different. PULSAR seemed to be a popular brand based on the research I had done. I ended up going with the PULSAR Apex XD38.
I worked with the crew at Reel Determined Outdoors to get this rig set up. If you haven’t checked out Reel Determined or the team up there you should give them a shout.
One initial note about night-vision gear. I was surprised at how expensive these technologies are so if you’re looking for a cheap night vision solution get ready to be surprised. However, I can tell you that once you use a night vision setup for coyotes you will never go back.
Sighting In a Thermal Scope
With the gun in hand and scope mounted on it we were ready to venture into the world of thermal night vision. Before we got to shoot at any coyotes however, we needed to sight it in. This is where we really started learning some stuff.
When you take a thermal scope out and look at a target you don’t see the lines on the target. This is because the scope is responding to heat signatures and, as you would imagine, the lines on the target aren’t putting out any heat. Yes, this would seem obvious, but to some rookies we didn’t think ahead about this too much. On our first attempts at sighting this thing in we ended up cutting the center of the target out and putting up some tin foil as the tin foil maintained different temperatures and we could *vaguely see the contrast in the scope. It was all we needed to get excited and get started though.
Once inside the scope I realized that we’d have to learn the menu systems inside of the PULSAR scope. At first sight it was a little overwhelming because I had no idea what all the icons represented. Yes there is a book that comes with it explaining it and yes we didn’t really read it before getting started! In retrospect the best thing I did was watch some YouTube videos of people talking through the menu items.
The menus are not difficult to understand I was just in initial shock of trying to understand them all. The icons make sense and there are 2 menus inside of the software. Yes, software… the thermal scope is essentially a computer system on your gun that’s giving you a screen with information on it and view into the dark. As such, it does require some time to boot up when you press the on button.
The thing that is important to understand about the menu is that you zero the sights in in the menu, that it can hold “sight-ins” for 3 different weapons, and there is a reset button. Sometimes I got lost in the menus and didn’t know what I was clicking and changed the weapon number and even clicked reset. This did indeed make for a frustrating time sighting in the weapon. Once I learned what buttons not to click things got easier.
Gavin and I ended up sighting this gun in about 3 or 4 times as we learned more, messed things up, saw that our scope wasn’t tight on the gun, and figured out the menu items. Once you understand how it works sighting it in is fairly easy. Another trick that made sense was to use hot-hands hands on the middle of your target. If you want to go the extra mile, soak a pizza pan in ice-water and then put it behind the hot-hands on the target. This creates a cool circle encompassing a hot center, which in the scope creates a good contrast for you to aim at.
After several times out with the gun and sighting it in we finally started hitting the target where we wanted to… in the bullseye.
Videoing with a Pulsar Recorder
One neat thing about digital night vision is the ability to record the footage from inside your scope. Since it’s a computer, why not right? PULSAR has different models and with the more recent models the video recording capabilities are getting even better and more user friendly. Our experience with the video recorder left some to be desired and required some learning on our behalf.
The video recorder for the model scope I have is the CVR 640 and it mounts on the weaver/picatinny rail… that is it can be attached to anywhere you see the grooved sections on the gun. In my scenario this meant I could attach the recorder on the side of the scope or on the front of the gun. I initially attached it on the front of the gun because this made ergonomic sense. The recorder holds an SD card and you simply pop the SD card out to download the footage. The recorder plugs into the base of the scope and screws in tightly. The odd thing about this is that your gun literally has cables running down & around it (however you handle your cable management that is).
I was very excited to video all the coyotes we would be busting in the near future! Sure enough it wasn’t long before we had coyotes in the scope and started pulling triggers. The first time I was sure that I was recording when I shot. I looked at the video box and noticed the blue light wasn’t on anymore. How terrible luck was it for the batteries to die right before the shot! So I got new batteries.
A few hunts later the same thing happened. Did I have a bad batch of batteries or what? After 8 live-action shots that were recording, but yet failed to record I had had enough. I’d put in numerous new batteries and nothing worked… I was going to get to the bottom of this. We had some hunts coming up and I left the gun with Gavin during one of our re-sight-in attempts. Gavin and I were both doing research on this issue. Gavin noticed that even though the recorder has a weaver rail and mounts to the gun it was NOT rated for recoil. I told Gavin to remove the video recorder from the gun, put it in his pocket and record himself sighting the gun in and see if the video stopped recording. BINGO! We’d found the culprit. Gavin said the video recorder continued to record during the shots when not attached to the gun. This let us know that the video recorder will record if it wasn’t attached to the gun when shooting.
The First Coyote on The Ground With Night Vision
With multiple times to the range figuring out the sighting in process and now with the video issue out of the way we were ready to rock and actually get some footage. We had been bummed about previous footage attempts because we had some great encounters. We were about to change that.
Gavin and I were requested to help a local farmer out who has a hog problem. We had indeed gotten hogs on camera at the location and were headed in to assist. When we arrived to the location we went in to the field scanning with the monocular as we walked toward our stand. Gavin saw that hogs were already in the field. So we dropped down to a knee and just watched. Right then a coyote started howling very close to us. To our surprise the coyote howl startled the hogs and they exited the field that they had just entered. I was surprised that hogs would be intimidated by coyotes, but thinking back on it the hogs has some young ones with them and maybe their leaving the field was to protect the young ones.
I told Gavin we should go to the area on the other side of the field where there is a deer stand and just be patient. I was sure the hogs would return. We agreed and slowly retreated to the other area of the field. We were just sitting there talking letting time pass when coyotes started howling very loudly again. This time there were more than one howling. We were hog hunting, but we did have the coyote call in the truck. Frustrated at the situation Gavin said “I’m going to the truck to get the call”.
After returning back from the truck Gavin set the call up and said “Get in the gun because when I hit this call they are going to come in”. So I did as Gavin instructed and turned the scope on.
If you’re wondering why my scope would even be off… night vision and thermal optics flat eat batteries. If you’re going thermal do yourself a favor and order the extended battery pack so that you are not like me and have to carry around packs of batteries in your pockets and constantly replace them.
Back to the story... Gavin told me to get in the scope and I did just that. Gavin played some coyote whimpers and a coyote duet, new sounds we’d just downloaded to the FoxPro before leaving. I was scanning left and Gavin was scanning right. We stopped the calls and it was quiet, crisp, and clear out. Nothing responded… no howl backs, no barks, nothing. Then all of a sudden Gavin whispered “There he is” and at that I turned to the right and saw a coyote crossing my face from right to left. I followed this coyote waiting on it to pause so that I could squeeze the trigger. Gavin said “What are you doing turn right turn right”. What we didn’t know until afterwards was that Gavin didn’t see the coyote I saw. He had seen another one, a bigger one, to our right. I told Gavin “Shut up” and he said “There’s a big one here on the right”. I said “Make him stop, say something, bark” and he responded “A big one on the right”. It was not easy to pull the scope off the one I was following and turn right, but I did. What I saw was indeed a larger coyote on our right. I put the crosshairs on him and squeezed off. I could tell from the video that I hit him! I then swiveled back left and got back on the coyote that I had seen earlier. It paused just enough and I dropped it on the spot.
It all happened so fast. My heart was pumping and adrenaline was racing, but one thing was for sure. We definitely had the scope sighted in correctly this time. And when I pulled the video recorder out of my pocket it was still recording! We had footage to review!
We looked and looked for the first coyote, but could not find it. We think it ran off and died somewhere, but we did recover the second coyote and got some pics. Man it was a fun hunt.
And now you can re-live the hunt with us in the below video:
Tips For Hunting With Thermal Night Vision
Throughout this process we’ve learned a good deal about AR-15’s, night vision scopes, PULSAR, and recording video. Here’s a list of things we’ve learned and hopefully they are helpful to you in some way:
I’ve recently read 3 new books on leadership. One of these books was given to me as part of leadership training at work and the other two I ordered. I wish I could read more and am going to try to make an effort to read more frequently.
Anyways it was good to read these books because they confirmed some concepts I believe in and naturally try to exercise, they shed light on new leadership traits I should probably try to implement, and best of all they made me think. So what am I talking about here… let’s look into it.
I saw someone retweet a tweet by a guy named Jon Gordon @JonGordon11. I liked the tweet and looked at his website and shortly thereafter I ordered this book “Training Camp” of his on Amazon.When I received the book I started reading it that day and also finished it in the same day. It is a good read, told in a story fashion, with short chapters that will keep you engaged the entire time. In the competitive world we live in everyone wants to know what the best do to separate themselves from the rest.
The setting of the story in this book is with a football player trying to make it into the big leagues. As a former football player myself I really identified with the stories, struggles, emotions, and feelings of the story. In case you read the book I won’t ruin the story for you, but along the way of trying to make the team the player finds out all the things that the best do better than the rest. What some may be surprised with is that the recipe for success is not some magic formula, it’s more about doing the simple things well, consistently, and with great focus and pride.
If you are looking for a good read that will help you get a recipe for hopefully becoming better than the rest I would recommend this book. One thing I also admire about Jon Gordon is that he lets his faith shine through his in his writing. In one of the chapters he speaks about how the best draw from a higher power, in this case, the Lord. Jon’s spiritual beliefs tie into his recipe for greatness and it all makes sense.
Buy Training Camp on Amazon
We are reading this book as part of leadership training at work and this read is somewhat longer than the other two books mentioned in this review. Though, while it is longer it is jam packed with great insights on leadership for leaders in the middle of organizations. John C. Maxwell is a popular author and he’s been studying leadership for some time. Reading this book was like reading several books at once due to Maxwell’s thoroughness and how he cites and quotes other books. The author, John. C. Maxwell, is obviously well read, informed, and experienced on leadership.
This book was awesome and made sense in all directions (leading up, across, and down) of the 360 degree leadership model. One thing I really liked is that the author does a great job of giving a real life example with nearly every point made in the book. The examples really drive the points home and makes the concepts easy to comprehend.
As a leader in the middle of an organization I can identify with several concepts conveyed in this book. Another thing I liked was that not only did the author describe a leadership challenge, but he would also follow it up with proposed solution steps or ways to work through the challenges as well. This book provided tremendous insight into leading up, down, and across the spectrum of an organization. I may re-read this book in a few years… it’s got that much helpful info.
If you are the top leader of your organization and you’re reading this there is a chapter for you as well. At the very end of the book there is a chapter directly speaking to top leaders that offers insight into how you can better manage organizations and leverage your 360 degree leaders.
Buy 360 Degree Leader on Amazon
After reading the Training Camp book by Jon Gordon I saw some other books that he wrote. It seemed there was a lot of positivity around his book “The Energy Bus” so I ordered in on Amazon as well. Following suit of the Training Camp book I found this to be a very engaging and easy read. I read it within one day as well! Jon Gordon’s writing style makes his books easy to follow because he’s telling a story and because the chapters are short so you feel like you’re making constant progress.
I liked this book and would recommend it as well. The concepts in this book all speak to going after your work with passion and, yes, energy! Being motivated and passionate about your work makes a big difference. The book also talks about getting the right people on your bus, not letting people drain the energy out of your team, leading with your heart, and loving your passengers. If you lead a team and you (or your team) needs an energy injection then you should give this book a read! Get on the bus!
Buy The Energy Bus on Amazon
I hope this brief review has helped you out in some way. If you read any of these books I’d be interested to hear your take on them. Tweet to me @CBPSC and let me know your thoughts or post here in the comment section
I have been recently trying to learn these very things! Dashboards are tricky, but I really enjoy the challenge. I have been reading Stephanie Evergreen's book called Presenting Data Effectively, stephanieevergreen.com is her site. Her book works for me as she has screenshots and checklists that I can follow to better equip myself when I am working on a presentation or what not.