<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" 
  xmlns:content="http://purl.org/rss/1.0/modules/content/" 
  xmlns:dc="http://purl.org/dc/elements/1.1/" 
  xmlns:atom="http://www.w3.org/2005/Atom" 
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" 
  xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Posts on Engineer&#39;s notes</title>
    <link>https://nantipov.org/posts/</link>
    <description>Recent content in Posts on Engineer&#39;s notes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>&amp;copy;{year}, All Rights Reserved</copyright>
    <lastBuildDate>Wed, 21 Oct 2020 11:52:50 +0200</lastBuildDate>
    
        <atom:link href="https://nantipov.org/posts/index.xml" rel="self" type="application/rss+xml" />
    
    
    

      
      <item>
        <title>Job looking situation</title>
        <link>https://nantipov.org/2020/10/job-looking-situation/</link>
        <pubDate>Wed, 21 Oct 2020 11:52:50 +0200</pubDate>
        
        <atom:modified>Wed, 21 Oct 2020 11:52:50 +0200</atom:modified>
        <guid>https://nantipov.org/2020/10/job-looking-situation/</guid>
        <description>English Hello everyone,
Hello Welcome to the special landing page for recruiters and creative people
interested in contacting me.
I am writing this to bring some information in regard of my current situation.
First of all, thank you for visiting my profile and being in contact with me.
I am always open for communication and glad to help.
Not looking for a job for now At the moment I am not looking for a job.</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        
        
        
        
          
            
              <category>en</category>
            
          
            
              <category>de</category>
            
          
            
              <category>ru</category>
            
          
            
              <category>recruiting</category>
            
          
        
        
          
            
              <category>en</category>
            
          
            
              <category>de</category>
            
          
            
              <category>ru</category>
            
          
            
              <category>recruiting</category>
            
          
        
        
      </item>
      
      <item>
        <title>Hunter Secretary</title>
        <link>https://nantipov.org/2020/09/hunter-secretary/</link>
        <pubDate>Mon, 21 Sep 2020 11:52:50 +0200</pubDate>
        
        <atom:modified>Mon, 21 Sep 2020 11:52:50 +0200</atom:modified>
        <guid>https://nantipov.org/2020/09/hunter-secretary/</guid>
        <description>Problem statement I have quite a number of unprocessed mails and messages in variety of communication platforms from recruiters. I respect people, but unfortunately cannot respond everyone in a fast manner. It takes time and therefore creates a back-pressure problem in a condition of consumption performance is lower than producing one.
Number of incoming messages is growing every week.
Solution I want to read a message, review it and put a label or mark it somehow indicating appropriate type of response:</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        <media:content url="https://nantipov.org/covers/hunter-secretary-mailbox.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>en</category>
            
          
            
              <category>recruiting</category>
            
          
            
              <category>java</category>
            
          
            
              <category>hunter-secretary</category>
            
          
            
              <category>gmail</category>
            
          
            
              <category>google-auth</category>
            
          
            
              <category>markdown</category>
            
          
            
              <category>html</category>
            
          
            
              <category>templates</category>
            
          
        
        
          
            
              <category>en</category>
            
          
            
              <category>recruiting</category>
            
          
            
              <category>tech</category>
            
          
        
        
      </item>
      
      <item>
        <title>Mono :: Motor driver</title>
        <link>https://nantipov.org/2020/02/mono-motor-driver/</link>
        <pubDate>Sun, 09 Feb 2020 13:05:34 +0100</pubDate>
        
        <atom:modified>Wed, 12 Feb 2020 00:00:00 +0000</atom:modified>
        <guid>https://nantipov.org/2020/02/mono-motor-driver/</guid>
        <description>Goal The goal of this Mono iteration is replacing the motor driver. In the earlier published post it was mentioned that L298N motor driver creates a significant voltage drop.
Well, I decided to go with the TB6612FNG chip as of the Pololu motor driver.
Pololu motor driver TB6612FNG Designing the Mono driving module Requirements Okay, we have
four motors and two motor drivers with the following pinout. Pololu motor driver TB6612FNG pinout Pin on the left Description I Description Pin of the right GND Logic ground I PWM for the engine A PWMA VCC Logic VCC 2.</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        <media:content url="https://nantipov.org/covers/IMG_2571.JPG" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>tech</category>
            
          
            
              <category>tinker</category>
            
          
            
              <category>en</category>
            
          
            
              <category>mono</category>
            
          
            
              <category>robot</category>
            
          
            
              <category>rover</category>
            
          
            
              <category>tb6612fng</category>
            
          
            
              <category>motor-driver</category>
            
          
            
              <category>pca9685</category>
            
          
            
              <category>raspberry-pi</category>
            
          
        
        
          
            
              <category>tech</category>
            
          
            
              <category>tinker</category>
            
          
            
              <category>en</category>
            
          
        
        
          
            
              <category>Mono</category>
            
          
        
      </item>
      
      <item>
        <title>Mono :: Power supply</title>
        <link>https://nantipov.org/2020/02/mono-power-supply/</link>
        <pubDate>Sat, 01 Feb 2020 13:05:13 +0100</pubDate>
        
        <atom:modified>Wed, 12 Feb 2020 00:00:00 +0000</atom:modified>
        <guid>https://nantipov.org/2020/02/mono-power-supply/</guid>
        <description>Goal The goal of this Mono iteration is improvement of the power supply setup. In the previous post it was mentioned that the Raspberry Pi and other infrastructure would be supported with two separated sources.
