UE to send PUCCH info on U slot for TDD pattern DDDSU

Uses a default table.

Is that somewhere in SIB?

K1 values are on slots:
2 3 4 6 7 8 9

Nope.
dci 1_0 would mean using the default table.

Oh! Is that during message 2?

I mean during msg4 it is sent using dci 1_0.

Details here:

https://www.sharetechnote.com/html/5G/5G_DCI.html#Format_1_0

What is your PDSCH-to-HARQ_feedback timing indicator in msg 4?

This is dci 1_0.

I only see in the log sib1 and dci 1_0, rach fails as shown here:

I don’t think this is the complete dci info!
It doesn’t even have the harq id.

Are you sure this is the one for msg4 and not msg2?

Which tool your using yo read these?

In UE log I don’t see rar message as well, just sib1 and msg1 sent to du.

The minute I change S slot to be configured for 2 UL symbol then UE attached, so weird.

Maybe here I need to remove slot 4 also since S slot is used for DL only?

Which simulator it is?
Keysight?

Surely it’s a config issue!
Your ACK is being send in S slot where there’s no UL.
Either change it is UL slot or have UL in S slot, which you have done.

So how to prevent that the ack to be on S slot? To remove the slot 4 from k1 values?

In other words the DU tells the UE where to send ack, so which parameters tells the UE where to send ack?
The DU must send it but which params responseable for ack alots?
K1 values I think.

Also what I think is that UE send ack on S slot, so my confusion what param tells the UE to send ack on S slot?
UE also has in DDDSU. Th UL slots which is full UL symbols so there can send PUCCH info.

Real UE.

K1 index in DCI 1_0, which points to a predefined list of k1 values.

This you mean?

Yes.

And just to add: this is qxdm log. It’s not an index here, but the absolute value!

So?
I mean I see its 2…

This is on PDSCH status info not dci 1_0 :point_up_2:

For dci 1_0 info I see this: :point_down:

Pdsch harq timing indicator, that’s the index.

I would recommend really going through the above ShareTech Notes i have shared above!

It will help!

Update: Found the issue, it was because was no guard symbols between dl-ul symbols so thats why!