ve.can:ve.can_resistive_tank_sender_adapter
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| ve.can:ve.can_resistive_tank_sender_adapter [2019-01-22 10:16] – external edit 127.0.0.1 | ve.can:ve.can_resistive_tank_sender_adapter [2022-01-27 09:34] (current) – [Volume unit] mvader | ||
|---|---|---|---|
| Line 88: | Line 88: | ||
| {{: | {{: | ||
| - | ===== DISQUS ===== | ||
| - | ~~DISQUS~~ | ||
| + | ===== Frequently asked questions ===== | ||
| + | |||
| + | === Q1: Can I configure a custom name? === | ||
| + | |||
| + | No. The VE.Can Tank Sender Adapter does not accept configuring a custom name. The method available to distinguish from one tank to another are the instances. | ||
| + | |||
| + | This is unlike the GX Tank 140 and as well as inputs available directly on the Cerbo GX: there it is possible to configure a name. | ||
| + | |||
| + | === Q2: Why is this tank sender adapter so expensive? === | ||
| + | |||
| + | That is because its expensive to produce. For lower cost options, consider a GX Device with direct tank inputs, such as the Cerbo GX. And to extend those, consider our GX Tank 140. Note that the GX Tank 140 takes 0-10V and 4-20mA senders, not resistive. | ||
ve.can/ve.can_resistive_tank_sender_adapter.1548148579.txt.gz · Last modified: by 127.0.0.1