Difference: AMC13DebugLog (127 vs. 128)

Revision 12809 Mar 2015 - EricHazen

Line: 1 to 1
 
META TOPICPARENT name="CmsSlhc"
Please log AMC13 test activity below, blog style (new entries at top)
Added:
>
>

2013-03-09, hazen

Testing firmware 0x222, 0x27 with software rel 34315 on CMS4. Seeing uHAL timeouts while reading data using 'df' command. Example:

  $ AMC13Tool2.exe -c 192.168.1.82
  $ Address table path "/home/hazen/work/amc13/amc13/etc/amc13" set from AMC13_ADDRESS_TABLE_PATH
  use_ch false
  Created URI from IP address:
    T2: ipbusudp-2.0://192.168.1.82:50001
    T1: ipbusudp-2.0://192.168.1.83:50001
  Using AMC13 software ver:34315
  > en 1-12 f t
  > localL1A o 1 10
  > lt c
  > lt d
  > df test.dat 9999
    ...
   Read 12340 words
   Wrote 12342 words to test.dat
   calling readEvent (53)...

  Caught microHAL exception.
  	Timeout (1000 milliseconds) occurred for UDP receive from target with URI: ipbusudp-2.0://192.168.1.83:50001

This problem does not occur when connecting from cms1.bu.edu. Tried both build 32534 (my current) and Dan's test build with uHAL 2.4. Back to cms4, update to 34988 (trunk) and re-build. No improvement.

Seems like some sort of network problem.

Use controlHub, all is well.

 

2015-02-09, hazen

TTC firmware superficially working. Lots of clean-up on address table to do.

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback