Virtual feasibility
Posted: Mon 26. Aug 2024, 22:36
I use two third-party (win X86) applications that communicate via physical CAN. This requires two PCAN USB adapters connected to the same PC with a short CAN cable in a loopback fashion. I want to replace the CAN hardware with virtual equivalents.
Today:
ProcessA.exe<--->PCANUSB 0x51<--->CAN CABLE<--->PCANUSB 0x52<--->ProcessB.exe
Is it possible to write a new intermediary application to spawn 2 virtual PCAN-USB devices for the original applications to communicate through or would each application have to be rewritten and recompiled to support virtual adapters using the Developer API?
Ideally, if an intermediary gateway application could be written, I could then spool up several virtual nets and allow multiple pairs of these third party processes to communicate.
Future fantasy:
ProcessA.exe_instance1<--->Virtual Net_1<--->ProcessB.exe_instance1
ProcessA.exe_instance2...
Today:
ProcessA.exe<--->PCANUSB 0x51<--->CAN CABLE<--->PCANUSB 0x52<--->ProcessB.exe
Is it possible to write a new intermediary application to spawn 2 virtual PCAN-USB devices for the original applications to communicate through or would each application have to be rewritten and recompiled to support virtual adapters using the Developer API?
Ideally, if an intermediary gateway application could be written, I could then spool up several virtual nets and allow multiple pairs of these third party processes to communicate.
Future fantasy:
ProcessA.exe_instance1<--->Virtual Net_1<--->ProcessB.exe_instance1
ProcessA.exe_instance2...