LOGOS release notes

LOGOS 1.8.1 — 18 November 2026

Priority: Serious — install it within about two weeks. Security fixes in the programs, a question before LOGOS opens a file on another computer, two-phase pumps, the batch window in Systema, the analysis tools on every core, AMD Artix-7 in the FPGA tool, and the LOGOS Server’s check of its file shares for SMB 3 and encryption.

Saved answers: a model or design saved by 1.8.0 or older keeps its answers. The new calculation methods (LOGOS 1.8.1’s methods) change only models with a two-phase pump, and are taken only when you choose Bring up to date, which shows what moves before it moves anything. Every sample LOGOS ships is on the newest methods; none moves.

Data: every file 1.8.0 saved opens with the same contents; the LOGOS Server’s data is kept. Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT. The notes for your IT are at the end.

Security

  • Fixed in the programs: a model could make an FPGA design’s ANALYSE run any program (it now runs only ghdl, nvc or vsim); Agora’s Open on a pool document could write outside its folder and run the file (it now opens only a document, in its own folder, marked as from the Internet); links in pools, vendor records and the parts catalogue open only as https, http, mailto or a file of a type Windows does not run. Found by our security sweep and checked by a penetration test on test copies.
  • A file on another computer is asked about first: before LOGOS opens a file on a share, a WebDAV folder or a mapped network drive, it names the computer and asks — Open, Cancel or Always for that computer — as Windows signs in to it with your account. Files on your PC and web addresses open as before.
  • The AI link’s credential stays off the command line: the AI instructions now have the AI tool keep it in a file (--link-file), so it is not written to Windows’ process logs.
  • Updated parts: Qt 6.11.2, SQLite 3.54.1 and cpp-httplib 0.66.0, and every program looks for its DLLs only in its own folder and Windows’ — never the folder of a file you opened.

New — two-phase pumps (LOGOS 1.8.1’s methods)

  • A displacement pump drawing a two-phase mixture displaces the mixture and carries its energy exactly.
  • A dynamic pump on a fluid that flashes at its inlet (CO2 with its pressure-enthalpy table, LOGOS:CO2_ph) runs on its liquid curve. Give its inducer and LOGOS checks the inlet’s vapour against the inducer’s vapour capacity (King, 1972), stopping the run past it; without an inducer, its inlet going into the dome stops the run.
  • A gas compressor whose inlet goes into the dome still stops the run, as in 1.8.0.

New — the batch window

  • TOOLS > Analysis > Batch…: a list of steps, each one or more runs of your model with its own changes — parameters (a value, a range, random draws, or a number taken from an earlier step), settings, a mission, a lookup table or a fluid — with checks, “run only if” and “stop on a failure”. No scripting: each step is a row.
  • What each run leaves: a results file, a CSV in the units you choose, pictures of plots (SVG, PNG or both), a summary table of every run and a log that says each failure in words. Your model is never changed.
  • Run it at night: save it as NAME.systema-batch.json; logos_run NAME.systema-batch.json runs it, and its exit code says whether every step passed.

Faster

  • Sweep / Monte Carlo, Batch, Sensitivity and Optimise use every core better. The answers are the same to the last digit on any number of cores. On our 16-core test PC: a small model’s 512-run sweep 0.74 s -> 0.26 s; a large model’s 32-run sweep 74 s -> 54 s; a Nelder-Mead optimisation 1.6 to 2.6 times sooner. A medium fluid network’s sweep was already near what the PC allows and is about as before.

New — AMD Artix-7 in the FPGA tool

  • The XC7A35T, 50T, 100T and 200T at speed grades -1, -2 and -3: the 7-series fabric (LUT6, block RAM, DSP48E1, clocking), its resources and timing from AMD’s data sheets, and 18 packages with full pin tables. The circuit board’s bank check uses them. The net and carry delays, which AMD’s data sheet does not give, are estimates, and the tool says so.
  • A new design from a part number takes the grade and package it names.

The V&V deck and the other decks

  • More deck rows explained: the windage and a compressor row are now EXPLAINED with the sources’ own scatter; a compressor test now runs on the rig’s own diffuser. No answer of LOGOS moves.
  • The security deck and the training deck cover 1.8.1 (Help > Decks (PDF)).

Our services (nothing to do)

  • The LOGOS Licensing Service now runs on .NET 10.0.15 in its own private network, with its keys closed to everything but the service. Its name, licensing.logosmodular.com, is unchanged; its IP address changed on 18 November – a firewall rule written by IP address must be changed to the name.
  • My Account has tighter checks on who can see a LOGOS Server organisation’s setup codes and recovery codes.

For your IT

  • A file on another computer: the policy OpenNetworkFiles = 0 (HKLM\SOFTWARE\Policies\LOGOS) turns such opens off. Blocking outbound SMB (TCP 445) and WebDAV to the Internet closes the same door for every program.
  • File shares, SMB 3 and encryption: the LOGOS Server reads the SMB dialect and encryption of each share its data and pools are on, shows them in the web console (Settings > File shares), warns below SMB 3.0 or unencrypted, and logs Windows events 1006 / 1007. server.json "requireSmb3Encrypted": true makes it a rule: the server does not start with such a share. The security guide has Microsoft’s commands to require SMB 3 and encryption.
  • The AI link: tools take --link-file (or --link - on standard input); --link on the command line still runs, with a note.
  • DLL search: every program, tool and the LOGOS Server loads DLLs named without a path only from its own folder and System32.
  • Files: a model or design on LOGOS 1.8.1’s methods is refused by 1.8.0, in words (open it in 1.8.1).
  • The update guide has a new “Before you start”, with the commands written out: Updating LOGOS.

LOGOS 1.8.0 — 18 November 2026

Priority: Moderate — install it with your next planned update. Two-phase flow in Systema, LOGOS 1.8.0’s calculation methods, named and floating seats on the LOGOS Server, your organisation’s own library of parts, a LOGOS Server that says plainly when it cannot reach the licensing service, and cleaner screens throughout the detailed designs and tools.

Saved answers: a model or design saved by 1.7.x keeps its answers. The new calculation methods (LOGOS 1.8.0’s methods) are taken only when you choose Bring up to date, which shows what moves for that model or design before it moves anything. Every sample LOGOS ships is on the newest methods, with the results this LOGOS writes.

Data: every file 1.7.x saved opens with the same contents; the LOGOS Server’s data is kept. Update the LOGOS Server to 1.8.0 before you use named seats. Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT. The notes for your IT are at the end.

