using ADS1115 ^{CODESYS Forge talk (Thread)}
using ADS1115
Last updated: 2024-11-01

ADS1115 values are lost after reboot ^{CODESYS Forge talk (Thread)}
ADS1115 values are lost after reboot
Last updated: 2023-05-21

Post by andrax on using ADS1115 ^{CODESYS Forge talk (Post)}
I have the ADS1115 running and have no problems. But have you used a level shifter between the ADS1115 and the Raspberry?
Last updated: 2024-11-01

Getting raw value as full resolution for ADS1115 ^{CODESYS Forge talk (Thread)}
Getting raw value as full resolution for ADS1115
Last updated: 2021-04-01

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
yes i took the library from another forum: https://forge.codesys.com/forge/talk/Runtime/thread/f1400b71b6/, it is made for the ads1115 but the ads1015 is almost the same device with same adresses i only changed the divide value of the analog value, because thats the only difference between the ads1115 and ads1015.
Last updated: 2024-11-07

Post by andrax on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
Ok, this is a test programme with ADS1115. It is currently configured for the TCA9548 muxboard. If you want to run the ADS1115 single, then change the settings to the default values: ‘Is Multiplex:’ False ‘Stage mux channel numbers:’ [0,0,0,0,0,0,0,0,0] It is also important that the libraries are installed correctly here. But should be in this project
Last updated: 2024-11-07

Post by vincentger on using ADS1115 ^{CODESYS Forge talk (Post)}
Any reason the ADS1115 wouldnt work with SP20.1 and Runtime 10.0.0.0 on the Raspberry Pi . Using Bullseye or Buster i run into the same issue: Libary and integration works in general as described above BUT i am seeing "bleeding" between the analog inputs . Specifically consecutive ones: So sometimes the raw from AI1 shows on AI2, AI2 on AI3, .. AI4 on AI1. Even with filtering i cant smoothen that out properly and i feel like something is wrong. Almost like the bus is stumbling over itself, or the request from Codesys to the device.
Last updated: 2024-10-28

Post by andrax on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
Hi, Communication with the ADS1115 is actually simple. 1. write config 2. write address pointer 3. read conversation register The ADS1115 works like a multiplexer. This means that you do this individually for each channel that you want to read. e.g: Channel 1: write config > write address pointer > read conversation register Channel 2: write config > write address pointer > read conversation register Channel 3: write config > write address pointer > read conversation register Channel 4: write config > write address pointer > read conversation register then you start again from the beginning You can also omit individual channels or read only one. It doesn't matter. I have written the driver so that I can also use it on the TCA9548. The driver is from Stefan Dreyer. In your case, the driver works and communication with the ADS1115 is running. As you can see, the cfgWrong:=FALSE If you could not write or read data, cfgWrong:=TRUE; This means that either something is wrong with your ADS1115 or you have connected something incorrectly. Question: what voltage do you want to measure?
Last updated: 2024-11-08

Post by andrax on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
your driver is not running. All libraries must be present first! Then you can try the following. Delete the ADS1115 and the I2C_maseter from the device tree. Create everything again.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
i created a new project and did what you said, but still the same problem unfortunately. The ADS1115 is constantly changing from running to not running.
Last updated: 2024-11-08

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
I also installed your codesys version with the codesys for raspberry pi package version 4.7.0. but with no succes, only the TCA multiplexer has a constant green turning circle, the ADS1115 still changing from running to not running.
Last updated: 2024-11-11

