This is original configuration: (link 1 of my LinkTree)
I create a DIY H-shifter, so I would like to clone the signal sent from the original one.
I would like to start one gear at a time, so I'm working for first gear now.
I used a logic analyzator to sniff I2C signal, I found this: (link 2 of my LinkTree)
So I wrote this sketch https://pastebin.com/aMV6pV3G
Address is the same (0x01) and I'm sure about connections (I used logic analyzator on SCL and SDA).
Anyway, my code doesn't work. I receive NAK and data are not transmitted.
(link 3 of my LinkTree)
So, I decided to try to read with an another Arduino the signal transmitted using original shifter.
I used this sketch (link 4 of my LinkTree) and I found this (link 5 of my LinkTree)
So, I am sure address is right and connection is right. Arduino can read but it can't write.
Why? Can anyone help me?
How can the capture of the original shifter be a I2C signal ?
It is wrong in every way. There is a START and a STOP, but that's all.
Can you try to sample at a higher rate ? Or do a analog capture ?
My logic analyzer is 24MHz and it only have digital function.
Anyway my code should work, check this forum: https://www.isrtv.com/forums/topic/24532-gearbox-connector-on-base/
There are two pages. If you need any download, please send me a screenshot and I will send you
The Youtube video is removed and there is no explanation how it was done.
There is only a hint that is was working with an Arduino, but without any proof.
Then I say that no one has it working, until proven otherwise.
I suggest to just try to get a ACK on the address.
Which Arduino board do you use ?
The Arduino Uno/Nano can not go lower than about 32kHz.
SCL is 90 kHz, that is okay.
There is a glith pulse on SDA at the last databytes before the ACK. That can often be ignored. It does not break the I2C protocol.
There are big gaps in the SCL signal. In a normal situation, it could be "clock pulse stretching" by the Slave. The Arduino Wire library supports that. The I2C data should still be valid. However, I think it is not "clock pulse stretching" by the Slave. I think they are delays by the Master software.
The Arduino Wire library can set the speed of the SCL clock, but it can not add gaps between databytes and it can not add gaps somewhere in the middle of a databyte.