V5 ~75%
Spud:
UpStart Definition
With regards to UpStart (US), the program itself has always seemed a little odd.
Putting aside its “cutesy dialogs”, how US specifies the UMIs input and outputs is backward.
Going forward I will refer to-
The three channels that respond to external stimuli as Inputs.
The two channels that provide contact closure are Outputs.
Summary:
The PI appears to be ~75% functional.
-All 5 channels appear
-Input channels 1 and 3 respond
-Input channel 2 does not
-Output channels 1 and 2 have not been tested
-The links don’t appear to respond either as they did with the HS2 PI. At this time that is not an issue.
The means of testing may be affecting channel 2. See “Trigger Issue?” below
I will move the UMI and the attached wiring panel from the cramped upper corner in the server room to a “lab” environment. With the assembly sitting next to my HS3 box the testing can be more precise.
If I remember correctly you are using borrowed equipment. I respect the timeline that imposes.
More detail should be available tomorrow morning.
Detail:
Because the family home is home today, the testing that least degrades WAF is to leave the garage doors alone.
Normally when testing like this, the modified CAT5 cable that travels to the garage is unplugged from the assembly. A dummy cable is used in it’s place.
Trigger Issue?
The dummy cable when plugged in completes the voltage sense for channels 1 and 2, illuminating the two UMI LED channel indicators simultaneously. Channel 3 is on a separate connector to the assembly and is not an issue. It is because of the cramped quarters that the dummy was made.
It is the simultaneous action on channels 1 and 2 that **may** be why Input 2's state change is not appearing in the PI.
Making a Channel 1 and a Channel 2 dummy would be faster than moving the assembly.
However….
In the US options for the UMI the Output channels are specified as momentary. I need to stand next to the UMI to see how the PI responds for those two seconds.
T
So, have you tested the UMI with 3.0.0.5? Does it work fine?
UpStart Definition
With regards to UpStart (US), the program itself has always seemed a little odd.
Putting aside its “cutesy dialogs”, how US specifies the UMIs input and outputs is backward.
Going forward I will refer to-
The three channels that respond to external stimuli as Inputs.
The two channels that provide contact closure are Outputs.
Summary:
The PI appears to be ~75% functional.
-All 5 channels appear
-Input channels 1 and 3 respond
-Input channel 2 does not
-Output channels 1 and 2 have not been tested
-The links don’t appear to respond either as they did with the HS2 PI. At this time that is not an issue.
The means of testing may be affecting channel 2. See “Trigger Issue?” below
I will move the UMI and the attached wiring panel from the cramped upper corner in the server room to a “lab” environment. With the assembly sitting next to my HS3 box the testing can be more precise.
If I remember correctly you are using borrowed equipment. I respect the timeline that imposes.
More detail should be available tomorrow morning.
Detail:
Because the family home is home today, the testing that least degrades WAF is to leave the garage doors alone.
Normally when testing like this, the modified CAT5 cable that travels to the garage is unplugged from the assembly. A dummy cable is used in it’s place.
Trigger Issue?
The dummy cable when plugged in completes the voltage sense for channels 1 and 2, illuminating the two UMI LED channel indicators simultaneously. Channel 3 is on a separate connector to the assembly and is not an issue. It is because of the cramped quarters that the dummy was made.
It is the simultaneous action on channels 1 and 2 that **may** be why Input 2's state change is not appearing in the PI.
Making a Channel 1 and a Channel 2 dummy would be faster than moving the assembly.
However….
In the US options for the UMI the Output channels are specified as momentary. I need to stand next to the UMI to see how the PI responds for those two seconds.
T
Comment