ip camp

Förderprojekt „PRIMA“ – ip camp stellt Ergebnisse auf ON Campus Festival der THI vor Anlässlich des 30-jährigen Geburtstags der Technischen Hochschule Ingolstadt (THI) fand am vergangenen Freitag das ON Campus Festival statt. Wissenschaft und Forschung öffneten dabei Kindern und Familien die Türen und stellten spannende Zukunftstechnologien im Bereich der künstlichen Intelligenz vor. IP Camp präsentierte dabei zusammen mit Prof. Dr. Hans-Georg Schweiger das gemeinsame Förderprojekt „PRIMA – PRedictive Industrial Maintenance Agent for Batteries“ am Forschungs- und Testzentrum CARISSMA. Das PRIMA-Projekt zielt darauf ab, eine IoT- und KI-Plattform zu entwickeln, um den Zustand von Batterien zu überwachen, Ausfälle vorherzusagen, präzise Wartungseinsätze zu planen (predictive maintenance) und Schäden an Batterien zu vermeiden. Das Thema sowie die vorgestellten Ergebnisse stießen auf großes Interesse bei den Besuchern des sehr gut organisierten Festivals der Technische Hochschule Ingolstadt. #ipcamp #PRIMA #PredictiveMaintenance #CARISSMA #THI

CONTACT 2024 - ip camp presents itself to future talents   Together with our sister companies digitalwerk GmbH Regensburg and e.telligent GmbH, we attended the career and recruiting fair CONTACT at the Technical University of Ingolstadt (THI) last week.   The fair gave us the opportunity to meet qualified students and graduates, answer their questions and give them an insight into our company. Our first appearance at CONTACT was a great success. We are already looking forward to next year's edition.

Connecta 2023 – ip camp auf der Suche nach neuen Talenten Die Connecta, die größte Karriere- und Recruitingmesse für Studenten in Bayern, hat im Jahr 2023 erneut ihre Tore geöffnet, und ip camp war zum wiederholten Mal mit von der Partie. Insgesamt nahm ip camp bereits zum dritten Mal in Folge an dieser bedeutenden Veranstaltung teil, um die Besucherinnen und Besucher der Messe über Karrieremöglichkeiten im Unternehmen zu informieren. Die Messe bot eine hervorragende Gelegenheit, mit motivierten und hochqualifizierten Studierenden und Absolventen in Kontakt zu treten, ihre Fragen zu beantworten und ihnen Einblicke in die spannende Arbeitswelt von ip camp zu vermitteln. Das mehrköpfige Messeteam teilte seine Erfahrungen sowie sein Fachwissen und zeigte den Interessierten, wie sie sich bei ip camp einbringen können. Eine Übersicht aller offenen Stellen gibt es hier: https://lnkd.in/eTFCUag3 Als stolzes Mitglied der INSTART group wurde ip camp auf der Connecta auch von den Schwesterunternehmen digitalwerk GmbH Regensburg und e.telligent GmbH begleitet, die gemeinsam in den Leittechnologiebereichen Elektromobilität, Autonomes Fahren und Big Data tätig sind. Die starke Präsenz des Unternehmensverbundes auf der Karriere- und Recruitingmesse verdeutlicht, dass die INSTART group junge, neue Talente herzlich willkommen heißt und bereit ist, in deren berufliche Entwicklung zu investieren. #ipcamp #connecta #recruiting #newtalents 

Mercury - Validating Logger Configurations based on trace files   Mercury enables OEMs to automate vehicle network trace file analysis. The following scenario is a basic use case for Mercury that helps analysts find a solution faster.   ECU software version updates and building in/out logger devices are expected when working with many test vehicles simultaneously. When a trace file makes it to an analyst who wants to find the reason for the error, it must have no foundational problems. Cables connected to the wrong ports or wrong configuration can cause such issues. Analysts must not use trace files from incorrectly configured loggers, but pre-validating them requires manual effort.    Mercury can automate this process. A simple Mercury script processes all incoming trace files. The analysts can define a list of channels and signal counts. Based on this information, Mercury checks if all the channels contain at least the number of expected signals in the trace file. Mercury marks the trace file as invalid if any signals are missing and generates a report about all the failures.   This automation reduces the daily workload of an analyst by some hours and increases the quality. The automation allows the analysts to work on the more essential failure investigations with proper trace files, getting to the most wanted results earlier. 

Keep your models clean from errors! Ensuring the consistency and integrity of AUTOSAR models throughout the development of vehicles is crucial. Errors introduced in the models can slow down the development process and, in the worst case, are only discovered during vehicle integration at the end of a long and expensive root cause analysis. The later a problem is found, the more impact it has on the system, thus the more costly it is to be corrected. Although most of the model editing tools available on the market provide built-in support for checking consistency and correctness, the models are sometimes edited with tools that disregard consistency and changes go unnoticed. In the process of creating and distributing models between the suppliers and the OEM, many in-house solutions (scripts, manual splitting/merging, transformations) are involved. As a result, inconsistent models are often delivered to suppliers or back to the OEM, leading to the problems above. Our easily automated solution makes it possible to keep your models clean from the mess. Our checker framework integrates easily into every process step, effectively detecting incompatibilities between descriptors and models. Thanks to the flexibility of the framework, not only the standard rules can be checked, but you can define your additional in-house modeling rules also.

Mercury - Validating Logger Configurations based on trace files   Mercury enables OEMs to automate vehicle network trace file analysis. The following scenario is a basic use case for Mercury that helps analysts find a solution faster.   ECU software version updates and building in/out logger devices are expected when working with many test vehicles simultaneously. When a trace file makes it to an analyst who wants to find the reason for the error, it must have no foundational problems. Cables connected to the wrong ports or wrong configuration can cause such issues. Analysts must not use trace files from incorrectly configured loggers, but pre-validating them requires manual effort.    Mercury can automate this process. A simple Mercury script processes all incoming trace files. The analysts can define a list of channels and signal counts. Based on this information, Mercury checks if all the channels contain at least the number of expected signals in the trace file. Mercury marks the trace file as invalid if any signals are missing and generates a report about all the failures.   This automation reduces the daily workload of an analyst by some hours and increases the quality. The automation allows the analysts to work on the more essential failure investigations with proper trace files, getting to the most wanted results earlier. 

Mercury - Validating Logger Configurations based on trace files   Mercury enables OEMs to automate vehicle network trace file analysis. The following scenario is a basic use case for Mercury that helps analysts find a solution faster.   ECU software version updates and building in/out logger devices are expected when working with many test vehicles simultaneously. When a trace file makes it to an analyst who wants to find the reason for the error, it must have no foundational problems. Cables connected to the wrong ports or wrong configuration can cause such issues. Analysts must not use trace files from incorrectly configured loggers, but pre-validating them requires manual effort.    Mercury can automate this process. A simple Mercury script processes all incoming trace files. The analysts can define a list of channels and signal counts. Based on this information, Mercury checks if all the channels contain at least the number of expected signals in the trace file. Mercury marks the trace file as invalid if any signals are missing and generates a report about all the failures.   This automation reduces the daily workload of an analyst by some hours and increases the quality. The automation allows the analysts to work on the more essential failure investigations with proper trace files, getting to the most wanted results earlier.