I solved following serial port related problems in ubuntu 18.04 as follows:
Problem 1 : Cannot open /dev/ttyACM0: Permission denied
Solution : Grant permissions to read/write to the serial port with this terminal command ---> sudo chmod a+rw /dev/ttyACM0
Here replace tty port with your respective ubuntu port.
Problem 2 : Failed to open /dev/ttyACM0 (...
Ok, so you're using a Nano, which you've programmed with AVRstudio4 and the ISP instead of Arduino IDE, and you're monitoring the results with Realterm. A quick look on Google tells me these programs are outdated. I imagine AVR Studio 4 is similar to Arduino IDE, except it seems to have debugging features lacking in the Arduino IDE. To be honest, I am ...
I'm using a Nano, programming with AVRstudio4 and the ISP and monitoring with Realterm.
If I disable DTR in RealTerm, the ATMEGA does not get reset on connection. Looks like the DTR resets the comms chip and the ATMEGA.
Something else however, semi random is resetting the program.
Here is sample corrupted data.
:318.104.22.168.58. :322.214.171.124.55. :329.59304.0.37....
Am I to understand that you are not using the Arduino IDE's Serial Monitor to display your data? In which case I would have to assume that you're using another IDE or program, or you're building your own software to interface with your Arduino ATMEGA328 hardware. I'm not sure I understand. Can you be more precise? Which program are you using as the "...
I have hard time to find a good example for this. Is this possible? If
so, is there any good example?
I don't see that it should be any more complicated than this: -
The slave reader would use the SCLK generated and use MOSI for its data input. It doesn't matter at all that the data may be arriving from the ADC rather than from the actual SPI master.
It depends on you clock speed. Theorically you could just split the line and it will work. At higher speed a buffer on each branch would output a better signal (due to many reasons). This is of course valid for both MOSI and SCLK
From the comments, it seems there is no actual i2c device that must be used, communication is always initiated by the central device, and UART lines are available on both ends. In that case I don't think there is any advantage to i2c. Half duplex RS485, for example, would use the same number of lines and perform better all around.
This answer is just for ...
I've narrowed down the options to I2C with a repeater or RS485.
The important thing that will make this work is that you have data and clock from only master to slave. In other words, you don't have clocked data back from a slave as per this statement: -
And, if that is the case, it should work just fine. I've done the same with ...
Why can't you simply use the PL2303? it's still manufactured and quite available AFAIK.
Another hugely popolar USB/TTL serial bridge it the FTDI FT232 (many different versions, also bootlegged ones)
As for the Android support you could look at https://github.com/mik3y/usb-serial-for-android, it should handle many chips (included the PL2303)
The master does not know which slave pulled the SDA low to send the ACK. It just means that at least some chip responds to the address sent. In reality there could be accidentally or intentionally many slaves at the same address so they all would pull the SDA low to send an ACK bit.
However the assumption is that each chip has one (or multiple) unique ...