| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| jpc:index [2026/03/26 02:31] – [Getting Started] mfranklin | jpc:index [2026/03/26 02:45] (current) – [Theory of Operation] mfranklin |
|---|
| ====== jPC - Industrial ARM Embedded Linux Panel PC ====== | ====== CPi-J070WR - Industrial ARM Embedded Linux Panel PC ====== |
| |
| {{ :jpc:jpc-home-screen.png?680 }} | {{ :jpc:jpc-home-screen.png?680 }} |
| | {{ :jpc:jpc-under.png?560 }} ||| | | {{ :jpc:jpc-under.png?560 }} ||| |
| |
| The jPC is an ARM industrial panel PC designed to be a practical successor and generational upgrade to the [[:cuwin:index|Windows CE–based CUWIN]], while preserving what made it great: an excellent platform for developing industrial HMI solutions in .NET. | The CPi-J070WR is an ARM industrial panel PC designed to be a practical successor and generational upgrade to the [[:cuwin:index|Windows CE–based CUWIN]], while preserving what made it great: an excellent platform for developing industrial HMI solutions in .NET. |
| |
| Although the jPC runs embedded Linux, the jPC can be programmed using the latest versions of Windows' software development tools, including Visual Studio 2026, C# (v14), .NET (v10), WinForms, and even remote deployment and debugging from within the IDE. | Although the panel PC runs embedded Linux, the panel PC can be programmed using the latest versions of Windows' software development tools, including Visual Studio 2026, C# (v14), .NET (v10), WinForms, and even remote deployment and debugging from within the IDE. |
| |
| But it gets even better! Because ARM Linux is an officially supported .NET target platform, developers are no longer limited to a crippled "Compact" framework. Windows development PCs and the jPC share the same modern .NET SDK, runtime, and libraries, so most applications can be developed and debugged (hot reload too!) on a Windows PC and then deployed to the jPC with minimal or no code changes. | But it gets even better! Because ARM Linux is an officially supported .NET target platform, developers are no longer limited to a crippled "Compact" framework. Windows development PCs and the panel PC share the same modern .NET SDK, runtime, and libraries, so most applications can be developed and debugged (hot reload too!) on a Windows PC and then deployed to the panel PC with minimal or no code changes. |
| |
| Also, the jPC's operating system is much more full-featured than Windows CE or Windows Embedded Compact. It provides a modern web server, a modern web browser (for Kiosks), remote desktop, secure shell, and much, much more. It may be small and compact, but it can be more capable than many Windows x86 industrial panel PCs while still being programmed like one. | Also, the panel PC's operating system is much more full-featured than Windows CE or Windows Embedded Compact. It provides a modern web server, a modern web browser (for Kiosks), remote desktop, secure shell, and much, much more. It may be small and compact, but it can be more capable than many Windows x86 industrial panel PCs while still being programmed like one. |
| |
| ===== Features ===== | ===== Features ===== |
| </html> | </html> |
| |
| The jPC's operating system is very efficient, consuming only about 250MB, leaving approximately 90% of the device's memory available for resource-demanding solutions. | The panel PC's operating system is very efficient, consuming only about 250MB, leaving approximately 90% of the device's memory available for resource-demanding solutions. |
| ===== Getting Started ===== | ===== Getting Started ===== |
| |
| |
| ===== Theory of Operation ===== | ===== Theory of Operation ===== |
| * [[.:storage:index|Understanding the jPCs Storage Configuration]] | * [[.:storage:index|Understanding the Storage Configuration]] |
| * [[.:autorun:index|Configuring a Program to Start Automatically]] | * [[.:autorun:index|Configuring a Program to Start Automatically]] |
| * [[.:remote_desktop:index|Remote Desktop]] | * [[.:remote_desktop:index|Remote Desktop]] |
