- Dieses Thema hat 11 Antworten und 2 Teilnehmer, und wurde zuletzt aktualisiert vor 8 Monaten, 3 Wochen von
.
-
Beiträge
-
-
Hi,
I’ve compiled MTC4PF with PlatformIO Core 6.1.9, Home 3.4.4
This are the sections, I’ve changed in controller_config.h
locoConf[0] = (MattzoLocoConfiguration){
.locoName = “BR103”,
.locoAddress = 103,
.accelerationInterval = 100,
.accelerateStep = 5,
.brakeStep = 10
};msConf[0] = (MattzoMotorShieldConfiguration){
.locoAddress = 103,
.motorShieldType = MotorShieldType::L9110,
.L298N_enA = 0,
.L298N_enB = 0,
.in1 = D1,
.in2 = D2,
.in3 = 0,
.in4 = 0,
.minArduinoPower = MIN_ARDUINO_POWER,
.maxArduinoPower = MAX_ARDUINO_POWER,
.configMotorA = 1,
.configMotorB = 0,
.irChannel = -1
};Yet the controller tells me:
loco id: BR 103
addr: 103
Message disregarded, as this controller does not handle train 103
<lc> node found. Processing loco message…Any pointers, what is going wrong here ?
/M
-
-
// Author: Dr. Matthias Runte
// Copyright 2020 by Dr. Matthias Runte
// License:
// Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
// The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
// THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.// This file is the configuration file for the firmware
// You need to adapt it to the specific requirements of the desired behaviour of the controller
// The file contains default values for the standard wiring layout of the MattzoLayoutController
// Check the examples in the “examples” directory for more inspiring creations// ************************************************
// Example file for a simple train with MTC4PF mini
// ************************************************// *****
// LOCOS
// *****// Number of locos (aka. MattzoLocos) controlled by this controller
const int NUM_LOCOS = 1;// List of MattzoLocos
// The parameters have the following meaning:
// – locoName: name of the loco as setup in Rocrail
// – locoAddress: address of the loco as setup in Rocrail
// – accelerationInterval: time interval for acceleration / braking (default: 100 ms)
// – accelerateStep: power increment for each acceleration step
// – brakeStep: : power decrement for each braking step
MattzoLocoConfiguration* getMattzoLocoConfiguration() {
static MattzoLocoConfiguration locoConf[NUM_LOCOS];locoConf[0] = (MattzoLocoConfiguration){
.locoName = “BR103”,
.locoAddress = 103,
.accelerationInterval = 100,
.accelerateStep = 5,
.brakeStep = 10
};return locoConf;
}// *************
// MOTOR SHIELDS
// *************
// Number of motor shields connected to this controller
const int NUM_MOTORSHIELDS = 1;// List of motor shields that are controlled by this controller
// The parameters have the following meaning:
// – locoAddress: loco that this motor shields is attached to
// – motorShieldType: motor shield type
// – L298N_enA, L298N_enB: PWM signal pin for motor A / B, if L298N is used.
// – in1..in4: pin for motor direction control for motor shields L298N and L9110 (in1: forward motor A, in2: reverse motor A, in3: forward motor B, in4: reverse motor B).
// – minArduinoPower: minimum power setting for Arduino based motor shields. You might need to adapt this to your specific shield and motor. 200 might be a good value for a start.
// – maxArduinoPower: maximum power setting for Arduino based motor shields (max. 1023). You might need to adapt this to your specific shield and motor. 400 might be a good value for a start.
// – configMotorA: turning direction of motor A (1 = forward, -1 = backward, 0 = unused). In case of LEGO IR Receiver 8884, this is the motor connected to the red port.
// – configMotorB: same for motor B; if IR receiver: blue port
// – irChannel: if a LEGO IR Receiver 8884 is used, the selected channel of the receiver. May be 0, 1, 2 or 3. If the loco uses multiple IR receivers on different channels, additional motor shields for the loco are required.
MattzoMotorShieldConfiguration* getMattzoMotorShieldConfiguration() {
static MattzoMotorShieldConfiguration msConf[NUM_MOTORSHIELDS];// Type of motor shield directly wired to the controller.
// (The different motor shield types are defined in MTC4PF.ino)
// Set to MotorShieldType::NONE if only virtual motor shields are used!
const MotorShieldType MOTORSHIELD_TYPE = MotorShieldType::L9110;msConf[0] = (MattzoMotorShieldConfiguration){
.locoAddress = 103,
.motorShieldType = MotorShieldType::L9110,
.L298N_enA = 0,
.L298N_enB = 0,
.in1 = D1,
.in2 = D2,
.in3 = 0,
.in4 = 0,
.minArduinoPower = MIN_ARDUINO_POWER,
.maxArduinoPower = MAX_ARDUINO_POWER,
.configMotorA = 1,
.configMotorB = 0,
.irChannel = -1
};return msConf;
}// *************************
// TRAIN LIGHT CONFIGURATION
// *************************// Number of train lights controlled by this controller
#define NUM_TRAIN_LIGHTS 0TTrainLightConfiguration trainLightConfiguration[NUM_TRAIN_LIGHTS] = {};
// ******************************
// FUNCTION MAPPING CONFIGURATION
// ******************************// Rocrail functions are used to MANUALLY switch train lights on and off
// Number of function mappings
#define NUM_FUNCTION_MAPPINGS 0TLocoFunctionMappingConfiguration locoFunctionMappingConfiguration[NUM_FUNCTION_MAPPINGS] = {};
// *********************************
// TRAIN LIGHT TRIGGER CONFIGURATION
// *********************************// Triggers are used to AUTOMATICALLY switch train lights on and off
// Number of train light triggers as defined just below
#define NUM_TRAIN_LIGHT_TRIGGERS 0TTrainLightTriggerConfiguration trainLightTriggerConfiguration[NUM_TRAIN_LIGHT_TRIGGERS] = {};
// ************************
// CONTROLLER CONFIGURATION
// ************************// Configuration for motorshield type Lego IR Receiver 8884
const uint8_t IR_LED_PIN=D5; // pin on which the IR LED is installed that controls all attached Lego IR Receiver 8884s.// Digital output pin to monitor controller operation (typically a LED)
// Set to false if no status LED is installed
const bool STATUS_LED_PIN_INSTALLED = true;
// If installed, the pin controlling the status LED
const uint8_t STATUS_LED_PIN = D8;
// If installed, set to true to flip high/low state of the status led pin
const bool STATUS_LED_REVERSE = false;
// Power level of the status LED (0..1023)
// Recommended max. power levels: white: 800, blue: 600, green: 500, yellow: 350, red: 300
const int STATUS_LED_POWER = 300;// Report battery level
#define REPORT_BATTERYLEVEL false // set to true or false to allow or omit battery level reports
#define SEND_BATTERYLEVEL_INTERVAL 60000 // interval for sending battery level in milliseconds
#define BATTERY_PIN A0
const int VOLTAGE_MULTIPLIER = 20000 / 5000 – 1; // Rbottom = 5 kOhm; Rtop = 20 kOhm; => voltage split factor
#define MAX_AI_VOLTAGE 5100 // maximum analog input voltage on pin A0. Usually 5000 = 5V = 5000mV. Can be slightly adapted to correct small deviations// ****************
// NETWORK SETTINGS
// ****************// Trigger emergency brake upon disconnect
const bool TRIGGER_EBREAK_UPON_DISCONNECT=true;// WiFi Hostname
// Hostnames must start with a-z, A-Z, 0-9. From 2nd character, hyphens (“-“) may also be used
const char* MC_HOSTNAME = “MTC4PF1”;// Syslog application name
const char* SYSLOG_APP_NAME = “MTC4PF1”; -
-
Yes, it’s in the “my” folder in the MTC4PF project folder named “controller_config.h” together with the network_config.h file. If the files weren’t in the right location, the board would not have the details to connect to my WiFi network either.
Additionally, the board tells me, it’s configured for BR103 / loco 103 and then turns around, that the controller is not configured to handle loco 103.
Output from the console:
loco id: BR103
addr: 103
Message disregarded, as this controller does not handle train 103/M
-
True. I assume you entered the correct loco Address in Rocrail, as the serial log shows it. Please check for any leading or trailing spaces before or after the “103” in Rocrail and delete them. Besides that, I do not know what the problem might be. I suppose it’s something really simple, but one of those things that are like a needle in the haystack.
-
The issue is, that I also have been testing with MTC4BT on an ESP32 board with the same loco and ID and there it works. So I’m also sure, that the RocRail configuration is correct.
You can see my initial tests with MTC4BT here: https://www.youtube.com/watch?v=9158apj1uVk
-
-
-
-
-
-
-
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.