DIAdem

cancel
Showing results for 
Search instead for 
Did you mean: 

Bus Log convertor Error/anomaly

Hello,

I have some difficulties with the bus log converter that I don't understand. I have files in ".asc" formats that I interpret with a standard J1939 ".dbc", I can't get any information, or I get error messages.

Because of this I am obliged to use another software. If someone has an idea? 

Attached is a zip including: a dbc to open the raw asc file, and the final TDM file obtained through Ipmotion. 

Best regards,  

POPPOTE_0-1602662910883.jpeg

POPPOTE_1-1602662929633.jpeg

 

0 Kudos
Message 1 of 14
(3,531 Views)

I am unable to read the IPmotion .TDM file 'HCLF_2020-10-01T16-01-09.TDM' you provided with DIAdem.  However, I was able to configure the DIAdem Bus Log Converter to read the file 'HCLF_2020-10-01T16-01-09.222Z.asc' along with the CAN database file 'j1939_ClaasAdapted.dbc'.   File 'HCLF_2020-10-01T16-01-09.222Z.asc' is a Vector ASCII (.asc) file. Below is an image of the contents of the Data Portal after a successful Bus Log Conversion.  

poppote(1).png

Below are images of the configuration of the DIAdem Bus Log Coverter:

poppote(2).pngpoppote(3).png

 

I also included a file named 'ascii_CAN_bus.zip' with a script to programmatically perform the bus log conversion (on multiple files).  

 

 Please reciprocate by letting me know if this was helpful.  

 

 

 

 

 

 

Message 2 of 14
(3,482 Views)

Thank you for your answer, and thank you for the script which will be very useful to me.

I don't understand why the tdm file doesn't work, I'll join you a new one . Indeed, I had not specified apart from the errors of the bus log converter that I can open a part of the file as you have shown (I but ID on J1939 to get more channels depending on the file), but it remains incomplete, that's the problem. The attached TDM file includes all the measurement channels that must be opened. Only Ipmotion or Vector canalyser manage to convert everything.

Thanks again for your help,

Sincerely 

POPPOTE_0-1603201194240.png

 

0 Kudos
Message 3 of 14
(3,469 Views)

I am still unable to read the IPmotion exported .tdm file.  A DataPlugin exists for IPmotion, so if you can export a *.IAD or *.ZIRPT file, that may work.

 

However, the attached image of the conversion result in DIAdem does give me more information.  

 

I tried more options with the DIAdem Bus Log Converter, but I was unable to create a result with more channels than previously demonstrated.  Sorry.  

 

 

 

0 Kudos
Message 4 of 14
(3,466 Views)

Thanks again,

indeed I have on my Pc the ipmotion data pluging, maybe that's the reason why.

The .iad file includes more channels other than thermal engine,  because I used a complementary dbc.

Best regards,  

0 Kudos
Message 5 of 14
(3,461 Views)

I can see from the DIAdem LogFile that many messages were not converted.  This could be because I don't have the "complementary dbc".  Could you please send me that file so I can try the conversion again?   markwkiehl@gmail.com

 

