Hardware in The Loop (HIL) SysML Simulation Solution Overview (Part1)

Поделиться
HTML-код
  • Опубликовано: 11 окт 2024

Комментарии • 6

  • @mfcoch
    @mfcoch 7 месяцев назад +1

    Keep it worm!😅 Nice work as always Dr. Saul!

  • @brianMoberley
    @brianMoberley 7 месяцев назад +1

    Awesome!! I like how you incorporated Blynk. I didn’t know about that capability. Does this have a plugin assisting with the Mosquito broker or is it necessary to set up the broker in a more manual way? Thanks for sharing!

    • @MBSEExecution
      @MBSEExecution  7 месяцев назад

      Thank you for the feedback. You need to run broker in advance. Ones installed it can start automatically. Blynk is very good IoT claud option. Can by any other too! Great flexibility here on software and hardware.

  • @humper2004
    @humper2004 7 месяцев назад +1

    I am more curious about the opaque behaviors for MQTT, and that set up. Have not used this approach before. Assuming something like:
    MQTTopen(host, port) {
    var clientSocket = new MQTTClient(host, port); // Instantiate MQTT client
    ALH.setGlobalVariable("MQTT_Connection", clientSocket); // Store the connection globally
    clientSocket.connect(); // Connect to MQTT broker
    }
    MQTTpublish(topic, message) {
    var clientSocket = ALH.getGlobalVariable("MQTT_Connection"); // Retrieve MQTT client connection
    if (clientSocket) {
    clientSocket.publish(topic, message); // Publish message to MQTT broker
    } else {
    // Handle error: Connection not found
    }
    }
    Saw your subscribe method in video.
    Assume your Cameo was running on same environment as MQTT client?

    • @MBSEExecution
      @MBSEExecution  7 месяцев назад

      You are absolutely right. We will share this library during MBSE Symposium.