Samed Sivaslioglu

Hi, I know I asked another question here and find a way around it, and it goes from getting response's transactionId but for some reason whenever i try AbstractModbusMaster udpModbus = blabla... udpModbus.getTransport().readResponse().getTransactionID(); It returns timeout exception. Is there a way to get this?

As the title says, I dont get "No Response" message when the connection is lost But what i want is when the connection is lost response is not null so its not throwing an exception in AbstractModbusMaster class' getAndCheckResponse() method. Because even though the connection is lost, its returning the same response over and over. And program doesnt give me any exceptions or anything. Just repeating over same response. So I had the idea to check the transactionId and if its the same I'd be throwing...

As the title says, I dont get "No Response" message when the connection is lost

I've the below code when the application I get data from is not open, modbus throws no response exception but when I connect to the application first time and then close the application it doesnt send no response exception. It may be cause of buffer thing, I'm not sure but it still gives the data it read from last time. How can I solve this issue? Map<String,String> areaBitVectorMap = new Hashtable<>(); for(Pair<Area,AbstractModbusMaster> AreaModbusPair : area_modbus_pairs){ AbstractModbusMaster...

I've the below code when the application I get data from is not open, modbus throws no response exception but when I connect to the application first time and then close the application it doesnt send no response exception. It may be cause of buffer thing, I'm not sure but it still gives the data it read from last time. How can I solve this issue? Map<String,String> areaBitVectorMap = new Hashtable<>(); for(Pair<Area,AbstractModbusMaster> AreaModbusPair : area_modbus_paris){ AbstractModbusMaster...