TLDR summary;
If you want to add PID terms for your 8E0909518AK logging, use notepad to edit and add these three lines to your logging setup .ecu file. Perform a SAVE AS to keep it as a .ecu rather than converting to a .txt (if you just hit save) then you can open it in ME7logger,  select the 3 new terms for your ME7logger configuration and they will be collected in subsequent data logs and available on the ECUxPlot BOOST menu.

lditv_w         , {BoostPID-I-Result}               , 0x384C90,  2,  0x0000, {%}       , 1, 0,        0.005,      0, {LDR PID I Result}
ldptv           , {BoostPID-P-Result}               , 0x384C96,  2,  0x0000, {%}       , 1, 0,        0.005,      0, {LDR PID P Result}
ldrdtv          , {BoostPID-D-Result}               , 0x384C98,  2,  0x0000, {%}       , 1, 0,        0.005,      0, {LDR PID D Result}

Longer Backstory;              
If you are using something other than a stock turbo and wastegate, in order to make changes to the boost-PID control it can be very helpful to log the three PID terms: ldptv, lditv_w, & ldrdtv in order to understand which of the PID inputs need to be changed to restore smooth boost control. In my case, I am using a KO4 turbo and KFLDIMX & KFLDRL modified for PID I-term pre-feed. ME7info is unfortunately unable to determine the RAM addresses for these 3 terms from the 8E0909518AK.bin. Other suggested means for finding the addresses are far above my remedial programming skills and available software. While looking at data logs from some other ME7.5 1.8T ECUs, I realized however that not all of them are missing these PID terms. Searching through a logging .ecu file that ME7info made from a 8N0906018H (225hp TT BAM) .bin, it does contain ldptv, lditv_w, & ldrdtv addresses and I noticed that these addresses were all clustered together close to other WGDC related terms. Working in a spreadsheet of the .ecu file, I sorted these and calculated each address distance away from term ldimxak_w {ChargeLimitPID-I} which did have its address defined in the 8E0909518AK.ecu Here is how the WGDC terms were arranged in the BAM 8N0906018H.ecu file;

;Name               {Alias}                                      HEX Address   distance from ChargeLimitPID-I
ldtvr_w          {WastegateDutyCycleBeforeLin}    0x3822FA        24
ldtv                {WastegateDutyCycleAfterLin}      0x3822F8        22
ldrdtv             {BoostPID-D-Result}                   0x3822EE        12
ldptv               {BoostPID-P-Result}                   0x3822EC        10
lditv_w             {BoostPID-I-Result}                   0x3822EA        8
ldimx_w             {BoostPID-I-Max}                     0x3822E8        6
ldimxak_w          {ChargeLimitPID-I}                   0x3822E2        0
ldimn_w              {BoostPID-I-Min}                     0x3822E0       -2

In the 8E0909518AK.ecu, chargeLimitPID-I was located at a completely different address of 0x384C8C but I thought it was worth checking to see if the PID term might also be clustered near to ChargeLimitPID-I as they were in the 8N0906018H.ecu. I performed trial and error testing of unoccupied addresses in the 8E0909518AK.ecu that were close to its ChargeLimitPID-I address 0x384C8C. I edited the 8E0909518AK.ecu file to include the PID terms at candidate "test" addresses, logged and reviewed the data until I got them all nailed down. Two of them (P and D terms) were at exactly the same +10, +12 distance from ChargeLimitPID-I as in the 8N0906018H.ecu file,  just  the I term was at a slightly different offset (+4 instead of +8). The .ecu file from a Golf 1.8T that I checked also had them all clustered similarly close together but at different distances away from ChargeLimitPID-I. The RAM addresses are fairly scrambled between the several ECUs that I checked but they do all use somewhat similarly grouped clusters for related terms. Data logs and edits to the PID terms make much more sense now that I can actually read the data! Similar offset comparison and trial and error approach might be helpful for finding any other missing logging terms in 8E0909518AK.ecu (torque intervention?) or any needed missing terms for other ECUs.