Seeking feedback on controllers

It's obvious you've put a lot of work into it and it does integrate all of the elements into one neat little box. Now it was a able to run a web server outputting to a monitor, effectively a lower cost option to a Raymarine Glass Cockpit, then I'd be interested.
Raspberry Pi running Openplotter is a Web server as Signal K is web page.
 
The problem you have is there are two ends of the market - the top end who buy the latest matching kit, so it all plays nicely together and uses N2K sensors etc. These people have money. They already have solutions for the things you are proposing from trusted suppliers.

Then at the other end are the people who have various components cobbled together over the years. They are either of the “I’ve been fine with analogue and paper chart for 30 yrs” type of are tinkerers who like to make stuff work together etc. That last group sound like they should be your target market? But they already have solutions in the form of a raspberry pi, openplotter, etc. not only do they not like spending money (or don’t have any!) but many of them actually enjoy messing around themselves. You might find there is some niche group who want this capability, haven’t worked out how to do it and are actually willing to spend money BUT don’t underestimate the customer support requirements of that group.
Absolutely agree.
Back in the late 70s/early 80s a couple of friends and I built a company focussed on supplying the DIY electronics/early computer market based around the Zilog Z80 micro processor. The company was moderately successful but the support was intense. It was more like a club of enthusiasts than a business. But it paid our salaries and we enjoyed it.
The serious money was made later when we branched into vertical markets that required the technical expertise that we had gained. But, as you say, those vertical markets were driven by customers who were able to pay proper money for the products/services that we offered.
 
Let me know your first impression of this www.techydem.com
My goal is to come up with an HW platform that meets most of HW needs and maybe 80% of SW needs. After, someone would finalize his customization.
Ok ... from your website and the specs (not a lot of real tech data) you are putting together an ARDUINO microcontroller with some interfaces ... some cables and some own developed SW to build a "yacht computer / server" for processing all signals and most of the engine data / parameters? You claim to be "open source" ? And you would like to get some money of course for the hardware box.

The project seems intresting - but for real usage on a boat / yacht we need some professional reliability, proven functionality and specifications on all input/output functionality. For me, this "tech box" seems to be an interesting amateur ARDUINO project - but it has to be transfered into an industrial grade boat controller. And to be "open source" you have to publish the SW coding and the scripts for review.
 
It's obvious you've put a lot of work into it and it does integrate all of the elements into one neat little box. Now it was a able to run a web server outputting to a monitor, effectively a lower cost option to a Raymarine Glass Cockpit, then I'd be interested.
An optional IP65 HDMI connector can be added to access the internal mini-HDMI of the Raspberry Pi; personnaly I prefer using an iPad that I can move around the boat.
 
Absolutely agree.
Back in the late 70s/early 80s a couple of friends and I built a company focussed on supplying the DIY electronics/early computer market based around the Zilog Z80 micro processor. The company was moderately successful but the support was intense. It was more like a club of enthusiasts than a business. But it paid our salaries and we enjoyed it.
The serious money was made later when we branched into vertical markets that required the technical expertise that we had gained. But, as you say, those vertical markets were driven by customers who were able to pay proper money for the products/services that we offered.
My goal before developping the controller was to get all the bells & whistles & features of the high end market at a low cost without having to stitch disparate devices together. Of course, I have to build my credibility before I become a "trusted supplier"
 
Ok ... from your website and the specs (not a lot of real tech data) you are putting together an ARDUINO microcontroller with some interfaces ... some cables and some own developed SW to build a "yacht computer / server" for processing all signals and most of the engine data / parameters? You claim to be "open source" ? And you would like to get some money of course for the hardware box.

The project seems intresting - but for real usage on a boat / yacht we need some professional reliability, proven functionality and specifications on all input/output functionality. For me, this "tech box" seems to be an interesting amateur ARDUINO project - but it has to be transfered into an industrial grade boat controller. And to be "open source" you have to publish the SW coding and the scripts for review.
When you say "not a lot of real tech data", what kind of tech data do you think is missing ? I made a Youtube video for the demo but maybe I need to add more.

