Sensor List

That sensor datasheet can not be viewed. From what we know, Dallas did not license 1-wire slave to any other party.  If any company licensed the 1-wire client logic, then it can be added, we will need to develop code to support those devices.
 
CAI_Support said:
That sensor datasheet can not be viewed. From what we know, Dallas did not license 1-wire slave to any other party.  If any company licensed the 1-wire client logic, then it can be added, we will need to develop code to support those devices.
 
 
Thanks; I put a return into the link
read.pudn.com/downloads155/
ebook/685866/TSic/ZMD%20TSic306%20Data%20Sheet%20V3.6.pdf
 
Is it an option that you allow upload of client libraries for sensors or actors?
 
thanks
 
By searching term TSic306, we can see that is a temp sensor similar to DS18B20.
However, we did not find its programming manual anywhere.  There are some sample code.  We need to read its programming spec to be able to evaluate.
 
CAI_Support said:
By searching term TSic306, we can see that is a temp sensor similar to DS18B20.
However, we did not find its programming manual anywhere.  There are some sample code.  We need to read its programming spec to be able to evaluate.
Thanks, it's not terrible urgent having that sensor for me, but an alternative to D1820 is good to have. The interesting point is if your clients may add sensor support themselves in an WC32+ version?  May be defining syntactically the communication?
 
Thanks for az1324 digging out that information. If that sensor is not addressable, then it means only one sensor on one bus.  That is not really a good idea.  DS18B20 is a very popular sensor and low cost.  Search on eBay will find many pre-assembled versions, including in the stainless steel tube already, with very reasonable price.
 
WC32 does allow user from remote query the 1-wire bus over the network.  However, in PLC those devices are not support. There is no easy way to add dynamic support in the firmware, because any different sensor will require different data structure and coding.
We do plan to add more support for different 1-wire devices, however, we need to know the part number and decide based on needs.
 
1-wire has certain timing that is too small for PLC to handle.
For the SPI/I2C interface, Ross already published how did he do it in PLC on this forum.
 
well 1-wire maybe because of the 6us delay but most other protocols could be done with interrupt callback in PLC
 
What kind of interrupt callback, do you have any details?  We care about users requests, especially opinion from you.
 
Because for different sensors there will be a different ways to handle it. without knowing which kind of sensor it would be difficult to provide support.  PortB input interrupt is not available for our current design, either.
 
Back
Top