New — two-phase flow

  • A volume can go into the saturation dome: on a fluid with a pressure-enthalpy table (CO2 has one, LOGOS:CO2_ph), a Volume with its energy balance on holds its mass and energy exactly and goes into the dome as a homogeneous equilibrium mixture, its quality a result, and on through the critical point without a stop. Checked against CoolProp.
  • The flashing orifice: an orifice or valve on such a volume takes the mixture’s flow, choked at the homogeneous equilibrium critical flow, with energy balanced exactly.
  • The two-phase pipe: a pipe on such a volume takes two-phase friction (Lockhart-Martinelli with Chisholm’s multiplier, or homogeneous).
  • A gas compressor whose inlet goes into the dome stops the run there, saying which compressor, when, the inlet’s state and what to change. Going from gas to supercritical and back never stops it. A pump’s or compressor’s model with a two-phase inlet is for a later release; until then such a machine is named after the run.
  • Faster two-phase runs: a model whose volumes go two-phase, many times slower in testing, now runs at about the speed it has on 1.7.0’s methods.

New — the LOGOS Server and your licence

  • Named and floating seats: on the new Team and Enterprise terms the administrator names each Full seat to a person (Seats & sessions > Named seats); others take a floating seat when one is free. A licence from before keeps every seat floating until it is renewed.
  • Your server says when it cannot reach the licensing service: as before, it keeps working for 14 days and recovers by itself. Now each failure is said in plain words, a refused sign-in says the licence has not ended, and an air-gapped server is warned 30 days before its licence file ends.
  • Three days’ notice: in the last 3 days before sign-ins would stop, every program shows a banner. An administrator whose server clock ran ahead can now say The clock was wrong in the web console.
  • Lost your only server administrator? Your licence holder asks for a one-time recovery code in My Account, and a Windows administrator on the server machine uses it. The console now warns while only one administrator can sign in.
  • A newer LOGOS on your server: when your server’s Get LOGOS page offers a newer installer, the programs show a quiet line saying so. Nothing is downloaded or installed by the program.
  • Moving the server to a new machine now goes through cleanly: the export makes its folder, and each step says in plain words what is wrong and what to do.
  • Classifications: only a pool’s Owner raises its classification or sends elements up into it; only the administrator lowers a server’s pool (a pool file: its owner). A send says first exactly what it will do, can be undone the same day, and Clean up copies takes out copies left by an earlier send.
  • Your organisation’s library of parts: part variants with your own values and locked inputs, sealed blocks, equation parts, tables and design presets, kept on your server. An item marked a trade secret keeps the model in your organisation’s pools.
  • Confidential feedback: a bug report or request can go to your own server’s web console only.

What Bring up to date moves (LOGOS 1.8.0’s methods)

A model or design on LOGOS 1.7.0’s methods or older is unchanged.

  • A compressor’s vaned diffuser: its channel’s efficiency from its own geometry (given its vane count), and a loss for incidence and stall toward surge.
  • The Seal part’s face seal on a 75 micro-inch film, and its serpentine seal’s drag per psi from a contacting face seal.
  • A Piston’s o-ring friction on Parker’s own formula (the friction doubles).
  • A labyrinth seal design’s stiffness and damping by two control volumes a cavity, closer to measured seals.
  • A Stress part’s fatigue line, where no S/N curve is given for the metal, from Shigley’s Mechanical Engineering Design, with new surface and reliability inputs.
  • Real-gas volumes on mass and energy, flashing orifices and two-phase pipes, where a model has them.
  • Where a default changes, a value you typed yourself is kept.

Easier to use

  • Help > Licence shows your organisation, your seat and the licence term when you sign in to a LOGOS Server.
  • The AI link gives the AI tool its own credential for that link’s pool, so the command-line tools run as you without your password; signed-in server users are no longer told the PC has no licence.
  • Units and numbers: one unit for each quantity in a design, four significant figures, pressure drops in psi, the failing checks listed first.
  • Drawings and toolbars: one header and toolbar style in every design and tool, DESIGN and ANALYSE as each page’s run button, a design that fits a 1280 x 720 screen, clearer bearing, gear and board drawings.
  • The 2-D plots page shows exactly the grid you choose, one plot a cell.
  • The V&V deck is on LOGOS 1.8.0’s methods, and marks each significant deviation FIXED, PARTLY, EXPLAINED or OPEN by release. Help > Decks (PDF).

For your IT

  • Update the LOGOS Server first. A 1.7.0 server reads a licence on the new terms as all floating seats (it keeps working); update it to 1.8.0 before you use named seats.
  • Files: a model or design on LOGOS 1.8.0’s methods is refused by 1.7.x, in words (open it in 1.8.0).
  • The licensing service unreachable, the clock, a lost administrator: Updating LOGOS, sections 8 and 9.
  • Tamper evidence: the programs and the server check their own files are the ones LOGOS Modular Systems signed; a failed check never touches your models, pools or settings. An online LOGOS Server tells LOGOS Modular Systems at its daily licence refresh which check failed and when (the kind of check, the first and last time, how many times), never names, accounts, models or pool data; an air-gapped server puts it in the licence report sent at renewal. Privacy.
  • The AI link’s credential needs a LOGOS Server 1.8.0; with an older server, sign the tools in from a terminal.

LOGOS 1.7.0 — 16 November 2026

Priority: Moderate — install it with your next planned update. Engineering drawings from the mechanism tool and a full drawing package for circuit boards, a circuit solver and an FPGA tool for the board, a gearbox design that picks its arrangement, a rotor balance grade, and every design and tool on one tab layout that can come off into a window of its own.

Saved answers: a model or design saved by 1.6.x keeps its answers. The new calculation methods (LOGOS 1.7.0’s methods) are taken only when you choose Bring up to date, which shows what moves for that model or design before it moves anything. Every sample LOGOS ships is on the newest methods, with the results this LOGOS writes.

Data: every file 1.6.x saved opens with the same contents; the LOGOS Server’s data is kept. Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT. The notes for your IT are at the end.

New — drawings and the circuit board

  • The mechanism tool’s engineering drawing: a framed sheet with your organisation’s title block, SECTION A-A of each housing and the end view, strokes and springs dimensioned, balloons, and the parts, springs, seals and ports tables from the design. Export to PDF, SVG or DXF (in or mm, at true size).
  • The circuit board’s drawing package: fabrication (with the drill table and the stack-up), assembly (with numbered assembly notes from IPC and J-STD standards, from your own inputs; a value you have not given is said so, never made up), a schematic by functional group, and the pick and place / BoM. One PDF, a sheet as PDF or DXF, the pick and place as CSV.
  • The board for other ECAD programs: a KiCad 7 board and schematic (which Altium Designer’s Import Wizard reads), IPC-2581 rev. C, an EDIF 2.0.0 netlist and the schematic as PDF and SVG, beside the Gerber and drill files.
  • The board drawn by hand or automatically: drag parts onto the board, connect, route with vias, with a live DRC; automatic placement and routing finish the work around what you lock.
  • The circuit solver: the board’s DC operating point, each signal path checked (also at the worst of a Monte Carlo over tolerances), Bode plots and transients, with the board’s copper as parasitics. Its reduced model runs in Systema’s new Circuit part (half bridge, buck, boost, H-bridge, three-phase inverter, rectifier, regulator, signal conditioner, comparator), which replaces the Half bridge with every answer the same.
  • Design the circuit from the signals: give each signal path’s input and output and LOGOS chooses and sizes its parts, from your own parts catalog when you ask (imported from CSV or Excel; LOGOS ships no maker’s catalogue).
  • The FPGA tool: the logic in an FPGA on the board as blocks on a canvas, simulated cycle by cycle, its resources estimated (Microchip IGLOO2 or a generic device) and checked, written out as VHDL-2008 with its testbench. Open it from the FPGA part on the board.

