x

.obsidian/workspace.json

@@ -13,12 +13,12 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "stockcropper/Motors.md",
+                "file": "AI - Barnes, Kempf.md",
                 "mode": "source",
                 "source": false
               },
               "icon": "lucide-file",
-              "title": "Motors"
+              "title": "AI - Barnes, Kempf"
             }
           }
         ]
@@ -165,6 +165,7 @@
   },
   "left-ribbon": {
     "hiddenItems": {
+      "table-editor-obsidian:Advanced Tables Toolbar": false,
       "bases:Create new base": false,
       "switcher:Open quick switcher": false,
       "graph:Open graph view": false,
@@ -177,11 +178,16 @@
   },
   "active": "c1cc7b2da22851f5",
   "lastOpenFiles": [
+    "Amazon Running Returns List.md",
+    "amazon returns running.md",
+    "09Oct2025.md",
+    "10Oct2025.md",
+    "08Oct2025 (conflicted copy 2025-10-08 100248).md",
+    "stockcropper/Motors.md",
     "stockcropper/1096-05.jpg",
     "08Oct2025.md",
     "Engineering Drawing Template.md",
     "Archive/Work Forum Outline - Thad's Side.md",
-    "Amazon Running Returns List.md",
     "Week of 05OCT2025.md",
     "Untitled 3.md",
     "Untitled 4.md",
@@ -199,12 +205,8 @@
     "stockcropper/SC Design 26AUG2025.md",
     "saturda.md",
     "Meal Prep.md",
-    "Archive/Fix your smell.md",
     "274663921659.jpeg",
-    "AI - Barnes, Kempf.md",
     "274039228009.jpeg",
-    "Archive/20AUG2025.md",
-    "Archive/07OCT2025.md",
     "274039825309.jpeg",
     "Untitled 3",
     "Untitled 2",
@@ -218,7 +220,6 @@
     "THF/51utv4Pw0sL._SL1100_.jpg",
     "THF/control-systems-CON.1609.WP.3.jpg",
     "THF/s-l400.jpg",
-    "THF/Pasted image 20241130114206.png",
     "Farm Planning/ZHTInstall.pdf",
     "Archive/Business Ideas/Weather Log Concept 1.pdf",
     "Stock Cropper",

Stock Cropper/433MHz.md

@@ -1,122 +0,0 @@
-
-Sketch:
-
-```
-// Arduino script using RCSwitch library to decode EV1527 OOK signals on pin 2
-
-  
-
-#include <RCSwitch.h>
-
-  
-
-RCSwitch mySwitch = RCSwitch();
-
-  
-
-void setup() {
-
-  Serial.begin(115200);  // Serial output at 115200 baud for clarity
-
-  while(!Serial);
-
-  mySwitch.enableReceive(0);  // Receiver on interrupt 0 => pin 2
-
-  Serial.println("Ready to receive EV1527 signals...");
-
-}
-
-  
-
-void loop() {
-
-  if (mySwitch.available()) {
-
-    if (mySwitch.getReceivedBitlength() == 24) {  // Filter for EV1527's 24-bit messages
-
-      unsigned long value = mySwitch.getReceivedValue();
-
-      Serial.print("Received EV1527 packet: ");
-
-      Serial.print(value);  // Decimal value
-
-      Serial.print(" (Hex: ");
-
-      if (value < 0x100000) Serial.print("0");  // Pad for consistent hex output
-
-      Serial.print(value, HEX);
-
-      Serial.print(")");
-
-      Serial.print(" / ");
-
-      Serial.print(mySwitch.getReceivedBitlength());
-
-      Serial.print(" bits / Pulse length: ");
-
-      Serial.print(mySwitch.getReceivedDelay());  // Typical: ~275-350 µs
-
-      Serial.print(" µs / Protocol: ");
-
-      Serial.println(mySwitch.getReceivedProtocol());  // Should be 6 for EV1527
-
-      delay(500);  // Delay to prevent flooding from repeated transmissions
-
-    }
-
-    mySwitch.resetAvailable();
-
-  }
-
-}
-```
-
-output:
-
-```
-08:53:19.607 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:53:21.379 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 354 µs / Protocol: 1
-08:53:24.444 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:53:25.552 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 349 µs / Protocol: 1
-08:53:26.427 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 353 µs / Protocol: 1
-08:53:27.054 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 353 µs / Protocol: 1
-08:53:27.733 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:53:28.490 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 352 µs / Protocol: 1
-08:53:30.107 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:53:30.966 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 352 µs / Protocol: 1
-08:53:32.402 -> Received EV1527 packet: 6098020 (Hex: 5D0C64) / 24 bits / Pulse length: 352 µs / Protocol: 1
-08:53:34.361 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:53:34.915 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 353 µs / Protocol: 1
-08:53:35.526 -> Received EV1527 packet: 6098020 (Hex: 5D0C64) / 24 bits / Pulse length: 355 µs / Protocol: 1
-08:53:36.400 -> Received EV1527 packet: 6098024 (Hex: 5D0C68) / 24 bits / Pulse length: 352 µs / Protocol: 1
-08:53:49.512 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 352 µs / Protocol: 1
-08:53:51.189 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 354 µs / Protocol: 1
-08:53:52.344 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:53:53.030 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 352 µs / Protocol: 1
-08:53:53.549 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 354 µs / Protocol: 1
-08:53:54.431 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:53:55.606 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 352 µs / Protocol: 1
-08:53:56.782 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 353 µs / Protocol: 1
-08:53:57.801 -> Received EV1527 packet: 6098018 (Hex: 5D0C62) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:54:05.964 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 353 µs / Protocol: 1
-08:54:06.525 -> Received EV1527 packet: 6098017 (Hex: 5D0C61) / 24 bits / Pulse length: 349 µs / Protocol: 1
-08:54:08.224 -> Received EV1527 packet: 6098020 (Hex: 5D0C64) / 24 bits / Pulse length: 350 µs / Protocol: 1
-08:54:08.917 -> Received EV1527 packet: 6098020 (Hex: 5D0C64) / 24 bits / Pulse length: 351 µs / Protocol: 1
-08:54:09.780 -> Received EV1527 packet: 6098024 (Hex: 5D0C68) / 24 bits / Pulse length: 350 µs / Protocol: 1
-08:54:10.516 -> Received EV1527 packet: 6098024 (Hex: 5D0C68) / 24 bits / Pulse length: 351 µs / Protocol: 1
-```
-
-Analysis:
-- button 1: 5D0C61
-- button 2: 5D0C62
-- button 3: 5D0C64
-- button 4: 5D0C68
-
-
-https://www.amazon.com/QIACHIP-Wireless-Receiver-Long-Distance-Transmitter/dp/B09P89RF8R:
-![[Pasted image 20250926101243.png]]
-
-https://www.adafruit.com/product/1096:
-![[1096-05.jpg]]
-
-Gama electronics could be useful

Stock Cropper/Gearboxes.md

@@ -1,7 +0,0 @@
-RV Gearbox: https://www.youtube.com/watch?v=IKkw4d7jyu0
-
-The thing that's in winches is called a Wolfrom drive: https://mevirtuoso.com/wolfrom-3k-planetary-drive/  ... or, well, it's really close to that 
-
-Guy on reddit calls them "split ring plantery gearbox" : https://www.reddit.com/r/robotics/comments/11pbxha/split_ring_planetary_gearbox_2nd_iteration/
-
-https://www.youtube.com/watch?v=Z0rGd7UO2Tk

Stock Cropper/Motors.md

@@ -1,28 +0,0 @@
-# Motor options
-
-C800: *it's just too weak.*
-Winches: *not robust, needs retrofit.*
-Tarping motors: *do they have the longevity? also, pretty oversized.*
-Brushless motors: *now we're talking, except, y'know, you need an ESC.*
-Semi-custom gearmotor: *this is probably the way. talk to bison.*
-
-# How do to clutching?
-- Built-in clutch on winch: *slick, but can you get it?*
-- Just don't: *too much resistance methinks, but...*
-- Quick pins on the wheel: *this is annoying to futz with*
-- Pin drive on a sprocket: *could be annoying to have pop back in place... unless, you make it dig-in-able? would this need to be unenclosed?*
-- Face spline hub on wheels: *that's a lot of torque and weirdness?*
-- Detension a belt: *Will the belt be strong enough?*
-- Centrifugal clutch: *but don't you want a built in parking brake?*
-- 
-
-
-# Lead screw sizing
-https://www.tolomatic.com/info-center/resource-details/truth-about-actuator-life-screw-drive-survival/
-
-
-I think that the motor is a bigger lift than I realized.
-Wonder if it needs to be jacked up/down in actuality
-Probably does still but...
-
-

Stock Cropper/SC Electronics Architecture.md

@@ -1,129 +0,0 @@
-1. MCU
-
-Looks like the **ESP32-WROOM-32** will work swimmingly. Pinout is as follows:
-
-| Peripheral       | Pin Assignment | GPIO Number | Notes/Functions                      |
-| ---------------- | -------------- | ----------- | ------------------------------------ |
-| Analog Input 1   | SENSOR_VP      | 36          | ADC1_CH0, input-only                 |
-| Analog Input 2   | SENSOR_CAPP    | 37          | ADC1_CH1, input-only                 |
-| Analog Input 3   | SENSOR_CAPN    | 38          | ADC1_CH2, input-only                 |
-| Analog Input 4   | SENSOR_VN      | 39          | ADC1_CH3, input-only                 |
-| Digital Output 1 | IO25           | 25          | General I/O, output-capable          |
-| Digital Output 2 | IO26           | 26          | General I/O, output-capable          |
-| Digital Output 3 | IO27           | 27          | General I/O, output-capable          |
-| Digital Output 4 | MTCK/IO13      | 13          | General I/O, output-capable          |
-| Digital Output 5 | MTMS/IO14      | 14          | General I/O, output-capable          |
-| Digital Output 6 | MTDO/IO15      | 15          | General I/O, output-capable          |
-| Digital Input 1  | VDET_1         | 34          | General input, input-only            |
-| Digital Input 2  | VDET_2         | 35          | General input, input-only            |
-| I2C SDA          | IO21           | 21          | I2C data, configurable               |
-| I2C SCL          | IO22           | 22          | I2C clock, configurable              |
-| CAN TX           | IO4            | 4           | TWAI TX, connects to transceiver TXD |
-| CAN RX           | IO5            | 5           | TWAI RX, connects to transceiver RXD |
-| RTC Crystal XP   | 32K_XP         | 32          | 32.768 kHz crystal for RTC           |
-| RTC Crystal XN   | 32K_XN         | 33          | 32.768 kHz crystal for RTC           |
-
-GPIO0, 2, 12, 16, 17, 18, 19, 23 are available for future expansion.
-
-2. CAN Bus
-	1. Just need a 3.3V CAN Transceiver - **SN65HVD231DR** 
-	2. Connector - M12 bulkhead? BoardLock bulkhead?
-		1. https://www.digikey.com/en/products/filter/circular-connectors/circular-connector-assemblies/436?s=N4IgjCBcoGwJxVAYygMwIYBsDOBTANCAPZQDaIAzABwUDscMIh1dcEAuoQA4AuUIAZR4AnAJYA7AOYgAvoXi1EIFJAw4CxMpQCscOFUXNdegCxMdeveYowADLe1Vrd2zAjMXMAEzP7MRh62YGBOgWBe7pR24WZhdL5g2toJdr5etoZRtukI8tq0XibJnCC8-EJiUrKEALQ%2B0MpQIgCuGiSQ5MUyciCMDaIAJvw1YEHmZZAg5jwAnly4-OjYKN1AA
-		2. T4140012081-000 $13.09
-		3. RTS712ND4S03 $15.97
-		4. https://www.digikey.com/en/products/filter/circular-connector-assemblies/436?s=N4IgjCBcoGwJxVAYygMwIYBsDOBTANCAPZQDaIAzABwUDscMIhALGGFXLSALqEAOAFyggAygIBOASwB2AcxABfQgFpmiECkgYcBEADdpaLHkIlI5GOwo9%2BQyCEUqATOs0SArrrPkArDwVKIIzQIJIAJsLKYAAMELbCTCACAJ58uMLo2CgBQA
-		5. 54-00216 $4.80 (4p male)
-		6. 54-00235 $5.05 (4p female)
-		7. I think we're gonna end up at M12 connectors for sensors and flying pigtails for motors
-
-3. Voltage Regulator
-	1. Most of the time will be spent sleeping. A low quiescent current, then, is actually more important than live current, perhaps?
-	2. **TLV1117-33IDCYR** would work but emits 4.35W at 500mA - thermals need looked into for this.
-	3. **TPS629210DRLR** is also good. Just need 2 resistors and an inductor as well. Good cost. Probably better.
-		1. 4.7 uF input cap
-		2. 22 uF output cap
-		3. 2.2 uH inductor - **BDCD002520122R2MS1** (1008 case)
-
-4. RTC (use builtin to MCU)
-	1. Need ext. osc: **CM315D32768DZFT** (2-SMD package)
-
-5. Jack Motor  - 1 AI, 2 DO
-	1. Motor:  **RP-785615**
-	2. Motor connector:  **AT06-2S**
-	3. Motor to cable connector:  **AT04-2P**
-	4. Cable: **16/2 PVC jacket cable**
-	5. Cable to Control Box: **PG9 Cord Grip + Faston Tabs**
-	6. Relays (2):  **A161CS12VDC.64** (25A current, 53.3 mA coil)
-	7. Relay driver: **2N7002AK-Q** (240 mA max) (TO-236AB, TO-236-3, SC-59, SOT-23-3 package)
-	8. Fuse:  **20A ATO fuse**
-	9. Current sensor: **ACS37042KLHBLT-030B3** (30A max, -030B5 exists which is a 5v variant)
-
-6. Fluffer (Accessory) Motor   - 1 AI, 2 DO
-	1. Motor:  *TBD*
-	2. Motor connector:  **AT06-2S**
-	3. Motor to cable connector:  **AT04-2P**
-	4. Cable: **16/2 PVC jacket cable**
-	5. Cable to Control Box: **PG9 Cord Grip + Faston Tabs** ([1217861-1](https://www.digikey.com/en/products/detail/te-connectivity-amp-connectors/1217861-1/1148769))
-	6. Relays (2):  **A161CS12VDC.64** (25A current, 53.3 mA coil)
-	7. Relay driver: **2N7002AK-Q** (240 mA max)
-	8. Fuse:  **20A ATO fuse** (3522-2 holder)
-	9. Current sensor: **ACS37042KLHBLT-030B3** (30A max, -030B5 exists which is a 5v variant) (SOT-23W)
-
-7. Drive Motor - 1 AI, 2 DO 
-	1. Motor:  **80ZYT-12/JW-7** -OR-  **80ZYT-12/JW-3B** (50A)
-	2. Motor connector:  **6mm Ring Terminals with Boots**
-	3. Cable: **12/2 PVC jacket cable**  
-	4. Cable to Control Box:  **PG9 Cord Grip + Faston Tabs**
-	5. Relays (2):  **A31CSP12VDC2** (70A current, 150 mA coil)
-	6. Relay driver: **2N7002AK-Q** (240 mA max)
-	7. Fuse:  No fuse, just the fuse/breaker for the main battery
-	8. Current sensor: **ACS37220LEZATR-100B3** (100A max, -100B5 exists which is a 5v variant) (7-PowerLQFN / 7-QFN)
-
-8. Jack Limit Switch  - 1 DI
-	1. Sensor:  **PBM6-AN-1H** (-1A exists also which is a 2m pigtail. -1H is a M12 connector)
-
-9. Odometry Geartooth Sensor - 1 DI
-	1. Sensor:  **PBM6-AN-1H** (-1A exists also which is a 2m pigtail. -1H is a M12 connector)
-
-10. Solar Charging Circuit
-	1. **BQ24650 charge controller**  
-	2. N-channel MOSFETs (Q1 high-side, Q2 low-side): 40V-rated, low RDS(on) (e.g., 20mΩ), such as **AO3400** or equivalent, for synchronous rectification.  
-	3. Inductor (L): 10µH, rated for at least 5A saturation current (e.g., Wurth **7447788220**) to support switching at 400kHz.  
-	4. Current sense resistor (R\_SR): 10mΩ, 1% tolerance, 5W rating (e.g., **WSMS5515L1000FEK**) for \~4A maximum charge current (differential voltage of 40mV).  
-	5. Input capacitors: 10µF ceramic (X7R, 35V) × 3, placed near MOSFETs.  
-	6. Output capacitors: 4.7µF ceramic (X7R, 25V) × 2, near the battery connection.  
-	7. Schottky diodes: For reverse protection (e.g., **1N5819**) and status indication.  
-	8. Resistors for voltage setting: Precision 1% types (e.g., R1 \= 100kΩ, R2 \= 576kΩ for 14.4V regulation).  
-	9. Optional: LEDs and resistors for charge status (e.g., bulk/absorption indication).
-
-11. Battery - 1 AI
-	1. Battery: **TL1212**
-	2. Battery to cable conn: **Female Fastons**
-	3. Cable: **12/2 PVC jacket cable with fuseholder**
-	4. Cable to control box: **PG9 Cord Grip + Faston Tabs**
-	5. Voltage divider to sense battery voltage (goes to ESP32) - **1M + 150k resistors**
-
-12. Display
-	1. Focus LCDs **C162A-FTW-DS23** (-30 to +80C operating range)
-	2. This will be driven by an I/O Expander. It could be shared with the buttons.
-		1. 8 bit: **PCF8574**
-		2. 16 bit: **MCP23017** - pin 7 of each 8-bit bank can only be used as an output which is odd. or PCF8575 which is a little more $. Or best yet TCA9555PWR
-
-13. Settings Adjust Buttons (4 buttons)
-	1. Option (SMD): **TL3305BF260QG**
-	2. Option (THT): **TS02-66-43-BK-260-SCR-D**
-
-14. Manual Override Buttons (4 buttons)
-    1. Option A: Hardwired, with an enclosed PCB
-    2. Option B: Hardwired, with simple waterproof switches
-    3. Option C: Remote
-
-
-| Pros of Remote                       | Pros of Hardwire                           |
-| ------------------------------------ | ------------------------------------------ |
-| Can operate from all around the coop | Can't lose it                              |
-| Easiest cable management             | Easy to repair                             |
-|                                      | No pairing required                        |
-|                                      | Easy interrupt (wake from sleep)           |
-|                                      | If you need to make it custom, it's easier |
-|                                      | No batteries to die                        |

Stock Cropper/SC-SOPS.md

@@ -1,122 +0,0 @@
----
-Revision Date: 07OCT2025
-Approved By: TJH
----
-	Rules are for the adherence of fools and the guidance of wise men.
-	- Douglas Bader
-
-Often documents like these are very formal and militaristic. We ought to adhere to this document. However, we will not let it hamstring us. If there are things that it doesn't allow us to do, and we need to do them, we will revise this document wisely. We will not simply deviate from this document without addressing the problem with the process that led us to the deviation. It's OK to do things that deviate from this document for a while and see how they go. It's not OK to put anything into production or push to `main` without first discussing those changes and incorporating them into this document.
-
-# Component Types and Numbering
-
-Components are given unique numbers. Why numbers? Numbers are cheap, succinct, clean, and consistent. The descriptions of parts may change over time, but the number stays the same.
-
-## Parts (SC-xxxx)
-Parts are individual items that aren't meant to be broken down further. Parts may be assembled (or even permanently assembled). This includes both custom and off the shelf components. 
-
-Parts are numbered: `SC-xxxx`
-
-Parts have these files associated with them:
-
-| File Type                  | Extension | Notes                                                                                   |
-| -------------------------- | --------- | --------------------------------------------------------------------------------------- |
-| SOLIDWORKS Model           | .sldprt   | Master CAD file - for 3D geometry                                                       |
-| SOLIDWORKS Drawing         | .slddrw   | Master Drawing file - contains all other information such as material, tolerances, etc. |
-| STEP Model                 | .step     | (exported, do not edit)                                                                 |
-| Drawing                    | .pdf      | (exported, do not edit)                                                                 |
-| Sheetmetal File (Optional) | .dxf      | (exported, do not edit)                                                                 |
-| STL Model (Optional)       | .stl      | (exported, do not edit)                                                                 |
-
-## Assemblies (SC-Axxx)
-Assemblies are a collection of parts that are meant to be installed together. 
-
-Assemblies are numbered: `SC-Axxx`
-
-Assemblies have these files associated with them:
-
-| File Type          | Extension | Notes                                                                                   |
-| ------------------ | --------- | --------------------------------------------------------------------------------------- |
-| SOLIDWORKS Model   | `.sldasm` | Master CAD file - for 3D geometry                                                       |
-| SOLIDWORKS Drawing | `.slddrw` | Master Drawing file - contains all other information such as material, tolerances, etc. |
-| STEP Model         | `.step`   | (exported, do not edit)                                                                 |
-| Drawing            | `.pdf`    | (exported, do not edit)                                                                 |
-
-## Harnesses (SC-Hxxx)
-
-Harnesses are wires, cables, and electrical connectors that are assembled together.
-
-Harnesses are numbered: `SC-Hxxx`
-
-Harnesses generally have these files associated with them:
-
-| File Type                     | Extension | Notes                                                                   |
-| ----------------------------- | --------- | ----------------------------------------------------------------------- |
-| SOLIDWORKS Model (optional)   | `.sldasm` | Usually a geometric representation. Not at all for production purposes. |
-| SOLIDWORKS Drawing (optional) | `.slddrw` |                                                                         |
-| WireViz Model                 | `.yml`    | A harness described in markup language                                  |
-| STEP Model (optional)         | `.step`   | (exported, do not edit)                                                 |
-| Drawing                       | `.pdf`    | (exported, do not edit)                                                 |
-
-%% TODO: figure this one out a lot more %%
-## Boards (SC-Bxxx)
-Boards are assemblies of electrical components that have been soldered together. They have a single custom PCB and several individual subcomponents that may have designators such as `C1`, `J_FTDI1`.
-
-Board design is in the form of a KiCAD project (which contains multiple files).
-
-Boards are numbered: `SC-Bxxx`
-
-%% TODO: put more detail on the particular files... especially BOMs %%
-## Weldments (SC-Wxxx)
-Weldments are a collection of parts that are welded together. Weldments consist of several parts.
-
-Weldments are numbered: `SC-Wxxx`
-
-Weldments have these files associated with them:
-
-| File Type          | Extension | Notes                                                                                   |
-| ------------------ | --------- | --------------------------------------------------------------------------------------- |
-| SOLIDWORKS Model   | .sldasm   | Master CAD file - for 3D geometry                                                       |
-| SOLIDWORKS Drawing | .slddrw   | Master Drawing file - contains all other information such as material, tolerances, etc. |
-| STEP Model         | .step     | (exported, do not edit)                                                                 |
-| Drawing            | .pdf      | (exported, do not edit)                                                                 |
-## Programs (SC-Pxxx)
-Programs are software that runs on hardware. They are numbered, but may only be numbered on a folder basis. Any built binaries are definitely numbered. This is pretty easy to deal with.
-# Revisions and Releasing Files
-The above are "base" filenames. These are the filenames one would use for the active project. However, at certain points, we will want to make releases for these files. Files associated with a particular release should have suffixes -Vx. Versions are cheap. Both the "source" files (such as SOLIDWORKS models and drawings) and "compiled" files (such as STEP models, PDFs) should be included.
-
-For example, when you are done with a part SC-0001 and wish to create a version V2, you should create these files (assuming SC-0001 was drawn in SOLIDWORKS):
-- `SC-0001-V1.sldprt`
-- `SC-0001-V1.slddrw`
-- `SC-0001-V1.step`
-- `SC-0001-V1.pdf`
-
-All of these files should then be put in the `released` folder.
-
-You should also then update the `SC-PARTNUMBERS.ods` spreadsheet.
-
-One may quickly notice that these are, thusly, "dependencies". Say that SC-A001 contains SC-0002 and SC-0003. If one updates SC-0002, SC-A001 should be revision-bumped.
-
-We will keep this a "should" for now and create tools that will help identify when this goes wrong.
-
-## SOLIDWORKS Part Files
-Everything but the `.stl` export is handled by the export tool. Make sure that you have all assemblies / parts referencing the part closed before running the export tool.
-- Save the `.sldprt`.
-- Save the `.slddrw`.
-- Save the `.sldprt` to a `.step` file, version AP242.
-- Save the `.slddrw` to a `.pdf` file.
-- If the part is sheet metal/plastic, save the flat pattern (including any bend lines) to a `.dxf`.
-- If the part is to be printed, save the model to a `.stl`.
-- Update the version in `SC-PARTNUMBERS.ods` and ensure the component description matches the drawing.
-- Move old version files to the `archive` folder, if applicable.
-
-## SOLIDWORKS Assembly Files
-Make sure that you have all assemblies / parts referencing the part closed before running the export tool.
-- Save the `.sldasm`.
-- Save the `.slddrw`.
-- Save the `.sldasm` to a `.step` file, version AP242.
-- Save the `.slddrw` to a `.pdf` file.
-- Update the version in `SC-PARTNUMBERS.ods` and ensure the component description matches the drawing.
-- Move old version files to the `archive` folder, if applicable.
-
-## KiCAD Files
-Everything but the `.stl` export is handled by the export tool. Make sure that you have all asse

Stock Cropper/Solar Charger/Solar Sailer.md

@@ -1,68 +0,0 @@
-E = 1/2 C V^2
-
-10x 2.7V 500F capacitors
-35 x 60mm
-500F:
--> E(14V) = 36 kJ
--> E(10V) = 25 kJ
--> E(14-10V) = 11 kJ
-
-
-
-
-16 x 27 mm
-
-
-12V x 20A = 240 W
-say a 4 second tug
-that's 1 kJ
-E = 1/2 C (Vf^2 - Vi^2)
-C = 2 E / (Vf^2 - Vi^2) = `2 * 1k / (14^2-10^2)` = 20 F
-So we're talking super-cap range
-
-A 9ah battery is like $22
-
-https://www.digikey.com/en/products/detail/abracon-llc/AHCR-S04R0SA227Q/23018981
-$7.20
-220F - max storage is 1.76 kJ
-
-https://www.digikey.com/en/products/detail/abracon-llc/AHCR-S04R0SA127Q/23018999
-$5.17
-100F - max storage is .80 kJ
-
-oh but these all have peak currents of like 10A
-and what do you do after dark
-and on and on
-
-just put a damn battery on it and move on to the next problem
-
-
-
-PWM vs MPPT chargers
-- MPPT are up to 30% more efficient, especially in lower light
-- PWM are simpler
-- Both need a microcontroller I guess
-
-
-https://www.instructables.com/DIY-1kW-MPPT-Solar-Charge-Controller/
-https://github.com/opensolarproject/OSPController/wiki
-https://www.arduined.eu/arduino-solar-charge-controller/
-https://hackaday.io/project/159708-arduino-pwm-solar-charge-controller
-http://www.andrewwhyman.com/blog/electronics/arduino-pwm-charge-controller/
-https://web.archive.org/web/20161023034412/http://256.uk/?page_id=23
-![[MPPTschematic.jpg]]
-
-https://www.solorb.com/elect/solarcirc/scc3/index.html
-
-
-how to drive an IRF4905 - should be able to replace BC337 with 2N3904 (but how are those BJTs not a short?)
-https://forum.arduino.cc/t/automotive-pwm-control-of-p-channel-mosfet-irf4905-as-high-side-switch/434372/93
-![[a5f9f8ce1c919c81156c09ffb5a3e5eed443ef58.gif]]
-
-
-https://www.instructables.com/ARDUINO-SOLAR-CHARGE-CONTROLLER-Version-20/
-
-
-https://github.com/gameinstance/switcharger
-
-![[getnt29x2jjg7gb9.png]]

Stock Cropper/StockCropper Development Pitch.md

@@ -1,128 +0,0 @@
-Priorities
-
-# #1: Femto (DIY kit)
-
-## + Features
-- Bolt-on module to a DIY barn/pen; will support salatin-style tractors
-- Automation that's fit for leaving for a weekend
-- Mounting for water tank (as ballast)
-
-## ? How
-- Basic automation of movement
-	- Timer-based?
-	- Odometry?
-- Basic automation of steering
-	- Set-it-and-forget-it ...
-	- "Manual vision" (networked camera for aiming, manually pick a target)
-	- Coulters?
-	- Corn/row crop feelers?
-- Mounting for water
-- Solar panel, charger, onboard battery
-- Pushbutton / LCD interface on-device
-- Slow-mode manual vision
-
-## - Probable Limitations
-- No auto-turn-around
-
-## ! Problems
-- Balance of the barn
-- Front-end 'mow through' ability
-- 
-
-## Development path
-- Majorly refine steering system - $2000 of materials, ??? time
-	- Motors / electric actuators - $1000
-	- Frame - $500
-- Solidify drive system - $2000 of materials, ??? time
-- Spec motors and jack and get suppliers - $2000 of materials, ??? time
-- Develop electronics - $2000 of materials, ??? time
-- App development
-- Handoff to electronics CMs
-- Handoff to hardware CMs
-- Find beta-test farmers
-
-8hr sit down and make the perfect design from scratch
-16hr find the best components
-8hr dfm that shit and make drawings
-16hr build the thing, $1000 of materials
-2hr install that shit
-
--> 1st prototype in 50hr + $1k
-
-5hr go back to the drawing board again and fix it
-5hr dfm the hell out of it
-16hr build the thing again
-
--> 2nd prototype in 24hr + $600
-
-16hr design the awesome control board bang it out in kicad
-5hr agonize over the control box
-8hr build it all
-
--> 1st electrical prototype in 30hr + $500
-
-
-
-
-# #2: Pico (Chickens only)
-
-### + Features
-- Same drive module as the Femto
-- Really nice robust chicken tractor
-
-### Development path
-- All the stuff in femto plus:
-- Develop electronics
-- Redesign frame with cost-down in mind
-- 
-
-# #3: Nano (Small multispecies for intercropping)
-
-### + Features
-- Metal barn
-- Pigs on slats
-- Sheep in front
-- Chickens in back
-- Interfaces with standard panels so you can add width
-- 4WD platform. Keep weight on the drive tires.
-
-### Development path
-- 
-
-# Steering
-Ways to do steering:
-- Vision: drive towards a flag / pole
-- Vision: drive towards ground markers
-- Vision: drive along a painted line
-- Vision: drive along a mowed path *so much SWE effort...*
-- "Corn head" feelers (can this work in a broadacre setup somehow?)
-- Taut tether
-- Wheel encoder feedback
-- Dig a trench
-- TOF Triangulation
-- GPS / RTK *can you set up your own RTK base station? Probably. *
-- Follow a buried wire
-- Coulters / stabilizer wheels
-- Coulters *with pressure sensors*
-- Ridge-till
-
-https://www.youtube.com/watch?v=d0lvag00HYY
-
-Remember you're only using steering a small portion of the time. You *could* use a floodlight in conjunction with retroreflective tape.
-
-This should be non-obnoxious though.
-# Telemetry
-- Why have telemetry? Lets you know if the barn is stuck. Lets you force a move. Maybe you want cameras?
-- Need long range, but not a lot of bandwidth (unless you want video)
-- WiFi isn't the right solution for this, LoRa is
-- Have a LoRa base-station in your office/shed... this could be an internet gateway or a PC-link...
-# Hold the presses. Stop it all. Everything.
-
-Make a walker.
-
-Lots of advantages. So many
-Big problem is how do you turnaround / tow it
-And maybe the answer there is "tow it" for the farmer but not for the homesteader
-_omnidirectional walking mechanism?_
-
-hey lol remember the _screw drive?_ The one Fordson made. Maybe for the nano

Stock Cropper/Walkers.md

@@ -1,8 +0,0 @@
-https://www.diywalkers.com/walker-abcs.html
-![[strider-linkage-with-and-without-toes-15_orig.gif]]![[4-bar-biped_orig.gif]]
-
-Can you put a walker on each side of a 16x16 pen?
-Or do you steer the walker?
-Oooh fun idea: multidimensional walker. When the foot is down, linear actuator pushes sideways so you can change course by nudging
-
-This is really a simple mechanism that does what you want, right? http://www.moltensteelman.com/thewalkingbeast.html

Stock Cropper/stockcropper.md

@@ -1,65 +0,0 @@
-# Stock Cropper Stream-of-Consciousness
-
-## Should I partner with Zach?
-## Is Zach the right person to partner with?
-## What is the vision, in terms of:
-### Finances, stake, shares, etc.?
-### Geography
-### Timeline / time-to-market
-
-
-## Is this even the right path to go down?
-
-# What are the facts?
-
-- Went to ACRES Field day
-- Met with the Stock Cropper guy
-- He's been in a bind, his manufacturing partner backed out, so he's looking for engineering support. He's not an engineer.
-- I've seen his idea and it really does look interesting, it allows for pasturing at a small scale and leveraging edge-effect on corn
-- But his engineering partner has taken him for a ride, frankly.
-- He and I talked and we see the same sort of thing: need to scale back the tech, lean it up
-- We aren't eye-to-eye on how much of a "finished polished bulletproof product" that needs to be offerred but there is room to align this
-- I think he gives a steadier hand and brings some branding/sales/networking to the table that I would desperately need
-- I bring the ability to technically drive the product to be what it needs to be
-- Still need to find manufacturing partners, but it's going to be leaner if the design is at least under the same roof
-- We will be calling and revisting sometime Friday.
-- Jason Mauck, host of the field day, wanted to call and catch up with something. I don't know what this is in regards to exactly, but he might be trying to get a company going to build equipment for his relay cropping.
-
-In parallel
-- On Saturday and Sunday I woke up with this nagging thought that the engineering is getting in the way of me farming.
-- Monday that wasn't there, I was just up and got going
-- Tuesday I awoke with a weird thought that I actually can't recall. It was something to do with perfectionism or something.
-
-- Sunday, talked with Jonathan about it. Got some good things to think about as to what questions I should be asking.
-- I also mentioned the sensation on Sat/Sun.
-- Independently he brought up religious life. Mentioned that I have thought about it. And I was going to visit a few monasteries this summer in KS/OK. Mentioned my reservations - mostly that there's just this disconnect from work.
-
-# So what am I pondering?
-
-0. What path do I need to take?
-
-To answer this -
-1. Where do I focus my energies and limited time?
-2. What questions do I need to be asking?
-3. What am I not seeing?
-
-# Questions to ask Zach
-- Financial
-	- Is there buy-in?
-	- Is there room to be paid?
-	- Have you worked out price points?
-	- Right now all you have is a waitlist... no deposits or any actual $$$ ?
-- Timeline
-	- Is this full time?
-	- Do I need to move?
-- Ethos
-	- FOSH?
-	- Are you Christian? What is your core north star?
-	- How are you vetting investors, how much say do they have?
-- Skillset / bring to the table?
-	- It sounds like you have sales experience...
-
-# Jordan
-"It has very little to do with my abilities or what I accomplish... it has more to do with will and grace"
-"The acts that I assent to are actually God's acts..."
-

amazon returns running.md

@@ -1,2 +0,0 @@
-![[274039228009.jpeg]]
-