search

psi46 / pxar

Life is too short for perfection
16 stars 46 forks source link

Running PreTest on a TBM 08b at KU #191

Closed jking79 closed 10 years ago

jking79 commented 10 years ago

We are trying to run pxar with M_CL_901 that has been switched to run with a 08b tbm. We reset tbmType to tbm08b in configParameters.dat. When we run pxar pretest we get: [12:31:59.928] WARNING: RPC Call hashes of DTB and Host do not match! [12:32:00.258] ERROR: <api.cc/stringToDeviceCode:L351> Unknown device "0"! [12:32:00.258] INFO: DUT info: [12:32:00.259] ERROR: <dut.cc/status:L481> DUT structure not initialized/programmed yet!

and Robert is away on vacation...

jking79 commented 10 years ago

We are using : [12:45:52.266] QUIET: Instanciating API for pxar 1.1.1 [12:45:52.267] INFO: Log level: INFO [12:45:52.280] QUIET: Connection to board DTB_WRMLUE opened. [12:45:52.283] INFO: DTB startup information --- DTB info------------------------------------------ Board id: 0 HW version:
FW version: 3.1 SW version: 3.2 USB id:
MAC address: 000000000000 Hostname:

Comment:

xshi commented 10 years ago

Hi,

Since you're using firmware 3.2, could you update your pXar to the latest version and do the test again?

Xin

On Fri, Jul 11, 2014 at 1:46 PM, jking79 notifications@github.com wrote:

We are using : [12:45:52.266] QUIET: Instanciating API for pxar 1.1.1 [12:45:52.267] INFO: Log level: INFO [12:45:52.280] QUIET: Connection to board DTB_WRMLUE opened. [12:45:52.283] INFO: DTB startup information --- DTB info------------------------------------------ Board id: 0 HW version:

FW version: 3.1 SW version: 3.2 USB id:

MAC address: 000000000000 Hostname: Comment:

— Reply to this email directly or view it on GitHub https://github.com/psi46/pxar/issues/191#issuecomment-48761103.

jking79 commented 10 years ago

I will Investigate that and update, thank you

jking79 commented 10 years ago

All right I upgraded to the latest version of pxar and insured I was using the new tbm paramter file for the 08b.. renamed to tbmParameters.dat.

Result:

pxar $ ./bin/pXar -d /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters/ -r PT_BB_PA.root -g [13:59:59.158] INFO: * Welcome to pxar *

On branch master

nothing to commit (working directory clean) [13:59:59.175] INFO: no rootlogon.C found, live with the defaults provided [13:59:59.176] INFO: pxar: reading config parameters from /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//configParameters.dat [13:59:59.186] INFO: pxar: dumping results into /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//PT_BB_PA.root logfile = /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//PT_BB_PA.log [13:59:59.206] INFO: reading /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//dacParameters_C0.dat , . . [13:59:59.432] INFO: reading /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//trimParameters_C15.dat [13:59:59.442] INFO: reading /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//tbParameters.dat [13:59:59.446] QUIET: Instanciating API for pxar 1.4.6 [13:59:59.446] INFO: Log level: INFO [13:59:59.460] QUIET: Connection to board DTB_WRMLUE opened. [13:59:59.463] INFO: DTB startup information --- DTB info------------------------------------------ Board id: 0 HW version:
FW version: 3.1 SW version: 3.2 USB id:
MAC address: 000000000000 Hostname:

Comment:

[13:59:59.467] INFO: RPC call hashes of host and DTB match: 392669958 [14:00:01.116] INFO: DUT info: [14:00:01.116] INFO: The DUT currently contains the following objects: [14:00:01.116] INFO: 2 TBM Cores (2 ON) [14:00:01.116] INFO: TBM Core alpha (0): 7 registers set [14:00:01.116] INFO: TBM Core beta (1): 7 registers set [14:00:01.116] INFO: 16 ROCs (16 ON) with 4160 pixelConfigs [14:00:01.116] INFO: ROC 0: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 1: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 2: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 3: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 4: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 5: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 6: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 7: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 8: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 9: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 10: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 11: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 12: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 13: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 14: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.116] INFO: ROC 15: 21 DACs set, Pixels: 0 masked, 4160 active. [14:00:01.650] INFO: reading /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//phCalibrationFitTanH_C0.dat [14:00:01.651] ERROR: <ConfigParameters.cc/readGainPedestalParameters:L897> cannot open /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//phCalibrationFitTanH_C0.dat for reading PH calibration constants [14:00:01.684] INFO: reading /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//phCalibrationFitTanH_C0.dat [14:00:01.684] ERROR: <ConfigParameters.cc/readGainPedestalParameters:L897> cannot open /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//phCalibrationFitTanH_C0.dat for reading PH calibration constants [14:00:01.743] INFO: reading /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//phCalibrationFitTanH_C0.dat [14:00:01.743] ERROR: <ConfigParameters.cc/readGainPedestalParameters:L897> cannot open /rfs/Bean/Testing/ModuleTesting/Modules/M_CL_901_V2/parameters//phCalibrationFitTanH_C0.dat for reading PH calibration constants [14:00:13.390] INFO: ###################################################################### [14:00:13.390] INFO: PixTestPretest::doTest() [14:00:13.390] INFO: ###################################################################### [14:00:13.390] INFO: ---------------------------------------------------------------------- [14:00:13.390] INFO: PixTestPretest::programROC() [14:00:13.390] INFO: ---------------------------------------------------------------------- [14:00:31.411] INFO: PixTestPretest::programROC() done: ROCs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 cannot be programmed! Error! [14:00:31.411] INFO: IA differences per ROC: 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.8 0.0 0.8 0.8 [14:00:31.512] INFO: ###################################################################### [14:00:31.512] INFO: ERROR: some ROCs are not programmable; stop [14:00:31.512] INFO: ######################################################################

Not sure if this is a hardware problem or a pxar problem?

jking79 commented 10 years ago

Follow up: Tested pxar 1.4.6 with M_CR_901 using its unmodified config files, no issues.

xshi commented 10 years ago

When you test with v1.4.6 of pxar, did you able to programROCs?

PixTestPretest::programROC() done: ROCs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 cannot be programmed! Error!

On Fri, Jul 11, 2014 at 3:25 PM, jking79 notifications@github.com wrote:

Follow up: Tested pxar 1.4.6 with M_CR_901 using its unmodified config files, no issues.

— Reply to this email directly or view it on GitHub https://github.com/psi46/pxar/issues/191#issuecomment-48772382.

jking79 commented 10 years ago

Xin

My next step is to test the module with psi46test will do on Monday. I have never done that before.
Going to try and get Roberts input over weekend without disturbing his vacation to much hopefully.

Thank you.

Sent from my iPhone

On Jul 11, 2014, at 3:31 PM, Xin Shi notifications@github.com wrote:

When you test with v1.4.6 of pxar, did you able to programROCs?

PixTestPretest::programROC() done: ROCs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 cannot be programmed! Error!

On Fri, Jul 11, 2014 at 3:25 PM, jking79 notifications@github.com wrote:

Follow up: Tested pxar 1.4.6 with M_CR_901 using its unmodified config files, no issues.

— Reply to this email directly or view it on GitHub https://github.com/psi46/pxar/issues/191#issuecomment-48772382.

— Reply to this email directly or view it on GitHub.

jking79 commented 10 years ago

Testing module with a tbm 08b using pxar 1.4.6, was unable to program ROCs : see above

xshi commented 10 years ago

If all ROCs are not programable in all the version of pxar, it's likely to be a hardware issue. It'll be interesting to see the psi46test result.

Xin

On Fri, Jul 11, 2014 at 5:25 PM, jking79 notifications@github.com wrote:

Testing module with a tbm 08b using pxar 1.4.6, was unable to program ROCs : see above

— Reply to this email directly or view it on GitHub https://github.com/psi46/pxar/issues/191#issuecomment-48784857.

jking79 commented 10 years ago

Xin

I'll try that. Wasn't sure if the 08b would work under a earlier version with the new configuration file.
I'll let you know the results.

Thank you.

Sent from my iPhone

On Jul 11, 2014, at 4:33 PM, Xin Shi notifications@github.com wrote:

If all ROCs are not programable in all the version of pxar, it's likely to be a hardware issue. It'll be interesting to see the psi46test result.

Xin

On Fri, Jul 11, 2014 at 5:25 PM, jking79 notifications@github.com wrote:

Testing module with a tbm 08b using pxar 1.4.6, was unable to program ROCs : see above

— Reply to this email directly or view it on GitHub https://github.com/psi46/pxar/issues/191#issuecomment-48784857.

— Reply to this email directly or view it on GitHub.

simonspa commented 10 years ago

Running a module with a tbm08 requires different tbm register settings to work. @MDallOsso knows about this, he was able to run atbm08 module with pxar.

On 12. Juli 2014 00:15:03 MESZ, jking79 notifications@github.com wrote:

Xin

I'll try that. Wasn't sure if the 08b would work under a earlier version with the new configuration file.
I'll let you know the results.

Thank you.

Sent from my iPhone

On Jul 11, 2014, at 4:33 PM, Xin Shi notifications@github.com wrote:

If all ROCs are not programable in all the version of pxar, it's likely to be a hardware issue. It'll be interesting to see the psi46test result.

Xin

On Fri, Jul 11, 2014 at 5:25 PM, jking79 notifications@github.com wrote:

Testing module with a tbm 08b using pxar 1.4.6, was unable to program ROCs : see above

— Reply to this email directly or view it on GitHub https://github.com/psi46/pxar/issues/191#issuecomment-48784857.

— Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub: https://github.com/psi46/pxar/issues/191#issuecomment-48789148

MDallOsso commented 10 years ago

Hi, what do you mean with this sentence? "Follow up: Tested pxar 1.4.6 with M_CR_901 using its unmodified config files, no issues." Is M_CR_901 a module with tbm08 or tbm08b?

As for the tbm registers, if you renamed the tbm08bParameters.dat to tbmParameters.dat it should be ok. Changing the tbm should not affect the ROCs 'programmability' and you should be able at least to read the current. Are Iana and Idig displayed properly on the gui? You can try to change manually Vana from h/w tab and see if they will change.

jking79 commented 10 years ago

Hello,

In response to :

what do you mean with this sentence? "Follow up: Tested pxar 1.4.6 with M_CR_901 using its unmodified config files, no issues." Is M_CR_901 a module with tbm08 or tbm08b?

Just a check to make sure I had the system set up correctly, so I used pxar 1.4.6 with a known good module. That module has a tbm08 and I used tbm08Parameters.dat with it, named tbmParameters.dat. I also rename the tbm08bParameters.dat to to tbmParameters.dat for testing of the module with the tbm08b.

Jack W King III