Single battery with huge capacity and 7.4V voltage I came up into solution with Li-Po battery which is known as long lasting power supply.
This is a battery up to 5200 mAh capacity and 7.4V voltage.</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        <media:content url="https://nantipov.org/covers/IMG_2520.JPG" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>tech</category>
            
          
            
              <category>tinker</category>
            
          
            
              <category>en</category>
            
          
            
              <category>mono</category>
            
          
            
              <category>robot</category>
            
          
            
              <category>rover</category>
            
          
            
              <category>power-supply</category>
            
          
            
              <category>lipo</category>
            
          
            
              <category>raspberry-pi</category>
            
          
        
        
          
            
              <category>tech</category>
            
          
            
              <category>tinker</category>
            
          
            
              <category>en</category>
            
          
        
        
          
            
              <category>Mono</category>
            
          
        
      </item>
      
      <item>
        <title>Mono :: First Steps</title>
        <link>https://nantipov.org/2020/01/mono-first-steps/</link>
        <pubDate>Sun, 26 Jan 2020 15:27:19 +0100</pubDate>
        
        <atom:modified>Mon, 24 Feb 2020 00:00:00 +0000</atom:modified>
        <guid>https://nantipov.org/2020/01/mono-first-steps/</guid>
        <description>Introduction Let me introduce Mono.
It is a small rover which I am going to build using simple set of existing modules.
As a base the ready chassis has been taken.
And here is the initial version for further experiments.
Mono view #1 Mono view #2 Components Let&amp;rsquo;s start with the following things:
Chassis with four motors; Motor drivers L298N (2x); Controller for generating PWM impulses PCA9685 (speed control); Brain as Raspberry PI Zero with WiFi; Batteries and power bank.</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        <media:content url="https://nantipov.org/covers/IMG_2508.JPG" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>tech</category>
            
          
            
              <category>tinker</category>
            
          
            
              <category>en</category>
            
          
            
              <category>mono</category>
            
          
            
              <category>robot</category>
            
          
            
              <category>rover</category>
            
          
            
              <category>raspberry-pi</category>
            
          
            
              <category>pca9685</category>
            
          
            
              <category>l298n</category>
            
          
        
        
          
            
              <category>tech</category>
            
          
            
              <category>tinker</category>
            
          
            
              <category>en</category>
            
          
            
              <category>mono</category>
            
          
        
        
          
            
              <category>mono</category>
            
          
        
      </item>
      
      <item>
        <title>Converting site from WordPress into Hugo</title>
        <link>https://nantipov.org/2019/12/converting-site-from-wordpress-into-hugo/</link>
        <pubDate>Sat, 14 Dec 2019 12:34:57 +0100</pubDate>
        
        <atom:modified>Sat, 14 Dec 2019 00:00:00 +0000</atom:modified>
        <guid>https://nantipov.org/2019/12/converting-site-from-wordpress-into-hugo/</guid>
        <description>What actually happened? My wife owns a web-site which was powered by WordPress.
Some time ago we decided to switch into static solution without databases and constantly running page generating / rendering process.
Idea was great, but I came to it quite late - just a day before hosting contract should be prolonged.
Trick was in switching also into another environment where only static files can be served. Having this, the</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        <media:content url="https://nantipov.org/covers/wordhugopress_not_found_screenshot.png" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>tech</category>
            
          
            
              <category>en</category>
            
          
            
              <category>ru</category>
            
          
            
              <category>wordpress</category>
            
          
            
              <category>hugo</category>
            
          
            
              <category>java</category>
            
          
            
              <category>spring-batch</category>
            
          
            
              <category>converter</category>
            
          
            
              <category>freemarker</category>
            
          
            
              <category>jsoup</category>
            
          
        
        
          
            
              <category>tech</category>
            
          
            
              <category>en</category>
            
          
            
              <category>ru</category>
            
          
            
              <category>fix</category>
            
          
            
              <category>java</category>
            
          
        
        
      </item>
      
      <item>
        <title>Fixing SAMSUNG LED UE49MU6179</title>
        <link>https://nantipov.org/2019/07/fixing-samsung-led-ue49mu6179/</link>
        <pubDate>Sat, 27 Jul 2019 23:37:41 +0200</pubDate>
        
        <atom:modified>Sat, 27 Jul 2019 00:00:00 +0000</atom:modified>
        <guid>https://nantipov.org/2019/07/fixing-samsung-led-ue49mu6179/</guid>
        <description>What actually happened? My TV stop working at some point in time. The red dot does not light up and nothing happens.
