Sonic R System

[Chiquita Palafox]

Becausewe are SONIC SYSTEMS, our specialties include ultrasonic cleaning units used in everything from the HOSPITAL and HEALTHCARE environment to AEROSPACE applications. Our products also include small benchtop cleaners to large capacity tanks for INDUSTRIAL and MILITARY use.

SAVE MONEY and TIME with an ultrasonic tank. Cleaning your tools and/or products ultrasonically will add years of life to the instruments you use. Tools that LOOK old, will become like NEW again, saving you money on new equipment, and if you are paying a lot to employees or outside services for cleaning, you will save money over the long haul, and YOU'LL SAVE TIME.

If you don't need our ultrasonic line, that's fine, as we can create most any product. We can take your idea for a metal project and design it, then cut, bend, weld, PEM, wire, and anything it else it might require, to make it come to life.

We are proud to make our products right here in Bucks County, PA. MADE IN AMERICA is important to us, and we are also proud of the high-quality work that we have ALWAYS done, for decades. We are known county wide for our quality and dependability.

We are Medical Grade. Now, what does that mean? It means that we create our products to the highest standards possible. If hospitals can trust us to clean their surgical tools, (that we hope you never have to have used on you) then you can trust that when you give your metal project to us to create, that the highest quality will follow.

The Lakewood Sonic System has been fitted to all our electro-acoustic guitars from 2005 until beginning of 2012. This system was the result of the co-operation of Martin Seeliger and Joe Marinic, who had the aim of dispensing with the routing cavity in the sides of a guitar. The idea was - at that time a new one - to mount the preamp of the pickup system in the soundhole of the guitar. It should still meet highest expectations in terms of ergonimics and tone, while offering a good range of sound varieties.

At the same time the Lakewood Classic System has been developed, which is particularly adapted to the needs of a nylon string guitar. Since it is not possible to pick up a nylon string magnetically, the system works with the "Nanoflex" transducer only. The controls are positioned in the sound hole as well. The pre-amp offers a volume control and two sound controls, which act in a high and a low frequency range. The result is an impressing nylon sound that possesses a remarkable transparency and awesome dynamics. Especially lovers of the Latin-American style will appreciate that uncomplicated system.As well as the Sonic System, the Classic System offers a simple battery change. The batteries are replaced just in a wink of an eye and the guitar is ready to go.The Lakewood Classic System fulfills the wishes that many guitarists have, a discreet but still efficiently working pickup system, that captures the original tone of the guitar and meets high quality expectations.

The Mini Sonic System was the simplified solution of the Lakewood Sonic System or the Classic System. It works with only one pickup, the Nanoflex under-saddle transducer.The control unit sits, as well as on the other systems, within the soundhole. It is slightly slimmer than the Lakewood Sonic System, though. Since there is only one lithium cell required, the "batterie drawer" is slimmer and thus enables the smaller case of the unit. That, of course, compliments the overall design.The adjustments are reduced to volume and tone control. The Mini Sonic System hasn't got a battery led and no phase switch.

SONiC system's architecture comprises of various modules that interactamong each other through a centralized and scalable infrastructure. Thisinfrastructure relies on the use of a redis-database engine: a key-valuedatabase to provide a language independent interface, a method for datapersistence, replication and multi-process communication among all SONiCsubsystems.

By relying on the publisher/subscriber messaging paradigm offered by theredis-engine infrastructure, applications can subscribe only to thedata-views that they require, and avoid implementation details that areirrelevant to their functionality.

SONiC places each module in independent docker containers to keep highcohesion among semantically-affine components, while reducing couplingbetween disjointed ones. Each of these components are written to beentirely independent of the platform-specific details required tointeract with lower-layer abstractions.

The following diagram displays a high-level view of the functionalityenclosed within each docker-container, and how these containers interactamong themselves. Notice that not all SONiC applications interact withother SONiC components, as some of these collect their state fromexternal entities. We are making use of blue-arrows to represent theinteractions with the centralized redis-engine, and black-arrows for allthe others (netlink, /sys file-system, etc).

Even though most of SONiC's main components are held within dockercontainers, there are some key modules seating within the linux-hostsystem itself. That is the case of SONiC's configuration module(sonic-cfggen) and SONiC's CLI.

