fischertechnik community forum

In der neuen 3.1.4 Version wurden ein paar Probleme gefixt.
Z.B. wurde der Zugang zur API via Swagger Doku angepassst.

@baschdl78:
Das wird besonders Dir gefallen: Der Zugriff via Swagger (mit EXECUTE aus den Beispielen) ist jetzt via Netzwerk
oder über den TXT4 als AccessPoint möglich.
Die Node-RED nodes für den Zugriff auf die API
(node-red-contrib-sse-client, node-red-contrib-multipart-stream-decoder, node-red-node-base64)
wurden der Node-RED Installation auf dem TXT4 ebenfalls hinzugefügt.

Damit ist jetzt ein direkter Zugriff auf die IOs des TXT4 via API Zugriff aus Node-RED möglich.

This are the REST-API?
What about the speed?
What about the sample rate for close loop controls stability?
Where is the official fischertechnik documentation?
=================================
Dies sind die REST-API?
Was ist mit der Geschwindigkeit?
Was ist mit der Abtastrate für die Stabilität der Closed-Loop-Regelung?

The swagger documentation is official ft documentation.
It is available on the webserver of your TXT4.

I think you will find no other pdf or paper documentation actually.
But this makes it interesting - isn't it?

The speed question is secondary for most of my Node-RED apps -
I like to place the logic inside Node-RED and need the IOs for the connection to ft world...

The APIs counter stream deliveres messages every 100ms, this is OK for my applcations.

However in compare with the TXT, 100ms is very slow for closed control loop applications.
For example, the fischertechnik pulswheel sensor is aiming to 10 ms.
How to combine Rest API with black box control loops created in Blockley?

In Node-Red I do the API access via HTTP request nodes sending header and payload to the API. I do not know if there is an equivalent functionality in Blockly...

Yes, in TXT4.0 firmware version 3.1.4 you can do the same in Python or C++.
In Node red you also create MQTT clients, which are publishing and subscribing to a MQTT broker.
But that was already possible with the TXT with a RoboPro SLI extension element, like I am using with the ft-factory (9V)
Th MQTT broker manages the subscriptions, QOS and retain.
The MQTT broker makes it also possible to connect to other MQTT brokers outside the LAN (bridge functionality).
Does not allow close control loops with a speed of 20 ms like the TXT with the Berkeley socket based Transfer Area.

The Mosquitto MQTT broker starts with the Mosquitto.conf:
https://mosquitto.org/man/mosquitto-conf-5.html
and
http://www.steves-internet-guide.com/mo ... %20Windows.
On the TXT, the user can have root access and adapted the MQTT conf to actual situation.

A lot of different Iot device can connect to a MQTT broker, so a mix of RaspPi's, TXT4.0, TXT, laptops, etc., etc is possible.
A subscriber is subscribing to Topic's and not to devices.

Yes, in TXT4.0 firmware version 3.1.4 you can do the same in Python or C++.
In Node red you also create MQTT clients, which are publishing and subscribing to a MQTT broker.
But that was already possible with the TXT with a RoboPro SLI extension element, like I am using with the ft-factory (9V)
Th MQTT broker manages the subscriptions, QOS and retain.
The MQTT broker makes it also possible to connect to other MQTT brokers outside the LAN (bridge functionality).
Does not allow close control loops with a speed of 20 ms like the TXT with the Berkeley socket based Transfer Area.

The Mosquitto MQTT broker starts with the Mosquitto.conf:
https://mosquitto.org/man/mosquitto-conf-5.html
and
http://www.steves-internet-guide.com/mo ... %20Windows.
On the TXT, the user can have root access and adapted the MQTT conf to actual situation.

A lot of different Iot device can connect to a MQTT broker, so a mix of RaspPi's, TXT4.0, TXT, laptops, etc., etc is possible.
A subscriber is subscribing to Topic's and not to devices.