New — machines and rotors

  • The gearbox, its arrangement chosen: a simple pair, a jackshaft, simple or compound planetaries, or two in series; the automatic design tries every arrangement that gives the ratio and keeps the lightest, the most compact or the most efficient, side by side.
  • The gear pair designed whole: profile shift, the ratio as a duty column, and an automatic design that picks the teeth, helix, shift, hardness and accuracy for the least centre distance or the least mass.
  • The rotor’s balance grade (ISO 21940-11), the tolerances it sets with a Monte Carlo, and LOGOS choosing the loosest fits that meet it; a new Balance page and balance tolerances on the drawing sheet. A rotor saved before keeps its typed unbalance.
  • The rotor’s cross-coupling stability margin, checked at least 2 (API 617’s Level I screen).
  • A pump’s and a compressor’s radial load from the casing, single or double volute, carried by the rotor; a measured radial load set in a calibration replaces it. A pump now has an impeller sheet.
  • Volutes and scrolls by their roll angle, joined on a tangent, for the compressor and the radial turbine.

What Bring up to date moves (LOGOS 1.7.0’s methods)

A model or design on LOGOS 1.6.0’s methods or older is unchanged.

  • A circuit board’s reduced model, checked from its operating point.
  • Gear face widths held to AGMA’s F/d of 2 unless you give another limit; new tip and contact-ratio checks.
  • A compressor’s volute rolled over the shroud, and the radial turbine’s start from no flow.
  • A pump’s and a compressor’s radial load, so the bearings’ loads move; the rotor’s new stability check may fail a rotor whose wheels are near their onset.
  • A face seal with high-speed edges (Zuk’s test faces now within 5 % of the measured leakage).
  • A liquid Fluid block on the old default viscosity, a vessel wall’s fatigue estimate, a piston’s o-ring friction.
  • Every shipped sample is now on LOGOS 1.7.0’s methods.

Easier to use

  • One tab layout everywhere: every design and tool shows Design, Assumptions, Checks, Results, Plots and Drawings; a 2-D plot grid you choose; Export to PDF with your logo, and to DXF, which AutoCAD and every CAD program open.
  • A window of its own: drag a design’s tab off and it gets its own window and taskbar button; drag it back to dock it. Ctrl+Tab goes round the open designs.
  • The busy bar in every program, with a progress bar where the work knows how far it is, and Cancel; the window keeps working meanwhile.
  • Units everywhere in the system you choose, in words and sheets as well as numbers; lengths on drawings to fixed precision in inches or millimetres.
  • Sources shown as their citations throughout, or marked Derived.
  • The mechanism tool shows what connects to what, and a crash in a click now says what failed and keeps the program open, with a recovery copy.
  • The V&V deck now covers every detailed design and tool, and marks each significant deviation FIXED, PARTLY, EXPLAINED or OPEN by release. The decks ship with LOGOS: Help > Decks (PDF).

For your IT

  • Update the LOGOS Server first.
  • Files: a model with a Half bridge is saved as a Circuit; a LOGOS older than 1.7.0 opens it but cannot run that part (a one-way change).
  • Files: a model or design on LOGOS 1.7.0’s methods is refused by 1.6.x, in words (open it in 1.7.0).
  • The AI link: an AI tool working as its person reaches a server pool only through a link that person opens, and writes only to its own AI branch, every write audited. It is off until the administrator turns it on (Settings > AI & command line), can be barred per project, and IT can switch it off in server.json ("ai": false).
  • The AI and command-line add-on can now be given to an administrator who also works in the programs, within the licence’s places (not where the sign-in rules forbid it).

LOGOS 1.6.0 — 13 November 2026

Priority: Moderate — install it with your next planned update. New turbomachinery models (compressor stall and choke, vaneless turbines, rolled volutes, disc friction with a leak), automatic design that picks the stator and the compressor’s exit, and many fixes from a usability review of every program.

Saved answers: a model or design saved by 1.5.x keeps its answers. The new calculation methods (LOGOS 1.6.0’s methods) are taken only when you choose Bring up to date, which now shows what moves for that model or design before it moves anything. Every new option is off until you choose it.

Data: every file 1.5.x saved opens with the same contents; the LOGOS Server’s data is kept. Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT. The notes for your IT are at the end.

New — turbomachinery

  • The compressor’s surge and choke, by what sets them (LOGOS 1.6.0’s methods): the surge line is the first of the inducer’s stall, a vaneless diffuser’s rotating stall (Senoo and Kinoshita’s limit), a vaned diffuser’s stall and the peak of the pressure ratio; the choke line includes the vanes’ throat. The map draws both lines, named.
  • New compressor options: a pinched vaneless diffuser; a volute rolled over the impeller’s shroud for a smaller casing; a collector in place of the scroll; a ported shroud (casing treatment, a first cut from published data). In the detailed design, drawn, and in Systema.
  • A radial turbine with no nozzle vanes: the scroll alone sets the swirl, so the flow angle follows the operating point. The turbine’s stator is now a choice — a collector with nozzle vanes, a scroll with no vanes (outside or rolled over the shroud, its vaneless space straight or pinched), or a scroll feeding nozzle vanes; only sensible combinations are offered.
  • Automatic design picks the turbine’s stator and the compressor’s exit (on LOGOS 1.6.0’s methods), lists every choice’s efficiency and says what the comparison rests on. You can still pin your own choice.
  • A flag for scroll volutes above 3,000 psig, where the tongue’s stress gets very high — a warning, with the limit on the form.
  • Disc friction with a leak across the face: the gas’s swirl in a rotor–stator cavity now follows the flow through it — an option on the Windage part, a shrouded compressor, the pump design and the rotor tool’s cavities.
  • A compressor surge-margin check (“Surge margin at least”, 10 % on a new design), on the stage without its casing treatment.

What Bring up to date moves (LOGOS 1.6.0’s methods)

