Finally got a chance to test both the TRH.12m that Chris and Antonio brought down during the December visit and the TRH.6m that we just retrieved today.

TRH.12m works fine, with the fan responding appropriately to changes in the fan duty cycle.  However, the RPM reading is flakey – reads mostly -99 with TRH057 and erratic values with TRH117.  We've labeled the housing "bad rpm".

TRH.6m also works fine in the cabin.  The fan RPM reports in the 5400 range for both TRH057 and TRH117.  We suspect that this fan just doesn't like the cold.  We'll label it as such.

Thus, we think that both TRH probes are fine.

Done with this task.

Other information (mostly for me):

  • we tested with the DSM labeled "spare 1", that comes up with wifi ID "s1".  With Gary's help we found that it's IP address is 192.168.1.221.
  • In the end, I used minicom dsm1, that was defined.  I also don't know if it was needed, but I also used dsm_port_config to set dsm1 to RS232.
  • No labels

1 Comment

  1. Gary Granger

    For the record, the spare DSMs for a project are often included in the hosts.xml file for the project, in the same directory as the nidas xml file, like sos.xml for the SOS project.  Here's an excerpt from SOS hosts.xml:

        <!-- spares -->
    <dsm name="s1" address="192.168.1.221" tags="nocheck">
    </dsm>
    <dsm name="s2" address="192.168.1.222" tags="nocheck">
    </dsm>

    If you at least know that the dsm is on the 192.168.1 subnet (as is usually the case for ISFS DSMs), and you have the nmap utility available (as it is on the DSMs and on the server laptops), then you can discover IP addresses as follows:

    1. Connect your computer directly to the DSM wired ethernet port.
    2. Configure your computer's ethernet interface to be a static IP address on the same subnet, like 192.168.1.19.  Field servers like ustar and wstar will already have a static IP 192.168.1.10.
    3. Run nmap like below:
    daq@cb:~ $ nmap -n -sn 192.168.1.1-250
Starting Nmap 7.70 ( https://nmap.org ) at 2023-01-20 18:36 UTC
Nmap scan report for 192.168.1.1
Host is up (0.014s latency).
Nmap scan report for 192.168.1.80
Host is up (0.099s latency).
Nmap scan report for 192.168.1.110
Host is up (0.020s latency).
Nmap scan report for 192.168.1.120
Host is up (0.017s latency).
Nmap scan report for 192.168.1.130
Host is up (0.041s latency).
Nmap scan report for 192.168.1.140
Host is up (0.0028s latency).
Nmap scan report for 192.168.1.141
Host is up (0.054s latency).
Nmap scan report for 192.168.1.142
Host is up (0.058s latency).
Nmap scan report for 192.168.1.143
Host is up (0.062s latency).
Nmap scan report for 192.168.1.144
Host is up (0.063s latency).
Nmap scan report for 192.168.1.201
Host is up (0.010s latency).
Nmap done: 250 IP addresses (11 hosts up) scanned in 9.06 seconds

    The -sn argument is a ping scan only, without the port scan.  If you need port information, leave that off, but it will take longer.  Add -T5  to run the ping scan faster, but at the risk of missing some responses.  The -n  prevents name resolution, which usually won't work anyway and just slows down the results.

    I will also add this information to Isabel's DSM user guide.