Replies: 7 comments 10 replies
-
|
Do you have any log at start that would confirm the PCA9685 is actually detected as a PC9685 by the driver ? Set weblog 4, restart and provide the logs here using proper copy/paste with triple-backtics, not screen shot |
Beta Was this translation helpful? Give feedback.
-
|
EDIT 00:00:00.001 HDW: ESP32-C2 v1.0 |
Beta Was this translation helpful? Give feedback.
-
|
It always recognized the INA219, but it was never connected. I have therefore set Driver14 to 0. It still displayed 0x70, 0,72 before, but they are gone. These addresses never existed but only these two, which are now displayed correctly. |
Beta Was this translation helpful? Give feedback.
-
I don't understand what you mean by this sentence But from the logs, the PCA9685 is not recognized So you have something wrong |
Beta Was this translation helpful? Give feedback.
-
Yes, I understand that, but the address must be the PCA9685. Nothing else is connected apart from these two. Ok then I deactivate the driver I have already deactivated the driver 14 because otherwise it showed me the INA219 which was and is never connected. Brief history The board in conjunction with the ESP went at the beginning of the year, after which I put it in the cupboard as I didn't need it yet. And about last week I took it out and wanted to try it again and suddenly the GUI showed IN219 with voltage, current and power, which made me wonder. |
Beta Was this translation helpful? Give feedback.
-
Not sure what you understood |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I understood that. But I have the question of why it shows the Ina219 even though I haven't completed it. I marked the INA with # in visual studio but it still showed it to me in the Gui.
Only when I deactivated it using I2CDriver 14 0. I think he was gone in the Gui but he still thinks that's why the PCA9685 doesn't come.
1. Now the question arises whether I didn't compile it correctly or whether it didn't accept the PCA9685 driver and dasur h can't find it. Because at the beginning of the year it still worked until I did a Tasmota update (compiled) and screwed on the board.
2. If I change the bus address on the PCA9685, do I also have to compile the new address in Tasmota?
…----- tested so far
1. The MCP23017 is recognized and provisional connected BME280 is also recognized.
2. I replaced the PCA9685 earlier. But the second one is not recognized; only the address 0x40 is displayed. According to my knowledge, it must be the PCA9685 or, as I misinterpreted it, the ina.
But what puzzles me is that "i2cdriver15 status" says error
Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
________________________________
From: Barbudor ***@***.***>
Sent: Sunday, November 3, 2024 8:20:20 PM
To: arendst/Tasmota ***@***.***>
Cc: Smarthome ***@***.***>; Author ***@***.***>
Subject: Re: [arendst/Tasmota] Problems with PCA9685 (Discussion #22422)
Ok then I deactivate the driver
Not sure what you understood
I wrote to disable all drivers but driver 1
That means disable all other drivers except driver 1 which has to remains enabled
—
Reply to this email directly, view it on GitHub<#22422 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOBCMCVMUVFMTETEVWHO2OLZ6ZZPJAVCNFSM6AAAAABRC65I26VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJTGYYTKMI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
You wrote about "I2CDriver 14 0" - which would not work. It should be "I2CDriver14 0" - that space makes a major difference to commands, but it does look like you did disable the driver. Since your When doing a custom build, I like to have the drivers disabled from the start, using Not having any experience with the PCA9685, but one potential risk factor could be if the driver has been tested on the ESP32-C2 MCU variant you use. If you decide to switch to another I2C address for the PCA9685, instead of Your log does show a problem, Tasmota is not able to connect to a NTP server to get correct time, which is needed for normal operation. When it comes to the MCP23017, I'd suggest you to use the enhanced mode 2, unless you specifically want the older mode 1. |
Beta Was this translation helpful? Give feedback.
-
|
INA219 is i2cdriver 14 while PCA9685 is i2cdriver 1 Have you tried disabling all drivers but the PCA one ?
Point 2: Yes, you have to recompile and define |
Beta Was this translation helpful? Give feedback.
-
|
@sfromis thank you very much for the help. I actually only want to use the outputs of the MCP23017. Would it work with Mode 2?
I have to set that up in the Tasmota Gui, right?
Is there a command where I can deactivate all unnecessary drivers in one line. Otherwise it will restart every time it is deactivated. I also suspect that he is interpreting the PCA9685 as a different sensor for whatever reason (as I said this morning as an INA sensor). And as a result the driver15 commands don't work. You can tell that the PCA9685 works hardware-wise and is accessible from the 0x40 address that is displayed to me at i2csan.
But communication doesn't work for whatever reason. Tomorrow I will compile a new Tasmota32c2 version with a different bus address.
Which one would be okay?, 0x47?
…________________________________
From: sfromis ***@***.***>
Sent: Sunday, November 3, 2024 10:22:03 PM
To: arendst/Tasmota ***@***.***>
Cc: Smarthome ***@***.***>; Author ***@***.***>
Subject: Re: [arendst/Tasmota] Problems with PCA9685 (Discussion #22422)
You wrote about "I2CDriver 14 0" - which would not work. It should be "I2CDriver14 0" - that space makes a major difference to commands, but it does look like you did disable the driver.
Since your I2CDriver command output includes number 1, it does appear that you managed to include the driver in the build. However, since several other sensors can also appear on I2C address 0x40, it could make sense, as barbudor suggested, to disable all the I2C drivers except for the ones you want to use.
Not having any experience with the PCA9685, but one potential risk factor could be if the driver has been tested on the ESP32-C2 MCU variant you use.
If you decide to switch to another I2C address for the PCA9685, instead of 0x40, you'll indeed have to do a new build with the selected address.
Your log does show a problem, Tasmota is not able to connect to a NTP server to get correct time, which is needed for normal operation. When it comes to the MCP23017, I'd suggest you to use the enhanced mode 2, unless you specifically want the older mode 1.
—
Reply to this email directly, view it on GitHub<#22422 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOBCMCW4BVIDXKNDENS3HF3Z62HXXAVCNFSM6AAAAABRC65I26VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJTGY3TCMY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
One reason for me posting how you can compile to have default I2CDriver setup be all disabled is that there is no command to do them all in one go. While you could do many commands on one line with What you get with MCP23017 driver mode 2 is that you can configure pins, and then use as "normal" button/switch/relay/output, and this is done with a bit of JSON in a file, not in the web UI. This makes usage of the expander pins much more straightforward. And barbudor is right about the PCA9686 driver being first, meaning that it is not "highly likely" that it is another driver getting in the way. The INA219 driver "should" only be able to kick in after the PCA9685 driver did not detect the device. This is why I speculated about the risk of the driver not being "well-tested" with ESP32-C2. I have no special recommendation for what to pick if you want to try with another I2C address for the PCA9685, |
Beta Was this translation helpful? Give feedback.
-
|
No, I'll do that tomorrow to deactivate all unneeded drivers.
And to recompile it with a different address, perhaps with 0x47 (or should I use a different one). I think despite deactivating driver14 it does not release the address for the PCA9685. But it looks like he at least recognizes the chip, even if it's wrong. I'm going to bed for today. I tried a lot today but nothing worked.
But I won't give up hope with the great support from you. 🙂
…________________________________
From: Barbudor ***@***.***>
Sent: Sunday, November 3, 2024 10:24:28 PM
To: arendst/Tasmota ***@***.***>
Cc: Smarthome ***@***.***>; Author ***@***.***>
Subject: Re: [arendst/Tasmota] Problems with PCA9685 (Discussion #22422)
INA219 is i2cdriver 14 while PCA9685 is i2cdriver 1
At boot, enabled drivers are tested in order so PCA9685 driver is the 1st to kick in
If the PCA driver doesn't detect the PCA chip and move's on to the INA, it is because the chip at address 0x40 failed the test
Have you tried disabling all drivers but the PCA one ?
I marked the INA with # in visual studio but it still showed it to me in the Gui.
????
Point 2: Yes, you have to recompile and define USE_PCA9685_ADDR to the new address in your user_config_override.h
—
Reply to this email directly, view it on GitHub<#22422 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOBCMCVPN7Y6J2L265GI2QDZ62IAZAVCNFSM6AAAAABRC65I26VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJTGY3TENI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
thanks also for the NTP time, I will change it tomorrow.
…________________________________
From: Barbudor ***@***.***>
Sent: Sunday, November 3, 2024 10:24:28 PM
To: arendst/Tasmota ***@***.***>
Cc: Smarthome ***@***.***>; Author ***@***.***>
Subject: Re: [arendst/Tasmota] Problems with PCA9685 (Discussion #22422)
INA219 is i2cdriver 14 while PCA9685 is i2cdriver 1
At boot, enabled drivers are tested in order so PCA9685 driver is the 1st to kick in
If the PCA driver doesn't detect the PCA chip and move's on to the INA, it is because the chip at address 0x40 failed the test
Have you tried disabling all drivers but the PCA one ?
I marked the INA with # in visual studio but it still showed it to me in the Gui.
????
Point 2: Yes, you have to recompile and define USE_PCA9685_ADDR to the new address in your user_config_override.h
—
Reply to this email directly, view it on GitHub<#22422 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOBCMCVPN7Y6J2L265GI2QDZ62IAZAVCNFSM6AAAAABRC65I26VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJTGY3TENI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Good evening, Now I just have to implement the tip with Mode2 on the MCP23017. And increase the frequency so that the LEDs no longer flicker when dimming. Do I have to enter this in the console or when compiling? Thank you both 17:51:01.978 RSL: RESULT = {"I2CScan":"Device(s) found at 0x20 0x40"} 17:52:01.006 RSL: STATE = {"Time":"2024-11-04T17:52:00","Uptime":"0T01:10:09","UptimeSec":4209,"Heap":64,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":20,"MqttCount":0,"Berry":{"HeapUsed":4,"Objects":53},"POWER1":"OFF","POWER2":"OFF","POWER3":"OFF","POWER4":"OFF","Dimmer":40,"Color":"296600","HSBColor":"96,100,40","Channel":[16,40,0],"Scheme":0,"Width":1,"Fade":"OFF","Speed":1,"LedTable":"ON","Wifi":{"AP":1,"SSId":"SmartHxxxxxxx","BSSId":"7A:8C:B5:AE:4D:10","Channel":7,"Mode":"HT40","RSSI":94,"Signal":-53,"LinkCount":1,"Downtime":"0T00:00:04"}} 17:52:01.032 RSL: SENSOR = {"Time":"2024-11-04T17:52:01","DS18B20":{"Id":"3C01B556A4AC","Temperature":24.7},"MCP230XX":{"D0":1,"D1":1,"D2":1,"D3":1,"D4":1,"D5":1,"D6":1,"D7":1,"D8":1,"D9":1,"D10":1,"D11":1,"D12":1,"D13":1,"D14":1,"D15":1,"OUT":{"OUT_D0":"OFF","OUT_D1":"OFF","OUT_D2":"OFF","OUT_D3":"OFF","OUT_D4":"OFF","OUT_D5":"OFF","OUT_D6":"OFF","OUT_D7":"OFF","OUT_D8":"OFF","OUT_D9":"OFF","OUT_D10":"OFF","OUT_D11":"OFF","OUT_D12":"OFF","OUT_D13":"OFF","OUT_D14":"OFF","OUT_D15":"OFF"}},"ESP32":{"Temperature":22.0},"TempUnit":"C"} 17:52:01.042 RSL: SENSOR = {"Time":"2024-11-04T17:52:01","PCA9685":{"PWM_FREQ":50,"INVERT":0,"PWM0":0,"PWM1":0,"PWM2":0,"PWM3":0,"PWM4":0,"PWM5":0,"PWM6":0,"PWM7":0,"PWM8":0,"PWM9":0,"PWM10":0,"PWM11":0,"PWM12":0,"PWM13":0,"PWM14":0,"PWM15":0,"END":1}}
|
Beta Was this translation helpful? Give feedback.
-
|
https://tasmota.github.io/docs/PCA9685/#driver-usage includes PWM frequency, instead of the default you can establish at build time. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, it should work via console |
Beta Was this translation helpful? Give feedback.
-
|
thank you
…________________________________
Von: sfromis ***@***.***>
Gesendet: Montag, 4. November 2024 18:16
An: arendst/Tasmota ***@***.***>
Cc: Smarthome ***@***.***>; Author ***@***.***>
Betreff: Re: [arendst/Tasmota] Problems with PCA9685 (Discussion #22422)
https://tasmota.github.io/docs/PCA9685/#driver-usage includes PWM frequency, instead of the default you can establish at build time.
—
Reply to this email directly, view it on GitHub<#22422 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOBCMCUROYBFJA6Q5TTD4DLZ66TWPAVCNFSM6AAAAABRC65I26VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJUGUZTGMI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I've been trying to put my PCA9685 into operation with Tasmota for days. But unfortunately it doesn't work.
After he always showed the INA219. I deactivated driver 14, which was never plugged in, see picture.
But the PCA9685 still doesn't work.
As you can see in the picture it is recognized with 0x40 (0x20 is an MCP23017 on the same bus).
I compiled the following lines but it doesn't work.
Do I need to enter anything else into the console? Except I2C driver1 1
Beta Was this translation helpful? Give feedback.
All reactions