Arduino + Softwareserial.h +TPUART

[sam77ma]

Hello,
Congratulations for this repository.
I recently used a project with Arduino SoftwareSerial Library, I was wondering if it works even with KNXdevice.h + TPUART interface.
So I did a test.

My configuration was:

1. Arduino nano (supply by PC)
2. • optocoupler pin7(Rx), pin8(Tx) Arduino Nano (supply: by PC and by bus_knx respectly)
3. • TPUART pin7==> pinTxD_knx ; pin8==>RxD_knx (supply by bus_knx)

Some pieces of code _test_softserial_knx.txt attach files.

However, I had the following compilation problem:....................................................................................................................

test_softserial_knx:85:35: error: no matching function for call to 'KnxDevice::begin(SoftwareSerial&, word)'
Knx.begin(SerialS, P_ADDR(1,1,80)); // start a KnxDevice session with physical address 1.1.80 on SerialS

\KnxDevice-master/KnxDevice.h:133:23: note: candidate: e_KnxDeviceStatus KnxDevice::begin(HardwareSerial&, word)
e_KnxDeviceStatus begin(HardwareSerial& serial, word physicalAddr);

\KnxDevice-master/KnxDevice.h:133:23: note: no known conversion for argument 1 from 'SoftwareSerial' to 'HardwareSerial&'
Uso la libreria KnxDevice-master nella cartella: ...\libraries\KnxDevice-master (legacy)
Uso la libreria SoftwareSerial alla versione 1.0 nella cartella: C:\Program Files (x86)\Arduino\hardware\arduino\avr\libraries\SoftwareSerial
exit status 1
no matching function for call to 'KnxDevice::begin(SoftwareSerial&, word)'
...........................................................................................................................

Is there a way to get around this problem?
Thank you.
Samuele
_test_softserial_knx.txt

[shyne99]

Its a bit late. The answer is on the error.

Since you are using SoftwareSerial, the Object signature of your Serial is "SoftwareSerial" and not as the expected "HardwareSerial".

I never tested this, but if you want to dig deeper, try switching every method and functions signature (and also the parameter) from harwareSerial to SoftwareSerial.

For exemple in your error, KnxDevice::begin(HardwareSerial&, word) is expecting the first argument to be of type HarwareSerial& but you gave it a SoftwareSerial& . Try switching this to SoftwareSerial and keep on your testing.

Regards.

[sam77ma]

Good morning Shyne99,
I did as suggested, especially I replaced hardwareserial to softwareserial in the following files:
KNXDEVICE.CPP, KNXDEVICE.H, KNXTPUART.CPP, KNXTPUART.H
So now the compilation / download is ok