A model or design on LOGOS 1.5.0’s methods or older is unchanged.

  • The compressor’s surge and choke lines, as above; a vaned stage near its throat’s choke.
  • A compressor design on a named ideal gas takes that gas’s own viscosity (before, a design on air used a dense-CO2 value): its Reynolds number and efficiency move a little (−0.4 point on our test stage).
  • A disc face wetted only from an inner radius: its friction regime by regime (Rosset and Schiffmann 2020) — up to a few per cent less drag on a ring face.
  • The shipped compressor, turbine and rotor samples are now on LOGOS 1.6.0’s methods.

Easier to use (from a usability review of every program)

  • Systema: a typed start pressure is kept by default, and any start value the solver moves is shown on screen; a fluid network with no Fluid block is refused in words; Bring up to date and the methods dialog scroll and list each change in plain words, with the record behind “Details”; clearer Properties (the Turbine’s values show again), results and compare.
  • Detailed designs: Bring up to date shows the design worked out both ways; sources cited by author and year; gas flows in acfm; the tip-speed limit from the wheel’s material; a missing input shown as “not checked”, apart from a failure; the compressor’s flow path drawn connected.
  • Agora, Kanon and Hodos: slips and durations in working days (“wd”); Kanon shows the value a verification reached beside PASS/FAIL; LATE vs OVERDUE; “Over budget (EAC − BAC)”; a form for a new requirement; local times everywhere.
  • The LOGOS Server’s web console: People & rights reordered, searchable, with the AI add-on’s places in use; a Settings > Backup card; the audit in words with filters; usable on a phone.

For your IT

  • Update the LOGOS Server first. A 1.5.x program works against a 1.6.0 server.
  • Files: a model or design on LOGOS 1.6.0’s methods is refused by 1.5.x, in words (open it in 1.6.0). Nothing else stored changes; the server’s database is unchanged.
  • The AI and command-line add-on can now be bought or added to an existing licence (when the shop offers it); the server picks it up at Settings > Licence > Refresh now.
  • Backups: Settings > Backup in the web console shows the data folder and the backup script’s command line.

LOGOS 1.5.0 — 12 November 2026

Priority: Serious — install it within about two weeks. A security fix for the LOGOS Server (a person with no right for a program could still learn about its elements: LSA-2026-07), and fixes for input that was read wrongly or dropped without a word, so a model could give a quiet wrong answer.

Saved answers: a model or design saved by 1.4.x keeps its answers, except for the fixes named under Fixed. The new calculation methods (LOGOS 1.5.0’s methods) are taken only when you choose Bring up to date, which lists what moves before it moves anything.

Data: every file 1.4.x saved opens with the same contents; the LOGOS Server’s data is kept. Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT. The notes for your IT are at the end.

Fixed — answers that move

  • Input that was read wrongly is now read right or refused, in words. A Speed source’s mission column in rads or rad_s was read as rpm; a mission column whose unit is not of its input’s kind was taken as a number; -10 typed in a field shown in K was taken below absolute zero; a parameter that holds no number (empty in the file) fell back to another number without a word. A unit written in a mixed case (mPa, Mbar, Mm) is read as the unit meant (MPa, mbar, mm) and the log says so.
  • A reservoir wired straight onto a Volume, or onto another reservoir, is refused – the second was dropped without a word, so the tank did nothing.
  • Impossible numbers are refused when the model is built, naming the part, the value and what it may be: a negative orifice area, a mass of 0, a gas’s gamma of 1 or less (it was raised to 1.001 without a word). A value the options chosen do not use (a perfect gas’s cp) is only noted. A discharge coefficient above 1 is built, with a note.
  • Hodos schedules where they were wrong: a milestone with nothing before it now sits at the project’s start (not the Friday evening before); a calendar’s shifts written afternoon first are read right; a trip’s actuals are counted once in the EAC; impossible dates and negative durations are refused.
  • Kanon: a cancelled check-out can no longer blank a requirement’s PASS; several new requirements saved at once are all stored.
  • The example hydraulic_accumulator keeps its accumulator’s starting pressure, 300 psia (it fell to 14.7 psia at the start; from 0.2 s on the run is within 0.01 psia of before).

What Bring up to date moves (LOGOS 1.5.0’s methods)

A model or design on LOGOS 1.4.0’s methods or older is unchanged. A new one starts on 1.5.0’s methods.

  • The rotor’s thrust balance counts the shaft’s own steps, each at the pressure of its zone of the secondary flows (the example rotor reve_tac1: net thrust -842.8 -> -1,418.3 lbf). On a rotor whose steps sit in its bearings’ drains this can be thousands of lbf, and a thrust check can change from fail to pass or the other way.
  • Ball bearings: the load factors X, Y by ISO 281:2007 (the default 6206: equivalent load -1.32 %, L10 life +4.08 %).
  • A helical gear pair’s churning on the transverse pressure angle (+0.18 % at a deep dip; the defaults do not move).
  • Disc friction: Schultz-Grunow’s laminar constant 2.66 as printed (0.37 % on a laminar disc only).
  • A finned tube’s film between Re 1000 and 4000, a face seal’s film leak by one law, a bearing in an oil mist on the oil’s own viscosity, a compressor design on a property table with the table’s viscosity.
  • A Volume is solved down to 0.0005 psia (was 0.5 psia); a real gas stops at its property table’s lower edge, and says so.

New

  • Axial thrust through a transient: Systema’s Turbine and Compressor can push the rotor and its thrust bearing (opt-in: thrustRule 1), so a start, a trip or a stop shows the thrust bearing’s load. The rotor tool’s Apply fills in the values they need from the rotor’s seals and shaft (check each wheel’s eye direction if your plant’s axial mass is drawn the other way round).
  • A model that goes wrong says where and why – in the window and in logos_run: what stopped it, why, the parts to look at (only those on that port’s side), and what the build said. A part that switches back and forth is reported as chattering; a signal loop with no state is named.
  • Every choice is picked in words, not typed as a code – in Systema, the detailed designs, Kanon and Hodos – and each start type says what it does. Nothing stored changes.
  • Detailed designs: the same panels in every design, the Design panel first; each reference beside the line it supports; machines’ iron and windage losses and the rotor’s gear meshes carried to Systema; Bring up to date names a part whose values came from a design on older methods, and what to do.
  • Kanon: documents and reviews as verification evidence, codes and standards cited by their clauses, several products in one pool, when verification is planned; Verify > Find orphans; derive loops refused, naming the chain; draft requirements may be released, marked DRAFT.
  • Hodos: the BOM’s production in the plan as linked rows; a Travel page (flights, hotels, cars and meals as one plan line); notes as a flag on their rows.
  • The pool: only Owners see the audit log, and only an Owner checks in or cancels another person’s check-out; a cancelled check-out takes its own links with it; reconciling onto a version approved meanwhile makes the next revision.
  • The command-line programs check every number they are given and refuse an option they do not know (exit 2): check your scripts for misspelled options.

