Not SavvyCAN problem... a PainINtheCAN problem

[striork]

@collin80 I was hoping to come back with good news to report...
Unfortunately, I genuinely believe it was easier to communicate with my ex-wife!
I seem to be at a bit of an impass... again! lol. I'm hoping someone sees this and can give me some pointers... the 2 other forums (Raspi & Ford Sync) nothing but crickets! Savvycan seems to be working... I unfortunately cannot "talk" to this network. Its a 2013 Ford Fusion. From what I gather, It has 2 HS can networks and an ms can network. The HS1 and HS3 networks meet and terminate at the car's dash. when I try to communicate with HS1 Its radio silence, MS radio silence and HS3 is where it gets squirrely.... I connect into HS3 at the radio (APM) node. I'm not creating a stub, I pulled the APM and tie directly in its place to the factory harness. with this board
https://seengreat.com/wiki/82/dual-ch-can-hat
As soon as i set the can up the dash completely shorts out. If I flip a turn signal the dash tries to light up, but fails. The dash is under the impression the car is not running when this happens as it will throw up a warning to the effect of "the car is not in park".

So sending messages back and forth between the 2 chips works just fine. Adding in a vcan also works. So the issues appear to be coming from the Ford. Ive started pulling it apart trying to start with some visuals. It didnt take long to find some trash. Someone was on this CANbus network before and they left it a mess! This is the state of the wiring behind the gateway.
all 3 networks are at 60ohm they read +- 2.5V fluctuating...

I cleaned up the dirty and open splices. I found 2 remote starters hooked up to the car! One was tapped into the MS CAN network. I disconnected both so i can start with a stock application.

Wanting to add a node on the MS network anyway, i spliced into the network behind the gateway.
With everything cleaned up, I am having the same issues while attempting coms with HS3. (as soon as I set can up) While attempting coms with HS1 or MS It’s radio silence…

jr@raspberrypi:~ $ dmesg | grep spi
[    3.263599] mcp251x spi0.1 can0: MCP2515 successfully initialized.
[    3.279308] mcp251x spi0.0 can1: MCP2515 successfully initialized.
jr@raspberrypi:~ $ dmesg | grep can
[    3.263599] mcp251x spi0.1 can0: MCP2515 successfully initialized.
[    3.279308] mcp251x spi0.0 can1: MCP2515 successfully initialized.
[  277.269863] can: controller area network core
[  277.274592] can: raw protocol

jr@raspberrypi:~ $ dmesg | fgrep -i can
[    3.232373] CAN device driver interface
[    3.263599] mcp251x spi0.1 can0: MCP2515 successfully initialized.
[    3.279308] mcp251x spi0.0 can1: MCP2515 successfully initialized.
[  277.269863] can: controller area network core
[  277.269908] NET: Registered PF_CAN protocol family
[  277.274592] can: raw protocol

those are all while connected to MS and/or HS1

then the only difference While connected to HS3 is the 2 dropped packets from can0

jr@raspberrypi:~ $ ifconfig
can0: flags=193<UP,RUNNING,NOARP>  mtu 16
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

can1: flags=193<UP,RUNNING,NOARP>  mtu 16
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0