Difference: NevisLabsELogJune2021 (10 vs. 11)

Revision 112021-06-28 - LaurelCarpenter

Line: 1 to 1
 
META TOPICPARENT name="NevisLabsELog"

June 2021 eLog

2021-06-28

Author: Colin

  • Tested remotely:
Changed:
<
<
>
>
 
    • It works now? Don't really understand why this wasn't working last Thursday, but w/e
Added:
>
>
Author: Laurel
  • Encountered same problem as Colin on 2021-06-14, with double PSU (/dev/ttyACM1) this time
    • confusing, because we added the following line to /etc/udev/rules.d/serial-ports.rules on Thursday, which should have resolved this?
      • KERNEL=="ttyACM0", MODE="0666"
    • I tried restarting again, and then it worked... maybe multiple restarts is for some reason necessary to actually update serial-ports.rules? weird
  • I'm wondering if maybe it would be best to assign the mode based on symlink as opposed to kernel, in the case that the PSU's are connected to different kernels (i.e. different usb ports), like so:
    • ATTRS{idProduct}=="049c", MODE="0666", SYMLINK+="psu1"
    • ATTRS{idProduct}=="0460", MODE="0666", SYMLINK+="psu2"
    • but for now this doesn't seem necessary
 

2021-06-24

Author: Colin, Laurel

Line: 18 to 27
 
    • > rm.list_resources()
  • The small PSU is currently on ASRL/dev/ttyACM0::INSTR
    • Which is apparently shortened to: /dev/ttyACM0
Changed:
<
<
  • Following directions at this link: https://msadowski.github.io/linux-static-port/
>
>
  • Following directions at this link: https://msadowski.github.io/linux-static-port/
 
  • We ran
    • SINGLE PSU: udevadm info --name /dev/ttyACM0 --attribute-walk
      • ATTRS{idProduct}=049c (under the second parent device)
    • DOUBLE PSU: udevadm info --name /dev/ttyACM1 --attribute-walk
      • ATTRS{idProduct}=0460 (under the second parent device)
Changed:
<
<
  • Then, like with solution from 6/14/2021 eLog, we added to /etc/udev/rules.d/serial-ports.rules
>
>
  • Then, like with solution from 6/14/2021 eLog, we added to /etc/udev/rules.d/serial-ports.rules
 
    • ATTRS{idProduct}=="049c", SYMLINK+="psu1"
    • ATTRS{idProduct}=="0460", SYMLINK+="psu2"
  • After a restart, these showed up when we ran "ls /dev/psu*"
Line: 54 to 63
 Jun 22 16:59:13 ctalab-Precision-3630-Tower upsmon[14298]: Communications with UPS nevis-ctalab-ups@localhost established
      • Unclear what any of this means
    • Maybe this helps:
Changed:
<
<
      • (Fix, but seems to assume a serial connection) https://www.truenas.com/community/threads/ups-repeatedly-gaining-and-losing-connection-with-server.40532/
>
>
      • (Fix, but seems to assume a serial connection) https://www.truenas.com/community/threads/ups-repeatedly-gaining-and-losing-connection-with-server.40532/
 
      • There's also some documentation of the issue here, potentially as it relates to upssched:
Changed:
<
<
        • https://github.com/networkupstools/nut/issues/219
>
>
        • https://github.com/networkupstools/nut/issues/219
 
        • Unclear if there's actually a resolution here as much as an acknowledgment of the issue.
      • Similar ideas here to make changes to timing things in conf files
Changed:
<
<
        • https://www.truenas.com/community/threads/data-for-ups-is-stale.20898/
        • https://forum.openmediavault.org/index.php?thread/4131-solved-ups-communication-instable/
>
>
        • https://www.truenas.com/community/threads/data-for-ups-is-stale.20898/
        • https://forum.openmediavault.org/index.php?thread/4131-solved-ups-communication-instable/
 
    • Advice from Bill
      • To suppress these messages, you want to edit the file:
        /etc/nut/upsmon.conf
        Do a search on NOTIFYFLAG. You probably want to remove the WALL option from something like:
        NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC
        Then restart upsmon:
        systemctl restart nut-monitor 
      • Nothing was set by default for NOTIFYFLAG in upsmon.conf
Line: 109 to 118
  File "/home/ctalab/anaconda3/envs/cta/lib/python3.8/site-packages/serial/serialposix.py", line 268, in open raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg)) serial.serialutil.SerialException: [Errno 13] could not open port /dev/ttyACM0: [Errno 13] Permission denied: '/dev/ttyACM0'
Changed:
<
<
    • Going to try and use the second option from this answer on stack overflow: https://stackoverflow.com/a/27886201
>
>
    • Going to try and use the second option from this answer on stack overflow: https://stackoverflow.com/a/27886201
 
      • Added it in at: /etc/udev/rules.d/serial-ports.rules
      • This seems to have resolved the problem
  • Starting to build up the base of the gui at /home/ctalab/software/control_guis/psu_gui.py
Line: 133 to 142
 
  • Replaced U6 with new ADP3338; the power supply immediately reaches compliance, lowering voltage from input 5V to 2V roughly. Also, ADP338 immediately starts heating up, there is still a short somewhere. Check capacitors FC05/6?

Changed:
<
<
-- Massimo Capasso - 2021-06-08
>
>
-- Massimo Capasso - 2021-06-08
 

Comments

Deleted:
<
<
<--/commentPlugin-->
 \ No newline at end of file
Added:
>
>

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