Skip to content
View logmanoriginal's full-sized avatar
41 followers · 7 following

Achievements

Achievement: Pull Sharkx3Achievement: YOLOAchievement: Starstruckx2Achievement: Arctic Code Vault Contributor

Achievements

Achievement: Pull Sharkx3Achievement: YOLOAchievement: Starstruckx2Achievement: Arctic Code Vault Contributor

Organizations

@VWS4LS

Block or report logmanoriginal

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
logmanoriginal/README.md

Hi, I'm Pascal

I'm a product developer with a background in automotive and industrial test systems and a bias toward technical clarity.

As an application engineer for 15 years, I have deployed hundreds of projects for automotive and industrial applications across the value chain - from workstations through integrated solutions to automated systems, in hardware and software.

I led the architecture working groups for linking and traceability in VWS4LS, a BMBF-funded research project on the Asset Administration Shell for the automotive wiring harness (results · authors). I contributed to the subprojects on information models, production processes, and AAS integration across the value chain, and participated in the working group behind OPC 40570 (OPC UA for Wire Harness Manufacturing).

As a product developer I analyze requirements and define the architecture that drives the next generation of products and infrastructure.

Currently I'm working on CRA readiness - semantic asset inventory, SBOM generation, and vulnerability management - and on where agentic engineering genuinely helps in architecture and development work.

Most of my public code is LabVIEW, because that's where the tooling gaps were: unit testing, coverage reporting, CI integration, serialization. The problems are the same in any language.

Selected work

Industrial interoperability (VWS4LS)

Testing and developer tooling (LabVIEW)

Working with

  • Interoperability and industrial protocols - AAS, OPC UA, Catena-X, CAN, CANopen, LIN, TCP/IP, COM, SSH
  • Languages - LabVIEW, C#, C, C++, Python, JavaScript, VBScript, ABAP, Lua, PHP
  • Data and formats - SQL, SQLite, XML, JSON, Markdown, LaTeX
  • Tooling and platforms - Git, GitHub Actions, Azure DevOps and Pipelines, Docker, Visual Studio, VS Code, Eclipse, SAP R/3, Confluence

Pinned Loading

  1. LabVIEW-Composition LabVIEW-Composition Public

    Compose and decompose data types in LabVIEW

    LabVIEW 11 4

  2. JSONtext-Object-Serialization JSONtext-Object-Serialization Public

    Object serialization strategies for JSONtext

    LabVIEW 8 3

  3. Caraya-JUnit-for-Azure-Pipelines Caraya-JUnit-for-Azure-Pipelines Public

    Generate JUnit test reports for Azure Pipelines

    LabVIEW

  4. lvssh2 lvssh2 Public

    LabVIEW­ bindings for libssh2

    LabVIEW 2 3

  5. lvunit lvunit Public

    LabVIEW Unit Testing with Coverage & Reporting

    LabVIEW 2

  6. TransparentAssertions TransparentAssertions Public

    LabVIEW assertion library with expressive test failures that supports different unit test frameworks

    LabVIEW 1