Hallo ich habe eine Frage, und hoffe ich habe sie beim durchsuchen des Forums nicht überlesen.
Ich versuche momentan den Controller mittels der C++ Native Library zum laufen zu bringen.
Grundsätzlich scheint es zu funktionieren aber wie steuere ich den Motor an und vor allem welche DutyWerte muss ich dem Controller für den Motor geben?
RoboProProggen
Forumsregeln
Bitte beachte die Forumsregeln!
Bitte beachte die Forumsregeln!
Re: RoboProProggen
Eine weitere Frage, welches Protokoll verwendet der Robo-Tx Controller zur Datenübertragung?
Re: RoboProProggen
The basic information about the data transfer you will find in the documentation from fischertechnik.
The FtMscLib is documented in unmanged C. The same for the transfer area (TA, communication protocol between the application and the hardware)
Because of the callback's you will have to deal with this problem when switching to C++.
The FTcomputing stuff don't give solution for this wrapper problems.
However there is enough to find about it on the internet .
http://www.fischertechnik.de/de/home/do ... uting.aspx
The FtMscLib is documented in unmanged C. The same for the transfer area (TA, communication protocol between the application and the hardware)
Because of the callback's you will have to deal with this problem when switching to C++.
The FTcomputing stuff don't give solution for this wrapper problems.
However there is enough to find about it on the internet .
http://www.fischertechnik.de/de/home/do ... uting.aspx
ROBO TX Controller
PC Programming ROBO-TXC Version 1.4 - 2,43 MB
Datenpaket für die Programmierung des fischertechnik ROBO TX Controllers vom PC aus, insbesondere für PC-Programmierer, die nicht mit der fischertechnik Programmieroberfläche ROBOPro arbeiten, sondern eigene PC-Programme für den ROBO TX Controller erstellen möchten. JETZT NEU: Für TXC -Firmware-Version 1.24 und mit vollständiger Bluetooth-Funktionalität
Zuletzt geändert von vleeuwen am 23 Feb 2012, 12:01, insgesamt 1-mal geändert.
Re: RoboProProggen
Hi,
@asimov
Which library do you mean with Native C++? I'm only aware of the ftMscLib which is C. Regarding the protocols, there are different connections and protocols:
PC - TX: CDC over USB and RFCOMM over Bluetooth (essentially serial port emulations), protocols: X1, console and X-modem 1K
TX - TX: RS485, protocol: X1 (connecting slaves to a master)
TX - TX: Bluetooth, protocol: proprietary (message exchange)
The ftMscLib relies mostly on X1 (at least for input/output). The trasfer thread keeps the input/output records synchronised by means of request/reply messages. Hence the TRANSFER_AREA concept is just an API to the underlying message interface. X1 is partly disclosed in the ftMscLib documentation. The missing parts are the exact handling of SID/TID and the values of the command field. The commands have small integer values (range about 0-30) and the replies have the same value+100. The associated payload is typically a certain record in the transfer area.
@asimov
Which library do you mean with Native C++? I'm only aware of the ftMscLib which is C. Regarding the protocols, there are different connections and protocols:
PC - TX: CDC over USB and RFCOMM over Bluetooth (essentially serial port emulations), protocols: X1, console and X-modem 1K
TX - TX: RS485, protocol: X1 (connecting slaves to a master)
TX - TX: Bluetooth, protocol: proprietary (message exchange)
The ftMscLib relies mostly on X1 (at least for input/output). The trasfer thread keeps the input/output records synchronised by means of request/reply messages. Hence the TRANSFER_AREA concept is just an API to the underlying message interface. X1 is partly disclosed in the ftMscLib documentation. The missing parts are the exact handling of SID/TID and the values of the command field. The commands have small integer values (range about 0-30) and the replies have the same value+100. The associated payload is typically a certain record in the transfer area.