Post by andrax on Meine Gerätesammlung basierend auf TCA9548 ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich programmiere öfters mal kleinere Messgeräte und Datenlogger. Je nach Einsatzzweck musste ich mir ein paar Gerätetreiber selber schreiben. Da es eine recht große Sammlung ist, stelle ich die hier einfach mal ein. Die Sammlung basiert auf den Gerätetreiber TCA9548 Multiplexer von Steffen Dreyer. Codesysversion: V3.5 SP18 Patch 4 Inhalt: -4channel Dimmer (Stefan Dreyer) -BMA456 (Andre Klien) -BME280 (Stefan Dreyer) -BMP280 (Stefan Dreyer) -EEPROM_24C512 (Stefan Dreyer) -ADS1115 (Andre Klien) -ICP10125 (Andre Klien) -PCA9555 (Stefan Dreyer) -PCA9685 (Stefan Dreyer) -PCF8575 (Stefan Dreyer) -SDP810 (Andre klien) -SSD1306 (Stefan Dreyer) -TCA9548 (Stefan Dreyer) -TSL2561 (Stefan Dreyer) Alle Gerätetreiber laufen über den Multiplexer, können aber auch ohne betrieben werden. Einschränkung: BMA456: Die Konfigurationsdaten werden erfolgreich in den Chip geschrieben, dieser meldet aber config wrong. Warum auch immer, der Sensor funktioniert und bringt hochempfindlich Beschleunigungsdaten. ADS1115: Hie habe ich nur die wichtigsten funktionen implementiert. 1-4 Kanäle, PGA, kontinuierlicher Modus, Datenrate. Alle anderen Funktionen (single-shot, komparator,alm) sind nicht implementiert. Das macht auch keinen Sinn, da diese Funktionen besser über die Steuerung realisiert werden können. Achtung beim ADS1115 ist zwingend ein Levelshifter notwendig, wenn ihr diesen mit 5V betreiben wollt. Ihr grillt sonst euren Raspi (SDA, SCL sind dann 5V) Gruß Andre
Last updated: 2023-12-18

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
Finnaly i get it working. There was a line in the file that set the ADS1015 chip in /boot/firmware/config.txt which i removed and after that the ADS1115 has a green turning circle and i got values. i created a new component so it fits our ADS1015. see screenshot. It works also with Codesys Control for Raspberry Pi 64 SL after adding the ULINT_TO_UDINT conversion in the library. i think the chip was all the time in use by the Raspberry pi itself. Thanks for your help!
Last updated: 2024-11-12

Post by andrax on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
Ok, with debug you suppress the errors, but that doesn't help you any further. You can find information about the missing drivers here https://forge.codesys.com/forge/talk/Runtime/thread/8981ce928a/ and here https://github.com/stefandreyer/I2C-Multiplex I'll have to have another look at which library you need. But you can easily find out. Create a completely empty project and insert the TCA9548. You don't need the board. Then look in the library and resolve all conflicts If you can compile the project without errors, delete the TCA9548 and insert the ADS1115. The driver should then also run. Small bonus: with the TCA9548 you can expand your network as you wish and use identical sensors multiple times
Last updated: 2024-11-08

Post by andrax on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
Ok, here are the libraries I use. First of all, try to get the ADS1115 to run completely on its own. Without MUX or other sensors. As muxboard I use this one: https://www.digikey.de/de/products/detail/sparkfun-electronics/BOB-16784/12714950?utm_adgroup=&utm_source=google&utm_medium=cpc&utm_campaign=PMax:%20Smart%20Shopping_Product_Zombie%20SKUs&utm_term=&productid=12714950&utm_content=&utm_id=go_cmp-18521752285_adg-_ad-__dev-c_ext-_prd-12714950_sig-Cj0KCQiA88a5BhDPARIsAFj595gkPXWPT8aa-EixL97BDWjO988WDhcx-iHOVbqb_H8CLpHBcwLuJW0aAu1JEALw_wcB&gad_source=1&gclid=Cj0KCQiA88a5BhDPARIsAFj595gkPXWPT8aa-EixL97BDWjO988WDhcx-iHOVbqb_H8CLpHBcwLuJW0aAu1JEALw_wcB All other boards don't work for me either. The terminating resistor is missing Important: Before you install the drivers, remove all other device drivers. My drivers are all located in ‘Raspberry I2C MUX_11_2023’
Last updated: 2024-11-11

Sort by relevance or date