RoboPro Light

[UMueller]

Hallo,

oh doch und schon am 7.10.2010 auf http://www.ftcomputing.de/roboLightVB.htm
es läuft in der Tat problemlos.

Gruß Ulrich Müller

[vleeuwen]

Hello elektrolutz,
I have some experiance with the TC-C.
It is using the actual FTLib 1.78a.
Only a subset of the TA is availlable (2 actuators and 3 multi function inputs)
There is no fundamental reason for.

I have a FtTlService of MS-RDS working.
I will show this FtTlService with the TL-C as controller for a trail follow FT-bot in Munster (13-11-2011).
The dotNet framework wrapper is offering events.

KInd regards,
Carel

[UMueller]

Hallo,
@vleeuwen,

das ROBO LT läuft problemlos mit Robo Pro v3.12, mit den alten Versionen nicht.
bei Betrieb mit umFish40.DLL ist v4.3.77 erforderlich.

Gruß Ulrich Müller

[UMueller]

Hallo,

den Haupteinsatz des ROBO LT sehe ich im Schulbereich und da meist auch in Zusammenhang mit den dort üblichen Programmiersprachen (Java dürfte der Spitzenreiter sein). Anfragen bekomme ich eigentlich nur aus dem Schulbereich (von Lehrern).

Seitens Robo Pro wird wohl kein Interesse bestehen, ein Konkurrenz Produkt zu Robo Light zu schaffen.
Wenn dann eher umgekehrt. Mit Robo Pro können ja auch -die gar nicht vorhandenen - O1-O4 Ausgänge und AX, AY und A1 Eingänge bedient werden.

Gruß Ulrich Müller

[vleeuwen]

Version 3.1.2(.2) has not a menu option (interface port settings) for the TL-C.
The TL-C is not mention in the help file.
So officially the TL-C is not supported by RoboPro yet.
I did not tested if the multi functionality of the input port is supported by RoboPro yet.

The TL-C works fine and is a good and cheep alternative for the TX-C in case of only use.

I have under MS-RDS good experiences with the TX-L.

[vleeuwen]

@elektrolutz
Good question:
The name on the box of the TX-C is "Robo TX controller" and the name on the the light brick is "Robo TL Controller" .
I guess that the Robo prefix has nothing to do with Knobloch but is an abbreviation of "Robotics".

The MS-RDS service are called FtTxService and FtTlService.

For the moment I can not deteminate the source for the name TX-L.
Notes: after some research: it is a writing error, orriginal I also was using TL-C.
(Most of the errors are already repaired now.
In the past I was using the work name "Baby controller"


I think that Robo TX (TX-C) and Robo TL (TL-C) will be better names to use.
I will ckeck my documentation on it.

I received the Robo TL before the release of RoboPro 3.1.2.
I did not test it with 3.1.2, my conclusion about the compatibility are based on the help description.
On the other hand the FtLib 1.78a indicates in the comment of the header files full support but this is not documented in the documentation.
Note: I tested it today. Choose for the Robo Interface a it works. But there are no warning in case that I was using the not existing inputs or outputs. I notice also so instability. The connection with RoboPro was lost several times.

The connection between MS_RDS and the TL-C (FtLib 1.78a) is very stable.

[vleeuwen]

Thanks, I was already acquainted with this review.
One think is not clear to me.
With RoboPRo I am not able to select the "Unique serial number"
Now my interface has 2 as current serial number.
If the serial number is not changeble, than it is not possible to connect more than one Robo TL-C with a PC.
The USB protocol demands unique serial numbers for each device.

The TX-C has the same problem.