Hello Monke,
You may add new ADC channel measurement either during one of the trigger events or, you may create a new trigger for it.
It seems that you tested both options.
In the first case (multiple conversions at a single trigger), the first command(s) should start 0x00 (normal sequence) and the sequence ends by command starting either 0x40, 0x80 or 0xC0 byte (end of sequence/list).
For example:
PR_SECTION(adcLists)
volatile char ADC1CommandList[6][4] = {
{0x00,0xCA,0x00,0x00}, // [normal] + no int [C0], phase voltage [CA], 4 clock cycles sample time [00], reserved [00]
{0xC0,0xD3,0x00,0x00}, // [end of list] + no int [C0], AN3 voltage [D3], 4 clock cycles sample time [00], reserved [00]
{0x00,0x00,0x00,0x00},
{0x00,0x00,0x00,0x00},
{0x00,0x00,0x00,0x00},
{0x00,0x00,0x00,0x00}
};
volatile unsigned short ADC1ResultList[6] = {0, 0, 0, 0, 0, 0};
PR_SECTION(DEFAULT_SEC)
The second option is to create a new PTU trigger - as you tried in the second case.
I suppose that command
PTUTriggerEventList[1][0][1] = PTUTriggerEventList[1][0][0] +Delay3; // ADC1 Second sample - AD1
is part of UpdateDutycycle() function.
Did you implement also limitations by MIN_ADC_TRIGGER_SECOND for Delay3?
Did you add a code for for ADC1ResultList[1] value reading (in ADC0done_ISR())?
Best regards
RadekS