Security fixes (Medium)

  • LOGOS Server: a person with no right for a program learned about its elements (LSA-2026-07). Such a person never received the elements, but did receive their links, the audit rows and commits about them, and check-outs, branches and files that were theirs, and could link to them. Every read is now filtered by the same rule as the elements.

For your IT

  • Update the LOGOS Server first. The security fix is in the server; a 1.4.x program works against a 1.5.0 server.
  • Rights: after the update only Owners (of LOGOS Agora, or of all programs) see the audit log, and only an Owner checks in or cancels another person’s check-out. A person with no right for a program is told “there is no such element” about its elements, as about one that does not exist.
  • Files: a model or design on LOGOS 1.5.0’s methods is refused by 1.4.x, in words (open it in 1.5.0). Nothing else stored changes; the server’s database is unchanged.
  • Scripts: the command-line programs now end with exit code 2 on an option they do not know.
  • Moving the LOGOS Server to another machine works from 1.4.1 to a new machine on the same release or newer: Updating LOGOS — for your IT, section 6.

LOGOS 1.4.1 — 11 November 2026

Priority: Serious — install it within about two weeks. Hodos gave a deleted task’s ID to the next new task, so board cards, risk steps, milestones and pool links still naming the old task went to an unrelated one. That is fixed, with LOGOS Server fixes from an install test and security hardening.

Saved answers: no answer of any model or design moves. Plans keep their task IDs; no saved plan’s schedule moves.

Data: every file 1.4.0 saved opens with the same contents; the LOGOS Server’s data is kept. Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT. The notes for your IT are at the end.

Fixed

  • Hodos: a deleted task’s ID is never given to a new task (Serious). A new task’s ID is now one past the highest ever used, also after saving and opening the plan again. “ID” in the task table and the Gantt is now “Row” (it is the row number and always was); a new Task ID column shows each task’s ID that never changes. Finish can be typed, and the actual duration is worked out.
  • Kanon: Link… > Verified by lists the verification records (a recorded PASS or FAIL), as the help says.
  • LOGOS Server: going back to 1.4.0 after an update failed as the guide described it – the guide now gives the steps an install test proved; and the other faults that test found.
  • The administrator’s two-step sign-in on an HTTPS server: the refusal says what waits for it.
  • Bug reports and feature requests (Help > Report a bug) now reach our support mailbox.

New

  • Moving the LOGOS Server to a new machine: one encrypted bundle (--export-move, --import-move) carries the whole server, its sealed secrets sealed again for the new machine, and the audit unbroken; the old server will not start again. Updating LOGOS — for your IT, section 6.
  • Signed organisation files: the LOGOS Server signs every organisation file it makes, and each PC refuses one signed by another key or changed after signing.
  • The Windows Event Log and an access log file for the LOGOS Server, and an alert when the audit export fails.
  • Start from the results at a time, with the missions continued (Run > Start from the results at a time…).
  • The methods are named by release (“LOGOS 1.4.0’s methods”, not “methods 4”); Agora’s Reconcile window shows the links each side added or removed; detailed designs show every detail their Systema part works out; a planetary reducer example in the rotor tool.

Security fixes (Medium)

  • The LOGOS Server’s service runs as its own account, NT SERVICE\LOGOSServer, and its data folder is open only to it, SYSTEM and the Administrators (it ran as LocalService, an account other services share).
  • The LOGOS Server’s port is its own: no other program on the machine can bind it while the server listens.
  • The licensing service hardened, and the programs trust a second licence signing key ahead of a key change.

For your IT

  • Update the LOGOS Server first. A 1.4.0 program works against a 1.4.1 server.
  • The service account changes to NT SERVICE\LOGOSServer at the update; the server’s data and sealed secrets move with it. Going back to 1.4.0: follow Updating LOGOS, section 4, in its order.
  • New server settings: "eventLog": false turns the Event Log off; the access log file’s days and size.
  • Two new policies for organisation files: RequireSignedOrgFiles and OrgSigningKey.

LOGOS 1.4.0 — 7 November 2026

Priority: Critical — install it within days. A 2-pole synchronous reluctance machine designed with its iron’s saturation (a lamination’s B-H curve) could be reported “not salient”, or worked out to an efficiency of nothing, and the design still ended as if it had worked. That is fixed, and a machine that cannot make its torque is now refused, saying why (below). Two Serious fixes and security fixes come with it.

Saved answers: a model or design saved by 1.3.0 keeps its answers, except for the fixes named under Fixed. The new calculation methods (level 4) are taken only when you choose Bring up to date.

Data: every file 1.3.0 saved opens with the same contents; the LOGOS Server’s data is kept, and a few things are added to it that a 1.3.0 server ignores. Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT. The notes for your IT are at the end.

Fixed — answers that move

  • A 2-pole synchronous reluctance rotor with a B-H curve (Critical). The saturation step put each flux barrier’s opening on the wrong side of the pole, so the machine came out “not salient”. Fixed (4 poles and more are unchanged to the bit), and such a rotor is now refused in words: with a shaft of 0.6 of its radius its iron cannot carry the d flux. The field solution agrees: 17 N.m of the 500 N.m the linear sizing promised. A design that cannot be worked out, has no efficiency, is not salient, or whose rotor iron cannot carry its flux now fails its checks, and logos_elementa run ends with REFUSED and writes no parameter set (it ended with a note and wrote one).
  • A machine’s parameter set no longer removes the part’s iron loss (Serious). A synchronous reluctance design with no iron loss of its own wrote a zero iron-loss resistance into its parameter set; applied, the Systema part lost its own iron loss without a word (on one plant +87 kW net). It is now left out, so the part keeps its own.
  • A run time written as [900, "s"] is read (Serious). It was taken as absent and the run lasted 1 s; it now runs 900 s, and a run time that cannot be read is said.
  • The heat exchanger’s gas radiation (Moderate). Its two emissivity tables were interchanged. Against Hottel’s charts at 1273 K: 0.182 -> 0.167 (chart 0.144). Only a side with gas radiation on (off by default) moves: a few tenths of a W/(m^2.K).
  • Systema’s steady start no longer takes a state stopped against its limit. A gas volume between two orifices could start at 10,000 F with no flow; it now starts at 100 F with 0.1369 lbm/s, the hand answer.
  • Large machines: a shaft’s torque is no longer stopped at 1e6 – 1e8 in.lbf (a 100 MW train carries 3e8); models that stopped at the start now run.
  • The rotor tool checks a book-rule rotor’s barriers by the design’s own rule (four rotors 0.736 FAIL -> pass).
  • Kanon: the next revision of a release with attribute columns no longer lists every requirement as changed; a Word release whose title holds a column’s word no longer reads its cover as requirements.
  • Agora’s Comments tab of a model lists the comments on its parts and parameters too, with a link that opens the model in Systema at that part.
  • A mechanism’s step run that stopped is run again with a finer step; RESULTS > compare overlays a CSV whose parts’ names carry brackets; a program started with no screen stops and says what it needs instead of waiting for ever.

