TX and TXT with i2c

[Mark010]

Hi, I have connected 3 TX controllers and 1 TXT controller via USB within RoboPro. I can run both the TX and the TXT commands in 1 program. But what I am unable to do, is gettting the i2c displays I have working. Both the TX and the TXT are set as the main controller and I suspect that something is going wrong there, but you have to set it this way otherwise you cannot operate them in 1 program (In Online mode).

Does anyone have an idea if it is possible to get the i2c displays working in this setting? If I only use the TX controllers, with the FT-extender, the displays work fine.

Thanks in advance!

b17fca77-3987-4549-a4e3-471c52bb4311.png (145.24 KiB) 246 mal betrachtet

7f27cf31-a334-4c26-a00c-73ef34636ed0.png (110.29 KiB) 246 mal betrachtet

f54b0980-1c38-43e6-8edf-47511a402c4a.png (117.85 KiB) 246 mal betrachtet

[elektrofuzzis]

Hi Mark,

Could you please share more details how you connected the TXTs with each other?

Do you use the extension port to connect some slave TXTs to a master and did you connect the master to your PC?

Or do you connect all TXTs to the PC and there is no interconnection between the TXTs.

Did you ever tried to run your program in offline more / without a PC connected?

Best regards

Stefan

[Mark010]

Hi Stefan,

I connected the 3 tx controllers (1 master, 2 slaves) with cables with each other via the EXT port. Also on the TX Master i have connected the FT-extender. The master is connected via USB on my PC.
The TXT is also connected on my PC with USB.

This works well, i can run all programms in online mode and in Offline mode. When i have not connected the TXT, so just a program for the 3 TX controllers, the I2C displays work fine in online (for testing, slow) and in download (quick).

Only when i add the TXT, the i2c display don't respond/work. Maybe because there is one TX in master mode and one TXT in master mode at the same time?

See also this post: https://forum.ftcommunity.de/viewtopic. ... %3F#p60243

Kind regards, Mark

[elektrofuzzis]

Hi Mark,

I never tried this combination.

My first idea was, you tried to connect TX and TXT with a ribbon cable and/or ftextender. In that case you would block the i2c bus on a hardware level. But TXT is connected via USB. Fits to your referenced ftc forum topic.

Beside i2c, you're fixed in that setup to online mode. Your PC is the bridge to both sides.

Running the TX part offline on the TXs including i2c seems to be fine. That's expected, because you're in one ecosystem.

Looking at the online mode using i2c. There had been some guys decoding the protocol. It seems, that robo pro is completely running on your PC, just sending io commands via USB to your controller.

I2c is the same. Just an io command.

In case of motor commands, the robopro command knows the port (and the controller where the port is). So it's easy to send the io command to the correct controller via USB.

But with the i2c commands there is no choice which controller should be used. From a logical point of view, robopro has to decide if it uses the TX or the TXT. If it sends the io command to the TXT your programm will fail.

It's not proven or tested. Just an idea.

Connect an i2c device to the TXT. Run a dry run just using the TXT only. If all is good, connect a TX as well. Try i2c via TXT and an use a tx motor output as well.

Hope this helps,

Stefan