Author |
|
mdsmith Newbie
Joined: April 24 2019 Location: United States
Online Status: Offline Posts: 14
|
Posted: November 07 2022 at 11:52 | IP Logged
|
|
|
I am using the Simply Automated UPB controller and MUI32
I/O device. The command ph_getdevicestat(5,"umi-32",0,0)
shows input ON when active, and input OFF non-active.
Under the Device UPB Detail assigning Channel 1 for Input
1, Channel 2 for Input 2, etc, should show which input is
active, but it does not work. Regardless which input is
active ( if input 1 is active ON, input 2 show active ON
when it is non-active) all input show active ON when only
input 1 is active. The same for input 2, when active shows
ON and all other inputs show ON when they are non-active.
Any fix (patch) available or help resolving this problem?
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: November 07 2022 at 21:40 | IP Logged
|
|
|
I tried to do some research on a MUI32 UPB device but couldnt really find anything. If there is some documentation you can
point me towards I can do some investigation.
Im not sure if the problem you're describing is a problem with the ph_getdevicestat function or a problem with the Device
Status screen. It sounds like this device has multiple UPB channels that you've configured in the UPB Device detail screen.
Each of these channels should have a detail line in the UPB Device Details screen, each with their own unique ID. Does the
device status screen properly reflect the values for each channel or not? If not, then the problem probably lies within the
UPB controller. When you control the MUI32 device, what does the PowerHome log show for UPB communication?
Not knowing how the device is supposed to work, it sounds as if only a single channel can be active at a time. If that is
the case and turning channel 1 on does not show that the other channels are turning off in the log, then the UPB controller
does not know to show the other channels off when a single channel is switched on. We would have to solve this by using
triggers.
One minor thing to correct would be the "umi-32" in the ph_getdevicestat function. This should be all caps for ID's although
in the current version it will work because searches in SQL Anywhere 11 are case insensitive. Sometime in the future, I plan
to change the database to SQL Server localdb and this feature may not be available.
If you can give me some info on the MUI32 device and how it is supposed to work, I should be able to determine the best
course of action to fix the problem for you.
Dave.
|
Back to Top |
|
|
|
|