What Bring up to date moves (methods 4)

A model or design on methods 1 to 3 is unchanged. A new one starts on 4; Bring up to date (in the window, or logos_elementa methods from the command line) lists each change for the parts the file has.

  • Systema’s steady start: the homotopy pulls toward the start value instead of away from it (122 of 146 starts reached, was 107); a closed gas leg keeps its charge (two tanks at 3000 and 14.7 psia: not reached -> 1507.35 psia).
  • The gearbox’s churning chosen by the immersion depth, blended smoothly (Leprince’s shallow-dip law; the default box 99.2 -> 37.7 W at 6000 rpm, nearer the measured).
  • Ball bearings: the operating clearance in the load zone, the life and the stiffness (Harris; one 6206 case’s life 15,899 -> 13,751 h); a duplex pair’s preload at the duty from its fits, temperatures and the shaft’s growth; the heaviest ball under a combined load. Only bearings given a play, a fit or a temperature move.
  • Tilting-pad journals at each mode’s own whirl frequency in the rotor’s damped analysis (checked against Cloud, Maslen and Barrett 2012).
  • The rotor’s torsion: a mode inside its separation margin passes when its forced stress is within the allowable (API 684’s route).
  • Synchronous reluctance machines: a magnetic shaft’s credit; a 2-pole rotor’s barriers as the flux lines past the shaft (18.1 -> 65.0 N.m on the field solution); a form-wound machine’s end windings worked out as wound; the ribs and the bore checked against the lamination’s yield; the Systema part’s two-axis saturation fitted to the maximum current, with flux maps.
  • The radial turbine’s exit swirl from its blocked exit throat (now near NASA’s measured surveys); the compressor’s inlet guide vanes by Aungier’s axial-cascade method; a heat exchanger’s dimples at the plain passage’s friction.

New

  • Start a model from its results at any time — Run > Start from the results at a time…, or right-click the plot: every state starts from the run at that time (also logos_run --start-from).
  • Agora’s Reconcile window shows what each side changed — for a model by part, each parameter old and new in your units; for a Hodos plan by task name (durations, constraints, resources, links by the linked tasks’ names, and where the scheduled dates move); for a Kanon requirement by ID and title (its text word by word, attributes; trace links are not merged in this window). A conflict is marked and must be picked, change by change or a whole side, before Reconcile.
  • Comments and Hodos cards in Slack and Microsoft Teams, from the LOGOS Server, with Slack replies coming back as comments; only Open data unless an administrator raises a project’s level (twice-confirmed for ITAR/CUI). Off for the whole server with one setting.
  • An individual licence — one person, every program on one Full seat; on the LOGOS Server an administrator account and a work account kept apart (CMMC 3.1.5, 3.1.6), one email address for both. In beta: ask us. Any organisation can now give an account a plain username with its email address kept apart.
  • New parts: the Combustor (fuel and air in, the products out; checked against CoolProp’s flame temperatures); the wound-field synchronous machine with its field winding, dampers and saturation (checked on Krause’s 325 MVA generator); the Jet pump; the Bootstrap accumulator; Linkage, Four-bar, Lever and Cam parts; friction that sticks and slips.
  • New designs: the axial compressor, the axial turbine and the axial pump, row by row at the mean line; the interior permanent-magnet and the wound-field synchronous motor/generator; the gear pair (AGMA 2001 or ISO 6336), applied to the Gearbox part and rated in the rotor tool’s gear train, with a planetary stage.
  • The mechanism tool, finished — drawn to scale and moving; levers, cams, shafts, cranks, lead screws, racks, four-bars, steppers, flow forces, seals and springs under load, wear.
  • The air release check: a liquid that falls below the pressure its air was dissolved at is flagged after the run (no answer moves).
  • A motor’s thermal network on the rotor’s secondary flows, solved together; a tilting pad’s pivot stiffness; Hiperco 50’s stator grade at 0.1 and 0.15 mm; optional loss sets from Aungier’s books for the radial turbine and the meanline compressor.
  • Saved plots and a fine-output window (a motor’s phase waveforms without aliasing); the flux-density map on a colour scale you set; the rotor canvas picks a part hidden under another; each clearance’s margin as a share.
  • Kanon by script: a “Derived from” column makes the links; kanon_release releases from the command line.

Security fixes (Serious)

  • Copying up is checked by the server itself: a bundle’s data level is trusted only from the server’s own seal, so a changed client can no longer copy higher-level data into a lower pool.
  • A served pool’s audit chain is keyed by the server (HMAC-SHA256), as the server’s own audit already was.
  • The identity provider’s secret is sealed with this installation’s own key material, not a fixed one.
  • A password the administrator sets must be changed at first use (CMMC 3.5.9); an optional setting links first sign-ins through the provider only by the administrator; pool files are taken only from the server’s pools folder and opened in SQLite’s defensive mode; sign-ins from one address are limited; a licence’s end cannot be brought back by setting the clock back. The SBOM now lists the CoolProp property tables.

For your IT

  • Update the LOGOS Server first. A 1.3.0 program works against a 1.4.0 server, with two exceptions: a person cleared above Open who copies into a lower pool must use 1.4.0; and a copy of a served pool opened directly by 1.3.0 calls its keyed rows changed.
  • The server’s database gains an email column and four tables for chat; a 1.3.0 server opens it. The identity provider’s secret is sealed again on first start, so a server put back to 1.3.0 needs that secret entered again.
  • New server settings (server.json): "chat": false turns Slack and Teams off for the whole server (do so on an air-gapped server); "allowPoolsOutsideRoot": true allows pools outside the pools folder (those registered before stay).
  • Files: a model or design on methods 4 is refused by 1.3.0, in words (open it in 1.4.0). A model with saved plots opens in 1.3.0 without them (saving there drops them). A heat exchanger side set to the new “bumps” option reads in 1.3.0 as another option: keep such a file to 1.4.0.
  • A security deck for IT directors and security leads comes with the documents: every connection, what leaves the network, CMMC Level 2 / NIST SP 800-171, and an onboarding checklist.

LOGOS 1.3.0 — 29 October 2026

Priority: Serious — install it within about two weeks. It fixes results that could be wrong without a word: a property table read past its pressure range, a results file’s rows between the solver’s steps, an AC source in a circuit with no state of its own, and a ground placed away from zero (below).

Saved answers: a model or design saved before 1.3.0 keeps its answers — except for the fixes named under Fixed. Newer calculation methods are taken only when you choose Bring up to date (below).

Data: your models, designs, plans, pools and the LOGOS Server’s data are kept; nothing is converted when it is opened. Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT. A 1.3.0 program works with a 1.0.0 or 1.2.x LOGOS Server.

Saved work keeps its answers: the methods level

  • Every model and design now records the calculation methods it runs on (its methods level). A file saved before 1.3.0 is on level 1 and gives the same answers as before, to the bit. A new model or design starts on the newest level, 3.
  • Bring up to date (Systema: Model > Bring up to date…; a design: Design > Bring up to date…) lists what would move and why, only for the parts the file has; for a design it works it out both ways and shows each check that moves. Nothing moves until you say so (in Systema, one Undo takes it back).
  • A file on a level newer than the program is refused in plain words (LOGOS 1.2.1 already does this; 1.2.0 and older would ignore the level, so open such files in 1.3.0 or later).

What Bring up to date moves (methods 2 and 3)

Each was checked against its published source or measured data; the old -> new numbers are in the full notes.

  • A pipe on a perfect gas takes that gas’s own viscosity, not air’s: a laminar hydrogen line was 51 % off, now within 0.03 % of Hagen-Poiseuille with CoolProp’s viscosity.
  • Windage: a CO2 machine takes Saari’s law by default (Miller et al.’s CO2 motor-generator: +32 % -> -6 % of the measured loss); law 0 takes its Reynolds number on the gap, as printed.
  • Rolling bearings’ friction is SKF’s model as SKF prints it, by the bearing’s series (new inputs: C0, the lubrication, the oil level).
  • The meanline compressor near surge: the inducer’s stall sets the surge line where it comes first (Sandia’s sCO2 compressor: 0.98 -> 1.53 kg/s, inside its measured line); a compressor design’s surge margin agrees.
  • The labyrinth seal’s leakage by Vermes’ own carry-over, the last tooth choked (+1 to +3 % on typical seals, more for a seal of few teeth).
  • The radial turbine’s Reynolds term below Re 100,000 and on the nozzle (NASA’s turbines: efficiency’s rise with Reynolds number 4.3 points against 4.4 measured, was 2.2), and an ideal gas’s own viscosity.
  • The dynamic pump’s head no longer drops above the NPSH at which cavitation starts.
  • The SR motor on Miller’s inductance profile; the battery on a measured cell’s voltage curve (Plett).
  • Every row of the results a consistent point of the model (every balance holds at every row, not only at the solver’s steps).
  • The rotor tool: the clearance budget (each turbomachine’s gap against the bearings’ clearances, the sag, the orbit and the growth, with rub checks); a pump’s impeller thrust and a fixed-pad thrust bearing at the rotor’s net thrust; a damped mode’s x and y pair listed twice, as it is.
  • Elementa: Inconel 718’s expansion and its 1200 F strengths from MMPDS-2026; a synchronous reluctance machine sized with its iron’s saturation.

Fixed (every file, not versioned)

  • A property table read past its range is said — in temperature and pressure, after the run (or the run stops, a setting). A CO2 vessel heated past its table’s 5000 psia had run 31 % low in pressure with nothing said.
  • A model file with no library section (written by a script) now runs its liquid as a liquid; a fluid table that cannot be found is refused, naming it.
  • Outputs between the solver’s steps are worked out from their own equations: a Divide through zero had read 30 % off at those rows, and logic outputs now read exactly 0 or 1. Only results-file rows between steps move.
  • An AC source holds the solver’s step to 1/40 of its period: a 480 V source into resistors had rows up to 647 V off; now within about 1 V.
  • A ground placed away from zero is where it sits (a spring from it pushed 100 lbf where it should push none).
  • Drop-down highlights are readable (dark text on the gold); a maximised window no longer runs under a laptop’s taskbar.

New in Systema and the detailed designs

  • The mechanism tool — a valve or actuator laid out, analysed (operating point, modes, frequency response, step, margins, leakage, wear) and placed on the canvas as a block of Systema’s parts.
  • The Stress part — a cylindrical shell, sphere, head or flat plate under pressure, temperature and loads, against its material at temperature or the ASME Code’s allowable, with buckling and fatigue.
  • New designs: the cage induction motor/generator (with its field solution and torque-speed curve) and the switched reluctance motor/generator; an inducer on the centrifugal pump.
  • The motor drive: Basic or Detailed — six-step, sine PWM and field-oriented control, with field weakening, the devices’ losses and the drive’s signals as results; an induction motor’s double cage for starts.
  • The rotor tool — a components window with select, change, move and Undo; each part’s body from its own design, drawn as it is; joints, preloads, chamfers and materials; torsion and a gearbox’s torsion and lateral coupling; g-load, vibration and shock studies; secondary flows on Systema’s own fluid parts, with each cavity’s windage.
  • Motor designs — editors with MWS magnet wire, shipped laminations (M19, Hiperco 50, Metglas, Somaloy, HyMu 80), the stator tooth in detail, end turns drawn as wound, wye or delta; the field solution in the background (a motor’s design that took 25 s to open now opens at once).
  • UN inch threads for bolts; splitter blades on the radial turbine; the programs carry the Compass mark.

Working from a LOGOS Server

  • The window stays responsive for check-out, check-in, Save, the library and the sign-in, not only for open and save.
  • Hodos saves to a server pool in a handful of requests — the first save of the example plan 326 -> 8 requests (139 s -> 2.6 s over a slow VPN). The pool holds exactly what it held before.

LOGOS 1.2.1 — 27 October 2026

Priority: Moderate — install it with your next planned update. Data: no change; update the server first, then the PCs (Updating LOGOS — for your IT).

  • Turning on the inlet Mach outputs no longer moves a run. In 1.2.0 the option machOut (the inlet Mach numbers on a meanline compressor or radial turbine) was meant to add results only, but on a whole plant it could change the solver’s path, and on a plant near an instability other results moved noticeably. Now those outputs are worked out from the solved values and never take part in the solve: with the option on or off, every other result is identical to the bit. If you compared runs with and without machOut in 1.2.0, compare them again. Models with the option off (every model saved before 1.2.0) give exactly what 1.2.0 gave.
  • A file saved with newer calculation methods is refused, not run on older ones. LOGOS 1.3.0 will record which calculation methods a model or design uses. LOGOS 1.2.1 refuses a file that asks for newer methods than it has, saying so plainly, instead of quietly working it out on its own older methods – so the same file never gives two different answers on two versions.

LOGOS 1.2.0 — 27 October 2026

Priority: Moderate — install it with your next planned update. Saved answers: no model’s or design’s answers change. Everything new is an option, a new screen or a new part. Data: your models, designs, plans, pools and the LOGOS Server’s data are kept; new kinds of records are added alongside (a 1.0.0 program simply ignores them). Update the LOGOS Server first, then the PCs: Updating LOGOS — for your IT.

