Dear all,
I need CR1000X connect AM16/32B (use 3WHB10K) help.
PT100 for Install 3WHB10K.
AM16/32B 4x16 mode
The program is as follows.
'CR1000X Series
'Created by Short Cut (4.3)
Public BattV
Public PTemp_C
Public LCount
Public PT100(5)
Public Soil_T(5)
Units BattV=Volts
Units PTemp_C=Deg C
Units PT100=C
DataTable(Table1,True,-1)
DataInterval(0,60,Min,10)
Average(1,BattV,FP2,False)
Average(1,PTemp_C,FP2,False)
Average(1,PT100(1),FP2,False)
Average(1,PT100(2),FP2,False)
Average(1,PT100(3),FP2,False)
Average(1,PT100(4),FP2,False)
Average(1,PT100(5),FP2,False)
EndTable
BeginProg
Scan(30,Sec,1,0)
Battery(BattV)
PanelTemp(PTemp_C,60)
'Turn AM16/32 Multiplexer On
PortSet(C2,1)
Delay(0,150,mSec)
LCount=1
SubScan(0,uSec,5)
PulsePort(C1,10000)
BrHalf3W(PT100(),1,mV1000,1,Vx1,1,2200, True,0,60,100.93,0.0)
PRTCalc(Soil_T(),1,PT100(),1,1.0,0)
LCount=LCount+1
NextSubScan
PortSet(C2,0)
Delay(0,150,mSec)
CallTable Table1
NextScan
EndProg
But.....Data is display: "NAN"
I don't know where the problem...
Program problem ? or 3WHB10K installation error?
3WHB10K-----nstall-----AM16/32B
(PT100)
H-----------------------------1H
L----------------------------- 1L
G----------------------------- G
hope to get an answer
Thank you everyone.
Ensure that the data types used in the program match the expected data types from the sensors. For example, check if the PT100 data type is compatible with the "FP2" data type used in the program.
did you use shortcuts to create the program? also as an example to get started?
Try to insert a delay before the measurement.
PulsePort(C1,10000)
Delay(0,150,mSec)
BrHalf3W(PT100(),1,mV1000,1,Vx1,1,2200, True,0,60,100.93,0.0)
While the relay is still closing, the logger is already taking the measurement, finding a circuit that is still open.
The MUX should be set as 2x32, otherwise you will have to use only the odd channels in the MUX, but I don't think it's just this because you should measure the even or odd ones.
How are the connections between logger and 10K reference?
How are the connections between logger and AM16/32?
Did you connect the pt100s only on the odd ones or are they all consecutive without leaving empty channels?
You're correct—setting the MUX as 2x32 is essential because if you don’t, you'll end up only being able to use the odd channels. This limits your measurement capability. It's critical to make sure that even and odd channels are available for measurements.
This post is under review.