From: MDallOsso [notifications@github.com] Sent: Monday, July 14, 2014 7:19 AM To: psi46/pxar Cc: King III, Jack Wallin Subject: Re: [pxar] Running PreTest on a TBM 08b at KU (#191)

Hi, what do you mean with this sentence? "Follow up: Tested pxar 1.4.6 with M_CR_901 using its unmodified config files, no issues." Is M_CR_901 a module with tbm08 or tbm08b?

As for the tbm registers, if you renamed the tbm08bParameters.dat to tbmParameters.dat it should be ok. Changing the tbm should not affect the ROCs 'programmability' and you should be able at least to read the current. Are Iana and Idig displayed properly on the gui? You can try to change manually Vana from h/w tab and see if they will change.

— Reply to this email directly or view it on GitHubhttps://github.com/psi46/pxar/issues/191#issuecomment-48893074.

jking79 commented 10 years ago

Robert,

So I loaded firmware 2.21 and ran decode with psi46test. Heres the readout:

DTB DTB_WRMLUE opened --- DTB info------------------------------------- Board id:    0 HW version:  FW version:  2.2 SW version:  2.21 USB id:      MAC address: 000000000000 Hostname:   

Comment:    

+-- control commands ------------------------------------------+ | h                  display this text                         | | exit               exit commander                            | +-- chip test -------------------------------------------------+ | test      run chip test                             | +--------------------------------------------------------------+

startmod

 ID = 462.3mA

 IA = 49.8mA

decode 32000 words allocated for data buffer 0 32000 words allocated for data buffer 1 words read 26, remaining 0  80 = 0000000010000000  90 = 0000000010010000  AC = 0000000010101100  B0 = 0000000010110000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  CF = 0000000011001111  DF = 0000000011011111  EF = 0000000011101111  FF = 0000000011111111  80 = 0000000010000000  91 = 0000000010010001  A0 = 0000000010100000  B0 = 0000000010110000

 17 = 0000000000010111  2F = 0000000000101111  3E = 0000000000111110  4A = 0000000001001010  50 = 0000000001010000  60 = 0000000001100000  CF = 0000000011001111  DF = 0000000011011111  EF = 0000000011101111  FF = 0000000011111111

TBM H1(0) H2(0) H3(C) H4(0)   EV(  0) STF(1) PKR(1) STKCNT( 0)  0. ROC-HD(8):  1. ROC-HD(8):  2. ROC-HD(8):  3. ROC-HD(8): TBM T1(F) T2(F) T3(F) T4(F)   NTP(1) RST(1) RSR(1) SYE(1) SYT(1) CTC(1) CAL(1) SF(1) D3(63)

TBM H1(0) H2(1) H3(0) H4(0)   EV(  1) STF(0) PKR(0) STKCNT( 0)  R1(7) R2(F) R3(E) R4(A) R5(0) R6(0)   Pixel [37765] 51/-66:   0 TBM T1(F) T2(F) T3(F) T4(F)   NTP(1) RST(1) RSR(1) SYE(1) SYT(1) CTC(1) CAL(1) SF(1) D3(63) words read 26, remaining 0  80 = 0000000010000000  90 = 0000000010010000  AC = 0000000010101100  B0 = 0000000010110000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  CF = 0000000011001111  DF = 0000000011011111  EF = 0000000011101111  FF = 0000000011111111  80 = 0000000010000000  91 = 0000000010010001  A0 = 0000000010100000  B0 = 0000000010110000

 17 = 0000000000010111  2F = 0000000000101111  3E = 0000000000111110  4A = 0000000001001010  50 = 0000000001010000  60 = 0000000001100000  CF = 0000000011001111  DF = 0000000011011111  EF = 0000000011101111  FF = 0000000011111111

TBM H1(0) H2(0) H3(C) H4(0)   EV(  0) STF(1) PKR(1) STKCNT( 0)  0. ROC-HD(8):  1. ROC-HD(8):  2. ROC-HD(8):  3. ROC-HD(8): TBM T1(F) T2(F) T3(F) T4(F)   NTP(1) RST(1) RSR(1) SYE(1) SYT(1) CTC(1) CAL(1) SF(1) D3(63)

TBM H1(0) H2(1) H3(0) H4(0)   EV(  1) STF(0) PKR(0) STKCNT( 0)  R1(7) R2(F) R3(E) R4(A) R5(0) R6(0)   Pixel [37765] 51/-66:   0 TBM T1(F) T2(F) T3(F) T4(F)   NTP(1) RST(1) RSR(1) SYE(1) SYT(1) CTC(1) CAL(1) SF(1) D3(63)

startmod3

 ID = 404.4mA

 IA = 51.4mA

decode 32000 words allocated for data buffer 0 32000 words allocated for data buffer 1 words read 22, remaining 0  80 = 0000000010000000  91 = 0000000010010001  A0 = 0000000010100000  B0 = 0000000010110000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  17 = 0000000000010111  2F = 0000000000101111  3E = 0000000000111110  46 = 0000000001000110

 52 = 0000000001010010  60 = 0000000001100000  CF = 0000000011001111  DF = 0000000011011111  EF = 0000000011101111  FF = 0000000011111111

TBM H1(0) H2(1) H3(0) H4(0)   EV(  1) STF(0) PKR(0) STKCNT( 0)  0. ROC-HD(8):  1. ROC-HD(8):  2. ROC-HD(8):  3. ROC-HD(8):  4. ROC-HD(8):  5. ROC-HD(8):  6. ROC-HD(8):  7. ROC-HD(8):  R1(7) R2(F) R3(E) R4(6) R5(2) R6(0)   Pixel [37763] 51/-65:  16 TBM T1(F) T2(F) T3(F) T4(F)   NTP(1) RST(1) RSR(1) SYE(1) SYT(1) CTC(1) CAL(1) SF(1) D3(63) words read 28, remaining 0  80 = 0000000010000000  91 = 0000000010010001  A0 = 0000000010100000  B0 = 0000000010110000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  78 = 0000000001111000  11 = 0000000000010001  25 = 0000000000100101  3D = 0000000000111101  45 = 0000000001000101  54 = 0000000001010100  6D = 0000000001101101

 78 = 0000000001111000  78 = 0000000001111000  17 = 0000000000010111  2F = 0000000000101111  3E = 0000000000111110  46 = 0000000001000110  52 = 0000000001010010  60 = 0000000001100000  CF = 0000000011001111  DF = 0000000011011111  EF = 0000000011101111  FF = 0000000011111111

TBM H1(0) H2(1) H3(0) H4(0)   EV(  1) STF(0) PKR(0) STKCNT( 0)  0. ROC-HD(8):  1. ROC-HD(8):  2. ROC-HD(8):  3. ROC-HD(8):  4. ROC-HD(8):  5. ROC-HD(8):  R1(1) R2(5) R3(D) R4(5) R5(4) R6(D)   Pixel [05352] 10/10: 173  6. ROC-HD(8):  7. ROC-HD(8):  R1(7) R2(F) R3(E) R4(6) R5(2) R6(0)   Pixel [37763] 51/-65:  16 TBM T1(F) T2(F) T3(F) T4(F)   NTP(1) RST(1) RSR(1) SYE(1) SYT(1) CTC(1) CAL(1) SF(1) D3(63)

Jack

On Monday, July 14, 2014 7:19 AM, MDallOsso notifications@github.com wrote:

Hi, what do you mean with this sentence? "Follow up: Tested pxar 1.4.6 with M_CR_901 using its unmodified config files, no issues." Is M_CR_901 a module with tbm08 or tbm08b? As for the tbm registers, if you renamed the tbm08bParameters.dat to tbmParameters.dat it should be ok. Changing the tbm should not affect the ROCs 'programmability' and you should be able at least to read the current. Are Iana and Idig displayed properly on the gui? You can try to change manually Vana from h/w tab and see if they will change. — Reply to this email directly or view it on GitHub.

jking79 commented 10 years ago

Hello,

When I ran pxar with the tbm08b module I could read Iana and Idig from the gui and they where normal values. Yes, I am using the tbm08bParameter.dat file renamed to tbmParameter.dat. From pxar I(ana) reads 0.053 and I(digi) reads 0.445. The power on/of from the gui works. I could not seem to change the currents by changing the voltage parameters in h/w.

MDallOsso commented 10 years ago

Ok, this "I could not seem to change the currents by changing the voltage parameters in h/w." is equal to the error you got during Pretest.

You can check if you see the SDATA signal on the oscilloscope and try to change the sda delay but I think that it can be an hardware problem due to some bad wire bond from tbm to hdi.

martino

jking79 commented 10 years ago

I did a second visual inspection of the Module and I think I found the problem. Thank You for the help.

xshi commented 10 years ago

Hi, just curious, is that a broken wire bonds?

Xin

On Tue, Jul 15, 2014 at 12:09 PM, jking79 notifications@github.com wrote:

I did a second visual inspection of the Module and I think I found the problem. Thank You for the help.

— Reply to this email directly or view it on GitHub https://github.com/psi46/pxar/issues/191#issuecomment-49054988.

jking79 commented 10 years ago

Xin,

I found what looks like a fragment of a copper wire shorting across two of the wire bonds.  I'm going to try to remove it today..  after a little practice with a can of air.

I included a picture of what I saw.

Jack

On Tuesday, July 15, 2014 10:22 PM, Xin Shi notifications@github.com wrote:

Hi, just curious, is that a broken wire bonds?

Xin

On Tue, Jul 15, 2014 at 12:09 PM, jking79 notifications@github.com wrote:

I did a second visual inspection of the Module and I think I found the problem. Thank You for the help.

— Reply to this email directly or view it on GitHub https://github.com/psi46/pxar/issues/191#issuecomment-49054988.

— Reply to this email directly or view it on GitHub.