Checking what is inside Hope to have fuse problem which could be simply fixable.
Disassembly Start with two holes on the bottom for getting cover off and then pull it step by step, latch by latch.
Left Disassembly hole Right Disassembly hole Ah, it is not a fuse issue Here is what I saw.</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        <media:content url="https://nantipov.org/covers/IMG_1699.JPG" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>tech</category>
            
          
            
              <category>en</category>
            
          
            
              <category>tv</category>
            
          
            
              <category>led</category>
            
          
            
              <category>samsung</category>
            
          
            
              <category>ue49mu6179</category>
            
          
            
              <category>bn94-12439c</category>
            
          
        
        
          
            
              <category>tech</category>
            
          
            
              <category>en</category>
            
          
            
              <category>fix</category>
            
          
        
        
      </item>
      
      <item>
        <title>GSM 7bit PDU encoding algorithm in Java</title>
        <link>https://nantipov.org/2019/03/gsm-7bit-pdu-encoding-algorithm-in-java/</link>
        <pubDate>Fri, 01 Mar 2019 11:58:21 +0100</pubDate>
        
        <atom:modified>Fri, 01 Mar 2019 00:00:00 +0000</atom:modified>
        <guid>https://nantipov.org/2019/03/gsm-7bit-pdu-encoding-algorithm-in-java/</guid>
        <description>Text to 7-bit PDU string converter Being honest I forgot why I had written this code some time ago. I put it here
from my another small blog page hosted on blogpost
(engnick.blogpost.com).
Now I remember how was it and decided to bring this piece of code, as maybe
it might be useful for somebody. I wrote this code when I was working in
MegaFon as part of automated testing tool for</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        
        
        
        
          
            
              <category>tech</category>
            
          
            
              <category>en</category>
            
          
            
              <category>java</category>
            
          
            
              <category>gsm</category>
            
          
            
              <category>pdu</category>
            
          
            
              <category>7bit</category>
            
          
            
              <category>converted</category>
            
          
            
              <category>sms</category>
            
          
            
              <category>ussd</category>
            
          
            
              <category>msisdn</category>
            
          
        
        
          
            
              <category>tech</category>
            
          
            
              <category>en</category>
            
          
            
              <category>java</category>
            
          
        
        
      </item>
      
      <item>
        <title>Recovering of data from damaged and quickly formatted HDD</title>
        <link>https://nantipov.org/2019/02/recovering-of-data-from-damaged-and-quickly-formatted-hdd/</link>
        <pubDate>Mon, 18 Feb 2019 14:07:13 +0100</pubDate>
        
        <atom:modified>Mon, 18 Feb 2019 00:00:00 +0000</atom:modified>
        <guid>https://nantipov.org/2019/02/recovering-of-data-from-damaged-and-quickly-formatted-hdd/</guid>
        <description>What actually happened? Friends asked me to check what can be done for &amp;ldquo;fixing&amp;rdquo; some &amp;ldquo;broken&amp;rdquo; hard-drive.
So, what we have?
Hard-drive 2.5&amp;quot; 500 Gi SATA; Correctly detected by Windows machine in 3 over 10 times; There are lots of pictures, images, songs, videos very important for
owner and his wife in particular; Should be NTFS partition. Quick remark: I am not a professional data recovery guru, so here is just</description>
        
        <dc:creator>Nikolai Antipov</dc:creator>
        <media:content url="https://nantipov.org/covers/img_1032_1.jpg" medium="image"><media:title type="html">featured image</media:title></media:content>
        
        
        
          
            
              <category>tech</category>
            
          
            
              <category>en</category>
            
          
            
              <category>hdd</category>
            
          
            
              <category>recover</category>
            
          
            
              <category>quick-format</category>
            
          
            
              <category>raspberry-pi</category>
            
          
            
              <category>raspbian</category>
            
          
            
              <category>testdisk</category>
            
          
            
              <category>photorec</category>
            
          
            
              <category>ddrescue</category>
            
          
            
              <category>organizemusic</category>
            
          
        
        
          
            
              <category>tech</category>
            
          
            
              <category>en</category>
            
          
            
              <category>fix</category>
            
          
        
        
      </item>
      

    
  </channel>
</rss>