Indietro

#cooling

3 APIs con questa etichetta

Heatsink Thermal API

Heatsink and thermal-resistance maths for electronics as an API, computed locally and deterministically. The junction endpoint computes the junction temperature of a component from its power dissipation, the ambient temperature and the thermal-resistance chain, Tj = Ta + P·(Rθjc + Rθcs + Rθsa) — junction-to-case, case-to-sink (the interface material) and sink-to-ambient — and also reports the case and sink temperatures and, given a maximum junction temperature, the headroom. The required endpoint solves the largest heatsink thermal resistance you may use to stay under a junction limit, Rθsa = (Tj_max − Ta)/P − Rθjc − Rθcs, and flags when no heatsink can do it. The power endpoint gives the maximum power a device can dissipate for a given thermal path, P = (Tj_max − Ta)/Rθtotal. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, power-supply and PCB-design app developers, heatsink selection and thermal-budget tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is conduction thermal-resistance; for convective Newton cooling use a cooling API.

api.oanor.com/heatsink-api

Degree Day API

Heating and cooling degree-day maths as an API, computed locally and deterministically. The daily endpoint computes the heating degree days, HDD = max(0, base − mean), and the cooling degree days, CDD = max(0, mean − base), for a single day from a base temperature and the daily mean — or the minimum and maximum, since the mean is taken as their average. The period endpoint sums the degree days over a list of daily temperatures (means or min/max pairs), returning the total HDD and CDD, the count of heating and cooling days and the average temperature — the standard way to characterise a heating or cooling season. The energy endpoint turns degree days into an energy estimate: the heat delivered is UA·DD·24/1000 kWh from the building heat-loss coefficient, the fuel or electricity input is that divided by the boiler efficiency (or a heat-pump COP), and — with an energy price — the cost. Everything is computed locally and deterministically, so it is instant and private. Ideal for building-energy, HVAC and facilities tools, heating-bill and fuel-budget estimation, weather-normalisation and energy-benchmarking apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is degree-day demand estimation; for U-value and heat-loss fabric calculations use a U-value API.

api.oanor.com/degreeday-api

API de calculadora de BTU para HVAC

Matemáticas de dimensionamiento de HVAC como API, calculadas local y determinísticamente a partir de factores estándar de regla general. El endpoint de refrigeración estima la carga del aire acondicionado para una habitación — en BTU por hora, toneladas de refrigeración y kilovatios — a partir del área del piso (en pies cuadrados o metros, o largo × ancho) usando una línea base de aproximadamente 20 BTU/h por pie cuadrado, con ajustes por el número de ocupantes, una cocina, exposición solar y altura del techo. El endpoint de calefacción estima la carga de calefacción a partir del área y una zona climática (templada a muy fría) o un BTU personalizado por pie cuadrado. El endpoint de conversión convierte entre BTU por hora, toneladas de refrigeración, kilovatios y vatios (una tonelada = 12,000 BTU/h ≈ 3.517 kW). Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Estas son estimaciones de regla general al estilo EnergyStar — se recomienda un cálculo de carga Manual J adecuado que tenga en cuenta el aislamiento, las ventanas y el clima local para una instalación real. Ideal para herramientas de HVAC y mejoras del hogar, guías de dimensionamiento de aires acondicionados y calefactores, aplicaciones de hogar inteligente y energía, y cotizaciones para contratistas. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es dimensionamiento de HVAC; para el costo de funcionamiento de electrodomésticos, use una API de costo de energía.

api.oanor.com/hvac-api