Your first paragraph is a good description of the hardware box. Around the microcontroller, there are all the electronics to convert the analog signal/pwm/rpm... into digital data, all the relays and drivers and the N2K interfaces. Everything running on the RaspberryPi is "Open source", including the yacht specific application that I have developped. The software running on the microcontroller is not open source for now because it can been seen as a driver layer between hardware and software running on the RPi.

I agree with you for the "some professional reliability, proven functionality and specifications"; that has to be built over time and right now I'm expecting the first users to be beta testers who don't want to spend hundred of hours to make their own solution.

For the "publish the SW coding and the scripts for review"; that is my plan; I need to figure out how to publish the Node Red code in a form that can be easily reviewable.
 
I agree with you for the "some professional reliability, proven functionality and specifications"; that has to be built over time and right now I'm expecting the first users to be beta testers who don't want to spend hundred of hours to make their own solution.
Are you expecting beta testers to pay £1k for finding your bugs but not to work out their own solution?

As I have a rasp pi and have gone through some of the learning curve on this stuff - did you consider just producing a “HAT” and perhaps a tool to configure OpenPlotter or a fork of that… it seems with a HAT and perhaps a case at a more sensible price, you might have had a lot more early adopters?
 
The beta tester would have a discount; I see my web site is missing that info so I will add it. The pricing can't lowered by much because I need to account for the hardware cost and manufacturing; just the PCB to support 15A relays is expensive. The hardware box has been used for a full season so I'm not expecting bug but certainly improvement in the Node Red code.

The idea of making an HAT would not be possible because there is too much electronic to fit on the surface of a HAT; however, the RPi is connected like an HAT on the main PCB and there is a provision to add an extra HAT (ex DaisyHAT).

I agree that if someone just wants to monitor some batteries, he could find a cheaper solution. If I make apple to apple comparison with some products available on the market, as show on my latest web site, then there is a significant price difference.
 
The beta tester would have a discount; I see my web site is missing that info so I will add it. The pricing can't lowered by much because I need to account for the hardware cost and manufacturing; just the PCB to support 15A relays is expensive. The hardware box has been used for a full season so I'm not expecting bug but certainly improvement in the Node Red code.

The idea of making an HAT would not be possible because there is too much electronic to fit on the surface of a HAT; however, the RPi is connected like an HAT on the main PCB and there is a provision to add an extra HAT (ex DaisyHAT).

I agree that if someone just wants to monitor some batteries, he could find a cheaper solution. If I make apple to apple comparison with some products available on the market, as show on my latest web site, then there is a significant price difference.
Is it intended to use a Raspberry Pi or a CM4/CM5
 
Wouldn't it be a more professional solution if you used a CM4?
The RPi 4B has all the USB, HDMI, Ethernet connectors while the CM4 would require to have those connectors on my main board, which would complicate the manufacturing and PCB design. Both CM4 and RPi4B share the same processor and GPU.
 
The RPi 4B has all the USB, HDMI, Ethernet connectors while the CM4 would require to have those connectors on my main board, which would complicate the manufacturing and PCB design. Both CM4 and RPi4B share the same processor and GPU.
Agreed but aren't you introducing extra connectors/interfaces which will make the design (IMO) messy.
For example, in post #9 you say that it has relays to control equipment such as pump, fan, lights, trim tab..
In that example case, you are probably designing interface electronics between the RPi's GPIO header etc and external connections to the boat.
If you were to use a CM4 or the more recent CM5, your bespoke hardware board (with a CM4 or 5 fitted) would handle everything internally and only need external connections on your bespoke board, The whole design would ne nicely integrated. Thats why the CM4 and CM5 exist.
IMO, a CM4/CM4 would be a much more bespoke and professional solution.
 
Top