Page 1 of 1
Missing bus information in transmit list
Posted: Wed 16. Jan 2019, 13:18
by hschill
Hello,
in my project, I have multiple busses on the same net in order to use multiple symbol files.
I want to create a xmt transmit list in order to save all the configuration messages neccessary for operation, but I can't get PCAN-Explorer to save the bus information in the transmit file.
My problem seems to be very similar to the one reported
here for PCAN-Explorer 5.
My version of PCAN-Explorer is 6.2.2.1986.
Thanks in advance.
Re: Missing bus information in transmit list
Posted: Wed 16. Jan 2019, 15:36
by PEAK-Support
I have test it with the PE6 and it works without any problem:
Code: Select all
;$FORMATVERSION=5.1
; D:\Kundensupport\PE6\Multible_Bus_Connection\Transmit List2.xmt
; CAN messages saved by PCAN-Explorer 6.2.2.1986
;
; Columns descriptions:
; ~~~~~~~~~~~~~~~~~~~~~
;+Bus
;| +Message ID
;| | +Reserved
;| | | +Cycle time in ms (0=manual)
;| | | | +Length of message
;| | | | | +Frame type: D)ata or R)emote request
;| | | | | | +Message data
;| | | | | | |
1 200h - 0 4 D 59h 01h 4Eh 00h
2 100h - 50 4 D E9h 00h E1h 10h
2 00000001h 00 150 8 D EBh 00h 00h 00h 00h 00h 00h 00h
The BUS Number ist the first Colum (in my sample using BUS 1 and 2 )
Attached you find a simple sample project for PE6.
Re: Missing bus information in transmit list
Posted: Thu 17. Jan 2019, 08:16
by hschill
If I create a new project, it works.
If the transmit list is created in an old project (which was originally created with version 6.1.1) it doesn't save the bus information.
Actually, if I modify the transmit list by hand and add the bus information, it works even in this case. At least until the transmit list is modified. PCAN-Explorer then removes the bus information again.
But thanks for pointing me in the right direction.
Re: Missing bus information in transmit list
Posted: Thu 17. Jan 2019, 08:41
by PEAK-Support
Keep in mind that BUS Numbers, Connection etc. are part of the Project. The transmitlist must FIT with the used BUS Numbers to your project! If not the BUS Numbers could not be used and you wiill see a sign that the BUS is not available.
- transmitlist_BUS.JPG (121.64 KiB) Viewed 11649 times
Re: Missing bus information in transmit list
Posted: Tue 29. Oct 2019, 08:28
by CTreffler
Hello,
I have the same problem as the original poster.
I'm using PCAN-Explorer 6.3.3.2130, freshly installed on a new machine. My project has 5 buses, 2 of them active. My transmit-list uses one of the active buses.
When I open the xmt-file in notepad++ I see this:
Code: Select all
; D:\Data\Documents\Projekte\19-08-02 - Project File Info - HX 3A, G - 01G258474684158\Sendeliste1.xmt
; CAN messages saved by PCAN-Explorer 6.3.3.2130
;
; Columns descriptions:
; ~~~~~~~~~~~~~~~~~~~~~
; +Message ID
; | +Cycle time in ms (0=manual)
; | | +Length of message
; | | | +Frame type: D)ata or R)emote request
; | | | | +Message data
; | | | | |
001EE500h 0 0 D ; BC an MRS: Shutdown
001FF001h 0 2 D 02h 01h ; Debug-Kommando: EEPROM
001FF001h 0 2 D 02h 03h ; Debug-Kommando: Von S anfordern
001FF001h 0 2 D 02h 02h ; Debug-Kommando: Zeit
001FF100h 0 2 D 00h 01h ; Debug-Kommando: EEPROM B
001FF100h 0 2 D 00h 04h ; Debug-Kommando: EEPROM in Puffer
001FF100h 0 2 D 00h 03h ; Debug-Kommando: Löschen
001FF100h 0 2 D 00h 02h ; Debug-Kommando: Zeit B
I tried to edit this according to the example code posted earlier in this thread. I also included the
When I open the edited file in PCAN-Explorer, the bus information is correct. However, when I edit it in PCAN-Explorer and save it, it reverts to the previous format without bus column.
When I open a completely new project I have the same problem. I tried this with a project with multiple buses and with a project with only one bus.
It would be nice to have this fixed. I'm working daily with this project and am a bit frustrated to have to set the info every morning.
TIA,
Christian Treffler
Re: Missing bus information in transmit list
Posted: Tue 29. Oct 2019, 08:38
by PEAK-Support
In your sampel Trace you do not includ the BUS Number. Please take a look at the Trace in the beginning of the Post. In the first column the BUS Number is placed
Code: Select all
; Columns descriptions:
; ~~~~~~~~~~~~~~~~~~~~~
;+Bus
;| +Message ID
;| | +Reserved
;| | | +Cycle time in ms (0=manual)
;| | | | +Length of message
;| | | | | +Frame type: D)ata or R)emote request
;| | | | | | +Message data
;| | | | | | |
1 200h - 0 4 D 59h 01h 4Eh 00h
Re: Missing bus information in transmit list
Posted: Tue 29. Oct 2019, 09:41
by CTreffler
Hello,
my point as stated in my post:
tried to edit this according to the example code posted earlier in this thread.
[...]
When I open the edited file in PCAN-Explorer, the bus information is correct. However, when I edit it in PCAN-Explorer and save it, it reverts to the previous format without bus column.
Regards,
Christian Treffler
Re: Missing bus information in transmit list
Posted: Tue 29. Oct 2019, 10:10
by PEAK-Support
If all entrys inside a Transmit List use only ONE Connection (BUS Number) the list will be saved in the single BUS Format, to be compatible to older Tools. When you open this file again, you need to assign a Connection if your project use more as one connection - which means that a Message Box with a selction pop up .
So you are definatlly right ! The Format information that you add manually get lost when save the file from the PCAN-Explorer again. We will place a ticket to add a Otion in the Setup to give the customer the choice how to save the Transmit List.
As a workaround, simply add one single line (maybe the first entry) with a CAN ID from the other Connection (BUS Number) with a cycle time off "0" so that it not start sending when it will be load. You also could add a dummy Connection to a Virtuel Device and use this BUS Number for the entry. Then the PCAN-Explorer will store the Trace File alsways in the Format Version 5.1. We hope that help you in your daily work...
Re: Missing bus information in transmit list
Posted: Tue 29. Oct 2019, 15:46
by CTreffler
Thank you for the explanation and the workaround. It works.
Regards,
Christian Treffler