221–230 of 814 posts
The HN crowd would enjoy the Global Village Construction Kit's work on an open-source tractor
https://www.opensourceecology.org/gvcs/
https://www.opensourceecology.org/portfolio/tractor/
https://www.opensourceecology.org/microtractor-workshop/
And their other open source machines they deemed "critical for civilization"
I think this is a reaction to the incredibly locked down ecosystem that most of these mfgs are pushing. However, the tech exists for a reason and is not inherently bad, the issue is the lock-in, the lack of choice and interoperability. IMO, there is plenty of space for an OEM who can play nice with others, offer an open (and vibrant ecosystem), and keep users coming back by choice, not by lock-in.
> However, the tech exists for a reason and is not inherently bad, the issue is the lock-in, the lack of choice and interoperability. These low-tech tractors could become a hot bed for open source experimentation. Nothing stopping someone from sticking a tablet on the dash. You could run GPS harvesting optimization software or some webthing locally. Could be cloud or clever DiY farmers could run their farm off a loca…
I think this is a reaction to the incredibly locked down ecosystem that most of these mfgs are pushing. However, the tech exists for a reason and is not inherently bad, the issue is the lock-in, the lack of choice and interoperability. IMO, there is plenty of space for an OEM who can play nice with others, offer an open (and vibrant ecosystem), and keep users coming back by choice, not by lock-in.
> However, the tech exists for a reason and is not inherently bad, the issue is the lock-in, the lack of choice and interoperability. The problem is computers and software enable lock-in, because of their flexibility and communications capability. Get rid of them, and you make lock-in much more difficult (or even impossible if you use "standard" parts). Also, computers and software are complex, and that complexity is…
In any case, EFI gives you more control over the engine and vastly simplifies the overall product. I don't know if you've seen the mechanical fuel-injection pumps used by tractor diesels; they are basically tiny engines unto themselves, with their own little block and camshaft [0]. There is an entire world of diesel performance modding with a subset of it dedicated to modifying the Bosh P1700 mechanical fuel-injection pump to change timings, handle higher RPMs, and run higher pressures. I would not call it, or its carburetor cousin in the gasoline world, "simple" compared to computer-controlled fuel delivery.
An open-source ECU project, on the other hand, enabled a hacker to implement Koenigsegg's Freevalve tech on a Miata [1].
[0]: https://blessedperformance.com/ddp-cummins-hot-street-p-pump...
Up until a year ago I was regularly using a Massy Fergusson 135 [0] (Perkins Diesel version), made sometime in the 1970s. It was wonderful! So amazing to drive and use. Clunky and heavy, but you really really felt like you were using a machine. In low gears, if you put you foot down on the accelerator the engine would roar, and your speed would barely change! And there was no fancy technology in it at all. If I was i…
> no fancy technology in it at all It's amazing we can use huge machinery with internal combustion engines and declare it "no fancy technology"
I don't think the issue is "smarts" in our cars/tractors/light-switches/etc but the lock-in and "authorized repair" bullshit. On the topic of Smart Home stuff (which is the only topic I'm even slightly qualified to talk about) I've heard about people wanting "dumb houses" after initially people wanting "smart houses". It's my opinion that this desire is driven mainly due to bad experiences and doing smart homes the "…
> What that means is everything I "enhance" with "smarts" should still work the old way that people are accustomed to. Also the easiest way to achieve high WAF. I added an internet-connected (but self-hosted) garage door controller. My wife instantly got defensive about things when I said I was going to do this until I said that nothing at all that works now would change. It would add a new feature, not subtract anyt…
> It would add a new feature, not subtract anything. The old remotes work. The wall buttons work. It's just that you can do it from your phone, too.
Exactly! If I'm doing my "job" correctly then I should be able to add "smarts" without anyone noticing at all. It's purely additive. It lowers my stress levels immensely as well since there is a never a "P1" emergency of "The lights won't turn on" or "I can't open the garage door" (unless something lower-level is broken, like the power is out or the garage opener burned out).
I want guests to be able to come to my house and not even notice it's "smart". They should be able to stay in the guest room and not think twice about it. Yes, there will be laminated sheet in the side table telling them what the lights/fan are called if they want to talk to the Echos to control it and there will be a labeled remote (Z-Wave) on the bedside table so they can toggle the fan/lights from the bed but none of that is required. They can control it all from the switches on the wall if they want.
Earlier quoted context omitted.
Plenty of options for putting auto steer on a dumb tractor already exist.
Cheap ones too -- aliexpress has them. But there's more to agtech than driving a tractor around, a lot of what these big integrated systems do (at the high end) is very data driven -- determining where and how to plant, irrigate, fertilize, etc. There's a lot of integration work beyond just making the tractor drive.
I think this is a reaction to the incredibly locked down ecosystem that most of these mfgs are pushing. However, the tech exists for a reason and is not inherently bad, the issue is the lock-in, the lack of choice and interoperability. IMO, there is plenty of space for an OEM who can play nice with others, offer an open (and vibrant ecosystem), and keep users coming back by choice, not by lock-in.
So a prerequisite might involve fixing the patent system...
Earlier quoted context omitted.
How do you define "electronics" and "computers"? Is a general-purpose computer running Java in the same category as a microcontroller running a tight loop with lookup tables for fuel and spark?
The problem: Once you have a microcontroller running a tight loop with lookup tables for fuel and spark, it's very tempting to make it run a tight loop with lookup tables for fuel, spark, and time since license renewal - and there's no outward difference between the two microcontrollers until one of them stops working. This is where regulations can help: if a manufacturer is afraid of a zillion dollar fine, they won'…
Ha - “Wilson saw the gap and drove a tractor through it.”
Earlier quoted context omitted.
Right, but that has nothing to do with a vendor making a dumb tractor. Why do we need to dismissively move the conversation from TFA. The data driven approach is made up of several parts, and we're looking at a specific part
Making a dumb tractor for the use-case of dumb tractor is obviously a winning idea. I just don't think you're going to effectively compete with big agtech by putting a bunch of parts in a box, shaking it, and hoping you end up with a beautifully integrated solution. Integration hell is the reason big commercial firms dominate when it comes to large integrated systems.