Files
BionxControl/bctransmitter.cpp

243 lines
6.7 KiB
C++
Raw Normal View History

2025-12-26 14:07:55 +01:00
/***************************************************************************
BionxControl
2026-01-03 23:51:14 +01:00
© 2025 -2026 christoph holzheuer
2025-12-26 14:07:55 +01:00
christoph.holzheuer@gmail.com
Using:
mhs_can_drv.c
© 2011 - 2023 by MHS-Elektronik GmbH & Co. KG, Germany
Klaus Demlehner, klaus@mhs-elektronik.de
@see www.mhs-elektronik.de
Based on Bionx data type descriptions from:
BigXionFlasher USB V 0.2.4 rev. 97
© 2011-2013 by Thomas Koenig <info@bigxionflasher.org>
@see www.bigxionflasher.org
Bionx Bike Info
© 2018 Thorsten Schmidt (tschmidt@ts-soft.de)
@see www.ts-soft.de
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.
@see https://github.com/bikemike/bionx-bikeinfo
***************************************************************************/
2025-12-20 16:33:00 +01:00
#include <QThread>
#include <QDebug>
#include <bctransmitter.h>
2026-01-03 20:10:30 +01:00
/**
* @brief Kosntruktion. Aktiviert erstmal den Dummy-Driver.
*/
2025-12-20 16:33:00 +01:00
BCTransmitter::BCTransmitter(QObject *parent)
: QObject(parent), _isBusy(false)
{
2026-01-02 22:15:50 +01:00
//_canDriver = new BCDriverTinyCan{this};
2026-01-03 20:10:30 +01:00
_canDriver = &_dummyDriver;
2025-12-20 16:33:00 +01:00
}
2026-01-05 17:57:13 +01:00
2026-01-03 20:10:30 +01:00
/**
* @brief Steuert die Verbindung mit dem 'echten' CAN-Bus Treiber.
* @param connect true: Vesuche den CAN-Bus Treiber zu laden und zu verbinden
* false: Disconnect & Cleanup
*/
void BCTransmitter::onToggleDriverConnection( bool connect )
{
qDebug() << " --- onToggleDriverConnection: " << connect;
// FIX! Ende der current op abwarten!
2026-01-05 23:39:45 +01:00
BCDriver::DriverState state = connect ? BCDriver::DriverState::DeviceReady : BCDriver::DriverState::NotPresent;
const QString& message = connect ? "Trying to connect" : " FAILED";
emit driverStateChanged(state, message);
return;
2026-01-03 23:51:14 +01:00
// Hier sind wir noch in GUI Thread
QMutexLocker locker(&_mutex);
2026-01-03 20:10:30 +01:00
// weitere operation stoppen
_isBusy = true;
connect ? connectCanDriver() : disconnectCanDriver();
2026-01-03 23:51:14 +01:00
_isBusy = false;
2026-01-03 20:10:30 +01:00
}
2025-12-20 16:33:00 +01:00
2026-01-05 17:57:13 +01:00
2026-01-05 23:39:45 +01:00
void BCTransmitter::onStartNativeDriver()
2026-01-05 17:57:13 +01:00
{
}
2026-01-03 20:10:30 +01:00
void BCTransmitter::connectCanDriver()
2025-12-20 16:33:00 +01:00
{
2026-01-03 20:10:30 +01:00
// hier gehts nur um den echten Treiber
// Treiber laden und/oder starten:
2026-01-03 23:51:14 +01:00
BCDriver::DriverStateResult result; //(defaults to 'NotPresent')
2026-01-03 20:10:30 +01:00
if( _tinyCanDriver.getDriverState() != BCDriver::DriverState::DeviceReady )
2026-01-03 23:51:14 +01:00
result = _tinyCanDriver.loadAndStartDriver();
2026-01-03 20:10:30 +01:00
2026-01-03 23:51:14 +01:00
QString message("FitzeFatze!");
2026-01-03 20:10:30 +01:00
// hat geklappt
2026-01-03 23:51:14 +01:00
if( _tinyCanDriver.getDriverState() >= BCDriver::DriverState::Opened )
2025-12-20 16:33:00 +01:00
{
2026-01-03 20:10:30 +01:00
uint32_t console = static_cast<uint32_t>(BCDevice::ID::Console);
uint8_t hwRev = static_cast<uint8_t> (BC::ID::Cons_Rev_Hw);
2025-12-20 16:33:00 +01:00
2026-01-03 20:10:30 +01:00
TransmitResult hwVersion = _tinyCanDriver.readRawByte( console, hwRev);
if( hwVersion.has_value() )
2026-01-03 23:51:14 +01:00
{
message = " ---- HAIL to the king!";
qDebug() << message;
// swap driver
_canDriver = &_tinyCanDriver;
}
2025-12-20 16:33:00 +01:00
else
2026-01-03 23:51:14 +01:00
{
2026-01-03 20:10:30 +01:00
qDebug() << "Console not responding";
2026-01-03 23:51:14 +01:00
}
2026-01-03 20:10:30 +01:00
}
2026-01-03 23:51:14 +01:00
else
{
message = result.error();
}
emit driverStateChanged( _tinyCanDriver.getDriverState(), message );
2026-01-03 20:10:30 +01:00
}
2025-12-20 16:33:00 +01:00
2026-01-03 20:10:30 +01:00
void BCTransmitter::disconnectCanDriver()
{
2026-01-03 23:51:14 +01:00
_tinyCanDriver.resetDriver();
_canDriver = &_dummyDriver;
emit driverStateChanged( _tinyCanDriver.getDriverState(), "Disconnected" );
2025-12-20 16:33:00 +01:00
}
2026-01-05 17:57:13 +01:00
void BCTransmitter::onEnqueueValue( BCValuePtrConst value)
2025-12-20 16:33:00 +01:00
{
2026-01-06 02:07:42 +01:00
// wir stellen hier auf die arte Tour sicher, das onEnqueueValue
// nicht aus dem Parent-Thread direkt sondern über die EventQueue aufgerufen wurde.
Q_ASSERT(QThread::currentThread() == this->thread());
2026-01-02 01:43:49 +01:00
// Hier sind wir noch in GUI Thread
2026-01-06 01:21:17 +01:00
//QMutexLocker locker(&_mutex);
_valueQueue.enqueue( value );
2025-12-20 16:33:00 +01:00
// wir wollen nicht den ganzen Value verschicken, erstrecht
2026-01-01 23:01:31 +01:00
// wollen wir nicht den Value in verschiedenen Threads gleichzeitig
2025-12-20 16:33:00 +01:00
// in die Hand nehmen, also hantieren wir nur mit den Inidizes.
// Trigger processing im Event-Loop des Worker Threads
// invokeMethod mit QueuedConnection entkoppelt den Aufruf,
2026-01-05 17:57:13 +01:00
// damit onEnqueueValue sofort zurückkehrt (non-blocking für den Aufrufer).
2025-12-20 16:33:00 +01:00
2026-01-06 02:07:42 +01:00
//QMetaObject::invokeMethod(this, "onProcessValue", Qt::QueuedConnection);
onProcessValue();
2025-12-20 16:33:00 +01:00
}
2026-01-05 17:57:13 +01:00
void BCTransmitter::onProcessValue()
2025-12-20 16:33:00 +01:00
{
2026-01-06 02:07:42 +01:00
//if (_isBusy)
// return;
2025-12-20 16:33:00 +01:00
_isBusy = true;
while (true)
{
2026-01-02 16:25:21 +01:00
BCValuePtrConst valuePtr{};
2025-12-20 16:33:00 +01:00
{
2026-01-06 01:21:17 +01:00
//QMutexLocker locker(&_mutex);
2025-12-20 16:33:00 +01:00
if (_valueQueue.isEmpty())
{
_isBusy = false;
break; // Schleife verlassen, warten auf neue Events
}
2026-01-02 16:25:21 +01:00
valuePtr =_valueQueue.dequeue();
2025-12-20 16:33:00 +01:00
} // Mutex wird hier freigegeben! WICHTIG: Execute ohne Lock!
2026-01-02 16:25:21 +01:00
// Kosmetik
const BCValue& value = *(valuePtr.get());
2026-01-02 01:52:48 +01:00
2026-01-06 02:07:42 +01:00
qDebug() << "------- DE.-.QUEUE: " << QThread::currentThreadId() << ": " << value.label;
2026-01-01 23:01:31 +01:00
// Value ist 'under construction'
2026-01-02 22:15:50 +01:00
//emit valueUpdated( value.deviceID, value.indexRow, BCValue::State::Locked );
2026-01-02 16:25:21 +01:00
2026-01-03 02:50:28 +01:00
2026-01-02 16:25:21 +01:00
uint32_t devID = static_cast<uint32_t>(value.deviceID);
uint8_t regID = static_cast<uint8_t> (value.registerID);
2026-01-02 22:15:50 +01:00
2026-01-02 16:25:21 +01:00
QString newVisibleValue;
2026-01-02 22:15:50 +01:00
BCValue::State newState = BCValue::State::NoState;
2026-01-02 16:25:21 +01:00
if(value.state.testFlag( BCValue::State::WriteMe ) )
{
2026-01-02 16:25:21 +01:00
}
2026-01-02 16:25:21 +01:00
// oder sollen wir hier beides erlauben ? readFlag & writeFlag ?
// Was kommt dann zuerst? Schreiben und lesen als verify ?
else if( value.state.testFlag( BCValue::State::ReadMe ) )
{
2026-01-02 16:25:21 +01:00
// wir sind hier im anderen thread! nicht einfach so reinschreiben, nur lesen
TransmitResult result = value.isWord ? readWordValue( devID, regID ) : readByteValue( devID, regID );
2026-01-02 16:25:21 +01:00
if( result.has_value() )
2026-01-02 22:15:50 +01:00
{
newVisibleValue = value.formatValue( result.value() );
2026-01-02 22:15:50 +01:00
newState = BCValue::State::InSync;
}
else
{
newState = BCValue::State::Failed;
}
}
2026-01-02 16:25:21 +01:00
2026-01-02 22:15:50 +01:00
emit valueUpdated( value.deviceID, value.indexRow, newState, newVisibleValue );
// __fix
2026-01-06 02:07:42 +01:00
//bc::processEventsFor(150);
bc::delay_millis(150);
2025-12-20 16:33:00 +01:00
}
}
2026-01-01 23:01:31 +01:00
TransmitResult BCTransmitter::readByteValue( uint32_t deviceID, uint8_t registerID )
2026-01-02 16:25:21 +01:00
{
2026-01-04 00:40:53 +01:00
//qDebug() << " --- YES: Read ByteValue: " << registerID;
// Wir lesen nur ein Byte und gut.
2026-01-02 16:25:21 +01:00
return _canDriver->readRawByte( deviceID, registerID );
2025-12-21 14:40:38 +01:00
}
2025-12-20 16:33:00 +01:00
2026-01-02 16:25:21 +01:00
TransmitResult BCTransmitter::readWordValue( uint32_t deviceID, uint8_t registerID )
2025-12-21 14:40:38 +01:00
{
2026-01-04 00:40:53 +01:00
//qDebug() << " --- YES: Read WordValue: " << registerID;
uint32_t result{};
// hi byte Leseversuch.
TransmitResult value = _canDriver->readRawByte( deviceID, registerID );
// Fehler? dann weg
if( !value)
return std::unexpected( value.error() );
// hi byte speichern
result = *value << 8;
// low byte, liegt im followup register: +1
value = _canDriver->readRawByte( deviceID, registerID+1 );
if( !value)
return std::unexpected( value.error() );
result += *value;
return result;
2025-12-20 16:33:00 +01:00
}