We also (with previous mentioned relay/contact boards) bought this PR46-15 0-10v DAC and PR33-8 4-20ma - I2C modules. Each talking separately to an I2C ethernet master.
192.168.2.152 - we can see device view in browser, and base station and alpha station see it.
We don’t see it listed in AnyI2C software - & that doesn’t seem to support an ethernet connection to the I2C master anyhow
Used API calculator to encapsulate the sample packet
sending this sample socket packet per your documents: “\xAA\x02\xFE\x21\xCB”
yes we are using port 2101
We are afraid to mess with baud rates, expecting them to be set to defaults, but will take your direction if needed
But so far are getting a connection failure. Can you give us a little guidance? Thanks!
= = = =
Guess we weren’t clear enough - we sent base station snap to prove we were talking to the ethernet module. It wasn’t responding to a correct socket API call “\xAA\x02\xFE\x21\xCB”.
Anyhow, that problem is solved! (just 10 min ago) We have 3 masters & 3 modules, we swapped & then swapped back, all ok for that simple socket query – they work now! Must’ve been a wiggle-the-connector issue.
Our current question - we have very simple needs for these 2 module types and are not finding the command sequences for that. (See above, we successfully reach them with a the socket command to test comm.) Each module talks to its own I2C ethernet master PR49-35.
PR33-8 4-20ma – just read value of each channel (2 of them)
PR46-15 0-10v DAC – write (also read to confirm) value for 0-10v output
Can you please tell us, or point us to the exact documentation? Thank you!
@Bhaskar@ryan1
Thank you for the response.
We see the API wrapper, we use that to talk to the relay boards we have.
Unfortunately, that document doesn’t have the byte commands for the modules/chips we are using at this site. What we need is the payload bytes for:
PR33-8 4-20ma chipset ADS1115 – just read value of each channel (2 of them) — that doc has AS1115, an LED driver, not ADS1115
PR46-15 0-10v DAC chipset MCP4725 – write (also read to confirm) value for 0-10v output
We would like to keep it simple - each of those operations, one at a time. And not having to get into internal I2C protocols.
FYI - we tried these generic I2C commands from that document:
I2C bus scan command (AA 02 C1 00 6D) our socket receives back 109 zero bytes.
and the I2C Stop Command 0xAA 0x03 0xFE 0x21 0xBB 0x87 - socket gets no response
for the commands will recommend checking the i2c chip datasheet.
for example
MCP4725
0x60, 0x41, data ( data is the value you want to write on DAC output)
@Bhaskar@ryan1@travis1
Bhaskar, thanks for the starting point.
But those documents are at a detail we don’t understand - example, for the ADS1115, what multiplexer, pointer, conversion, config registers would we use? How do we address each of the 2 4-20ma inputs?
MCP4725: In your response above, what is the ‘data’ input format? a range of 4096 is greater than 1 byte. We see some bit shifting etc in the code excerpt that we don’t understand.
So, please - these are boards you sell, with your I2C master. They are very practical for us. We are not the only customers who need a simple answer for them. So just tell us exact byte payload for:
PR33-8 4-20ma chipset ADS1115 – just read value of each channel (2 of them)
PR46-15 0-10v DAC chipset MCP4725 – write value for 0-10v output
Question:
PR46-15 – can we use the samples in this doc for the payload?
If so, is there a similar set of examples for 4-20ma sensor?
This product line was designed for engineers who want to write their own code. We’ve provided examples for a wide range of I2C devices to help get you started. Since all I2C devices follow the same communication structure, it’s not practical to offer examples for every individual chip.
Also, examples for end-node devices do not apply to I2C devices—they operate on completely different protocols.