This section aims to provide a description of the functionality enclosedwithin each docker container, as well as key SONiC components thatoperate from the linux-host system. The goal here is to provide thereader with a high-level introduction; a more graphical and (hopefully)intuitive approach will be followed in subsequent sections.

Teamd container: Runs Link Aggregation functionality(LAG) in SONiC devices. "teamd" is a linux-based open-sourceimplementation of LAG protocol. "teamsyncd" process allows theinteraction between "teamd" and south-bound subsystems.

Pmon container: In charge of running "sensord", adaemon used to periodically log sensor readings from hardware componentsand to alert when an alarm is signaled. Pmon container also hosts"fancontrol" process to collect fan-related state from the correspondingplatform drivers.

Snmp-agent (sonic_ax_impl): This is SONiC's implementation of anAgentX snmp subagent. This subagent feeds the master-agent (snmpd)with information collected from SONiC databases in the centralizedredis-engine.

Lldp_syncd: Process in charge of uploading lldp's discovered stateto the centralized system's message infrastructure (redis-engine).By doing so, lldp state will be delivered to applications interestedin consuming this information (e.g. snmp).

Bgp container: Runs one of the supportedrouting-stacks: Quagga or FRR. Even though the container is named after the routing-protocolbeing used (bgp), in reality, these routing-stacks can run various otherprotocols (such as ospf, isis, ldp, etc).

zebra: acts as a traditional IP routing-manager; that is, itprovides kernel routing-table updates, interface-lookups androute-redistribution services across different protocols. Zebra alsotakes care of pushing the computed FIB down to both kernel (throughnetlink interface) and to south-bound components involved in theforwarding process (through Forwarding-Plane-Manager interface--FPM--).

Database container: Hosts the redis-database engine.Databases held within this engine are accessible to SONiC applicationsthrough a UNIX socket exposed for this purpose by the redis-daemon.These are the main databases hosted by the redis engine:

APPL_DB: Stores the state generated by all application containers-- routes, next-hops, neighbors, etc. This is the south-bound entrypoint for all applications wishing to interact with other SONiCsubsystems.

STATE_DB: Stores "key" operational state for entities configured inthe system. This state is used to resolve dependencies betweendifferent SONiC subsystems. For example, a LAG portchannel (definedby teamd submodule) can potentially refer to physical ports that mayor may-not be present in the system. Another example would be thedefinition of a VLAN (through vlanmgrd component), which mayreference port-members whose presence is undetermined in the system.In essence, this DB stores all the state that is deemed necessary toresolve cross-modular dependencies.

ASIC_DB: Stores the necessary state to drive asic's configurationand operation -- state here is kept in an asic-friendly format toease the interaction between syncd (see details further below) andasic SDKs.

Swss container: The Switch State Service (SwSS)container comprises of a collection of tools to allow an effectivecommunication among all SONiC modules. If the database container excelat providing storage capabilities, Swss mainly focuses on offeringmechanisms to foster communication and arbitration between all thedifferent parties.

Swss also hosts the processes in charge of the north-bound interactionwith the SONiC application layer. The exception to this, as previouslyseen, is fpmsyncd, teamsyncd and lldp_syncd processes which run withinthe context of the bgp, teamd and lldp containers respectively.Regardless of the context under which these processes operate (inside oroutside the swss container), they all have the same goals: provide themeans to allow connectivity between SONiC applications and SONiC'scentralized message infrastructure (redis-engine). These daemons aretypically identified by the naming convention being utilized: *syncd.

Portsyncd: Listens to port-related netlink events. During boot-up,portsyncd obtains physical-port information by parsing system'shardware-profile config files. In all these cases, portsyncd ends uppushing all the collected state into APPL_DB. Attributes such asport-speeds, lanes and mtu are transferred through this channel.Portsyncd also inject state into STATE_DB. Refer to next sectionfor more details.

Neighsyncd: Listens to neighbor-related netlink events triggered bynewly discovered neighbors as a result of ARP processing. Attributessuch as the mac-address and neighbor's address-family are handled bythis daemon. This state will be eventually used to build theadjacency-table required in the data-plane for L2-rewrite purposes.Once again, all collected state ends up being transferred toAPPL_DB.

3a8082e126