pyxcp and Matlab

[tuttoaldoc]

Hi,
some months ago I opened a couple of discussions to understand if it was possible to communicate with a Matlab application using pyxcp. Thanks to the support received I suceeded. Now I'm doing some cleaning and I reminded that I had to touch the library in order to start the communication. In particular I touched 2 points:

1. getDaqInfo in the last part when it requests the maxEventChannel because it seems mathworks doens't support the command. I just substituted the for with an if 0

    result["resolution"] = resolutionInfo
    channels = []
    daq_events = []
    
    #for ecn in range(dpi.maxEventChannel):
    if 0:
        eci = self.getDaqEventInfo(ecn)
   

2. in the DaqProcessor setup, at line 137 of the init when in the setDaqListMode is used the priority paramater with value 0xFF: mathworks supports only priority 0

        self.xcp_master.setDaqListMode(
            daqListNumber=i, mode=mode, eventChannelNumber=daq_list.event_num, prescaler=1, priority=0x0 # Matlab doens't manage the priority 0xFF
        )
   

I would like to not touch the library. How do you suggest to manage this 2 points?
thanks
Michele

[christoph2]

@tuttoaldoc

Hi Michele,

First half is done:

I've added priority and prescaler parameters to DaqList, the run_daq example is updated accordingly.
Note: Both parameters are optional and using the save defaults 0 resp. 1 , see here

Yes, I was wrong, as the XCP specification states:

If the ECU doesn’t support the prioritization of DAQ lists, a DAQ list priority > 0 is not
allowed and will be indicated by returning ERR_OUT_OF_RANGE.

The other problem was expectable, as pyXCP depends on the (optional) services GET_DAQ_PROCESSOR_INFO, GET_DAQ_RESOLUTION_INFO, GET_DAQ_EVENT_INFO.
I think the Matlab XCP implementation does not support the last one (maybe a configuration parameter?)
But this can be solved with user-supplied data structures; I am working on this issue.

[tuttoaldoc]

hi Christoper,
thank you so much for the support. Yes I guess mthworks doesn't support one of the parameters. I will test you first modification. Let me know if I can do further verifications.
Michele

[tuttoaldoc]

I confirm that the priority point is solved. Thanks!

[christoph2]

@tuttoaldoc

Turns out: Event list information is essential for STIM, but not required for DAQ lists. Therefore, the getDaqEventInfo() call can be skipped in this case.
see updated method

[tuttoaldoc]

Thank you so much, everything work fine!