M150 and C125 VPN remote connection

Information on getting your PC to talk to your MoTeC product via RS232, CAN, USB or Ethernet.

M150 and C125 VPN remote connection

Postby Cosmo99 on Mon Jan 10, 2022 11:36 pm

Hi, I use a router to connect the M150 and the C125 dash to a common LAN and access from PC over wifi. I would use a bridged VPN server installed on the router to remotely access the LAN network from PC as a clinet. Both the programs, M1 Tune and C125 dash manager, discover the devices. I can connect without problems to the dash, but when I try to connect to the ECU, M1 Tune is not responding and crashes.
Could anyone help me?
Thanks
Cosmo99
 
Posts: 4
Joined: Sun Jan 09, 2022 2:41 am

Re: M150 and C125 VPN remote connection

Postby Stephen Dean on Mon Jan 10, 2022 11:53 pm

Hi,

Is this causing M1 Tune to generate a dmp file? If so, can you email that file to support@motec.com.au thnaks.
Stephen Dean
MoTeC Research Centre Melbourne, Australia
User avatar
Stephen Dean
Site Admin
 
Posts: 1614
Joined: Tue Dec 02, 2014 10:29 am
Location: Melbourne

Re: M150 and C125 VPN remote connection

Postby Cosmo99 on Wed Jan 12, 2022 8:45 pm

Thanks for reply.
No, there's no dmp file.
Cosmo99
 
Posts: 4
Joined: Sun Jan 09, 2022 2:41 am

Re: M150 and C125 VPN remote connection

Postby Stephen Dean on Thu Jan 13, 2022 10:35 am

Hi,

In M1 Tune, under the View drop down menu, you will find the Show Messages and Show ECU Monitor window options, if these are both enabled and an attempt is made to connect to the M1, what errors come up?
Stephen Dean
MoTeC Research Centre Melbourne, Australia
User avatar
Stephen Dean
Site Admin
 
Posts: 1614
Joined: Tue Dec 02, 2014 10:29 am
Location: Melbourne

Re: M150 and C125 VPN remote connection

Postby Cosmo99 on Fri Jan 21, 2022 1:26 am

The ECU messages window shows this:

2671.817 xcp_udp:XCP connect [fe80:0000:0000:0000:61f4:1cfb:a68f:9041]:62628
2671.826 xcp_udp:../xcp/eth.cpp(197): XCP connected
2672.498 xcp_udp:../genio/stream_info.cpp(524): ctx 000007ed Size=5060
2688.555 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2690.234 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2691.096 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2692.307 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2693.433 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2694.572 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2695.254 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2696.564 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2697.212 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2698.983 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2699.843 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2700.347 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2702.012 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2702.388 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2704.324 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2704.872 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2705.784 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2706.712 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2707.929 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2709.015 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2710.584 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2711.035 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2712.377 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2713.177 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2714.283 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2716.016 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2716.959 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2717.358 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2719.029 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2720.053 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2720.316 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2721.799 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2722.746 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2723.317 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2725.612 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2725.613 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2725.616 xcp_udp:../genio/stream_info.cpp(524): ctx 00000021 Size=96
2726.753 xcp_udp:../xcp/xcp/stack.cpp(544): <- pid=0xFE, error_code=0x00 646
2735.129 xcp_udp:XCP connect [fe80:0000:0000:0000:61f4:1cfb:a68f:9041]:65492
2735.138 xcp_udp:../xcp/eth.cpp(197): XCP connected
Cosmo99
 
Posts: 4
Joined: Sun Jan 09, 2022 2:41 am

Re: M150 and C125 VPN remote connection

Postby Cosmo99 on Sun Feb 06, 2022 10:11 am

Anyone could help me?

Thanks
Cosmo99
 
Posts: 4
Joined: Sun Jan 09, 2022 2:41 am


Return to MoTeC PC Comms

Who is online

Users browsing this forum: No registered users and 2 guests