Multiple CAN devices crashes Tunerstudio

Ted75zcar · Post by **Ted75zcar** » Fri Dec 23, 2016 7:50 pm

Hello All,

First post ... asking for help.

I am running MS2 (MS2PNP by DIYautotune for '90-93 Miata, MM9093)
FW: MS2/Extra 3.4.2 20160421
3 CAN devices - jbperf TinyIOx v1.2 with 0.2.0 Alpha FW
Tunerstudio MS Ultra v3.0.15

I have all 3 expansion boards on the MS CAN bus. When I enable realtime data for any single instance, performance is choppy, but it seems to work. As soon as I enable realtime data for any combination of 2 or 3 devices, Tunerstudio oscillates between offline and online. Occasionally one or more of the devices will lose connectivity and be removed from the project. I have seen this oscillatory behavior with a single device, but it is intermittent and uncommon. While in this oscillatory state, the CAN device menu in Project Properties -> Preferences -> Connected Device does odd things. Device IDs will change, or devices will disappear all-together. I am trying to determine if anybody has successfully integrated multiple TinyIOx devices to the MS2, but am not having an luck there.

I am attaching the project backup, as well as 3 datalogs. One datalog is taken with all three devices connected, but realtime data off. This appears to work normally. The second has a single realtime data enabled, and the last one has 2 devices with realtime enabled.

I do not see anything that is particularly glaring in the first log (to my untrained eye). We do seem to have a mismatched CRC for page 1 in all configurations. I do not know anything about CAN, so I guess it could be because page 1 contains the updated data ... I believe that the use of the smoothRPM data in my calculation of approximate torque is causing the "Debug: Could not get value for OutputChannel:approxTorque" entries. The MS is on the bench for this testing, no simulated inputs. We also get these:

-Warning: Controller Reported an Under-run
-Debug: call failed protocol validation, running stats: 1 failed validation, 64 successful.
-Debug: Protocol reported error after write 0x80, waiting 20ms and retry

In the second log, we start to see the following messages that drew my interest:

12/23/16 4:29:58 PM :Info: D2XX Closed: USB Serial Converter
Dec 23, 2016 4:29:58 PM com.ftdi.FTDevice getDevices
INFO: Found devs: 1 (All:1)
12/23/16 4:29:58 PM : Debug: Opening Connection to FTDI Device: USB D2XX, Serial #FTGFDW9O @ 115200 Baud
Device: FTDevice{devDescription=USB Serial Converter, devSerialNumber=FTGFDW9O}
Device Type: DEVICE_232R
Device ID: 67330049
Device Location ID: 19
12/23/16 4:29:58 PM :Info: D2XX Opened: USB Serial Converter

Tunerstudio does not appear to go offline with only 1 device sending realtime.

The Third file has several of these USB closed messages. it also has these messages:

12/23/16 4:37:14 PM :Info: D2XX Closed: USB Serial Converter
Dec 23, 2016 4:37:14 PM com.ftdi.FTDevice getDevices
INFO: Found devs: 1 (All:1)
12/23/16 4:37:14 PM : Debug: Opening Connection to FTDI Device: USB D2XX, Serial #FTGFDW9O @ 115200 Baud
Device: FTDevice{devDescription=USB Serial Converter, devSerialNumber=FTGFDW9O}
Device Type: DEVICE_232R
Device ID: 67330049
Device Location ID: 19
12/23/16 4:37:14 PM :Info: D2XX Opened: USB Serial Converter
12/23/16 4:37:15 PM :Warning: Controller Reported an Under-run
12/23/16 4:37:15 PM : Debug: call failed protocol validation, running stats: 1 failed validation, 9 successful.
12/23/16 4:37:15 PM : Debug: Protocol reported error after write 0x80, waiting 20ms and retry
12/23/16 4:37:15 PM :Warning: Controller Reported a Out of Range
12/23/16 4:37:15 PM : Debug: call failed protocol validation, running stats: 2 failed validation, 9 successful.
12/23/16 4:37:15 PM : Debug: Protocol reported error on 2nd attempt after write 0x80, waiting 20ms and retry
12/23/16 4:37:15 PM :Warning: Controller Reported a Out of Range
12/23/16 4:37:15 PM : Debug: call failed protocol validation, running stats: 3 failed validation, 9 successful.
12/23/16 4:37:15 PM : Debug: Protocol retry FAILED!!! Failed 3 attempts, giving up.
12/23/16 4:37:15 PM : Debug: Controller reported Comms error, skipping runtime data read. Response packet failed validation: Controller Reported a Out of Range, 3 attempts made.
12/23/16 4:37:15 PM : Debug: No Remaining Queue Write instructions
12/23/16 4:37:15 PM : Debug: Went offline
12/23/16 4:37:15 PM :Info: D2XX Closed: USB Serial Converter
12/23/16 4:37:15 PM : Debug: No Remaining Queue Write instructions
12/23/16 4:37:15 PM :Info: Went offline 2
Dec 23, 2016 4:37:15 PM com.ftdi.FTDevice getDevices
INFO: Found devs: 1 (All:1)
12/23/16 4:37:15 PM : Debug: Opening Connection to FTDI Device: USB D2XX, Serial #FTGFDW9O @ 115200 Baud
Device: FTDevice{devDescription=USB Serial Converter, devSerialNumber=FTGFDW9O}
Device Type: DEVICE_232R
Device ID: 67330049
Device Location ID: 19
12/23/16 4:37:15 PM :Info: D2XX Opened: USB Serial Converter

Sorry for the long post, and I sure could use the help. Super Frustrated here

Ted75zcar · Post by **Ted75zcar** » Fri Dec 23, 2016 7:58 pm

First attachment was too big. Reattach

Post by **jsmcortina** » Sat Dec 24, 2016 8:39 am

Are the CAN devices set to different CANids and is you main project set to match? What does you Project Properties -> CAN Devices page look like.

James

Ted75zcar · Post by **Ted75zcar** » Sat Dec 24, 2016 9:03 am

jsmcortina wrote:Are the CAN devices set to different CANids and is you main project set to match? What does you Project Properties -> CAN Devices page look like.

James

Yes each device has a unique ID, verified by another external application (the jbperf port scanner). Each unique ID is associated with a unique CAN device in the CAN Devices page, each unique CAN device is pointing to a unique ini.

If realtime data is turned off in the CAN devices page, devices will reliably show up in the connected devices menu properly. Once realtime data is turned on, this menu becomes prone to displaying connected devices at other addresses, as well as connected devices disappearing.

example:
CAN hardware devices are assigned CAN IDs 3,4,6. When initially configuring MS2, the connected devices menu properly shows "Tiny ..." devices at 3,4,6

each device initially configured with realtime data turned turned off. Each device can be configured as expected from the "Device" pulldown on the tunerstudio main screen.

enable real time data for a single CAN instance (any) -> Tunerstudio UI performance appears to be degraded a little, but CAN device data is correctly reported in Tunerstudio

enable real time data for any combination of 2 or 3 devices -> Tunerstudio cycles between offline/online. When online, we do seem to get 1 or 2 valid data points for the main controller as well as the realtime enabled Tiny's. Realtime counter in the protocol window increments a few counts, as do canData and okcount, no other values change. An online/offline cycle will clear all protocol fields.

Ted75zcar · Post by **Ted75zcar** » Sun Dec 25, 2016 10:43 am

So, while I am not sure of this, this thread:

http://www.msextra.com/forums/viewtopic ... 9&start=40

seems to be describing similar behaviors to what I am seeing.

Did the issues described in this thread ever get a conclusive Failure Analysis and Solution?

Thanks,

Ted75zcar · Post by **Ted75zcar** » Sun Dec 25, 2016 10:48 am

oh, and Tunerstudio creates a debug log no matter what I do with the Comm debug log radio button under Communications.

EDIT: Just noticed that the log is much more verbose when the radio button is checked. Sorry!

Ted75zcar · Post by **Ted75zcar** » Sun Dec 25, 2016 6:32 pm

so don't google search

megasquirt l.E.z (lol)

starting to dig in a little more.

These logs are taken with the FTDI bridge wired directly to the B&G UART (with a Win 10 machine). I confirmed similar behavior on another XP machine.

I don't really know what I am looking at, but when any single CAN channel real time data is enabled, the controller reads 49 bytes. When I enable real time data on a second channel, the controller reads 49 bytes from the first, and then 249 from the second. It then throws an error, and closes the serial port

Single CAN enabled with RTD (TIOx2)

Code: Select all

12/25/16 6:19:08 PM :Debug: old style time to read outpc: 37 ms.
12/25/16 6:19:08 PM :Debug: Real OchDelay for TIOx2: 15, timeout=300
12/25/16 6:19:08 PM :Time: 0:24.224: SENT 13 bytes, 13 bytes
x00 x07 x72 x03 x07 x00 x00 x00 x2D x97 xF0 xEC xB7                   ..r.....-....

12/25/16 6:19:08 PM :Time: 0:24.233: READ 3 bytes, 3 bytes
x00 x2E x06                                                           ...

12/25/16 6:19:08 PM :Time: 0:24.249: READ 49 bytes, 49 bytes
x07 x8F x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x03 xEA       ................
x00 x01 x00 x00 x01 x20 x01 x83 x03 xFE x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x7C xBC x52       .............|.R
x9B                                                                   .

12/25/16 6:19:09 PM :Time: 0:24.250: SENT 13 bytes, 13 bytes
x00 x07 x72 x03 x07 x00 x8A x00 x01 x49 x8A x1E x02                   ..r......I...

12/25/16 6:19:09 PM :Time: 0:24.265: READ 3 bytes, 3 bytes
x00 x02 x06                                                           ...

12/25/16 6:19:09 PM :Time: 0:24.265: READ 5 bytes, 5 bytes
x00 x17 x83 xB5 x79                                                   ....y

12/25/16 6:19:09 PM :Debug: Blocked time to read outpc: 42 ms.
12/25/16 6:19:09 PM :Debug: Real OchDelay for 1991Miata_2016-12-22: 120, timeout=300
12/25/16 6:19:09 PM :Time: 0:24.385: SENT 7 bytes, 7 bytes
x00 x01 x41 xD3 xD9 x9E x8B

2 RTD enabled CAN devices

Code: Select all

12/25/16 6:14:22 PM :Debug: Real OchDelay for TIOx2: 15, timeout=300
12/25/16 6:14:22 PM :Time: 0:09.181: SENT 13 bytes, 13 bytes
x00 x07 x72 x03 x07 x00 x00 x00 x2D x97 xF0 xEC xB7                   ..r.....-....

12/25/16 6:14:22 PM :Time: 0:09.195: READ 3 bytes, 3 bytes
x00 x2E x06                                                           ...

12/25/16 6:14:22 PM :Time: 0:09.195: READ 49 bytes, 49 bytes
x06 x7C x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x03 xE9       .|..............
x00 x01 x00 x00 x01 x20 x01 x78 x03 xFF x00 x00 x00 x00 x00 x00       .......x........
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x6A xB5 xC9       .............j..
xD2                                                                   .

12/25/16 6:14:22 PM :Time: 0:09.196: SENT 13 bytes, 13 bytes
x00 x07 x72 x03 x07 x00 x8A x00 x01 x49 x8A x1E x02                   ..r......I...

12/25/16 6:14:22 PM :Time: 0:09.211: READ 3 bytes, 3 bytes
x00 x02 x06                                                           ...

12/25/16 6:14:22 PM :Debug: Blocked time to read outpc: 30 ms.
12/25/16 6:14:22 PM :Time: 0:09.211: READ 5 bytes, 5 bytes
x00 x17 x83 xB5 x79                                                   ....y

12/25/16 6:14:22 PM :Debug: Real OchDelay for TIOx3: 15, timeout=300
12/25/16 6:14:22 PM :Time: 0:09.212: SENT 13 bytes, 13 bytes
x00 x07 x72 x0C x07 x00 x00 x00 xF5 xEE xAE x04 x84                   ..r..........

12/25/16 6:14:22 PM :Time: 0:09.243: READ 3 bytes, 3 bytes
x00 xF6 x06                                                           ...

12/25/16 6:14:22 PM :Debug: Blocked time to read outpc: 63 ms.
12/25/16 6:14:22 PM :Time: 0:09.275: READ 249 bytes, 249 bytes
x06 x26 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x03 xE2       .&..............
x00 x00 x00 x00 x01 x1F x01 x80 x03 xFE x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x01 xF4 x01 xF4       ................
x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4       ................
x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x93 x93 x93 x93       ................
x93 x93 x93 x93 x93 x93 x93 x93 x93 x93 x93 x93 x00 x00 x00 x00       ................
x00 x00 xE3 x3F xE2 x9F x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ...?............
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x03 xFF x03 xFF x03 xFF       ................
x03 xFF x03 xFF x03 xFF x03 xFF x03 xFF x01 xBC x01 xBC x01 xBC       ................
x01 xBC x01 xBC x01 xBC x01 xBC x01 xBC x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x51 xCF x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ..Q.............
x00 x00 x00 x00 x00 x31 xA2 xA4 x73                                   .....1..s

12/25/16 6:14:22 PM :Debug: Comm Exception Caught: Invalid runtime data received.
Dec 25, 2016 6:14:22 PM h.q run
WARNING: Comm Timeout Caught
z.b: Invalid runtime data received.
	at l.E.z(Unknown Source)
	at h.p.k(Unknown Source)
	at h.q.run(Unknown Source)

12/25/16 6:14:22 PM :Info: Re-establishing connection to: RS232: Port:COM7, Baud:115200
12/25/16 6:14:22 PM :Debug: JSSC ControllerInterface Close Connection currentPort == null:false
12/25/16 6:14:22 PM :Info: Closing Port
12/25/16 6:14:23 PM :Info: Successfully Closed Port
12/25/16 6:14:23 PM :Info: Opening port: COM7

2 different CAN devices enabled, TIOx1 and TIOx2

Code: Select all

12/25/16 6:16:59 PM :Debug: Real OchDelay for TIOx1: 15, timeout=300
12/25/16 6:16:59 PM :Time: 0:14.599: SENT 13 bytes, 13 bytes
x00 x07 x72 x04 x07 x00 x00 x00 x2D x8A xF5 xDC x0F                   ..r.....-....

12/25/16 6:16:59 PM :Time: 0:14.612: READ 3 bytes, 3 bytes
x00 x2E x06                                                           ...

12/25/16 6:16:59 PM :Time: 0:14.612: READ 49 bytes, 49 bytes
x06 x9A x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x03 xE7       ................
x00 x00 x00 x00 x01 x1A x01 x84 x03 xFE x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x89 xC0 xEC       ................
x5C                                                                   \

12/25/16 6:16:59 PM :Time: 0:14.613: SENT 13 bytes, 13 bytes
x00 x07 x72 x04 x07 x00 x8A x00 x01 x54 x8F x2E xBA                   ..r......T...

12/25/16 6:16:59 PM :Time: 0:14.628: READ 3 bytes, 3 bytes
x00 x02 x06                                                           ...

12/25/16 6:16:59 PM :Time: 0:14.628: READ 5 bytes, 5 bytes
x00 x17 x83 xB5 x79                                                   ....y

12/25/16 6:16:59 PM :Debug: Blocked time to read outpc: 30 ms.
12/25/16 6:16:59 PM :Debug: Real OchDelay for TIOx2: 15, timeout=300
12/25/16 6:16:59 PM :Time: 0:14.629: SENT 13 bytes, 13 bytes
x00 x07 x72 x03 x07 x00 x00 x00 xF5 x1F xF8 xB6 x51                   ..r.........Q

12/25/16 6:16:59 PM :Time: 0:14.660: READ 3 bytes, 3 bytes
x00 xF6 x06                                                           ...

12/25/16 6:16:59 PM :Debug: Blocked time to read outpc: 63 ms.
12/25/16 6:16:59 PM :Time: 0:14.692: READ 249 bytes, 249 bytes
x07 x13 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x03 xEB       ................
x00 x01 x00 x00 x01 x20 x01 x8D x03 xFF x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x01 xF4 x01 xF4       ................
x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4       ................
x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x01 xF4 x93 x93 x93 x93       ................
x93 x93 x93 x93 x93 x93 x93 x93 x93 x93 x93 x93 x00 x00 x00 x00       ................
x00 x00 x21 x6C x62 xFF x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ..!lb...........
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x03 xFF x03 xFF x03 xFF       ................
x03 xFF x03 xFF x03 xFF x03 xFF x03 xFF x01 xBC x01 xBC x01 xBC       ................
x01 xBC x01 xBC x01 xBC x01 xBC x01 xBC x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x18 xFE x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x37 x0E x5A xC9                                   .....7.Z.

12/25/16 6:16:59 PM :Debug: Comm Exception Caught: Invalid runtime data received.
Dec 25, 2016 6:16:59 PM h.q run
WARNING: Comm Timeout Caught
z.b: Invalid runtime data received.
	at l.E.z(Unknown Source)
	at h.p.k(Unknown Source)
	at h.q.run(Unknown Source)

12/25/16 6:16:59 PM :Info: Re-establishing connection to: RS232: Port:COM7, Baud:115200
12/25/16 6:16:59 PM :Debug: JSSC ControllerInterface Close Connection currentPort == null:false
12/25/16 6:16:59 PM :Info: Closing Port
12/25/16 6:16:59 PM :Info: Successfully Closed Port
12/25/16 6:16:59 PM :Info: Opening port: COM7
12/25/16 6:17:00 PM :Debug: No Remaining Queue Write instructions
12/25/16 6:17:00 PM :Debug: Went offline
12/25/16 6:17:00 PM :Debug: JSSC ControllerInterface Close Connection currentPort == null:false
12/25/16 6:17:00 PM :Info: Closing Port
12/25/16 6:17:00 PM :Info: Successfully Closed Port
12/25/16 6:17:00 PM :Debug: No Remaining Queue Write instructions
12/25/16 6:17:00 PM :Info: Went offline 2
Dec 25, 2016 6:17:00 PM h.q run
INFO: Inside read error
z.b: Invalid runtime data received.
	at l.E.z(Unknown Source)
	at h.p.k(Unknown Source)
	at h.q.run(Unknown Source)

12/25/16 6:17:00 PM :Info: Opening port: COM7

I know these monster posts aren't particularly effective, but I have hope

Ted75zcar · Post by **Ted75zcar** » Mon Dec 26, 2016 3:45 pm

Just got it to happen with only 1 Tiny enabled for real time data

Code: Select all

12/26/16 3:41:45 PM :Debug: Real OchDelay for TIOx3: 15, timeout=300
12/26/16 3:41:45 PM :Time: 3:59.227: SENT 13 bytes, 13 bytes
x00 x07 x72 x0C x07 x00 x00 x00 x2D x66 xA6 x5E x62                   ..r.....-f.^b

12/26/16 3:41:45 PM :Time: 3:59.241: READ 3 bytes, 3 bytes
x00 x2E x06                                                           ...

12/26/16 3:41:45 PM :Time: 3:59.241: READ 49 bytes, 49 bytes
x03 xA9 x00 x64 x00 x00 x02 x71 x00 x00 x00 x00 x00 x00 x03 xE7       ...d...q........
x00 x00 x00 x00 x01 x1D x01 x87 x03 xFD x00 x00 x00 x00 x00 x00       ................
x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 x00 xB7 xC8 x33       ...............3
xF2                                                                   .

12/26/16 3:41:45 PM :Time: 3:59.242: SENT 13 bytes, 13 bytes
x00 x07 x72 x0C x07 x00 x8A x00 x01 xB8 xDC xAC xD7                   ..r..........

12/26/16 3:41:45 PM :Time: 3:59.257: READ 3 bytes, 3 bytes
x00 x02 x06                                                           ...

12/26/16 3:41:45 PM :Time: 3:59.257: READ 5 bytes, 5 bytes
x00 x17 x83 xB5 x79                                                   ....y

12/26/16 3:41:45 PM :Debug: Blocked time to read outpc: 30 ms.
12/26/16 3:41:45 PM :Debug: Comm Exception Caught: Invalid runtime data received.
Dec 26, 2016 3:41:45 PM h.q run
WARNING: Comm Timeout Caught
z.b: Invalid runtime data received.
	at l.E.z(Unknown Source)
	at h.p.k(Unknown Source)
	at h.q.run(Unknown Source)

12/26/16 3:41:45 PM :Info: Re-establishing connection to: RS232: Port:COM7, Baud:115200
12/26/16 3:41:45 PM :Debug: JSSC ControllerInterface Close Connection currentPort == null:false
12/26/16 3:41:45 PM :Info: Closing Port
12/26/16 3:41:45 PM :Info: Successfully Closed Port
12/26/16 3:41:45 PM :Info: Opening port: COM7
12/26/16 3:41:45 PM :Debug: Real OchDelay for 1991Miata_2016-12-22: 120, timeout=300
12/26/16 3:41:45 PM :Time: 3:59.729: SENT 7 bytes, 7 bytes
x00 x01 x41 xD3 xD9 x9E x8B

racingmini_mtl · Post by **racingmini_mtl** » Tue Dec 27, 2016 3:48 pm

As I said on my forum, I checked a few of the log snippets posted above and everything seems to be fine in the messages exchanged from TS and the ECU. The responses from the TIOx contains the correct amount of data in response to the TS requests and the delay is short according to the time stamps which would mean the TIOx is responding and behaving correctly. The format and size of the response message are also correct and I checked that the CRC32 is also valid (checked for a few of them before the error message) which means that the MS2 is doing its job of forwarding and formatting the messages between TS and the TIOx.

So either there is something not shown in the logs that TS expects to see (no unanswered messages or malformed or delayed ones) or TS is declaring an error that is not actually there.

Hopefully Phil will see this and reply. Maybe this should be moved to the TS forum?

Jean

Ted75zcar · Post by **Ted75zcar** » Sat Dec 31, 2016 10:49 pm

Hello Phil,

Have you had a chance to look into this yet? I am at a point where I need to make some decisions based on whether I will be able to collect data from these three CAN devices at the same time.

Thanks,

Ted

LT401Vette · Post by **LT401Vette** » Wed Jan 04, 2017 2:48 pm

I created a project with an MS3-Pro, CAN EGT and MicroSquirt Trans Controller.

It seems to work fine.

Perhaps something is mis configured or something not in those log snippets.

Send a full comm debug log and a Project backup to support <at> efianalytics. com
with a link to this thread and we can have a look.

Ted75zcar · Post by **Ted75zcar** » Wed Jan 04, 2017 2:59 pm

awesome, will do tonight. Thanks!

Edit: The full logs are provided in an earlier post.

racingmini_mtl · Post by **racingmini_mtl** » Wed Jan 04, 2017 3:02 pm

Phil,

I will try to reproduce it on my end but I wondered if you had multiple identical CAN devices that you could use (obviously with different IDs). I was wondering if the problem is due to having multiple CAN devices with the same ini and with the same default ID in the ini.

Jean

Ted75zcar · Post by **Ted75zcar** » Wed Jan 04, 2017 6:14 pm

where in the ini's is this default ID defined?

racingmini_mtl · Post by **racingmini_mtl** » Wed Jan 04, 2017 7:02 pm

Ted75zcar wrote:where in the ini's is this default ID defined?

In the case of the TinyIOx, this is defined in the commands. Each time you see 'x04', that's the default CAN ID that TunerStudio changes to the value defined in the project.

That's actually the legacy way of defining the default ID and I was wondering if that could be a contributing factor.

Jean

Ted75zcar · Post by **Ted75zcar** » Sat Jan 07, 2017 8:50 am

Phil, have you had a chance to review the files I sent you?

Thanks,

Ted

Sent from my iPhone using Tapatalk

LT401Vette · Post by **LT401Vette** » Mon Jan 09, 2017 6:50 am

From what I see so far, all looks right in your project.

I am wondering if the error is related to something in your custom.ini files.

Can you try it without any TIOxX_custom.ini files?

Ted75zcar · Post by **Ted75zcar** » Mon Jan 09, 2017 9:33 am

The debug files I sent you are WITHOUT custom ini files. The custom ini files were created later.

Have you tried your setup with two of the same CAN based devices on the same bus?

LT401Vette · Post by **LT401Vette** » Mon Jan 09, 2017 9:45 am

I don't have multiple IO Extenders here.
Being the same _shouldn't_ matter. Each ECU configuration is run in it's own space. But you never know.
Has Jean been able to reproduce this?

Ted75zcar · Post by **Ted75zcar** » Mon Jan 09, 2017 12:00 pm

Jean said he is going to try it out, but needs to get his set-up in order.

I am curious if ANY combination of 2 of the same devices on the same bus presents a problem. 2 EGTs ... 2 Transmission controllers ... Anything where one would have real-time data enabled, with Tunerstudio requesting data.

might help pinpoint where the issue is happening.

Megasquirt Support Forum (MSEXTRA)