In 2002, we took on a marine project that was technically successful but commercially “aborted.” Nevertheless, the lessons and reflections it left me with have benefited me to this day. Today, I would like to share this story from over twenty years ago, along with its technical details, the joy of success, and the ultimate regrets.
1.Project Background: Opportunities and Research Demands in Typhoons
In 2002, a local research institute approached us with a very urgent need: precious fish fry and seafood were raised in large fish cages. Whenever a typhoon struck, the cages would be destroyed, resulting in significant losses. Could we design a system that would allow the cages to automatically submerge 5 meters before a typhoon to avoid the storm and then automatically resurface afterward?
After receiving this project, we inspected the aquaculture site in Rongcheng, where we saw large fish cages floating on the sea, impressive yet fragile—at that time, Chinese manufacturing was not as strong as it is today, and these cages were all imported from Norway.
The core difficulty of this project was clear: there was no power source at sea, communication was limited, and the system had to withstand harsh conditions of high temperature, high humidity, and high salt mist. Additionally, hidden within the client’s demands was a key piece of information: this was an important outcome for their research project application, which was related to the team’s professional title evaluation.
I understood that this was not just a technical project but also bore the special mission of a “title sprint.”
2.Technical Solution: Combining PIC16F877A with Vacuum Technology
1. Core Idea: Buoyancy Control
To make a large fish cage sink and float is essentially to change its overall buoyancy.
·Submerging: Using a vacuum pump to extract air from the cage, reducing net buoyancy, and adding some ballast to make the cage sink.
·Floating: Reversing the vacuum pump to inflate the cage, increasing net buoyancy, causing the cage to float.
2. Control System:PIC16F877A as the “Brain at Sea”
The control core of this system is a control board I designed based on the PIC16F877A.
Why PIC16F877A? Because it is “sufficient and reliable.” With 40 pins, it provides enough I/O to control the vacuum pump, pressure sensors, and GSM module; the built-in EEPROM can store key parameters; its industrial-grade anti-interference capability is sufficient to withstand the harsh conditions of high temperature, high humidity, and high salt mist at sea.
3. Communication and Power Supply
·Communication: Back then, mobile phones were dominated by Nokia, Siemens, and Ericsson. We chose a Siemens GSM module, connecting it to the PIC16F877A via UART (serial port). Users only need to send a text message like (submerge) or (float), and the system will automatically execute all actions.
·Power Supply: A large-capacity battery pack combined with solar panels ensures that the system can operate stably at sea for long periods without human supervision.
3.On-Site Debugging: The Joy and Sense of Achievement at the Moment of Success
The most unforgettable part of the project is always the on-site debugging phase.
We brought the entire system for a sea test. That day, the sea breeze was strong, and the waves rocked the small boat. When I sent the command “submerge” from my phone on the boat, the indicator light of the GSM module flashed in response, and the relay on the PIC board clicked as it engaged, and the vacuum pump started working. Through the clear seawater, we could clearly see the cage slowly and steadily sinking underwater, with a smooth speed and a precise depth reaching the preset 5 meters.
At that moment, the code in the laboratory and the lines on the circuit diagram transformed into real actions happening before my eyes, executing according to my will. This sense of achievement, akin to being a “creator” who turns virtual ideas into physical reality, is something that no amount of money can measure.
The subsequent command to “float” also perfectly brought the cage back to the surface. The entire system operated stably and accurately. The teachers from the research institute were very satisfied, and we successfully obtained the project acceptance report.
4.Project Outcome: Technical Success, Yet Became a “One-Time Product”
However, this technical “success example” became a commercial “final version.”
After the project ended, we eagerly prepared to welcome subsequent bulk orders, but we never received any. Later, we learned that the research institute successfully applied for a higher-level project based on this project, and the relevant teachers also successfully evaluated their professional titles. Their academic demands had been met, and the commercialization of the technology and bringing it to market was not their core concern.
Thus, this project was simply “over.”
5.Reflections and Advice for Young Engineers
Many years have passed since this incident, and I have long since come to terms with it, but the lessons learned have saved me from countless detours in subsequent industrial R&D, which I would like to share with young colleagues:
1. Technical Success ≠ Commercial Success. Your code and circuit board are just part of the value chain; the market, channels, costs, and sustainable business models are the keys to a product’s survival.
2. Achieve “Synchronous Resonance” with Partners. Before collaborating, be sure to clarify the other party’s core demands—whether it is solving a long-standing production problem or completing a short-term research target. This determines the project’s lifecycle.
3. Protect Your Intellectual Property and Labor Achievements. In similar collaborations, have a basic awareness of contracts, clarify the ownership of technical achievements and the rights to subsequent development, and avoid “making clothes for others.”
4. Do Good Deeds Without Asking for the Future. Although the project did not have a follow-up, during this process, I greatly enhanced my understanding of the reliability of the PIC microcontroller in extreme environments and deepened my understanding of GSM communication and mechatronic design. These experiences have become invaluable assets for my future development of other industrial products.
Conclusion
The offshore fish cage system based on PIC16F877A is a shining coordinate in my technical career, reminding me of the pride of being an engineer and warning me of the realities of the business world.
For engineers, there are no wasted projects; even if they ultimately fail, the skills honed and experiences accumulated during the process will become the confidence for the future.
Have you encountered similar “regrets” in project collaborations? Or do you want to learn about the anti-interference design of PIC microcontrollers in extreme environments? Feel free to leave a message in the comments!
More valuable content is coming, and let’s progress together in the world of microcontrollers.