CanDUE, EVShield, GVRET and SavvyCan Transmit Problem
Posted: Mon Feb 04, 2019 10:44 pm
Hey guys,
Can anyone help? I've built up an Evshield from Damien's GitHub page https://github.com/damienmaguire/EVShield.
I've fitted it to an Arduino Due and flashed it with the latest GVRET firmware from the collin80 repository.
I'm running the latest SavvyCan V187 on a windows 7 PC.
I can read CANBus data no problem, but transmitting is data is more temperamental.
Starting from a freshly booted Due, I can create a connection and activate it. I can then use the SavvyCan frame sender to send frames, say every 10ms on Bus 1 (which makes sense as that's the Due Can port that the transceiver is connected to). I can see some data on the transceiver input and Can Hi and Lo lines on the scope.
So far so good. However, when I disable the signal in the frame sender, the data continues to be transmitted on the CANBus and nothing seems to change that until I power the Due down.
I think the hardware is OK. It looks like some problem with the connection between the PC and Due. I can see commands in the SavvyCan serial port monitor, but the Due seems to be ignoring some of them.
Anybody else using any of this stuff and have you seen anything similar?
Can anyone help? I've built up an Evshield from Damien's GitHub page https://github.com/damienmaguire/EVShield.
I've fitted it to an Arduino Due and flashed it with the latest GVRET firmware from the collin80 repository.
I'm running the latest SavvyCan V187 on a windows 7 PC.
I can read CANBus data no problem, but transmitting is data is more temperamental.
Starting from a freshly booted Due, I can create a connection and activate it. I can then use the SavvyCan frame sender to send frames, say every 10ms on Bus 1 (which makes sense as that's the Due Can port that the transceiver is connected to). I can see some data on the transceiver input and Can Hi and Lo lines on the scope.
So far so good. However, when I disable the signal in the frame sender, the data continues to be transmitted on the CANBus and nothing seems to change that until I power the Due down.
I think the hardware is OK. It looks like some problem with the connection between the PC and Due. I can see commands in the SavvyCan serial port monitor, but the Due seems to be ignoring some of them.
Anybody else using any of this stuff and have you seen anything similar?