5 Bus Log Converter note: Cannot find the following bus IDs in the configured databases:
Id: 217056256 (0xcf00400), bus number: 1001
Id: 218000384 (0xcfe6c00), bus number: 1001
Id: 419360768 (0x18fef000), bus number: 1001
Id: 201326595 (0xc000003), bus number: 1001
Id: 217057793 (0xcf00a01), bus number: 1001
Id: 256 (0x100), bus number: 1001
Id: 257 (0x101), bus number: 1001
Id: 258 (0x102), bus number: 1001
Id: 259 (0x103), bus number: 1001
Id: 260 (0x104), bus number: 1001
Id: 261 (0x105), bus number: 1001
Id: 419356672 (0x18fee000), bus number: 1001
Id: 1296 (0x510), bus number: 1001
Id: 1280 (0x500), bus number: 1001
Id: 418382080 (0x18f00100), bus number: 1001
Id: 419279616 (0x18fdb300), bus number: 1001
Id: 419279872 (0x18fdb400), bus number: 1001
Id: 419351041 (0x18feca01), bus number: 1001
Id: 419370243 (0x18ff1503), bus number: 1001
Id: 417922816 (0x18e8ff00), bus number: 1001
Id: 419362304 (0x18fef600), bus number: 1001
Id: 419287041 (0x18fdd001), bus number: 1001
Id: 1575 (0x627), bus number: 1001
Id: 1281 (0x501), bus number: 1001
Id: 1282 (0x502), bus number: 1001
Id: 417398528 (0x18e0ff00), bus number: 1001
Id: 419224576 (0x18fcdc00), bus number: 1001
Id: 419341312 (0x18fea400), bus number: 1001
Id: 419353856 (0x18fed500), bus number: 1001
Id: 419265536 (0x18fd7c00), bus number: 1001
Id: 419358976 (0x18fee900), bus number: 1001
Id: 419362560 (0x18fef700), bus number: 1001
Id: 419360256 (0x18feee00), bus number: 1001
Id: 419348736 (0x18fec100), bus number: 1001
Id: 486445569 (0x1cfe9201), bus number: 1001
Id: 419357696 (0x18fee400), bus number: 1001
Id: 419355393 (0x18fedb01), bus number: 1001
Id: 419364867 (0x18ff0003), bus number: 1001
Id: 419366915 (0x18ff0803), bus number: 1001
Id: 418317571 (0x18ef0503), bus number: 1001
Id: 417988611 (0x18ea0003), bus number: 1001

0 Kudos
Message 6 of 14
(3,454 Views)

Hi, 

Here are all the dbc that will allow me to translate a large part of the signals to my knowledge.

 

regards, 

0 Kudos
Message 7 of 14
(3,450 Views)

The two additional CAN database (.dbc) files are what was needed.  Modifying the script I gave you to include them resulted in a total of 12 channel groups, and a total of 68 channels.  

 

So now you can use DIAdem to decode those CAN bus Vector .asc log files.  

 

Dim oDbBusDic, sFolderBusLog, sFolderDbFiles, sFolderResultTDM, oBulkBusLogConv
Set oDbBusDic = CreateObject("Scripting.Dictionary")
'oDbBusDic  key = database filename, value = bus name & number (CAN1, LIN2, etc.).
Call oDbBusDic.Add("j1939_ClaasAdapted.dbc","CAN1")
Call oDbBusDic.Add("CanaloggerCT_1.00_Elec.dbc","CAN1")
Call oDbBusDic.Add("PCAN-GPS PH.DBC","CAN1")
sFolderBusLog = "D:\DIAdem\data\no index - my sample data\ascii_CAN_bus\"
sFolderDbFiles = "D:\DIAdem\data\no index - my sample data\ascii_CAN_bus"
sFolderResultTDM = "D:\DIAdem\data\no index - my sample data\ascii_CAN_bus\"
'Function oBulkBusLogConversion(ByVal sExtBusLog, ByVal sFolderBusLog, ByVal sFolderDbFiles, ByVal sFolderResultTDM, ByVal oDbBusDic, ByVal bStopOnConvFail)
Set oBulkBusLogConv = oBulkBusLogConversion("asc", sFolderBusLog, sFolderDbFiles, sFolderResultTDM, oDbBusDic, True)
Set oBulkBusLogConv = Nothing
Call LogFileWrite("The bus log conversion result .TDM files can be found in '" & sFolderResultTDM & "'")
Call MsgBox(sFolderResultTDM, vbOkOnly, "Look in the folder listed below for the TDM files with the Bus Log Covnersion results")

 

0 Kudos
Message 8 of 14
(3,442 Views)

Thanks again for your help,

the result is more complete with the other dbc, but that wasn't the problem. The problem is that there are many more measurement channels around the engine, and the Diadem log converter bus only sees 3 messages: Sequence,TotalVehicleDistance,TripDistance and that ipemotion .

Below is an image of the engine measurement channels open in Diadem converted by ipemotion.

and an .asc file converted by ipmotion with only the dbc "classadapted" engine.

 
 
 
 
 

 

 

 

 
 

 

 

0 Kudos
Message 9 of 14
(3,409 Views)

bandicam 2020-10-26 11-32-12-448.jpg

0 Kudos
Message 10 of 14
(3,407 Views)