you can rename the filename extension to something else to get through email then on the other end the user renames it back to .exestevieturbo wrote: ↑Mon Apr 15, 2019 6:29 pm ...I should have most of them too I can email you ( although emails can be funny about .exe files )
ECU connection problem following SSuite update
Re: ECU connection problem following SSuite update
Re: ECU connection problem following SSuite update
just removed ecu from case (carefully). still fails to see any device to connect to.
car starts so ECU fucntional.
ipconfig /all revealls the following
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
data omitted
Default Gateway . . . . . . . . . :
data omitted
DNS Servers . . . . . . . . . . . : fe80::9e97:26ff:fe96:437c%13
so the default gateway is blank. as is the DNS suffix. Does that shed any light on it? I just read this as confirmatiopn that it pc can't see ecu
when connected to my home LAN (as I have to be to write on this forum) ipconfig /all returns
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : lan
data omitted
Default Gateway . . . . . . . . . : 192.168.1.254
data omitted
DNS Servers . . . . . . . . . . . : 192.168.1.254
So... yeah pc ethernet is working ok...
proper stumped. Anybody from SYVECS got an opinion on what to try next?
car starts so ECU fucntional.
ipconfig /all revealls the following
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
data omitted
Default Gateway . . . . . . . . . :
data omitted
DNS Servers . . . . . . . . . . . : fe80::9e97:26ff:fe96:437c%13
so the default gateway is blank. as is the DNS suffix. Does that shed any light on it? I just read this as confirmatiopn that it pc can't see ecu
when connected to my home LAN (as I have to be to write on this forum) ipconfig /all returns
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : lan
data omitted
Default Gateway . . . . . . . . . : 192.168.1.254
data omitted
DNS Servers . . . . . . . . . . . : 192.168.1.254
So... yeah pc ethernet is working ok...
proper stumped. Anybody from SYVECS got an opinion on what to try next?
Last edited by rpw on Wed Apr 17, 2019 8:31 pm, edited 1 time in total.
Re: ECU connection problem following SSuite update
At least having removed from the case you've ruled out a dumb short circuit.
I know that the ECUs don't connect using IP addresses but use a lower level protocol (MAC address, layer 2, if not even layer 1). That's a random comment and doesn't in itself help you, sorry.
Have you emailed Syvecs tech support directly?
I know that the ECUs don't connect using IP addresses but use a lower level protocol (MAC address, layer 2, if not even layer 1). That's a random comment and doesn't in itself help you, sorry.
Have you emailed Syvecs tech support directly?
Re: ECU connection problem following SSuite update
Thanks for the offers of earlier SSuite but Im now pretty sure that it's not a PC/SSUite suite centric problem.