Navigation

    • Register
    • Login
    • Search
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. hard-shovel
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    hard-shovel

    @hard-shovel

    30
    Reputation
    78
    Posts
    567
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    hard-shovel Follow

    Best posts made by hard-shovel

    • RE: Trouble wiring a Dalla 18B20 to Arduino D1 Mini

      @sirzlimz It may be stating the obvious but the photo shown is not a arduino processor but a ESP8266.
      Therefore the I/O pins listed in the sketch refer to the GPIO pin number on the ESP8266.
      So if PIN 2 is listed in the Sketch it refers to GPIO2 which is the pin marked D4 on the D1 mini module..

      The photo shows the Data jumper connected to D2, So trying moving this to D4 with the original sketch.

      posted in Hardware
      hard-shovel
      hard-shovel
    • RE: Trouble wiring a Dalla 18B20 to Arduino D1 Mini

      @sirzlimz I have just tried this circuit out myself on a D1 module and the using the library listed from milesburton it does not work on the ESP8266 in parasitic mode.
      If you move the jumper over for powered mode it will work fine.

      Trying on an Arduino nano with the same device and breadboard it works fine in both modes.

      So testing again and reading the data sheet on the DS18B20 and the section on "Powering the DS18B20" page 7 some insight can be obtained.

      Anyway a quick fix is to put another 4.7K resistor in parallel with the first and the system should work with one sensor,

      so two possible ways of connection are shown

      Powered Mode with the Jumper to 5V, Recommended method, I always power my DS18B20's
      This works with multiple devices, (I have just tried with 10 devices on the D1 [with multiple device sketch])
      0_1520624348000_IMG_3652.JPG

      Parasitic Mode with two 4.7K resistors (this trick only works with one device on the bus)
      0_1520624437698_IMG_3653.JPG

      posted in Hardware
      hard-shovel
      hard-shovel
    • RE: Trouble wiring a Dalla 18B20 to Arduino D1 Mini

      @sirzlimz There are lots of pinout diagrams on the web like below.

      For the the arduino use the GPIO number as the pin number

      ie
      GPIO5 --- marked D1 in Arduino IDE use 5
      GPIO13-marked D7

      0_1520633752967_esp8266-wemos-d1-mini-pinout.png

      posted in Hardware
      hard-shovel
      hard-shovel
    • RE: Is it really required to remove the voltage regulator to save power?

      @benhub Short answers, No, Yes, Yes

      The regulator will use power if connected.
      If your circuit is power hungry then removing the regulator will have limited effect.
      The sparkfun schematic on the article that you listed notes to disconnect the regulator for low power, so the advice is consistent.
      Unless you are using the genuine sparkfun versions of the pro-mini where the jumper can be cut then physically removing the regulator is recommended.
      0_1542936362010_Arduino-Pro-Mini-v14 regulator part.png

      posted in Hardware
      hard-shovel
      hard-shovel
    • RE: 💬 PogoPins

      I made a simple adapter for Pro Minis, Used on it own for new boards with connection holes
      0_1539605590332_Img_4455y.jpg

      If you slide on some dupont cable covers as a guide it makes it easy to program a soldered board
      0_1539605765924_Img_4456y.jpg

      0_1539605916766_Img_4462y.jpg

      0_1539606003550_Img_4457y.jpg

      posted in OpenHardware.io
      hard-shovel
      hard-shovel
    • RE: Water Sensor

      The Led is not actualy runing on AC. Part of the IC generates an low voltage AC signal (Nothing to do Mains Power) then other parts of the IC detect changes to this signal via the pair of diodes at the bottom, and then generate the two signals for the red and green leds.

      The bicolor color led has a common terminal in the center and the two outer pins control the two outer pins power the red and green leds.

      Utilizing a optocoupler has a safety advantage, as it isolates the power on the sensed unit from the mysensor node. It also allows systems using different control signal voltages to be interconnected.

      If you have the arduino analogue pin connected to Pin3, where do you have the arduino GND connected?

      As there is a relay that is connected in parallel to the the Upper LED drive transistor,
      I recommend using a optocoupler and resistor connected to the relay terminals shown, as these connections are easy to solder wires to.
      The resistor will need to be sized to match the voltage on the relay to limit current through the optocoupler led. 0_1516034196873_Electrolux Control Board 213.jpg

      posted in Hardware
      hard-shovel
      hard-shovel
    • RE: Water Sensor

      The TLP222A are opto-Mosfet devices so ideal for powering LEDs and small Relays etc as they have a 500mA rating, and the price listed is good value.

      However for your application, use the 4N35 that you already have.
      Your diagram is reversed as you need to drive the led in the optocoupler from the relay coil connections.

      Use the existing 10K as a pullup resistor at the input to the arduino,
      On the relay side use a series resistor R1 of about 1Kohm for 12Vdc (expected from a 9Vac supply).0_1516275929555_Water Sensor 213-B.jpg

      posted in Hardware
      hard-shovel
      hard-shovel
    • RE: With MySensors PC cold start!

      The pins on the sketch and the schematic do not match,
      You need to be more careful on matching the items as it will make troubleshooting more difficult.

      This sketch is a quick and dirty method, that does basically to work for me using OpenHAB as a controller. (only tested using LED outputs not with an actual computer).
      If i was actually going to implement this, I would monitor the POWER LED on the computer for feedback and control of the pulses. ie for shutdown, try short pulse first for controlled shutdown and if not shutdown within expected time span, then preform a hard shutdown.

      /*
       * PC Power On/Off & Reset Sketch
       *  Power Pin Pulse         = PC Starts if Already Off,     *** PC Shutsdown if already on   ## this is the operation of my Computer ##
       *  Power Pin 5 Seconds Low = PC Forced Shutdown
       *  Reset Pin Pulse Low     = PC Reset (if already on)
       *  
       *  Using three child IDs 
       *  1 = Power On/Off
       *  2 = Forced OFF
       *  3 = Reset
       *  
       *  Version 1.0 2018-01-19
       */
      
      /**
       * The MySensors Arduino library handles the wireless radio link and protocol
       * between your home built sensors/actuators and HA controller of choice.
       * The sensors forms a self healing radio network with optional repeaters. Each
       * repeater and gateway builds a routing tables in EEPROM which keeps track of the
       * network topology allowing messages to be routed to nodes.
       *
       * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
       * Copyright (C) 2013-2015 Sensnology AB
       * Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
       *
       * Documentation: http://www.mysensors.org
       * Support Forum: http://forum.mysensors.org
       *
       * This program is free software; you can redistribute it and/or
       * modify it under the terms of the GNU General Public License
       * version 2 as published by the Free Software Foundation.
       *
       *******************************
       *
       * REVISION HISTORY
       * Version 1.0 - Henrik Ekblad
       *
       * DESCRIPTION
       * Example sketch showing how to control physical relays.
       * This example will remember relay state after power failure.
       * http://www.mysensors.org/build/relay
       */
      
      
      // Enable debug prints to serial monitor
      #define MY_DEBUG
      
      //#define MY_NODE_ID AUTO
      #define MY_NODE_ID 155            // my test Node ID,  Comment out for Auto ID
      
      // Enable and select radio type attached
      #define MY_RADIO_NRF24
      //#define MY_RADIO_NRF5_ESB
      //#define MY_RADIO_RFM69
      //#define MY_RADIO_RFM95
      
      // Enable repeater functionality for this node
      #define MY_REPEATER_FEATURE   // if you need the repeater function uncomment
      
      #include <MySensors.h>
      
      // Wait times
      #define LONG_WAIT 500
      #define SHORT_WAIT 50
      #define PULSE_TIME 500UL      // half a second
      #define FORCED_TIME 5000UL    // 5 seconds
      boolean goPulse;
      unsigned long pulseStartTime;
      
      #define POWER_PIN   4         // Arduino Digital I/O pin number for PC Power control
      #define RESET_PIN   5         // Arduino Digital I/O pin number for PC Reset control
      
      #define RELAY_ON    1         // GPIO value to write to turn on attached relay
      #define RELAY_OFF   0         // GPIO value to write to turn off attached relay
      #define CHILD_ID_POWER       143        // these ID used for my test machine.   change to suit ie 1
      #define CHILD_ID_FORCEDOFF   144        // change to suit ie 2
      #define CHILD_ID_RESET       145        // change to suit ie 3
      boolean Status_Power      =  0;
      boolean Status_Forcedoff  =  0;
      boolean Status_Reset      =  0;
      boolean is_Power          =  0;
      boolean is_ForcedOff      =  0;
      boolean is_Reset          =  0;
      
      // Setup Messages
      MyMessage msg(CHILD_ID_POWER,V_STATUS);
      
      void before() {
        //  Set the pins to output mode
          pinMode(POWER_PIN, OUTPUT);
          pinMode(RESET_PIN, OUTPUT);
        //  Set the Pin states to known state
          digitalWrite(POWER_PIN, RELAY_OFF);
          digitalWrite(RESET_PIN, RELAY_OFF);
      }
      
      void setup() {
      
      }
      
      void presentation() {
          // Send the sketch version information to the gateway and Controller
          sendSketchInfo("Relay", "1.0");
          wait(LONG_WAIT);        // Give gateway time to Process
      // Present child ids to conroller
          present(CHILD_ID_POWER, S_BINARY, "PC Power on-off");
          wait(SHORT_WAIT);        // Give gateway time to Process
          present(CHILD_ID_FORCEDOFF, S_BINARY, "PC Forced off");
          wait(SHORT_WAIT);        // Give gateway time to Process
          present(CHILD_ID_RESET, S_BINARY, "PC Reset");
          wait(SHORT_WAIT);        // Give gateway time to Process  
      }
      
      
      void loop() {
      Serial.println();  
      Serial.print ("loop start ");
      
      
      send(msg.setSensor(CHILD_ID_POWER).set( Status_Power));
      send(msg.setSensor(CHILD_ID_FORCEDOFF).set( Status_Forcedoff));
      send(msg.setSensor(CHILD_ID_RESET).set( Status_Reset));
      wait(100000);        // wait for testing 
      }
      
      void receive(const MyMessage &message)
      {
          // We only expect one type of message from controller. But we better check anyway.
          if (message.type==V_STATUS) 
          switch (message.sensor) {
          case CHILD_ID_POWER:
            is_Power = message.getBool();
            Serial.print("incoming change for Power:");
            Serial.print(message.sensor);
            Serial.print(", New status: ");
            Serial.println((is_Power ? "On":"Off"));
            powercmd();        // process pulses etc in subroutine
            break;
          case CHILD_ID_FORCEDOFF:
            is_ForcedOff = message.getBool();
            Serial.print("incoming change for FORCED Power OFF:");
            Serial.print(message.sensor);
            Serial.print(", New status: ");
            Serial.println((is_ForcedOff ? "On":"Off"));
            forcedcmd();
            break;   
          case CHILD_ID_RESET :
            is_Reset = message.getBool();
            Serial.print("incoming change for Reset:");
            Serial.print(message.sensor);
            Serial.print(", New status: ");
            Serial.println((is_Reset ? "On":"Off"));
            resetcmd();
            break;
      
          default:
            Serial.print("Unknown/UnImplemented message type: ");
            Serial.println(message.type);
        }
      
      }
      
      
      
      void powercmd() {
        // process power pin 
        if (is_Power != Status_Power) {
          digitalWrite(POWER_PIN, RELAY_ON);
          delay(PULSE_TIME);          // delay used as pulse time is short & multiple processes are not expected
          digitalWrite(POWER_PIN, RELAY_OFF);
          Status_Power = is_Power;
        }
      }
      
      void forcedcmd() {
        // process forced power off command
          if (is_ForcedOff = 1 ) {
          digitalWrite(POWER_PIN, RELAY_ON);
          delay(FORCED_TIME);          // delay used as multiple processes are not expected, quick and dirty
          digitalWrite(POWER_PIN, RELAY_OFF);
          Status_Forcedoff = 0;          // reset status for next time
          Status_Power =  0;          // power status also reset if power shutoff
          }
      }
      
      void resetcmd() {
        // process reset command
        if (is_Reset != 1 ) {
          digitalWrite(RESET_PIN, RELAY_ON);
          delay(PULSE_TIME);          // delay used as multiple processes are not expected, quick and dirty
          digitalWrite(RESET_PIN, RELAY_OFF);
          Status_Reset = 0;
        }
      }
      
      
      posted in My Project
      hard-shovel
      hard-shovel
    • RE: Only a hard reset works.

      @robert the NUMBER_OF_RELAYS is already defined in your sketch, just use as pasted.

      I use OpenHAB so i just tried to install Dormotiz and was supreised that it took less than a an hour to install and get working with the relays. (Most of that time was trying to get them to shown up on the dashboard)

      Dormotiz is communication fine with my node and i can switch on and off the relays from the Dashboard

      0_1539548686702_Domoricz RS485 3.png

      In the sort time i have checked i do see that the Last Seen time only changes when i change the state of the relay.

      So your program that you posted works for me with both my normal OpenHAB and the new test Domoticz.

      I think that i may be miss understanding your actual problem.

      posted in General Discussion
      hard-shovel
      hard-shovel
    • RE: Combining DS18B20 and relay..

      @mela You are presenting the devices as Relay Child 1, and Temperature sensors as Child Ids 5 and 6.

      But when sending you are sending the temperatures as Child Ids 0 and 1

      Change the following send line

            // Send in the new temperature
            send(msg.setSensor(i).set(temperature,1));
      

      to

            // Send in the new temperature
            send(msg.setSensor(i+5).set(temperature,1));
      

      so the send function matches the presentation values.

      posted in Troubleshooting
      hard-shovel
      hard-shovel

    Latest posts made by hard-shovel

    • RE: Modifying A0 value to Percentage

      @mrhutchinsonmn

      try changing

       moistureLevels[i] = map(moistureLevel,0,650,0,99); // The maximum voltage output of the capacitive sensor is 3V, so since we're measuring 0-5v about 614 is the theoretical highest value we'll ever get.
      

      to

       moistureLevels[i] = map(moistureLevel,325,650,99,0); // The maximum voltage output of the capacitive sensor is 3V, so since we're measuring 0-5v about 614 is the theoretical highest value we'll ever get.
      
      posted in General Discussion
      hard-shovel
      hard-shovel
    • RE: Is V_RGB Supported in OpenHAB?

      Hi

      Openhab and the MySensors binding use the HSTtype format (hue, saturation, brightness) for color information.
      The binding automatically converts the HSBtype to the MySensors format of RRGGBB.
      So you need to use the HSBType fromRGB(int R, int G, int B) function

      items

      Color   Mock_RGB_LED     "Mock RGB LED (HSB)     "  (test254) { channel = "mysensors:rgbLight:gatewayWIFI3:Mock_RGB_LED:rgb" } 
      String  test_RGB_HexString "Test Color RGB hexS [0x%s]" (test254) 
      Number  test_RGB_Red	" Test Colour Red    [%s]"  (test254)
      Number  test_RGB_Green  " Test Colour Green  [%s]"  (test254)
      Number  test_RGB_Blue   " Test Colour Blue   [%s]"  (test254)
      

      Rules

      val String filename = "rgb-light.rules"
      
      rule "System startup"
              when
                      System started
              then
      /*Initial value of colors*/
          if (test_RGB_Red.state == NULL) test_RGB_Red.postUpdate(0)
      	if (test_RGB_Green.state == NULL) test_RGB_Green.postUpdate(0)
          if (test_RGB_Blue.state == NULL) test_RGB_Blue.postUpdate(0)
      end
      rule "Test Colour Channels RGB to Mysensors"
      when
      	Item test_RGB_Red   changed or
      	Item test_RGB_Green changed or
      	Item test_RGB_Blue  changed
      then
          val int r = (test_RGB_Red.state as Number).intValue
          val int g = (test_RGB_Green.state as Number).intValue
          val int b = (test_RGB_Blue.state as Number).intValue
          logInfo(filename, "Input Conversion: r:" + r + " g:" + g + " b:" + b)
         var HSBType hsb = HSBType.fromRGB(r, g, b)
          logInfo(filename, "Input Conversion: hsb" + hsb)	
          Mock_RGB_LED.sendCommand(hsb)
      end
      
      
      rule "RGB Hex -> HSB"
      when
          Item test_RGB_HexString received update
      then
          var rgb = test_RGB_HexString.state.toString
      
          var r = Integer::parseInt(rgb.substring(0, 2), 16)
          var g = Integer::parseInt(rgb.substring(2, 4), 16)
          var b = Integer::parseInt(rgb.substring(4, 6), 16)
      
          logInfo(filename, "Input Conversion: r" + r + " g" + g + " b" + b)
          var HSBType hsb = HSBType.fromRGB(r, g, b)
          logInfo(filename, "Input Conversion: hsb" + hsb)
          
          Mock_RGB_LED.sendCommand(hsb)	
      end
      
      /* I find this most useful for testing the node the Node */
      rule "Test Colour Channels RGB to Mysensors"
      when
          Item test_RGB_Red   changed or
          Item test_RGB_Green changed or
          Item test_RGB_Blue  changed
      then
          var int r = (test_RGB_Red.state as Number).intValue
          var int g = (test_RGB_Green.state as Number).intValue
          var int b = (test_RGB_Blue.state as Number).intValue
          logInfo(filename, "Input Conversion: r:" + r + " g:" + g + " b:" + b)
          var HSBType hsb = HSBType.fromRGB(r, g, b)
          logInfo(filename, "Input Conversion: hsb" + hsb)	
          Mock_RGB_LED.sendCommand(hsb)
      end	
      
      
      
      posted in OpenHAB
      hard-shovel
      hard-shovel
    • RE: OpenHAB MySensors binding 2.5: V_VAR1 and String values

      I have tried this on my test system and i get the same results as you using the VAR1 -- VAR5 with the cover (RollerShutter) thing.

      However if you add CustomSensor thing to your node then using the VAR1-VAR5 work as expected with the mapping. With numbers to and from the node.

      things

      cover    Mock_Cover        [nodeId=254, childId=6 ]
      text     Mock_info         [nodeId=254, childId=7 ]
      

      Items

      Rollershutter	Mock_Cover_State       "Mock Cover State       [%s]"   <rollershutter>     (test254) { channel = "mysensors:cover:gatewayWIFI3:Mock_Cover:cover" } 
      
      Number  Mock_Info_Var1			"Mock Info Variable 1 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" }
      String  Mock_Info_Var1s			"Mock Info Variable 1 (string) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" }
      Number  Mock_Info_Var1m			"Mock Info Variable 1 (number) [MAP(curtains.map):%s]"      (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" }
      String  Mock_Info_Var1sm        "Mock Info Variable 1 (string map) [%s]" (test254) { channel="mysensors:text:gatewayWIFI3:Mock_Info:var1" [profile="transform:MAP", function="curtains.map"]  } 
      Number  Mock_Info_Var2			"Mock Info Variable 2 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var2" }
      Number  Mock_Info_Var3			"Mock Info Variable 3 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var3" }
      Number  Mock_Info_Var4			"Mock Info Variable 4 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var4" }
      Number  Mock_Info_Var5			"Mock Info Variable 5 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var5" }
      

      Node

      #define CHILD_ID_COVER 6
      #define CHILD_ID_CUSTOM 7
      
      present(CHILD_ID_COVER, S_COVER, "Roller Shutters");
      present(CHILD_ID_CUSTOM, S_CUSTOM, "Reasons");
      

      Or you if you want to send strings you could use

      String  Mock_Info_Text			"Mock Info text sting [%s] "                                (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:text" }
      
      posted in OpenHAB
      hard-shovel
      hard-shovel
    • RE: OpenHAB MySensors binding 2.5: V_VAR1 and String values

      Just use the V_Var1-5 to send a number to the node ( saves bandwidth) and back then use the MAP transform function to shown the human readable strings.

      Make sure you have the Map Transformation installed in Transformations add-ons

      The add a mapping file in the transformation folder

      example file blinds.map

      NULL=unknown Reason
      -=unknown Reason
      0=initial
      1=Closed for Sunset
      2=Closed for Sun Protection
      3=Closed for Sleeping
      4=Closed for Alexa Command
      5=Closed for User Command
      6=Closed for Security
      7=Closed for Privacy
      8=Closed for Migraine
      9=Closed due to schedule
      10 = Closed due to riots
      
      33=Open for Sunrise
      34=Open Ended Sun Protection
      35=Open for Wakeup
      36=Open for Alexa Command
      37=Open for User Command
      38=Open for Security
      39=Open for No Privacy
      40=Open for end of Migraine 
      41=Open due to schedule
      
      initial = 0
      Closed for Sunset =1
      Closed for Sun Protection = 2
      Closed for Sleeping = 3
      Closed for Alexa Command = 4
      Closed for User Command = 5
      Closed for Securitry = 6
      Closed for Privacy = 7
      Closed for Migraine = 8
      Closed due to schedule = 9
      
      Open for Sunrise = 33
      Open Sun Protection Ended = 34
      Open for Wakeup = 35
      Open for Alexa Command = 36
      Open for User Command = 37
      Open for Securitry = 38
      Open for No Privacy = 39
      open end of Migraine = 40 
      open due to schedule = 41
      
      
      

      add the map transformation to item

      Sample Items

      // Blind Nodes 234,235,236
      Number Blinds1_Reason	 "Bedroom 1 Blinds  [MAP(blinds.map):%s]"  (blinds, test1)  { channel = "mysensors:customSensor:gatewayWIFI2:Blinds234:var1" }
      Number Blinds2_Reason	 "Bedroom 2 Blinds  [MAP(blinds.map):%s]"  (blinds, test1)  { channel = "mysensors:customSensor:gatewayWIFI2:Blinds235:var1" }
      Number Blinds3_Reason	 "Bedroom 3 Blinds  [MAP(blinds.map):%s]"  (blinds, test1)  { channel = "mysensors:customSensor:gatewayW5100:Blinds236:var1" }
      

      see https://www.openhab.org/addons/transformations/map/ for full details.

      posted in OpenHAB
      hard-shovel
      hard-shovel
    • RE: Sensor required to detect PVC insulated COPPER wire

      @yemesvee
      If using a digital sensor mounted as per Kimot diagram you will receive a pulse stream, check the width of the pulsed to find if mesh or cable.

      0_1546463575890_Img_4675x.jpg

      use the function pulseIn to determine the pulse width.

      
      
      The simple example of the time duration of a pulse
      
      int SensorPin = 3;
      unsigned long duration = 0;
      unsigned long CableDuration = 100;     // Set to suitable value
      unsigned long CableCount = 0;
      
      void setup()
      {
        pinMode(SensorPin , INPUT);
      }
      
      void loop()
      {
      
        duration = pulseIn(SensorPin , HIGH);
        Serial.print("Duration  : ");
        Serial.println(duration);
        if (duration >= CableDuration) {
          ++ CableCount;
          Serial.print("Cable detection  :");
          Serial.println(CableCount);
        }
      }
      
      
      
      posted in My Project
      hard-shovel
      hard-shovel
    • RE: Sensors error

      @ek-wik you are describing sensor repeatability,

      posted in General Discussion
      hard-shovel
      hard-shovel
    • RE: Multiple Dallas Temperatuur sensors at one sensor node

      @dzjr To get the extra resolution sent to the controller try using

        send(msg.setSensor(i+21).set(temperature,2));
      posted in Troubleshooting
      hard-shovel
      hard-shovel
    • RE: Sensor required to detect PVC insulated COPPER wire

      If the mesh moves at constant speed, How about a simple optical IR Sensor (break beam or Reflective), then checking pulse width of signal to detect mesh vs cable. Otherwise synchronize pulse width detection ratio in correlation to mesh speed.

      Similar to this
      0_1543047362376_IMG_4549.JPG

      posted in My Project
      hard-shovel
      hard-shovel
    • RE: Is it really required to remove the voltage regulator to save power?

      @benhub Short answers, No, Yes, Yes

      The regulator will use power if connected.
      If your circuit is power hungry then removing the regulator will have limited effect.
      The sparkfun schematic on the article that you listed notes to disconnect the regulator for low power, so the advice is consistent.
      Unless you are using the genuine sparkfun versions of the pro-mini where the jumper can be cut then physically removing the regulator is recommended.
      0_1542936362010_Arduino-Pro-Mini-v14 regulator part.png

      posted in Hardware
      hard-shovel
      hard-shovel
    • RE: Multiple Dallas Temperatuur sensors at one sensor node

      @dzjr you have the define

      #define TEMPERATURE_PRECISION 12
      

      In the github code this is not utilized, so the sensors are operating in 9 bit resolution.

      You need to add the following in the before or setup

      sensors.setResolution(TEMPERATURE_PRECISION);
      
      posted in Troubleshooting
      hard-shovel
      hard-shovel