Why Field Welding Is Governed by Codes
A weld is unique among construction operations in that its quality cannot be fully verified after the fact. A bolt can be torqued and checked, a column can be measured, but a completed weld hides its internal structure, its fusion, its penetration and its microstructure, beneath a bead of solidified metal. Radiography and ultrasonic testing can see much of what is inside, but not everything, and destructive testing of a production weld is obviously out of the question. The industry’s answer to this verification problem is the welding code: a body of rules that controls the inputs to a weld, the procedure, the materials, the machine, the welder and the process variables, so that the output can be trusted because the inputs were proven in advance.
For field welding this control problem is sharper than for shop welding. In a fabrication shop, the welding power source is a fixed, calibrated machine on a stable supply, the environment is controlled, and the same crew welds the same joints week after week. In the field, the power source is an engine driven welder that may be towed five hundred kilometers between jobs, fed from a drum of fuel of uncertain quality, operated at altitude or in humidity, and asked to reproduce an arc that was qualified a continent away. The code does not care about any of these inconveniences; it requires the production weld to match the qualified procedure. The engineering task of the field contractor is to make the engine driven welder a stable, documentable part of that equation.
This article is written for international buyers, welding engineers, QA/QC managers and contractors who use engine driven welders on pipelines, structures and pressure work. It explains the code landscape, the power source’s formal and practical role in qualification, how engine driven machines earn and keep that role, and how modern digital engine driven welders, such as the DENVO / ENGINE WELDER HW series, can make code compliance easier rather than harder. The thread throughout is a simple principle: the code governs what must be true, and engineering determines how to make it true on a remote right-of-way at six in the morning.
The Code Landscape: API 1104, AWS D1.1 and ASME IX
Three code families dominate field welding in international practice. API Standard 1104, Welding of Pipelines and Related Facilities, governs the overwhelming majority of onshore pipeline construction. It defines what a qualified welding procedure is, how welders are qualified to it, how production welds are visually inspected and non-destructively examined, and what acceptance criteria apply to imperfections. API 1104 is written around the realities of cross-country pipeline spreads, mechanized and manual, cellulosic downhill root passes and all, and its influence extends to most pipeline projects in Asia, Africa, the Middle East and Latin America, frequently invoked contractually even where local regulations also apply.
AWS D1.1, Structural Welding Code, Steel, governs welded steel structures: buildings, bridges, towers, cranes and miscellaneous metal. Its clause structure covers the complete life of a structural weld, from the welding procedure specification through prequalification, contractor qualification, inspection and repair. D1.1 is distinctive for its prequalified WPS framework: a defined envelope of base metals, filler metals, processes and parameters within which procedures need no qualification test, provided the rules are followed exactly. For a field contractor using engine driven welders on structural erection, D1.1 prequalification is where most day-to-day compliance lives, and its precise parameter limits, amperage ranges, travel speed and heat input, map directly onto what a digital welding machine can display and record.
ASME Boiler and Pressure Vessel Code, Section IX, governs welding procedure and performance qualification for pressure equipment: boilers, pressure vessels, piping under ASME B31.1 and B31.3, and refinery and chemical plant systems. Section IX is the most rigorous and systematic of the three in its treatment of variables, every procedure characteristic is classified as essential, supplementary essential or nonessential, and a change in an essential variable requires requalification. Section IX’s discipline has been adopted far beyond the United States, and most national pressure-piping codes reference or parallel its structure. Around these three sit specialist codes, AWS D15.1 for railroad, AWS D1.5 for highway bridges in the United States, ISO 15614 and ISO 9606 series in ISO jurisdictions, and owner specifications that layer their own requirements on top. The first engineering task on any project is to establish which code governs, because the answer determines everything downstream.
The Power Source’s Role in Qualification
A natural first question is whether the welding power source itself is a qualification variable at all. In all three major codes, the formal answer is essentially no: the codes qualify the procedure and the welder, not the machine. A WPS does not list a brand or model of power source, and a welder qualified under one machine is qualified to the process and variables, not to the hardware. This reflects a sound engineering principle, that what matters to the weld is what happens at the arc, current, voltage, polarity, travel speed, electrode, and any machine capable of delivering those variables consistently is formally interchangeable.
The formal position is correct and simultaneously incomplete. The codes’ silence about power sources is a silence about trust: they assume the machine will deliver the set parameters faithfully, because the procedure was qualified with a machine that did. An engine driven welder earns its place in a qualified operation not by appearing on any document, but by delivering an arc that is electrically equivalent to the one under which the procedure and the welder were qualified. Arc stability under CC load, voltage response to arc-length changes, current accuracy across the dial, performance at the ends of the range, these are the characteristics that make one machine interchangeable with another under the code’s assumption, and their absence is how field welds drift out of procedure without anyone intending it.
This has a direct commercial consequence for buyers. A machine whose current output sags under load, whose OCV is marginal for cellulosic electrodes, or whose engine governor hunts and drags the arc with it, can fail a production weld that a qualified procedure and a qualified welder should have produced. The code will still attribute the defect to the welding, and the repair cost, the retest and the schedule damage land on the contractor. In practice, sophisticated owners and inspection authorities therefore look hard at the power sources on a project even though no clause requires them to. A fleet of uniform, well-maintained engine driven welders with documented output accuracy is one of the strongest signals a contractor can give an inspector that the procedures on paper are the procedures in the ditch.
Essential Variables and the Engine Driven Welder
Although the machine itself is not an essential variable, nearly every essential variable passes through the machine on its way to the arc, and understanding this mapping is the core of using an engine driven welder in code work. In API 1104, the essential variables for a procedure include the process, the filler metal, the direction of welding, the thickness range, the position, the number of passes and, critically, the range of amperage, polarity and travel speed. In Section IX, amperage and polarity are essential variables for most processes, and voltage and travel speed are essential for the mechanized processes increasingly used on pipelines. In D1.1’s prequalified regime, amperage ranges are fixed per electrode diameter and position, and heat input limits may apply.
The practical translation is that every time an operator adjusts the machine, a code question is being answered. Moving the amperage control from 120 to 140 A on a procedure qualified at 110 to 130 A is not an adjustment; it is an unqualified procedure, and every weld made with it is technically outside qualification. Field crews under schedule pressure make exactly this mistake constantly, usually by dialing up current to fix fusion on a cold joint or compensate for a long cable run. A conventional analog engine driven welder makes such drift invisible: no record exists, and the error surfaces only if an inspector reads the machine during the weld or a metallurgical problem appears. This is the point at which the machine becomes a compliance instrument, and the distinction between an analog welder and a digital one becomes a compliance distinction rather than merely a convenience one.
Long welding cables deserve particular attention in this mapping. A voltage drop across 50 meters of cable does not change what the machine regulates, a CC machine holds current, the arc compensates by lengthening, but operators respond to a cold arc by raising current, and the drift begins. The disciplined field practice is to size cables per the project’s voltage-drop allowance, keep connections clean and tight, and treat any need to run at the top of the qualified amperage range as a signal to fix the circuit, not to exceed the window. On multi-operator spreads, the same reasoning applies to the shared generator: two welders striking simultaneously on a marginal machine can pull both arcs out of their qualified envelope for the moment that matters, root pass initiation.
CC Output, Arc Stability and Cellulosic Downhill Qualification
Cellulosic downhill welding is the signature process of cross-country pipeline construction, and it places demands on the power source that go beyond the general requirement of parameter accuracy. E6010, E7010 and E8010 electrodes have coatings rich in cellulose, which decomposes in the arc into a fierce gas jet and a deep, forceful penetrating arc. They are designed for direct current electrode positive and they demand a power source with high open-circuit voltage, typically above 70 V, and a drooping constant-current characteristic that tolerates the operator’s rapid arc-length changes without extinguishing. API 1104 projects qualify their procedures around exactly this arc behavior.
An engine driven welder intended for pipeline work must therefore be validated for cellulosic duty in the field sense, not merely the datasheet sense. The engineering questions are concrete. Does the machine strike E6010 easily at low current with a scratch start? Does the arc force remain stable at the bottom of the rod? Does the governor hold engine speed, and therefore arc characteristics, steady when the arc is struck and broken repeatedly? Does the output remain within tolerance across the fuel and temperature range the machine will actually see? Machines in the DENVO / ENGINE WELDER HW class are engineered around these questions, with high OCV CC output and governor strategies designed for the strike-break-strike cadence of pipe welding, and pipeline contractors evaluating engine driven welders should insist on a rod-running demonstration with the project’s actual electrodes as part of acceptance.
Arc stability under field conditions is the second half of the qualification-relevant performance. A hunting governor, voltage dips when a second operator strikes, or current droop as the machine heats up will all express themselves in the weld: inconsistent penetration, slag trapping on stops and restarts, and root-pass internal defects of exactly the kind that radiography and AUT reject under API 1104 acceptance criteria. These defects are always attributed to welding technique, and sometimes correctly, but the machine is a silent co-author. The disciplined approach is to treat power source verification as part of welder and procedure qualification day: run the qualification coupons on the actual engine driven machines that will be used in production, in the actual configuration, cable lengths and all, so that the code’s assumption of equivalence between qualification and production is engineered rather than presumed.
Qualifying Procedures with Engine Driven Power (PQR)
Procedure qualification is where the code’s requirements become physical test coupons, and the power source’s job during a PQR is simply to be a faithful, stable machine. The qualification weld is made on the project’s pipe or plate, with the project’s filler metals and the full parameter set of the intended WPS: process, diameter, amperage range, polarity, layers, travel speed range and position. API 1104 then subjects the coupon to its tensile, nick-break, root and face bend, and, where the contract requires it, notch toughness tests. Section IX selects mechanical tests by the component’s service requirements; D1.1’s qualified procedures are tested per its clause 5 regime where prequalification does not apply.
Making the PQR coupon with an engine driven welder, on site rather than in a shop, is legitimate under every code and is increasingly the recommended practice for field-heavy contracts. The advantage is exactness: the machine, the cables, the ambient conditions and even the fuel are the production ones. If the qualified procedure later produces questionable welds in the field, the list of suspects is shorter, because the qualification itself already contained the field machine. Many owners now specify that qualification for remote projects be performed with the actual field power sources for precisely this reason, and contractors should embrace the requirement, it converts the power source from a compliance risk into documented evidence.
The procedure qualification record itself does not name the power source, but wise contractors record it anyway. A PQR that notes “qualification welded on HW-series engine driven welder, serial number, 4/0 cables at 30 m, 26 degrees Celsius, 900 m elevation” is not more compliant than one that does not mention the machine, but it is vastly more useful: it anchors the procedure to a proven configuration and gives the field engineer a baseline for troubleshooting when a weld problem appears two years later on another continent. This documentation habit costs nothing and pays for itself at the first dispute, and modern digital engine driven welders with parameter logging make it nearly automatic, the machine can supply the record of what was actually delivered during the coupon, not merely what was intended.
Dual-Operator and Multi-Process Qualifications
Engine driven welders in the heavier classes frequently offer dual-operator output: two simultaneous welding stations from one machine. For code work this capability must be understood precisely. Each welding station, each operator, each procedure, is qualified independently as always. What dual operation changes is the shared machine behind both arcs: when both operators strike simultaneously, the combined load draws on the same engine and generator, and the question is whether both outputs remain within their qualified windows under that combined load. A machine engineered for true simultaneous dual CC output maintains independent regulation of both stations; a machine that simply divides capacity will let one operator’s arc influence the other’s.
The qualification-day practice for dual-operator machines is straightforward: qualify both stations under simultaneous operation, with two welders striking and welding together, so that the interference question is answered by coupons rather than argument. Contractors should also verify output tolerance at the extremes, both stations at maximum current simultaneously, one at minimum while the other is at maximum, since these corner cases are where shared-capacity designs reveal themselves. The same logic extends to machines like the HW450D-class dual-torch digital platforms used with external welding carriages on pipelines: the two torches share the power source, and the WPS must be qualified in the configuration in which it will run, both torches active, so that the inter-pass timing and heat input of the real joint are represented in the coupons.
Multi-process capability raises a parallel set of considerations. A single engine driven machine that offers SMAW, GMAW, FCAW and gouging can support several procedures, each qualified separately on the same hardware. The efficiency gain for a field crew is real, one machine serves the root with cellulosic SMAW, the fill and cap with FCAW, and gouges repairs, but each transition is a code event: change of process is an essential variable everywhere, and each process has its own parameter windows that must be displayed, controlled and recorded. Digital platforms that store per-procedure parameter sets make these transitions fast and auditable; analog machines make them a matter of operator memory, which is to say, a matter of time until the first drift.
Welder Performance Qualification in the Field
Welders, like procedures, are qualified by test, and the power source participates in every one of those tests. Under API 1104, a welder qualifies by welding a test coupon in the position and with the process of production, then passing the same mechanical and visual tests demanded of the procedure. Under Section IX, performance qualification tracks essential variables for the welder, process, filler metal form, position, backing and so on. Under D1.1, welders test per the applicable clause with visual and bend or radiographic acceptance. In all three, the coupon must be welded under supervision, and the machine on which it is welded is, again, formally anonymous but practically decisive.
The reason is fairness and representativeness. A welder qualified on a shop inverter with a stable 380 V supply and then sent to the field with an engine driven welder of indifferent arc quality is being tested twice: once by the code and once by the machine. Qualifying welders on the field machines eliminates the second test and guarantees that the certificate describes a welder who can produce on the equipment actually deployed. Forward-looking contractors schedule welder qualification days at the yard, using the engine driven fleet, the project electrodes and the project pipe, so that the qualification event doubles as machine acceptance and equipment familiarization. The practice also surfaces machine problems early: a governor that hunts or an OCV that will not sustain E6010 strikes shows up immediately, on coupons, where the cost of failure is a retest rather than a production reject.
Continuity requirements link qualification to the calendar. Codes require a welder to have used a process within a defined period, commonly six months, for the qualification to remain in force, and field projects with interrupted schedules must manage this actively. The same continuity discipline applies implicitly to machines: an engine driven welder that sat through a tropical monsoon season with water in its fuel system is not the machine that qualified anything, and a prudent contractor runs a verification pass, machine output check and rod test, before restarting work after any layup. Fleet management and welder qualification management are, in this sense, the same administrative task: both are keeping promises made on qualification day.
Documentation, Data Logging and Traceability
Code compliance is ultimately a documentary discipline. The weld itself exists for decades; the evidence that it was made correctly exists only in records: the WPS, the PQR that supports it, the welder qualification certificates, the weld map assigning every production weld to a welder and a procedure, the inspection reports, and the NDT records that clear each joint. Field operations compress all of this into a daily rhythm, and the power source’s contribution to that rhythm has been, historically, silence, analog engine driven welders record nothing, and every parameter on every weld was an act of trust.
Digital engine driven welders change the evidentiary position of field welding. A machine with stored procedure libraries can hold the project’s WPS parameter sets, root, hot, fill and cap, with amperage limits enforced at the machine rather than remembered by the welder. Machines with data logging can record actual current and voltage per weld, per pass, with timestamps, and a fleet with telematics can deliver that record to the project’s QA system at the end of each shift. On projects where heat input limits apply, Section IX supplementary essential variables, D1.1 where specified, the machine can compute heat input from measured values, eliminating the manual estimation that has historically been the weakest link in field records. None of this substitutes for the code’s required records; it strengthens them, converting claimed parameters into measured ones.
Traceability extends to the machine’s own history. A fleet number on each welder, a maintenance log per machine, and a fuel and relocation record sound like depot bureaucracy, but they answer questions that arise in disputes: whether the machine that made joint 47 was within calibration, whether it had been serviced since the storm, whether the same unit made both the rejected welds and the accepted ones. Buyers evaluating engine driven welders for code-governed work should treat logging capability and data export as selection criteria of the same rank as output current. The HW-series digital platforms, for example, store procedures and expose operating data, which allows contractors to align machine records with weld maps without additional instruments.
The integration of machine data into project QA systems deserves planning rather than improvisation. A project that decides, before welding begins, how logs will be named, transferred, retained and matched to weld numbers will find the data an asset; a project that decides afterwards will find it noise. The practical pattern is simple: each machine is assigned to a crew and a weld sequence range per shift; the export at shift end is filed against that range; exceptions, over-limit events, aborted welds, restarts, are reviewed at the daily welding coordination meeting. Fifteen minutes of review converts a logging feature into a compliance system, and it is the single highest-leverage QA habit available to a field contractor today.
Maintaining Qualification Continuity
Qualification is not a certificate in a drawer; it is a live status with expiry conditions, and the field environment attacks it from several directions at once. For welders, continuity of process use must be maintained within the code’s window, typically six months, and interrupted projects, monsoon seasons, permit delays, financing gaps, are the classic continuity killers. The remedy is scheduled practice: a welder two months from lapse welds test coupons at the yard, under supervision, which preserves continuity, refreshes technique and, if the coupons are tested, doubles as early warning of skill decay. Contractors who institutionalize the practice lose far fewer welder-days to requalification than those who discover lapses at the welder’s dispatch to the line.
Procedures lapse differently, through change rather than idleness. Every essential variable change, a new electrode classification, a thicker wall, a new position, a range extension for travel speed, triggers requalification or at minimum a documented review against the code’s variable tables. Field projects generate these changes constantly as the alignment sheet moves from station to station, and the engineering function that tracks wall thickness changes and fitting types against the WPS portfolio is as much a part of pipeline welding as the machines themselves. The engine driven welder fleet enters this discipline through configuration control: a machine whose software holds stored procedure sets must be updated when a WPS is revised, and the fleet procedure, who loads which set into which machine and when, belongs in the project’s quality plan beside the welder continuity log.
Machines, too, have a continuity of qualification in the practical sense established earlier. A power source that demonstrated output tolerance at qualification and then drifted through a season of hard use has quietly withdrawn the evidence on which the code’s interchangeability assumption rested. The disciplined answer is periodic verification: a simple daily or weekly output check with a welding meter at representative settings, logged per machine, restores the evidence cheaply. Digital platforms simplify this further, their measured-parameter displays can be verified against a reference meter on a schedule and logged like any other calibration. A contractor who can produce a year of machine verification logs alongside welder continuity records has, in inspection terms, a closed loop, and owners notice.
Inspection and Testing After Field Welding
Everything upstream of the finished weld, procedures, welders, machines, exists to survive what happens after it: visual inspection and non-destructive testing. Under API 1104, production welds are examined visually and, per the contract’s percentage, by radiography or automatic ultrasonic testing, with acceptance criteria for porosity, slag, incomplete fusion, penetration and cracks that vary by weld type and criticality. Under D1.1, structural welds are inspected visually against the code’s tolerance classes and, where the contract requires, by UT or RT. Section IX’s parent codes apply their own examination regimes, hydrostatic testing for vessels, leak and pressure testing for piping, NDT per the construction code.
Rejection is where the power source’s contribution becomes visible, because rejection patterns tell stories about machines. Incomplete joint penetration and incomplete fusion concentrated at root passes point toward arc heat and manipulation, and the machine’s current accuracy, cable voltage drop and the operator’s response to a cold arc are all in the causal chain. Porosity clustered at starts and restarts implicates ignition characteristics, OCV, arc force behavior and governor response to the strike. Slag lines in fills implicate technique and parameter drift. A contractor who logs rejections by welder, by procedure and by machine has the data to find a drifting power source weeks before the NDT trend would otherwise be blamed on people. This is the quiet commercial argument for uniform engine driven fleets: identical machines make machine effects separable from welder effects, which is the entire game in defect analysis.
Repairs are the code’s final intersection with the welding machine. A repair is a new weld, governed by its own acceptance, often with tighter criteria and always with full documentation of removal, re-welding and re-examination. Engine driven machines with gouging capability, carbon arc at 400 A and above, perform the removal; the repair weld itself is made under the same or a specially qualified repair procedure; and every parameter of it must sit inside a qualified window, at exactly the moment when schedule pressure is highest. The machines that make repair discipline easiest, stable CC output at low current for the root of the repair, enforced parameter limits, instant arc ignition, are the machines that keep the rejection-to-repair loop short. The loop’s length, measured in schedule days, is one of the largest hidden costs in field welding, and it is a power source variable as much as a people variable.
Common Compliance Pitfalls and How to Avoid Them
The same handful of failures recurs on field projects across every continent, and most of them are administrative rather than technical. The first is amperage drift outside the qualified window, discussed above, born of analog dials, cold arcs and schedule pressure. The countermeasures are mechanical: digital machines with settable limits, current verification at the machine during daily inspection, cable lengths standardized per the WPS, and a standing instruction that a cold arc is fixed by tracing the circuit, not by turning the dial. The second is undocumented parameter changes between qualification and production, the machine at the yard was set by the welding engineer, the machine at the ditch is set by memory. Stored procedure sets and a one-page WPS at each station close this gap almost entirely.
The third pitfall is qualification on hardware that production never uses, the shop inverter for coupons, the engine driven welder for the work, or qualification with short cables and production with long ones. The cure is to weld qualifications on the fleet machines in the field configuration, and to record the configuration on the PQR. The fourth is continuity failure, welder and machine alike, cured by the scheduling discipline described earlier. The fifth is the dual-operator interference assumption, two stations qualified separately and run together without ever being tested together; cured by qualifying and periodically demonstrating simultaneous operation. The sixth is heat input estimation, where required, done by optimistic manual math; cured by machine-measured values logged per pass.
The seventh pitfall is subtler: treating the machine as exempt from the quality system because the code does not mention it. The code’s silence, as established, is a trust, and the trust is repaid through the quality plan, machine verification schedules, maintenance records, fleet configuration control, or it is quietly defaulted on. Contractors who have stood in front of an owner’s engineer explaining a cluster of root defects on a pipeline spread know that the question “what changed” is answered fastest by those with machine records, and slowest by those with only welder records. The pitfall list is, in the end, a list of evidentiary gaps, and every one of them can be closed with instruments and paperwork that cost a fraction of a single repair campaign.
Working with Inspection Authorities and Owners
Field welding compliance is a relationship as much as a rulebook. The inspector’s authority under the contract is to verify that production matches qualification; the contractor’s interest is to make that verification fast and uneventful. The practical currency of the relationship is evidence produced proactively: the weld map, the WPS portfolio, welder continuity records, machine verification logs and NDT results, presented in an organized daily flow rather than retrieved under request. An inspector who receives this package routinely spends the day inspecting welds; an inspector who must extract it spends the day inspecting the contractor, and the difference colors every discretionary judgment on the project.
Power source presentation is part of this currency. Uniform, clean engine driven welders with visible fleet numbers, current WPS cards at the station and calibrated meters available on request communicate control before a word is spoken. Machine data, where the fleet is digital, can be offered at the daily meeting: yesterday’s parameter compliance summary, exceptions noted and explained. Owners on high-consequence projects, gas transmission, process piping, road and rail bridges, increasingly ask for exactly this, and contractors able to provide it are moving the inspection conversation from sampling to verification, which is faster for everyone. There is no adversarial residue in this; the codes themselves push both parties toward documented process control, and the machine is the most documentable element in the entire chain.
For international buyers, the supplier’s role in this relationship should be part of the purchase decision. A manufacturer that provides output accuracy statements, calibration guidance, procedure-storage features, data export formats and responsive technical documentation equips its customers for inspection regimes anywhere in the world. Beijing Anjie Weida Technology Co., Ltd. supports the DENVO / ENGINE WELDER engine driven welder range, including the HW-series platforms used on pipeline, structural and municipal work worldwide, with engineering documentation and direct technical support, so that qualification day and every production day after it run on machines whose behavior is known, recorded and reproducible.
Conclusion: The Machine Behind the Certificate
Welding codes govern procedures and welders, and say almost nothing about power sources. That silence has always been a trust: the code trusts that whatever machine carries the qualified arc will carry it faithfully, delivering the qualified amperage, the qualified polarity and a stable arc from the first strike of the root pass to the last cap bead. For field welding, that trust is carried by the engine driven welder, towed, rained on, refueled and run hard, at the center of every code-governed joint made away from a shop.
The engineering argument of this article is that the trust should be earned visibly rather than assumed silently. Qualify procedures and welders on the actual machines, in the actual configuration. Keep welder continuity and machine verification on the same calendar. Map every machine adjustment to the essential variable it touches. Use digital platforms that store procedures, enforce limits and log what actually happened. Present the resulting records to inspectors proactively, and let rejection analysis separate machine effects from welder effects instead of laundering one into the other. None of this adds a clause to any code; all of it makes the code’s existing clauses true.
The reward is measured in repair rates, schedule days and inspection outcomes, and it compounds over every project. A contractor whose engine driven welder fleet is uniform, verified and instrumented is not merely well equipped; it is structurally aligned with the way the codes already think, controlling inputs because outputs cannot be fully seen. Field welding will always be performed far from the conditions under which its rules were written, and the machine that bridges that distance, reliably, documentably and year after year, is the quiet partner of every certificate on the wall.
For product specifications and inquiries:
📞 Tel: 86-010-86468776
📱 Tel/WeChat: 13521628344
📧 Email: sales@denohgroup.com
🌐 Website: https://www.denohgroup.com/