Communication on the KNX bus, however, did not work, I discovered that the problem was due to the SoftwareSerial library that does not include the Even Parity control which instead is configured in the KNXTPuart.cpp file (see KNXTPUART.CPP _serial.begin (19200, serial_8e1);
So I have changing softwareSerial and I managed to communicate my card on a KNX bus. In particular I can now keep the USB converter (FDTI232) to the Pro-Mini simultaneously and communicate with KNX bus. I can then activate Arduino monitor or download the code.

One thing I still have to understand, if you don't connect bus KNX the KNX.TASK () blocks or slows very much Void loop (), if you connect KNX bus all ok, if you then disconnect KNX bus on the fly after it was turning it remains everything ok (No slowdown in the void loop ()). I did the tests with "KNXDEVICE_PUSHBUTTON.INO" (modified with My SoftwareSerial).

Thanks again for your suggestions.
Greetings

[shyne99]

Noice. Try to define KNXTPUART_DEBUG_ERROR and share the output with between which message it hangs.

[sam77ma]

Good evening,
I tried to understand how to make the request for error, but I wasn't sure, so instead I used the "KnxTpUart_UnitTests.ino" example modified with my softwareserial. I used the Arduino monitor to send the command. I sent the "init" command twice. with and without connection of the KNX bus
With connected KNX bus , the results are the following:

########## Init Tests ##########
### Testing NORMAL mode Init with error KNX_TPUART_ERROR_NOT_INIT_STATE (254)
Init return val = 254
### Testing NORMAL mode Init with error but empty list warning
Requesting Reset...
KNXTPUART INFO: Reset successful
Init return val = 253
### Testing NORMAL mode Init with error KNX_TPUART_ERROR_NULL_EVT_CALLBACK_FCT (253)
KNXTPUART INFO: AttachComObjectsList successful
Init return val = 253
### Testing NORMAL mode Init with error KNX_TPUART_ERROR_NULL_ACK_CALLBACK_FCT (252)
Init return val = 252
### Testing NORMAL mode Init with no error
KNXTPUART INFO: Init : Normal mode started
Init return val = 0
### Testing NORMAL mode Init after hot reset
Requesting Reset...
KNXTPUART INFO: Reset successful
Init return val = 0
KNXTPUART INFO: Destructor: connection closed, byebye
### Testing MONITOR mode
Requesting Reset...
KNXTPUART INFO: Reset successful
Init return val = 0
KNXTPUART INFO: Destructor: connection closed, byebye

Then with bus KNX disconnected, the results are the following:

########## Init Tests ##########
### Testing NORMAL mode Init with error KNX_TPUART_ERROR_NOT_INIT_STATE (254)
Init return val = 254
### Testing NORMAL mode Init with error but empty list warning
Requesting Reset...
KNXTPUART ERROR: Reset failed, no answer from TPUART device
Init return val = 254
### Testing NORMAL mode Init with error KNX_TPUART_ERROR_NULL_EVT_CALLBACK_FCT (253)
Init return val = 254
### Testing NORMAL mode Init with error KNX_TPUART_ERROR_NULL_ACK_CALLBACK_FCT (252)
Init return val = 254
### Testing NORMAL mode Init with no error
Init return val = 254
### Testing NORMAL mode Init after hot reset
Requesting Reset...
KNXTPUART ERROR: Reset failed, no answer from TPUART device
Init return val = 254
KNXTPUART INFO: Desctructor: byebye
### Testing MONITOR mode
Requesting Reset...
KNXTPUART ERROR: Reset failed, no answer from TPUART device
Init return val = 254
KNXTPUART INFO: Desctructor: byebye

you see the differences (Init return val = always 254 , and no answer from TPUART device.
However, I don't understand how to get around the problem of void loop slowed down if KNX Disconnected.
For now I comment the KNX.TASK function as long as I don't need the KNX bus.

void loop(){ 
  //Knx.task();
.........
// my code  
}

thanks for your help

[shyne99]

Can you pinpoint where in the log does the code hangs ?

[sam77ma]

I saw Knx.task(); is defined on knxdevice.cpp, but I don't know how to debug them inside. What should I do?

I tried to observe all situations with this simple code:

void setup() {		
	pinMode(SOFTTX, OUTPUT);
	pinMode(SOFTRX, INPUT);		
	delay(100);
		
	Serial.begin(9600);	
	Serial.println("Ready to receive from Pro-Mini");		
	delay(1000);	
    
	Knx.begin(mySerial, P_ADDR(1,1,80)); // start a KnxDevice session with physical address 1.1.80 on mySerial
	delay(1000);		
}

void loop() {	
	Knx.task();	
	currentTmain= millis(); 
	if (currentTmain - prevTMain >= btmain) //test timer ms
	{	prevTMain+=btmain;  //currentTmain; 					
		
		Serial.print("prevTMain:"); Serial.println(prevTMain); 
		
	} //fine Tmain		
}

Response when KNX is disconnected(pro-mini remains powered by USB Converter (FTDI232)) :

Ready to receive from Pro-Mini
Ready to receive from Pro-Mini
Ready to receive from Pro-Mini
Ready to receive from Pro-Mini
.........

I think that Pro-mini restarts continuously . I don't know why I didn't apply any watchdog
As soon as I connect KNX bus, the operation returns normal.
Note! If you disconnect or connect KNX bus after PRO mini is already started, it works normally.
So the problem is in the initialization (at first start of pro-mini without KNX bus).

Response when KNX is connected(works normally) :

Ready to receive from Pro-Mini
prevTMain:1000
prevTMain:2000
prevTMain:3000
prevTMain:4000
prevTMain:5000
prevTMain:6000
prevTMain:7000
prevTMain:8000
prevTMain:9000
......

[sam77ma]

I have any news.
The problem is the ARDUINO restart when bus KNX is disconnected,
I see this fact because I entered only in the Void Setup () On/Off Digital Output and control with oscilloscope. When there is no problem I see only one On/Off, when there is the problem I see on/off repeated every 10ms.
This allowed me to find which part of the code triggers this event.
In the KNXTPUART.CPP file, inside Void KNXTPUART :: RXTASK (Void), if you commentately else the code and leave only (see below):

void KnxTpUart::RXTask(void)
{
byte incomingByte;
word nowTime;
static byte readBytesNb; // Nb of read bytes during an EIB telegram reception
static KnxTelegram telegram; // telegram being received
static byte addressedComObjectIndex; // index of the com object targeted by the received telegram
static word lastByteRxTimeMicrosec;

......... Code commented
 if (_serial.available() > 0) 
  {
  } // if (_serial.available() > 0)
}
..... Code commented

the problem still comes, if I comment in this way:

IF (/*_serial.available()*/ 1> 0)
   { 
   } // if (_serial.available() > 0)

The problem disappears !
The cause therefore should be _serial.available ().
I don't know why this.
Note!
I tried this problem, it happens both with hardwareserial, and with softwareserial library.

Do you know a way to get around the problem?
Thank you