Working together

  • A project journal in Agora — one log per project of everything that happened: comments, entries anyone writes directly, saves and what changed, check-outs and check-ins, baselines, approvals and reviews, meeting notes, and software updates. Filter, search and export it.
  • Comments on any item — a part or parameter in Systema, a requirement in Kanon, a task, risk or milestone in Hodos, any element in Agora: right-click > Comment…, or the COMMENTS panel beside it. Authors can withdraw their own; Owners can delete one (the journal keeps a line saying so). Stakeholders can comment too.
  • The suite’s link map — every link between requirements, model parts, verifications, tasks, risks and documents in one picture in Agora, with suspect links marked; focus on one item and its neighbours.
  • The organisation’s library — one list of vendors and resources (people, machines, contractors) shared by every project’s plans; everyone reads it, and those with the right edit it.

Systema and the detailed designs

  • Results kept with the model — a run’s results are saved with the model in the pool (and beside a model file), and shown when you open it, marked out of date if the model has changed since. Save named result sets, compare two, and open the model exactly as it was for a run.
  • Kanon checks on a saved result set — a requirement can be checked on a named run’s numbers; it is flagged for re-verification if that run goes out of date, is replaced, renamed or deleted.
  • Inlet guide vanes for compressors and pumps, and a variable nozzle for radial turbines — as a setting or driven by a control signal; off by default. Inlet Mach numbers on the design cards (and, as an option, as outputs of any meanline compressor or radial turbine).
  • A surface permanent-magnet motor/generator design, checked against Krause’s design case, with its own magnetic field solution (back-EMF, cogging, torque).
  • Flux-density maps of a machine’s field solution, and one colour scale with a legend and a probe on every coloured plot (film pressures, machine maps): hover to read a value, click to pin it.
  • A bearingless machine’s support spread over its stator’s length (an option).
  • The detailed design windows drawn as blueprints — grids, rulers, zone letters and a title block — and Subsystem blocks drawn as see-through 3-D boxes.
  • Materials: 15-5PH steel, more forms of Inconel 718, and 440C steel.
  • Machine operating limits — the maximum-torque-per-amp line, field weakening and the torque-speed envelope, from a machine’s field solution.
  • The sleeve’s eddy-current loss as a new output of the electrical machine designs (metallic sleeves are where it matters; a carbon sleeve’s low conductivity across its fibres keeps it small).
  • The rotor tool: the magnetic pull at the rotor’s sag in the bearings’ loads (an option); a pedestal from a measured frequency response; a housing pedestal’s base contact stiffness.
  • The radial turbine checked against NASA’s Brayton turbines with their geometry given, and NASA’s Reynolds-number correction as an option.
  • The induction machine checked against Krause’s textbook cases, and its constants can be taken from IEEE 112 test results.
  • A tie bolt with a UN thread (its stress area).

Hodos

  • Risks among the inputs; milestones and gates are now one thing (a milestone can be a review gate); tasks, risks and milestones link to each other both ways.
  • A Vendors page — contacts, NDA status, capabilities, certifications (ISO, AS9100, NADCAP, ITAR, CMMC) with expiry warnings — picked by tasks, BOM lines, contracts and resources.

Working from a LOGOS Server

  • You can see when a program is waiting on the server — a thin gold bar and a status line saying what it is doing.
  • The window stays responsive during a save to or an open from the server’s pool; an open can be cancelled.
  • For administrators: a setting “administrators may not hold rights” (strict CMMC 3.1.6), off by default; a pool can be moved to another project.
  • Downloads: the server’s backup script and this IT guide now come with each release.

LOGOS 1.0.0 — 26 October 2026

Priority: Serious — install it within about two weeks. Data: your models, designs, plans, pools and the LOGOS Server’s data are kept. The server makes its own copy of its database before it first starts on 1.0.0. How to update: Updating LOGOS — for your IT.

What 1.0.0 means

LOGOS 1.0.0 is the baseline from which saved work keeps its answers. From 1.0.0 on, every change in a release is one of two kinds:

  • Update — bug and security fixes, speed, new screens and new options that change no saved answer. Every install takes these.
  • Versioned change — a change of method that moves an answer. A model or design keeps the methods it was made with until someone chooses to bring it up to date, and LOGOS shows what will move first.

Each release also says how soon to install it: Critical (within days), Serious (within about two weeks), Moderate (with your next planned update) or Routine (when convenient). Your LOGOS Server’s web console shows the priority under Settings > Updates.

Fixed

  • The mouse wheel no longer changes values nobody picked. Scrolling a window could change a drop-down, number box or date box that happened to be under the pointer, changing a model or plan without anyone noticing. A box now takes the wheel only after you click or type in it; otherwise the wheel scrolls the window. (This is why 1.0.0 is marked Serious.)
  • Agora on a LOGOS Server now lists your projects on the dashboard after you sign in, and shows a server pool’s documents (the Elements list now shows documents by default).

Faster when working from a LOGOS Server over a VPN

Opening, saving and browsing a pool on a server now takes a handful of requests instead of thousands. Measured with 60 ms of network delay each way: opening a large model went from about 10 minutes to about 4 seconds; a first save to a pool from about 4 minutes to under 2 seconds. Agora, Kanon and Hodos are faster too. Nothing about the server’s data changes.

For your organisation’s administrators

  • Several administrators, added from the web console (People & rights > Administrators). An administrator may also hold a right in a project.
  • Invitations can be sent from Gmail or Outlook on the web with one button.
  • Get LOGOS — your server can offer the LOGOS installer to your people at https://<your server>/get, with the server’s address set for them.
  • Silent updates that keep your data — both installers update in place, silently (msiexec /i ... /qn), and keep the options IT gave at the first install. A backup script for the server comes with the release.

New in the programs

  • Automatic design optimises a design at its design points for the goals you set.
  • Housings: a pressure casing design, and the housing as a rotor’s pedestal in the rotor tool (optional).
  • A second-opinion solver: any Systema run can be checked with SUNDIALS IDA (logos_run --check-solver ida).
  • SynRM field solution: an optional finite-element solution of the rotor and stator field.
  • Units: motor constants and suspension gains follow the units you choose.

Numbers that may move from 0.14.0

Before 1.0.0, LOGOS kept some older calculation methods for files saved earlier. 1.0.0 runs every model and design on today’s methods, the baseline from here on. Some 0.14.0 models and designs give slightly different numbers in 1.0.0, for example: a gas volume’s wall now takes part in its heat transfer by default, gearbox churning losses follow the published method exactly, and unit conversions use exact factors. A file that relies on a removed older method still opens, but LOGOS will not run it until the setting is changed, and says exactly which part and setting to change. Re-run your key models after updating and compare.