:: Marine PCB Design ::

Location Map

Why New Design is Required ?

When marine system is non operational often end up with a defective PCB which in no more in production with OEM, while everything else of the machinery is OK. If PCB is damaged beyond repair or unavailability of discrete component for replacement of defective parts, only solution is to design a new PCB for the same function so that original equipments can be made functional. Systems like CPP or Steering or autopilot or crane etc. not easy for complete replacement with out considerable time and money. In such cases by designing a PCB is an ideal solution.

When designing marine PCB / product, the first steps are to identify the need of the PCB/product. Designing a PCB involve analog, digital, microcontroller, mixed signal, software programming etc. It is also required inspect the system to study various inputs, interfacings, connections and logics. Our engineers are specially trained for assessment of defective system so that new PCB or products equivalent can be designed. Finally we build up a specification for a new product positioned successfully. This is detailed a little more in our guide to writing a new product spec.This guide describes our process for designing a new electronic circuit board, typically one that is microprocessor based with embedded firmware. This same process is used for most products we design. Usually an industrial designer is employed to produce the product enclosure or case, with labeling and graphics. We deliver working prototypes and technical documentation to the client - and then the product goes on to beta testing, pilot run, and production release.

The Printed Circuit Board Layout :

The Printed Circuit Board (PCB) is the laminate to which all the electronic components are soldered, with one or more layers of etched metal tracks making the connections. The components and connections in the PCB Layout are derived from the circuit diagram, and physically placed and routed by the designer to get the best result. The PCB Layout defines the final physical form of the circuit, and enclosure and labeling details can be finalized as the layout is completed.

ProtoTypes :

At ACSPL, we usually make 2 or 3 identical prototypes at the same time. The Prototype circuitry is debugged in stages. The debugging proceeds according to the debug test procedure, which is written for the product as it is designed. Prototype microprocessor circuits are generally debugged with specially written diagnostic code, again progressing in stages. When confidence has been gained in the operation of the prototype hardware, debug of the actual prototype program ("Firmware") can begin, on the target.

FirmWare : Software for the electronics is often 50% or more of the design works in a project. The programming that controls the microprocessor usually gives the electronic product its features and "glitz" whereas the hardware is the purely functional side of the equation. The programming or coding for electronic products is usually written in 'C' or assembler, whereas the programming that runs on a PC will normally be written in C++, java or another language (and almost certainly not assembler). The programming for microcontrollers is totally different from that for a PC in any case - it is usually "more detailed" and less "generic" than the type of programming made for a personal computer, because it is more tightly coupled
o the electronic hardware on which it runs, and because it usually has to respond more quickly - that is it has to run in "real time". There is usually a great deal of care and testing involved with programming for electronic products - while for some reason clients seem willing to accept bugs in windows software as somewhat normal, they are pretty unacceptable in, say, an engine control unit for a modern car. The firmware may be developed by a separate team, and it is at the prototype stage that the two projects come together. When the two components are integrated and prototype testing is complete, the finished project is handed over to the customer. The trouble with doing something right the first time is that nobody appreciates how difficult it was. -- from "Fortunes"

	Pilot Run : To test the product further, a Pilot run normally follows the prototyping stage. In the Pilot run, a small quantity of units (for instance 25) is field trialed in a beta test. The Pilot run is also an opportunity to assess the manufacturability of the design, and the usability of the documentation (See: More info - PCB Documentation).

Production :

Following the pilot run there will likely be changes to the firmware, and possibly the circuit design, as the unit develops into a stable, final product. This process is controlled by ECOs and version numbers. We handle the actual production of electronics for some customers, but others prefer to produce the circuitry in house, or use other assembly subcontractors. Our technical documentation is sufficiently detailed for our customers to have the electronics produced by a third party subcontractor. The cost of the final production, and to some degree the style of design, is heavily influenced by the number of units manufactured