Skip to content

OpenECraft 0.1.2

Latest

Choose a tag to compare

@github-actions github-actions released this 15 Nov 12:12
· 5 commits to master since this release
Immutable release. Only release title and notes can be modified.
5ac04ff
  • Website with live demos: website/ is a page that presents the project and
    runs it: the schematic editor and the panel in 3D as canvases, the project check,
    the reports, a console with the commands of the command line and the exports, all
    on one example project in the browser, in the 20 languages of the editor. It is
    deployed as static files (cd website && trunk build --release) or with the Docker
    image ghcr.io/nilres/openecraft-website, which serves the web editor at /editor/
    as well (website); where the links of the page lead (web editor,
    repository, downloads, documentation, issues) is set in config.js or with
    environment variables of the image (OPENECRAFT_EDITOR_URL, …). The 3D routing
    of the examples comes with the page; that of a changed project is searched in a
    worker, so the page stays usable meanwhile. The demos are the editor's own code: its
    shell tables, document state and drawing views moved into the library crates
    openecraft-shell, openecraft-session and openecraft-canvas.
  • Legal notice on the website: the operator of a site sets a legal notice
    (Impressum: name, address, email, phone, representative, register entry, VAT ID,
    responsible person, further text) in legal of config.js or with the variables
    OPENECRAFT_LEGAL_… of the Docker image; the footer then links to it, labelled in
    the language of the page (website). The image
    writes config.js with a start script, so any character is allowed in a setting.
  • Website for search engines and link previews: the page has Open Graph and
    Twitter card tags, structured data (SoftwareApplication), a translated title,
    texts for the pictures of the gallery, which are WebP files of a fourteenth of the
    size of the screenshots, and headings in order. With its public address
    (OPENECRAFT_SITE_URL of the Docker image, or installer/docker/website-site.sh
    on a page deployed by hand) it gets a canonical address, a preview image for links,
    a sitemap and a robots.txt naming it
    (website).
  • Automatic saving of shared projects: a project opened from the project server
    is saved to it by itself, 30 seconds after a change and every 30 seconds while the
    work goes on (Settings › Servers or the Project server pane: on / off, 10 to
    600 s). Unfinished drags and text inputs are not sent, saves run one at a time and
    release no locks; Ctrl+S still saves at once. The status bar and the pane show
    Saved, Not saved yet, Saving…, Waiting for the server, Save failed and
    Partly saved apart, with the time of the last save the server confirmed. During
    an outage the changes wait, the local recovery copy is written at once (and named
    only once it is written) and the save follows when the session goes on
    (project server).
  • Properties and copies of server projects (#186): the project list of the
    Project server pane selects a project; Properties… shows its properties as
    saved on the server and changes them without opening the project (for who may
    change the project data, while nobody has locked it; only the properties are
    written, never the whole project). Copy project… shows the properties of the copy
    at once: a free name on the server and the title, description, company, author,
    date, revision and project properties of the original to adjust; Create and open
    creates the copy from the saved state and opens it, Cancel leaves nothing on the
    server. The original, its sessions, locks and access rights stay untouched; the
    copy belongs to who created it and starts without the original's review records,
    released revisions and baselines unless asked for. Unsaved changes of the open
    project are asked about first; a project changed on the server meanwhile is
    reported before the copy is made. The server records the project and revision a copy
    was made from. Needs the updated project server.
  • View cube in the 3D views: the 3D view of the panel layout shows a view cube
    in its top right corner and an axis triad (x red, y green, z blue) bottom left. A
    click on a face, edge or corner of the cube turns the camera to look from there
    (26 views, the corners isometric), a drag on it orbits; its buttons turn the view
    by 90°, go back to the starting view or show everything. It replaces the buttons
    of the standard views. The 3D previews of parts (part editor, data portal,
    installation) have a small cube without labels and glide to the view clicked.
  • Who created and last changed a shared project: the project list of the
    Project server pane and of the server's web page shows Created by, Last
    changed by
    and Last changed for each project (created_by, created_at,
    changed_by, changed_at of GET /api/v1/projects). The project server records
    the signed-in user of the creation and of every save that changes the project;
    opening, keeping a session alive and saving unchanged content do not count.
    Projects of earlier versions show Unknown until their next change.
  • Docker image of the web editor: ghcr.io/nilres/openecraft-web serves the
    web editor with nginx on port 8080, built by installer/docker/Dockerfile
    (target editor-web) and published with the server images;
    installer/docker/compose.yaml starts it with both servers
    (installation).
  • Web page of the project server: started with --web (or
    OPENECRAFT_PROJECT_WEB=true, web = true in its configuration file), the project
    server serves a web page with the projects the user may see and a read-only view of
    each: the pages by section or by structure, the devices with their places and the
    pages drawn as on paper, with the locks of the users working on them. Project
    managers edit the permissions of their projects; administrators get an
    administration area for the users, the access rights (access without sign-in,
    roles, grants) and the directories (Active Directory, LDAP, with a test), and a
    view of the open sessions (user, project, saves, locked pages) with the history of
    the ended ones, which the server keeps in sessions.jsonl of its data directory. The
    server also offers the directories over its API (/api/v1/directories) and tells
    the caller's user and rights in /api/v1/info. The page shares its sign-in, access
    administration and styles with the parts server's data portal (new crate
    openecraft-web), and its project views with the editor's navigator (new crate
    openecraft-view).
  • Shared projects recover expired sessions (#183): the editor tells a server
    that does not answer, an ended project session (expired, or the server restarted)
    and an invalid sign-in apart. An ended session opens the project again with the
    existing sign-in, without asking for the password; your unsaved changes are put
    onto the server's current project and lock again, while changes another user
    made meanwhile (or pages they removed) win and your version is kept in
    Project server › Kept changes. After an invalid sign-in, signing in again in the
    Project server pane continues the project. A failed save now shows the lost
    connection at once; the pane and the status bar show the connection apart from
    whether your changes are saved on the server, and a restored connection clears the
    old connection error but not an unsaved failed save. Keep working on a local
    copy
    ends the shared session and keeps the project with your changes locally.
  • Freestanding PV arrays: ground-mounted PV arrays on the plot, added in the
    Buildings pane (Freestanding PV arrays) or clicked into the site plan: rows of
    tilted tables with modules on top of each other, on rails over table beams on rammed
    posts (generic GEN.PV-POST-RAM and GEN.PV-TABLE-BEAM), free of shade in winter.
    Their modules and mounting go into the bill of materials, they have strings like the
    arrays on the roofs, their leads run through a cable trench to the devices, and the
    site plan and the 3D view draw them. Checked for arrays on each other, on a room and
    outside the plot boundary. Commands add_pv_array / set_pv_array without building
    and roof, with stack and clearance
    (panel layout).
  • Roofs picked in 3D: a click on a roof in the 3D view shows it in the Layout
    properties, where a PV array or a roof window is added at the point clicked. The
    PV array window adds a string to the array with + String beside its strings.
  • Shared saves one at a time (#182): a save to the project server waits for
    the answer to the one before it (Save or Ctrl+S again sends the project as it is
    then), and an answer marks only what its request sent as saved: edits or Undo
    made while saving stay unsaved. Save and release keeps a page edited again
    while saving and requests its lock again. Answers that arrive out of order no
    longer take the project back to an older revision, a failed save sends and
    releases nothing more, and closing or replacing a shared project ends its
    session only after the save under way. The live project server tests run with
    scripts/test-project-server-live.ps1 (formerly test-cable-rename.ps1).
  • Keep me signed in (#184): optional project-server sign-in persistence on
    Windows using Credential Manager, separately for each server and account. The
    editor validates the saved session and reads current account rights before
    using it. Sign out preserves open work as a local recovery copy, removes the
    remembered credential and ends the account session after pending project closes.
    Change user keeps the remembered sign-in for switching back. Reauthentication
    retains pending save confirmations; stale windows cannot delete newer tokens.
    Browser, macOS and
    Linux sign-ins remain in memory only; remembering does not extend server expiry.
    Remembered sign-in requires the updated project server; older servers still
    support manual sign-in.
  • Shared saves keep conflicting local edits (#181): when the project server
    leaves changes out of a save (locked or changed by another user), when a lock
    is refused or lost, or when another user changed a target first, the editor
    keeps your version before it shows the server's. Project server › Kept changes
    lists these copies to compare with the open project, take over again as an
    undoable edit (not while another user holds the lock), export as a project file
    or discard; they are stored and survive closing the app or reopening the
    project. A partial save is reported as such and never marks the project as
    saved; the unsaved-changes question mentions the kept copies. Changes still
    waiting for their lock are no longer replaced by a refresh.
  • Cable core labels (#172): automatic text clearance from definition lines,
    wires, nearby symbols and labels; direct text dragging without selecting the
    wire first, with a hover target. Align the crossed core labels of a definition
    with a page preview, common side and clearance. Applying replaces only those
    label positions in one undo step; manual offsets retain their original meaning.
    Unresolved placement conflicts are outlined in the editor and block alignment.
    The same positions are used by screen, SVG and PDF, and by the registered
    preview_core_labels / align_core_labels commands.
    Rendering change for existing projects: automatic labels without manual
    offsets use the new layout, including on released pages and in PDF/SVG exports.
    Release protection prevents edits; it does not select the previous renderer.
    Saved manual offsets retain their positions. Page drawing reuses the caller's
    index and the editor shares one label layout for drawing and pointer targets.
  • Quick cable rename (#174): select a cable definition or its label and use
    Rename cable… in the context menu, the properties or the cable navigator.
    The dialog selects the complete tag, validates it before applying and updates
    references across pages in one undo step. Shared projects acquire all affected
    locks first. Also available as the rename_cable CLI/MCP/plugin command.
    Canvas context menus stay open during a left-button press so their commands
    actually run on release.
    Session-bound snapshots keep own locks identifiable when loading concurrent
    page changes. Older servers use their GET snapshot and an authenticated status
    at the same revision, preserving own locks without guessing from user names.
    Cancelling an in-flight rename releases its new locks after the request has
    finished; existing locks and locks protecting other local edits are kept.
  • Cable core assignment (#173): preview crossed wires, free cores and the
    assignment order from the line start. Insufficient cores or conflicting wire
    assignments leave all pending assignments unchanged and show a persistent
    check warning. Correct the cable/core list before assigning again. Existing
    assignments and cores used on other pages are preserved. CLI/MCP can inspect
    preview_cable_definition and explicitly apply_cable_definition.
    Rejected new definitions do not create unused cables. Imported core names
    without a cable are preserved as conflicts; disabled assignment buttons explain
    the reason. Interactive previews reuse the session index.
  • PV arrays in 3D: a click on an array opens its properties (modules and their
    data, peak power, mounting and material, earthing, strings with their values and the
    lengths of their leads, problems, and its settings). The cabling of the strings is
    drawn from module to module and down to the generator junction box (combiner) with
    the DC main cable on to the inverter: every module's plus lead (red) meets the next
    module's minus lead (black) at a connector; Show › See-through PV modules shows it
    under the modules. The mounting gets roof hooks
    and an earthing point with its clamp on each rail or row of mounting bases, bonded by
    the earthing conductor to an earthing busbar (set_pv_array earthing). Show ›
    Hide PV modules
    shows the mounting. A room under the roof shown alone shows the
    arrays and the roof windows over it; roof windows are no longer covered by the roof
    seen through from outside. Example 16 places the inverter and the bonding busbar in
    the attic (panel layout).
  • Earthing and lightning protection: buildings get earth electrodes (foundation
    earth electrode in meshes, ring earth electrode, earth rods; connected to a main
    earthing busbar) and a lightning protection system of class I - IV (air-termination
    conductors on ridges and hips or as a mesh on flat roofs, air-termination rods, down
    conductors with test joints into the electrodes), added in Site › Earthing and
    lightning protection
    (rods clicked into the site plan), with their material,
    diameter and mounting hardware (conductor holders, rod holders or concrete bases),
    selected by a click in 3D or the site plan and set in their properties, drawn in 3D and in the site plan,
    their material in the bill of materials, checked (down conductors per class, PV
    arrays in the protection angle). Commands: add_earth_electrode,
    set_earth_electrode, set_lightning_protection, add_air_rod, set_air_rod
    (panel layout).
  • Moving buildings: Site › Move buildings is an edit mode of the site plan in which
    buildings are dragged to their places and turned by 90°, with the rooms standing in
    them.
  • Outlets, switches and heating: the menu has tabs, a search, filters by maker and
    type and a 3D preview of the part picked; outlets and switches are drawn with their
    models in the 3D view (frames, sockets with earthing clips, tilted rockers).
  • Split projects for version control. A project can be stored as
    a folder of small files instead of one .oec file: the index <name>.oecp, one file
    per page, one per device, part, cable and other record of the project-wide data, and
    the embedded documents and images as plain files named by their hash. Every JSON
    file is one line and depends only on the content, so a change touches only the files
    it concerns and two people editing different pages do not conflict. convert_project --format oec|oecp|oecz converts between the project file, the split project and the
    archive; --project <name>.oecp, open_project, save_project, templates,
    subprojects, the project index and batch changes read and write split projects. In
    the desktop editor File › Save as split project… writes one (into a folder of its
    own when the chosen folder holds other files), Open, the recent files, templates,
    the comparison, subprojects and the project database read them, Save rewrites only
    the changed files, and the installers open .oecp files with the editor. The web
    version cannot open folders and keeps .oec and .oecz. Archives (.oecz) are
    written in version 2
    : they hold the files of a split project instead of one
    project.oec, so an embedded file used several times is stored once; the manifest
    names the version (version), archives of version 1 are still read, and versions
    of OpenECraft before this one cannot read the new archives. The project server
    stores its projects as split projects
    (<name>/<name>.oecp in the data
    directory) and writes only the files a save changed; project files of earlier
    versions are converted at the first start and kept as <name>.oec.bak. For git,
    saving writes a .gitattributes that keeps the files unconverted, and the merge
    driver merge_project_file merges the JSON files record by record (fields of a
    record, records by their id, the order of pages and records, the id counter);
    check_project_data --repair renumbers ids two branches gave twice
    (docs/command-line.md). Copies of a split project start the ids of their new
    objects at different random places, so that this is rare. A save writes only the
    files this side changed: what another program changed in the folder meanwhile (a
    git pull) is kept and read in, and a file changed by both is not overwritten.
    A file git merged as text is named when the project is opened. Large split
    projects stay fast: the records of a kind are spread over 16 folders, a save
    writes only the pages and data that changed, the folder is read once on all
    threads, and a save is one step that a crash either leaves undone or the next
    access finishes (journal .oecp-save). The .oec file stays the default (#149).
  • Parts server: groups, catalog permissions, directories and a dashboard. Users
    are gathered in groups of the server (Administration › Groups, /api/v1/groups;
    the groups of local accounts become such groups at startup), and grants to a group
    apply to its members, local or from a directory. Each catalog gets permissions
    of users and groups (Catalogs › Permissions, grants on catalog:<id>), which
    apply to the catalog and its parts whatever their manufacturer. Users who may change
    parts create them on the web page (New part) and edit or delete those they may
    change. The Active Directory / LDAP connections are set up and tested in
    Administration › Directories. A dashboard shows graphs of the parts (per
    manufacturer, group, catalog, lifecycle, changes per month, completeness);
    administrators hide it on the web page, with --dashboard false,
    OPENECRAFT_DASHBOARD or dashboard in the configuration file. Exports carry the
    version of the server
    (export in export.json, which is now an object with
    parts, a first line in export.csv, the meta table of backups, the header
    X-OpenECraft-Server-Version). The web page shows the OpenECraft logo, its title
    leads back to the start page and the list shows 10 to 200 parts per page.
    Catalogs have company logos (Administration › Catalogs › Edit,
    /api/v1/catalogs/{id}/logo), shown on the catalog cards and on their parts; the
    bundled catalogs bring the manufacturers' logos (from Wikimedia Commons, name badges
    for COSMO, Janitza, MDT and Pylontech). The editor's Data portal shows the logo of a
    part's catalog and the parts manager the logos of its catalogs, where they are also
    changed or removed; Settings › Appearance › Data portal (editor) and Logos (parts
    manager) hide them (parts server, access control).
  • Enclosure packages of configurators (#176): Import parts (editor, Parts
    Manager, parts_import) reads the ZIP archive of the Rittal configurator: the parts
    of its bill of materials, the configured enclosure with size, GTIN, configuration id,
    the preview of its EPLAN macro as picture, the bodies of the EPLAN Pro Panel macro
    (or else the STEP model) as 3D model, the place of its mounting plate (part data
    Mounting origin, used by new enclosures of the part) and its restricted areas, and
    the macro, EPLAN project, STEP file and PDFs as attachments
    (parts). Restricted areas of enclosure parts (mounting
    data, on the faces of the enclosure) are drawn hatched in the panel layout, which
    reports devices in a placing area and cutouts and holes in a cut-out area
    (panel layout), shown in the 3D view
    and edited in a table of the part editor. An enclosure of a maker's part that names
    its system keeps that part instead of the catalog's body (also in the bill of
    materials), and the 3D view and 3D exports show the maker's model of the
    enclosure. Mounting plates that are not centred get their size (Mounting size,
    mounting_size). Importing a part again refreshes the project's copy with what the
    import brings (models, mounting data, technical data). Unpacked EDZ files and vendor
    folders take 3D models from their 3D macros, and macros with bodies in a form not
    read are reported. The 3D macros of EDZ files give their parts a 3D
    model. Import parts tells its result in a box at the bottom right. Cabinet doors
    can be hinged on the right (Door hinge, door_hinge, part data Door hinge; the
    Rittal import finds it from the hinge blocks): the door view, the 3D view and the
    door wiring follow it. STEP files whose arcs are given by their vertices
    only (as Open CASCADE writes them) are read now, and a body STEP cannot convert no
    longer fails the whole model.
  • Logos in title blocks (#165): title blocks and drawn report forms get image
    elements (➕ Image), with a picture of their own (e.g. the company logo, kept in the
    title block and its file) or the new project logo of Project properties › Logo
    (e.g. the customer's), fitted with its aspect ratio; the cover page shows the project
    logo above the project name or at a place and size of its own (set_cover_logo). Texts of forms can be bold, italic and rotated, and new placeholders show the
    previous and next page ({page.previous}, {page.next}) and revision tables
    ({rev.1.name}, {rev.2.date} …). Commands: list_title_blocks, set_title_block,
    delete_title_block, set_default_title_block, set_page (title_block),
    add_title_block_image, set_project_info (logo)
    (reports and checks).
  • Customised forms and drawings: elements of title blocks and drawn forms can be
    limited to page types or to a filled placeholder (revision tables), get their own
    colour and dashes, and QR codes encode texts with placeholders. Title blocks follow
    the page type and the plot frame (Title block by page type, frame property). A
    stamp across every page follows the revision workflow (DRAFT, FOR APPROVAL,
    nothing or AS BUILT when released) and {rev.status}, {rev.approved_by},
    {rev.approved_date} show who approved. Report forms get total rows, shaded rows
    and column alignment. The company library on the parts server shares title
    blocks, report schemes and plot frames between projects (GET / PUT /api/v1/libraries/forms). Commands: set_stamp, set_default_title_block
    (page_type), set_frame (title_block), parts_company_forms
    (publish)
    (reports and checks).
  • More data from EDZ files (#162): connection points keep the wires their clamps
    take (smallest and largest cross-section, most wires), and the new check Wires at
    connection points
    warns about more wires than that or wires too thin or too thick.
    Drilling patterns tell tapped from through holes and give the cutout of a part (an
    HMI panel's 197 x 141 instead of a Ø141 hole); EPLAN's rail data or a text naming
    the rail make a part one for a mounting rail of that size. The product picture is
    kept with the part and shown in the part details with its mounting and wiring data,
    and the part XML of an unpacked EDZ file is read with its connection points, drilling
    pattern, macros and picture (parts).
  • Placed cutouts (#162): a part has any number of cutouts and door cutouts, each with
    its centre, turn and corner radius (table and preview in the Mounting tab of the part
    editor, text 197 x 141 @ 0/-6.5 R3 15°, read from EDZ drilling patterns). The
    openings sit there and turn with the device, the NC data carry turn and radius, and
    the manufacturing check reports cutouts beyond the device front or in the free edge
    of the door and the walls (panel layout).
  • Scaled symbols (#162): Scale in the properties of a placed library symbol (or
    update_symbol with scale) draws an imported symbol larger or smaller, its texts
    at their size and its wires following (symbols).
  • Administration of the parts server on its web page: Administration shows an
    overview of the server and manages the users (create, change, delete, last sign-in,
    sign out everywhere), the access rights (sign-in for reading, roles, grants), the
    catalogs (also installing the bundled ones), the import of parts, and exports and
    backups: the parts as CSV or JSON, catalogs, users, access settings (also restored)
    and the whole database as one SQLite file. On a new server an administrator signs in
    with the access token. New API: GET /export.json, GET /backup, GET /bundled,
    POST /bundled/{id}, DELETE /users/{name}/sessions; GET /users also returns the
    open sessions and the last sign-in (parts server).
  • Registration on the parts server: users can create an account themselves
    (Register next to the sign-in) and become readers, when it is switched on in
    Administration › Access rights or with --registration, OPENECRAFT_REGISTRATION
    or registration in the configuration file; it is closed by default. New accounts
    wait for the approval of an administrator (Administration › Users: approve or
    reject) unless approval is switched off. Registrations are throttled per client,
    names that grants refer to cannot be taken. Command line / MCP:
    parts_registration (enabled, approval), parts_user_approve. New API:
    POST /register, GET|PUT /registration, POST /users/{name}/approval; /info
    tells whether the registration is open.
  • EPLAN Data Portal downloads: DXF and commercial-data downloads use the current
    POST API, and the connection test checks the protected file-provider service without
    downloading commercial data. On Windows, an explicit Remember token option lets
    a verified PAT be shared securely between the editor and CLI/MCP through
    Credential Manager (parts server). The first
    GUI request loads the saved PAT in the background automatically, without requiring
    a connection test. Concurrent requests share the lookup.
  • Straight ferrules and terminals: a wire or cable core with a ferrule or a crimped
    terminal runs straight out of its connection point for the length of it (with its
    collar or insulated sleeve) and bends only behind it, in the 3D routing and in the 3D
    view, instead of bending the ferrule where it goes into the device
    (panel layout).
  • Keys and gestures: File › Settings › Keys and gestures configures every key,
    modifier and gesture in one place: the keyboard shortcuts (now also the keys that
    move through the 3D view, and the panel layout follows the keys of Rotate, Delete and
    Fit), the modifier keys (adding to the selection, opening links, a single item of an
    assembly, Keep connections reversed for a move, rotating back, moving faster in 3D,
    the wheel turned sideways or zooming),
    the mouse buttons that pan, orbit, cancel, rotate while moving and the double-clicks,
    and what the wheel does, two fingers (pan and zoom together, zoom only or pan only)
    and three fingers on a touch screen. It replaces the Navigation and
    Keyboard shortcuts settings (user interface).
  • Moved wires stay connected (#133): a wire moved on its own no longer leaves the
    connection points it ends at; it gets a new leg from the point, or slides along the
    rail it ends on. Edit › Keep connections (on by default) switches this and the
    stretching of attached wires off, so the selection moves alone; Alt held at the
    start of a drag reverses it for that drag. Dragging the square handle at an end of a
    selected wire moves only that end, to disconnect it or connect it elsewhere. Commands:
    move_items (keep_connections), move_wire_end
    (schematic).
  • Server administrator from the environment: OPENECRAFT_ADMIN_USER (parts server)
    and OPENECRAFT_PROJECT_ADMIN_USER (project server) name the administrator account
    created at startup, as --admin-user does, so a Docker container gets its first user
    from environment variables alone (installation).
  • Full-canvas schematic crosshair: File › Settings › Appearance can extend the
    placement crosshair to the edges of the schematic canvas, following the snapped
    working point.
  • AppImage on more systems: the AppImage carries the keyboard and cursor libraries
    of X11 (xkbcommon, Xcursor, Xi), so the editor and the parts manager start on systems
    without them instead of quitting with Library libxkbcommon-x11.so could not be
    loaded
    .
  • Invisible grid lines: connection points and wire ends off the drawing grid, as in
    imported drawings or on device boxes of any size, add invisible grid lines through
    them. The pointer snaps to them where they are nearer than the grid, so wires can be
    drawn from such points and things connected to such wires. A symbol being placed or
    moved snaps from its own connection points, so they land on such lines and
    auto-connect joins them (schematic).
  • Auto-connect hints: while a symbol is placed or moved with the mouse, faint
    dotted lines show the wires auto-connect would draw
    (schematic).
  • Cut, copy and paste in the panel layout (#153): right click an item in the front
    view for Cut, Copy, Paste, Properties and Remove (devices go back to the
    devices to place), or use Ctrl+X / Ctrl+C / Ctrl+V. Rails, ducts and the other
    items are copied with what is mounted on them, without devices; cut devices go back
    to the devices to place. The copy follows the pointer until a click places it
    (panel layout). New command
    copy_panel_items.
  • Profile sizes on mounting layouts (#152): cable ducts, mounting rails and busbar
    systems are labelled with their cross-section and cut length
    (60 × 100 mm, L = 940 mm) on mounting layout pages and in the panel layout, on the
    longest stretch no device covers (only the length where the whole label does not
    fit), beside the end of a full one. The panel legend lists them after the devices with part number, cross-section
    (width × height) and cut length; the bill of materials lists the pieces to cut below
    each of their parts (2 pcs, Cut length 550 mm, +CAB1).
  • Panel layout profile sizing (#135): select a mounting rail or cable duct and drag
    either end to change its length while the opposite end stays put.
  • Connection symbols (#96): Auto-connect wires the branch of a T-junction that sits
    on one continuous wire, as it does on a wire split at the junction. While a connection
    symbol tool is active, Tab (Next routing of the connection symbol to place) cycles
    the routing or orientation of the next symbol, Rotate turns it, and the Properties
    pane shows its routings to pick from; a placed symbol is no longer selected, so these
    changes never alter it; the tools show the Properties pane again when it was closed.
    A T-junction placed where three wires meet keeps the chosen routing. Connection
    symbols follow their wires when wires or devices move, also in fast drags, sliding
    along the rail with their drop, and wires branching off a moved wire stretch with it.
  • Trackpads and touch screens (#134): every 2D and 3D view (schematic, front,
    floor and site plan, 3D view, field plan, symbol editor) zooms with a pinch and pans
    with two fingers, both in one movement; on a touch screen the first finger no longer
    selects, moves or orbits while two are down. The horizontal mouse wheel and
    Shift+wheel pan sideways. Settings › Keys and gestures › Wheel and touch chooses what scrolling does:
    Automatic (trackpads pan, mouse wheels zoom, told apart on macOS), Zooms (mouse
    wheel)
    or Pans (trackpad), and can invert the direction of panning by scrolling.
    The symbol editor's canvas pans too (also with the middle mouse button).
  • Settings after an update check: checking for updates no longer collapses Settings
    into an unusable title bar. Dialogs already stuck this way recover their contents.
  • Wire jumps (#132): wires that cross without a connection can jump over each other
    with an arc, a square bridge or a gap, besides the plain crossing of before; the
    vertical or the horizontal wire jumps. T-connections show a dot, a large dot or no
    dot (a plain T); connections of four or more wires always keep their dot. Set in
    Connections › Wire crossings… (Settings › Wire crossings) with a preview, saved
    with the project and in settings schemes, drawn alike on screen and in PDF, SVG and
    DXF. Command wire_settings.
  • Rerouting moved connections (#132, off by default): with Route the connections
    of moved items anew
    a wire left diagonal by a move is routed again together with
    the corners after it, up to the next connection point, junction or branch: the
    way of the least weight, its length in grid steps plus 1.2 per bend and 1.5 per
    wire crossed. Labels and connection definition points come along; without a way the
    wire is squared as before.
  • Startup and the source of the project (#129): File › Settings › On startup
    chooses what opens when the editor starts: the start page with the local files and
    the projects of the project server (Show project manager), the last project from
    where it came – a server project is opened on the project server again, asking for a
    sign-in if needed (Reopen last project, the default), the project list of the
    project server without the last project (Open project server) or always the same
    local file or server project. A project file opened from the file manager still
    opens instead. The status bar always says where the project is saved: Local file:
    …
    , Project server: … / Project: … (with connection lost while the server does
    not answer) or Local recovery copy of server project: … – a project restored from
    the last session or closed on the server is never shown as the shared project, and
    the tooltip of Save names the destination. If the project server of the start is
    not available, a dialog offers Retry connection, Sign in…, Choose another
    project
    and Open local recovery copy; unsaved changes of the copy are saved or
    discarded on purpose before the shared project replaces them.
  • EDZ parts without a usable macro (#131): a part whose first function is a
    generic one (the connection points of a drive or an HMI) is placed as a black box
    with room for its connection points instead of an earth electrode. Elliptic arcs of
    EPLAN macros keep the ratio of their axes and start and end where the macro says (the
    S7-1200 CPU 6ES7212-1HG50-0XB0 had a half circle of 400 mm across the page), and
    texts keep their justification (table labels stood on their lines, right-aligned
    texts ran into their neighbours). Open polylines of EPLAN macros stay open (each edge
    of the CPU was closed back to its start), and the schematic no longer draws spikes
    where a line turns back on itself. The part selection of Add part… no longer grows
    to the height of the screen.
  • Wire ends in 3D: the 3D view of the panel layout shows the end of each wire and
    cable core at its connection point: the ferrule (metal sleeve and collar in its
    DIN 46228-4 colour) where Wire ends with ferrules is set, otherwise the bare copper
    conductor as long as it is stripped.
  • Terminations per wire end: each end of a wire or cable core gets its own
    termination: bare conductor, ferrule, twin ferrule, ring, fork or pin terminal, flat
    plug or flat receptacle (insulated in red, blue or yellow by the cross-section,
    uninsulated tubular cable lugs from 10 mm²). It is chosen in the properties of a
    wire (Wire ends) or a cable (Cable ends, for all cores at one device), or with
    the command set_termination for a connection point, a device or one wire;
    terminations lists them. Ends without one keep the ferrule setting of the layout.
    The 3D view draws every termination (rings round the connection point, flat plugs,
    forks, pins and insulated sleeves in their colour, each cable core with its own
    cross-section); the production wire list shows the termination and parts of both
    ends, and the wiring assistant, the machine exports, the harness data and the bill of
    materials (with the new catalog parts) take them too.
  • Twin ferrules for two wires: a twin ferrule belongs to the two wires ending at
    one connection point. Chosen for one of them it is chosen for the other one too
    (offered only where exactly two wires end), it is shown once in 3D, counted once in
    the bill of materials, named with the other wire in the production wire list and the
    wiring assistant (which puts the two wires one after the other, to be crimped
    together) and carried by the first of them in the machine exports (new fields Twin
    ferrule with (from)
    / (to)). Two cross-sections get the ferrule for the larger
    one. The check Twin ferrules warns about one with a single wire, at a point with
    more than two wires or for two cross-sections. New layout setting Twin ferrules where
    two wires share a connection point
    (command set_ferrules).
  • Workspaces show their view again: a workspace chosen in the title bar shows its
    main view (the panel layout, the workbench, …) even where the page was left in front
    of it, and the commands of the layout view (3D view, floor plan, mounting plate,
    tools, …) bring it to the front instead of changing it unseen behind the page.
  • Rotate while moving a selection: right-click during a drag to rotate its electrical
    components 90° clockwise; Shift+right-click turns them counter-clockwise. The
    selection stays attached to the pointer, in both schematic editing and panel layout.
  • 3D routing keeps a route apart from itself: a cable, wire or pipe whose ends lie
    too close for its bend radius no longer runs back across or alongside its own way
    (the supply cable =GRID-W1 of the example building_services crossed itself below
    the house connection box); it takes a loop that keeps its thickness from itself, its
    bends and the nozzle it comes out of, and is reported as not routable where there is
    none. Cables and pipes through one wall penetration pass it side by side instead of
    through one point. The example building_services has its cable entry lower in the
    wall, the water service sleeve in front of its building entry and the couplings of
    the compressed air outlets beside their units, so that every line has room for its
    bends.
  • One cable per cable gland: a cable gland takes one cable (the free one whose
    clamping range fits, nearest to where the cable heads); a cable that finds every
    gland of its cabinet taken is not routed and reported as an error that names the
    cabinet, instead of being drawn through a gland with another cable. Cable entry
    flanges still take several cables side by side. Cable glands are drawn with a model
    of their own in the colour of their material: outside the hexagon body, neck and
    dome on the outer surface of their wall (they floated a centimetre above it), inside
    the locknut and the end of the thread, which other routes keep clear of; and the
    generic catalog gains them in brass nickel-plated (GEN.GLAND-M16-MS …
    -M63-MS), as EMC glands with a contact spring for the shield braid
    (GEN.GLAND-M16-EMC … -M40-EMC) and two LAPP SKINTOP glands (ST-M and MS-M
    20x1.5) as manufacturer parts. The example building_services has a gland for every
    cable, sized to it, and the conveyor (conveyor, engineering_workflow) one for its
    motor cable, which came in through the middle of the bottom.
  • Connection point designations (#116): each designation of a selected symbol can
    be dragged on its own, put left, right, above or below its connection point or reset
    to automatic placement (Properties › Property placement); the placement is stored
    with the symbol and turns and mirrors with it, without changing the connection point.
    Placed automatically, a designation follows the lead of its connection point and
    moves along it, to the other side or out beside the wire to keep clear of the
    symbol's graphics, wires, nearby symbols and its other texts (the surge protective
    device's PE no longer runs into its arrow). Command place_pin_label.
  • Interruption points: the name and the cross reference no longer crowd the arrow:
    horizontal points show the name above and the cross reference below the conductor,
    inside the page, vertical ones beside the arrow. Both can be put above, below, left
    or right of the arrow for
    all selected points at once, or dragged on their own without moving the symbol, and
    reset to the automatic placement; the places are saved and exported, the cross
    reference keeps its link. Command place_interruption_texts
    (schematic).
  • CAD drawing imports return original geometry bounds and their page origin, so
    external importers can recover drawing coordinates without changing page placement.
  • Device boxes with device connection points: a dashed box of any size drawn on
    the schematic is a device of its own (power supply, measuring instrument, control
    module) without a library symbol; device connection points placed on its outline
    belong to its device, lead away from its edge and are numbered on. Each point is a
    separate connection (-A1:L, -A1:+24V) in the connection reports; designations,
    directions, the box of a point and the place and alignment of its designation are
    editable, resizing a box takes the points on a moved edge and their wires along, and
    moving, copying, deleting and macros take a box with its points. Commands
    add_device_box, update_device_box, add_device_connections,
    update_device_connection, list_device_boxes
    (schematic).
  • Device box roles: a device box with the tag of a device placed elsewhere can add
    connection points to it (Extension) or show only selected connection points of it
    on another page (Pin view). Wires at a view belong to the point it shows, reports
    list that connection once, and neither role counts as a second main function. Role
    on add_device_box and update_device_box, command show_device_pins
    (schematic).
  • Cable cores at the cable definition line: the stroke, core designation and cable
    tag of each core sit where a cable definition line of its cable crosses the wire, so
    they line up on wires of different lengths (30 % of the wire without a line). The core
    designation and the cable tag of a selected wire can be dragged into place; they keep
    their offset when the line moves, Reset in the wire properties places them
    automatically again. update_wire takes core_offset and cable_offset
    (connections).
  • Plot boundary: the boundary of the plot is drawn in the site plan corner by corner
    and its corners are dragged afterwards; all buildings have to stay inside it, the check
    reports rooms, roofs and cabinets outside it and the site plan draws them red.
    Commands plot, set_plot (panel layout).
  • Georeferenced reference point: a point of the plant with its easting, northing,
    height and coordinate reference system and the direction of grid north; the site plan
    shows the coordinates under the pointer and a north arrow, list_buildings the
    coordinates of the buildings, IFC exports the plot's name, latitude and longitude.
    Site › Measure measures distance and direction between two points. Commands
    set_reference_point, locate, measure.
  • A level in 3D: a level clicked in the navigator while the 3D view is shown shows
    all rooms of that level side by side at their places, with their cabinets, floor
    slabs and stairs.
  • Project properties: the name and value fields of the custom properties use the
    width of the dialog instead of shrinking to a few characters; the dialog can be
    resized, and a long list of properties scrolls. A renamed property is applied when
    its name field loses focus (Esc keeps the old name), so the text cursor no longer
    jumps to another property while typing.
  • Wires in 3D: a wire starts in the opening of its connection point and leaves it
    along the direction the point opens in (up or down out of the upper or lower edge of
    a device) before it comes down to the cable duct, instead of running straight back
    along the device to the mounting plate. The generated connection points of DIN rail
    devices lie in their end faces below the screws (40 % of the depth above the rail
    instead of 75 %, in front of the screws), and the generated models of DIN rail devices
    and contactors show these wire entries. NH fuse switch disconnectors on busbars are
    wired into the clamps in their terminal compartments (57.5 % of the depth, entered
    from the end faces below the screws) instead of in front of their terminal covers,
    and the strips for 185 mm busbars are drawn with their fuses one above the other and
    the connection compartment at the bottom. Devices drawn as boxes (parts without a 3D
    model) show the openings of their connection points.
  • Structure boxes: Insert › Structure box draws a rectangle whose devices take other
    function (=) or location (+) identifiers than the page (also installation site and
    product); only the aspects set on the box override the page, nested boxes resolve to
    the innermost. Devices follow when their main function moves into or out of a box or
    the box is moved, resized or changed (in one undo step); aspects set on a device stay,
    and a tag that exists already is refused instead of merging two devices. Tags on the
    page omit what the box shows; the symbol properties show where each aspect comes from;
    the structure check reports overlapping boxes and devices inside a box with another
    structure. Commands add_structure_box,
    update_structure_box, list_structure_boxes
    (schematic).
  • Tag blocks clear of neighbouring symbols: a tag block placed automatically that
    would run into a neighbouring symbol goes on the other side of its symbol, above or
    below, whichever is clear of symbols and wires; the tag of functions of one device
    side by side in a row is shown once, at the first of them (the surge protective
    devices -F1 of the transformer metering examples no longer overlap). Tag blocks
    placed by hand stay where they are.
  • Preserve imported plot-frame artwork and live page fields as reusable frames, separate from selectable page content, including canvas, frame preview and exports.
  • PLC addresses that are not byte.bit addresses, such as imported card positions like A1.3.1, are compared as whole texts, so different addresses are no longer reported as duplicates.
  • Keep the closing window responsive while preparing recovery data, with progress for the previous autosave, project, parts database and macro library.
  • Reuse Insert center symbol groups and search results while scrolling, refreshing them when definitions, parts, search text or language change.
  • Keep the Insert center responsive while scrolling large libraries by drawing only visible list rows and previews and reusing unplaced-function results until the project or catalog changes.
  • Add live function cross-reference fields with native page links, multiline attribute flow and a shared reference query. Authored tag fields can retain reference placement without freezing sheet names.
  • Expose native symbol definition reconciliation to importers, preserving local revisions and reusing equal definitions.
  • Continue new page numbering after imported alphabetic subpages such as 20a and 20.a, within each section.
  • Preserve explicit cabinet rotations through front artwork, meshes, pins, wire exits and drilling; expose orientation editing through the editor and plugin commands.
  • Distinguish plugin defaults from explicit false for optional boolean form fields.
  • Renaming a placed cable marker follows its explicit cable reference and keeps
    ordinary devices with a shared tag independent. Unambiguous cable material-owner
    references follow renames and are cleared when the cable is removed.
  • Placed wire labels read live core, cable, wire number or colour values, retain
    their layout through routing splits, joins, rotation and portable copy/paste,
    and can be edited in wire properties or the shared update_wire command.
  • Cable properties in symbol attribute blocks and placed annotations follow the
    linked inventory entry, including custom marker captions. Placed part properties
    show the selected article consistently with attribute blocks and exports.
  • Cable tag entry commits on Enter or leaving the field; empty, duplicate and
    invalid tags leave the inventory and drawing references intact. The editor and
    table command share validation, including released drawings.
  • Explicit cable markers follow the current cable article through property,
    table and catalog edits, including when their displayed caption is customized.
  • Cable renames keep explicitly linked drawing markers, connection definitions,
    cable definition lines and inactive options synchronized; shared ordinary
    device tags stay separate. Portable copies retain the cable association.
  • Keep frame references to the previous, next and last sheet current within their section, including schemes whose numbering starts above one.
  • Keep page and project property blocks live in drawing graphics, expose local sheet numbers and section page counts, and retain editable page defaults in reusable page templates. Offer page and project fields in the symbol editor's property picker.
  • Advertise parallel cable-core support to external importers so a newer verification CLI cannot mask an older running editor.
  • Resolve portable macro parameters in symbol graphics, pin labels and library defaults as well as placed instance data.
  • Keep imported cable symbol article references current when choosing or typing a new cable part, while preserving ordinary device selections.
  • Preserve explicit function article lookup when an ordinary device and a cable share an authored tag, without duplicating cable material.
  • Retain distinct parallel cable cores between the same terminals in physical connections and regenerated cable reports.
  • Preserve owned cable definitions, catalog parts and core assignments when copying circuits or inserting macros, with fresh consistent tags.
  • Include imported project cable parts in the cable picker, preserve local catalog overrides, and expose the same available parts through the shared registry.
  • Apply declared catalog cable diameters when selecting a part, return to the routing estimate when the new part has no valid diameter, and expose cable part application through the shared plugin command.
  • Keep missing lengths of cable sold by metre as unknown material quantities and prices. Retain known partial totals and identify the cables that need a length through the shared project check.
  • Preserve individual wire junction policies when inserting imported macros into existing drawings. Keep existing implicit contacts, trace imported physical routes, expose editable policies through the shared API and wire properties, and preserve different conductor properties during cleanup.
  • Preserve device properties, material owners and literal extra quantities when inserting portable macros. Keep local counts when extending an existing device and reserve incoming tags before assigning collision replacements.
  • Keep cabinet-only devices in the device and material lists independently of their extras. Count undrawn individual cabinet terminals once and keep their quantity stable when the corresponding schematic terminal is added.
  • Preserve cabinet material ownership independently of mounting geometry. Exclude duplicate physical articles or whole devices from the BOM, retain editable material-only devices, and derive optional rail spacers from actual support height.
  • Preserve literal additional-article quantities, including zero, without multiplying them by terminal positions. Keep primary material growth for newly drawn terminals, avoid counting physical cabinet articles twice and expose quantity modes and physical article bindings through the shared API.
  • Retain explicit cabinet mounting origins and unnumbered single-part footprints without adding implicit plates, repeated terminal strips or accessory stacks. Keep open assembly routing free of invented walls and count explicit plate articles.
  • Place individual terminals with their own parts and physical routing points while retaining whole-strip placement for existing projects.
  • Represent open mounting assemblies and explicit mounting plates without invented enclosure geometry. Retain instance mounting datums, support vertical DIN rails, carry mounted descendants on moves and resize operations, and preserve mounting references in portable and pattern copies through the shared panel API.
  • Convert every digital channel of complete PLC modules when changing the station address scheme, synchronizing linked views while retaining custom address text and signal names.
  • Preserve PLC channel addresses when changing only hardware metadata. Offer explicit readdressing through the shared API and avoid inventing PROFINET ports for imported CPUs with no network data.
  • Count every logical channel of complete PLC modules in part functions and reserve-function checks. Recognize analog part functions in hardware descriptions and exclude occupied module channels from the unplaced navigator even with custom addresses.
  • Preserve card-relative PLC channel numbers across split electrical symbols and sheet reordering, including continued projects imported before explicit channel indices were stored.
  • Link multiple PLC channel representations into one logical I/O entry, prefer electrical pins for navigation, and synchronize channel edits across views, including property edits and configuration import. Keep copies on other device tags independent.
  • Edit the selected channel's address, signal name and comment in the PLC overview without overwriting its module or other channels. Keep row identity stable while addresses change and respect released pages.
  • Preserve complete PLC module symbols with independent channels, physical pin mappings, editable addresses, signal names and comments. Configure and exchange their channels through the PLC table and shared API.
  • Load external plugin folders from Manage plugins and remember them for later launches. Clear previous Find results after successful plugin commands.
  • Clear cached Find results when opening or creating another project.
  • Let wires and connection definitions be selected inside decorative symbol bounds.
  • Trace conductor attributes through valid wire contacts and expose physical wire routes to plugins.
  • Preserve editable conductor types in wire properties, connection tables, API and reports.
  • Add editable, flowing symbol attribute blocks that resolve current function and part properties in drawings and exports, with library defaults for new placements.
  • Select an assigned part independently for each device function, retain the selection when earlier parts are removed, and report removed selected parts. Expose live function manufacturers, selection text and batch attribute inspection to plugins.
  • Keep explicitly placed function text linked to editable instance data, retain user-symbol function text defaults on placement, and avoid a duplicate automatic annotation.
  • Preserve locally displayed product designation levels on imported symbols, and update them when the device is renamed. The symbol editor and plugins can choose the displayed level count.
  • Keep directional imported ports and explicit wire junctions from shorting circuits at side crossings or attaching wires to intermediate device ports. Preserve authored wire endpoints and internal jumper rails, and use port directions when adding new automatic connections.
  • Preserve physical wire targets through imported junction paths and drawn branches, and keep internal component bridges out of manufacturing connections. Junction paths remain editable in the symbol editor and through plugins; list_connections exposes the resulting pin-to-pin wiring.
  • Let imported conductors retain separately placed annotations while keeping their editable wire and cable properties.
  • Preserve editable fluid port functions on user symbols independently of their connection point numbers.
  • Keep scoped interruption points electrically separate while preserving their displayed names and scoped cross references.
  • Connect intermediate terminal attachments along continuous jumper rails, and expose their net membership to plugins.
  • Keep decorative imported artwork and plot frames from blocking automatic connections and wire routing.
  • Preserve device assignments and catalog parts in portable macros, and render their bundled symbol definitions in previews before insertion.
  • Preserve transparent and palette PNG images in PDF output, and support source plot frames and component-name fields on imported pages.
  • Keep custom symbol definitions with portable native macros, preserve local edits on insertion, and distinguish internal jumper attachments from physical terminals.
  • Expose macro insertion and native net membership through plugins, and accept large CLI parameter objects from JSON files.
  • Let imported parts select project symbol definitions across editor, CLI and MCP placement, and retain vendor source records with projects.
  • Preserve embedded bitmaps in imported symbol libraries, including rotated and mirrored instances on the canvas and in SVG and PDF output.
  • Preserve the connectivity domain of imported fluid and process symbols so their ports stay distinct from electrical connections.
  • Keep imported property text angles and pin designation fields editable and linked to their placed symbol.
  • Support imported secondary device functions and local junction paths without adding spurious main functions or device endpoints.
  • Accessories from macros: a macro can list in device_part_additions the literal
    accessory articles of its devices to add when it extends an existing device; the other
    articles and the local quantities of that device stay as they are.
  • Reusing failed route searches: with the routing rule reuse_failed_searches (off by
    default), a search that found no route is not repeated when later routes only fill the
    channels.

Downloads

Check a download with sha256sum -c SHA256SUMS --ignore-missing.
Its origin (build provenance of this workflow) with gh attestation verify <file> --repo nilres/OpenECraft.
The licenses of the libraries and fonts the programs contain are in THIRD-PARTY-LICENSES.html.

Docker images

The parts server, the project server and the web editor as containers (docs/installation.md):

docker pull ghcr.io/nilres/openecraft-parts-server:0.1.2
docker pull ghcr.io/nilres/openecraft-project-server:0.1.2
docker pull ghcr.io/nilres/openecraft-web:0.1.2

The Windows setup is not code signed: SmartScreen asks for confirmation on first start (More info › Run anyway).

The macOS apps are not notarized: Gatekeeper asks for confirmation on first start (System Settings › Privacy & Security › Open Anyway).