You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SATP3 has been getting frequent failures (epics failures) on the bias_dets function, on both crates. The frequency seems to be correlated with our power cycle on January 6th around 1:20 am UTC. The pysmurf controller and smurf streamer logs during the failure are attached below. The issue was resolved by restarting the RSSI connection for the slot with the failure (https://github.com/simonsobs/daq-discussions/discussions/113#discussioncomment-10845936)
Pysmurf controller log:
ERROR:pyrogue.Variable.RemoteVariable.AMCc.FpgaTopLevel.AppTop.AppCore.SysgenCryo.Base[6].CryoChannels.etaI[22]:int too big to convert
Traceback (most recent call last):
File "/usr/local/src/rogue/python/pyrogue/_Variable.py", line 324, in set
self._block.set(self, value)
File "/usr/local/src/rogue/python/pyrogue/_Block.py", line 362, in set
ba = var._base.toBytes(value)
File "/usr/local/src/rogue/python/pyrogue/_Model.py", line 128, in toBytes
ba = value.to_bytes(byteCount(self.bitSize), self.endianness, signed=True)
OverflowError: int too big to convert
ERROR:pyrogue.Variable.RemoteVariable.AMCc.FpgaTopLevel.AppTop.AppCore.SysgenCryo.Base[6].CryoChannels.etaI[22]:Error setting value '44729' to variable 'AMCc.FpgaTopLevel.AppTop.AppCore.SysgenCryo.Base[6].CryoChannels.etaI[22]' with type Int16. Exception=int too big to convert
1736874256.985186:pyrogue.epicsV3.Value: Error setting value from epics: smurf_server_s4:AMCc:FpgaTopLevel:AppTop:AppCore:SysgenCryo:Base[6]:CryoChannels:etaMagArray
ERROR:pyrogue.Variable.RemoteVariable.AMCc.FpgaTopLevel.AppTop.AppCore.SysgenCryo.Base[7].CryoChannels.etaI[0]:"Memory Error for AMCc.FpgaTopLevel.AppTop.AppCore.SysgenCryo.Base[7].CryoChannels.etaI[0] at address 0x81b10000 Invalid value '-91420' for base type <class 'int'> with bit size 16"
ERROR:pyrogue.Variable.RemoteVariable.AMCc.FpgaTopLevel.AppTop.AppCore.SysgenCryo.Base[7].CryoChannels.etaI[0]:Error setting value '-91420' to variable 'AMCc.FpgaTopLevel.AppTop.AppCore.SysgenCryo.Base[7].CryoChannels.etaI[0]' with type Int16. Exception="Memory Error for AMCc.FpgaTopLevel.AppTop.AppCore.SysgenCryo.Base[7].CryoChannels.etaI[0] at address 0x81b10000 Invalid value '-91420' for base type <class 'int'> with bit size 16"
1736874260.670343:pyrogue.epicsV3.Value: Error setting value from epics: smurf_server_s4:AMCc:FpgaTopLevel:AppTop:AppCore:SysgenCryo:Base[7]:CryoChannels:etaMagArray
The text was updated successfully, but these errors were encountered:
@jlashner I reset the RSSI connection and ran bias dets again and this worked, so we'll see if the solution remains effective (and doesn't require a hammer).
SATP3 has been getting frequent failures (epics failures) on the bias_dets function, on both crates. The frequency seems to be correlated with our power cycle on January 6th around 1:20 am UTC. The pysmurf controller and smurf streamer logs during the failure are attached below. The issue was resolved by restarting the RSSI connection for the slot with the failure (https://github.com/simonsobs/daq-discussions/discussions/113#discussioncomment-10845936)
Pysmurf controller log:
![Screenshot 2025-01-14 at 8 58 48 PM](https://private-user-images.githubusercontent.com/80904219/403198425-410e6699-c74b-4e1c-833b-7f84c7890b96.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2NDgyNDIsIm5iZiI6MTczOTY0Nzk0MiwicGF0aCI6Ii84MDkwNDIxOS80MDMxOTg0MjUtNDEwZTY2OTktYzc0Yi00ZTFjLTgzM2ItN2Y4NGM3ODkwYjk2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE1VDE5MzIyMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWFlYjk5ZDAwNzJjODNiOTQzMTcwNWIyNGI3MzVlODRjMTdlNWI1MzJlNjIzMjBkMTZmODQyODY4Mjk1ZDI2NmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Qsu_aykWVlm3n6dLSujNE2PHqcVyvtThcRHaqlgWqWE)
The text was updated successfully, but these errors were encountered: