You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Joris Suppers <j....@sotec.eu> on 2020/05/29 08:11:07 UTC
S7 DATA_BLOCKS error
Hey Everyone,
We are currently testing the Siemens S7 connector (S7_1200) using the
scrapper, and have come into an issue.
When testing the values as shown in the "Getting Started" page (
https://plc4x.apache.org/users/plc4j/gettingstarted.html) we can
successfully read the following values:
builder.addItem("value-1", "%Q0.4:BOOL");
builder.addItem("value-2", "%Q0:BYTE");
builder.addItem("value-3", "%I0.2:BOOL");
However when testing:
builder.addItem("value-4", "%DB.DB1.4:INT");
There is a Connection-Alias error:[image: image.png]
I have also tried the other syntax shown in "
https://plc4x.apache.org/users/protocols/s7.html" However, no luck.
We are using a 0.7.0-SNAPSHOT version, I have also tested with 0.7.0.
Is there something that still needs to be done? Any suggestions or comments
would be appreciated.
Many thanks,
Joris
--
Joris Suppers | SOTEC | j.suppers@sotec.eu | T +49 7033 5458 72
--
www.sotec.eu <http://www.sotec.eu/>
SOTEC Software Entwicklungs GmbH
+ Co Mikrocomputertechnik KG
Calwer Straße 11, D-75395 Ostelsheim
Sitz
Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, Geschäftsführer:
Florian Holz
Re: S7 DATA_BLOCKS error
Posted by Joris Suppers <j....@sotec.eu>.
Added the logback file get the following logs:
[main] INFO org.apache.plc4x.java.PlcDriverManager - Instantiating new PLC
Driver Manager with class loader
jdk.internal.loader.ClassLoaders$AppClassLoader@2626b418
[main] INFO org.apache.plc4x.java.PlcDriverManager - Registering available
drivers...
[main] INFO org.apache.plc4x.java.PlcDriverManager - Registering driver for
Protocol modbus (Modbus)
[main] INFO org.apache.plc4x.java.PlcDriverManager - Registering driver for
Protocol s7 (Siemens S7 (Basic))
[main] INFO
org.apache.plc4x.java.scraper.config.triggeredscraper.ScraperConfigurationTriggeredImpl
- Assuming job as triggered job because triggerConfig has been set
[main] INFO
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperImpl -
Starting jobs...
[main] INFO
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperImpl - Task
TriggeredScraperTask{driverManager=org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager@35a50a4c,
jobName='ScheduleJob', connectionAlias='DeviceSource',
connectionString='s7://
192.168.0.15?remote-rack=0&remote-slot=1&controller-type=S7_1200',
requestTimeoutMs=1000,
executorService=java.util.concurrent.ThreadPoolExecutor@1f021e6c[Running,
pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0],
resultHandler=eu.cloudplug.cpe.plc4x.PLC4XScrapper$$Lambda$59/0x0000000800bc8840@103f852,
triggerHandler=org.apache.plc4x.java.scraper.triggeredscraper.triggerhandler.TriggerHandlerImpl@587c290d}
added to scheduling
[triggeredscraper-scheduling-thread-1] WARN
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperTask -
Exception during scraping of Job ScheduleJob, Connection-Alias
DeviceSource: Error-message: null - for stack-trace change logging to DEBUG
[triggeredscraper-executor-thread-2] INFO
org.apache.plc4x.java.transport.tcp.TcpChannelFactory - Configuring
Bootstrap with Configuration{local-rack=1, local-slot=1, remote-rack=0,
remot-slot=1, pduSize=1024, maxAmqCaller=8, maxAmqCallee=8,
controllerType='S7_1200'}
[triggeredscraper-executor-thread-1] INFO
org.apache.plc4x.java.transport.tcp.TcpChannelFactory - Configuring
Bootstrap with Configuration{local-rack=1, local-slot=1, remote-rack=0,
remot-slot=1, pduSize=1024, maxAmqCaller=8, maxAmqCallee=8,
controllerType='S7_1200'}
[triggeredscraper-scheduling-thread-1] WARN
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperTask -
Exception during scraping of Job ScheduleJob, Connection-Alias
DeviceSource: Error-message: null - for stack-trace change logging to DEBUG
[triggeredscraper-executor-thread-3] INFO
org.apache.plc4x.java.transport.tcp.TcpChannelFactory - Configuring
Bootstrap with Configuration{local-rack=1, local-slot=1, remote-rack=0,
remot-slot=1, pduSize=1024, maxAmqCaller=8, maxAmqCallee=8,
controllerType='S7_1200'}
[nioEventLoopGroup-2-1] WARN io.netty.channel.DefaultChannelPipeline - An
exceptionCaught() event was fired, and it reached at the tail of the
pipeline. It usually means the last handler in the pipeline did not handle
the exception.
[nioEventLoopGroup-4-1] WARN io.netty.channel.DefaultChannelPipeline - An
exceptionCaught() event was fired, and it reached at the tail of the
pipeline. It usually means the last handler in the pipeline did not handle
the exception.
java.net.SocketException: Connection reset
at
java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:345)
at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:376)
at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133)
at
io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:830)
java.net.SocketException: Connection reset
at
java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:345)
at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:376)
at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133)
at
io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:830)
[triggeredscraper-executor-thread-1] WARN
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperImpl -
Unable to instantiate connection to s7://
192.168.0.15?remote-rack=0&remote-slot=1&controller-type=S7_1200
org.apache.plc4x.java.api.exceptions.PlcConnectionException:
org.apache.plc4x.java.api.exceptions.PlcConnectionException:
java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:117)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:100)
at
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperImpl.lambda$getPlcConnection$2(TriggeredScraperImpl.java:302)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1771)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:830)
Caused by: org.apache.plc4x.java.api.exceptions.PlcConnectionException:
java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.connect(DefaultNettyPlcConnection.java:110)
at
org.apache.plc4x.java.PlcDriverManager.getConnection(PlcDriverManager.java:74)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.access$201(PooledPlcDriverManager.java:37)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager$1.create(PooledPlcDriverManager.java:89)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager$1.create(PooledPlcDriverManager.java:82)
at
org.apache.commons.pool2.BaseKeyedPooledObjectFactory.makeObject(BaseKeyedPooledObjectFactory.java:62)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.create(GenericKeyedObjectPool.java:1051)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:347)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:270)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:115)
... 6 more
Caused by: java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
at
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2070)
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.connect(DefaultNettyPlcConnection.java:101)
... 15 more
Caused by: org.apache.plc4x.java.api.exceptions.PlcIoException: Connection
terminated by remote
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.lambda$connect$0(DefaultNettyPlcConnection.java:92)
at
io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:577)
at
io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:551)
at
io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:490)
at
io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:615)
at
io.netty.util.concurrent.DefaultPromise.setSuccess0(DefaultPromise.java:604)
at
io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromise.java:104)
at
io.netty.channel.DefaultChannelPromise.trySuccess(DefaultChannelPromise.java:84)
at
io.netty.channel.AbstractChannel$CloseFuture.setClosed(AbstractChannel.java:1158)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:760)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:736)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:607)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.closeOnRead(AbstractNioByteChannel.java:105)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.handleReadException(AbstractNioByteChannel.java:127)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:174)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
... 1 more
[triggeredscraper-executor-thread-3] WARN
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperImpl -
Unable to instantiate connection to s7://
192.168.0.15?remote-rack=0&remote-slot=1&controller-type=S7_1200
org.apache.plc4x.java.api.exceptions.PlcConnectionException:
org.apache.plc4x.java.api.exceptions.PlcConnectionException:
java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:117)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:100)
at
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperImpl.lambda$getPlcConnection$2(TriggeredScraperImpl.java:302)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1771)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:830)
Caused by: org.apache.plc4x.java.api.exceptions.PlcConnectionException:
java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.connect(DefaultNettyPlcConnection.java:110)
at
org.apache.plc4x.java.PlcDriverManager.getConnection(PlcDriverManager.java:74)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.access$201(PooledPlcDriverManager.java:37)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager$1.create(PooledPlcDriverManager.java:89)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager$1.create(PooledPlcDriverManager.java:82)
at
org.apache.commons.pool2.BaseKeyedPooledObjectFactory.makeObject(BaseKeyedPooledObjectFactory.java:62)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.create(GenericKeyedObjectPool.java:1051)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:347)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:270)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:115)
... 6 more
Caused by: java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
at
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2070)
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.connect(DefaultNettyPlcConnection.java:101)
... 15 more
Caused by: org.apache.plc4x.java.api.exceptions.PlcIoException: Connection
terminated by remote
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.lambda$connect$0(DefaultNettyPlcConnection.java:92)
at
io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:577)
at
io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:551)
at
io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:490)
at
io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:615)
at
io.netty.util.concurrent.DefaultPromise.setSuccess0(DefaultPromise.java:604)
at
io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromise.java:104)
at
io.netty.channel.DefaultChannelPromise.trySuccess(DefaultChannelPromise.java:84)
at
io.netty.channel.AbstractChannel$CloseFuture.setClosed(AbstractChannel.java:1158)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:760)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:736)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:607)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.closeOnRead(AbstractNioByteChannel.java:105)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.handleReadException(AbstractNioByteChannel.java:127)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:174)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
... 1 more
[triggeredscraper-scheduling-thread-4] WARN
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperTask -
Exception during scraping of Job ScheduleJob, Connection-Alias
DeviceSource: Error-message: {} - for stack-trace change logging to DEBUG
org.apache.plc4x.java.api.exceptions.PlcRuntimeException:
org.apache.plc4x.java.api.exceptions.PlcConnectionException:
org.apache.plc4x.java.api.exceptions.PlcConnectionException:
java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperImpl.lambda$getPlcConnection$2(TriggeredScraperImpl.java:305)
at
java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1771)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:830)
Caused by: org.apache.plc4x.java.api.exceptions.PlcConnectionException:
org.apache.plc4x.java.api.exceptions.PlcConnectionException:
java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:117)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:100)
at
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperImpl.lambda$getPlcConnection$2(TriggeredScraperImpl.java:302)
... 4 more
Caused by: org.apache.plc4x.java.api.exceptions.PlcConnectionException:
java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.connect(DefaultNettyPlcConnection.java:110)
at
org.apache.plc4x.java.PlcDriverManager.getConnection(PlcDriverManager.java:74)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.access$201(PooledPlcDriverManager.java:37)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager$1.create(PooledPlcDriverManager.java:89)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager$1.create(PooledPlcDriverManager.java:82)
at
org.apache.commons.pool2.BaseKeyedPooledObjectFactory.makeObject(BaseKeyedPooledObjectFactory.java:62)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.create(GenericKeyedObjectPool.java:1051)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:347)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:270)
at
org.apache.plc4x.java.utils.connectionpool.PooledPlcDriverManager.getConnection(PooledPlcDriverManager.java:115)
... 6 more
Caused by: java.util.concurrent.ExecutionException:
org.apache.plc4x.java.api.exceptions.PlcIoException: Connection terminated
by remote
at
java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
at
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2070)
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.connect(DefaultNettyPlcConnection.java:101)
... 15 more
Caused by: org.apache.plc4x.java.api.exceptions.PlcIoException: Connection
terminated by remote
at
org.apache.plc4x.java.spi.connection.DefaultNettyPlcConnection.lambda$connect$0(DefaultNettyPlcConnection.java:92)
at
io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:577)
at
io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:551)
at
io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:490)
at
io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:615)
at
io.netty.util.concurrent.DefaultPromise.setSuccess0(DefaultPromise.java:604)
at
io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromise.java:104)
at
io.netty.channel.DefaultChannelPromise.trySuccess(DefaultChannelPromise.java:84)
at
io.netty.channel.AbstractChannel$CloseFuture.setClosed(AbstractChannel.java:1158)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:760)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:736)
at
io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:607)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.closeOnRead(AbstractNioByteChannel.java:105)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.handleReadException(AbstractNioByteChannel.java:127)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:174)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
... 1 more
[triggeredscraper-executor-thread-4] INFO
org.apache.plc4x.java.transport.tcp.TcpChannelFactory - Configuring
Bootstrap with Configuration{local-rack=1, local-slot=1, remote-rack=0,
remot-slot=1, pduSize=1024, maxAmqCaller=8, maxAmqCallee=8,
controllerType='S7_1200'}
[triggeredscraper-scheduling-thread-3] WARN
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperTask -
Exception during scraping of Job ScheduleJob, Connection-Alias
DeviceSource: Error-message: null - for stack-trace change logging to DEBUG
On Fri, 29 May 2020 at 10:24, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hi Joris,
>
> could you please set the logging to DEBUG?
> Usually this is done by adding a logback.xml in your application and
> setting the log level there.
>
> This one even sets it to "TRACE" which should log even more than DEBUG.
>
> https://github.com/apache/plc4x/blob/develop/plc4j/examples/hello-world-plc4x/src/main/resources/logback.xml
>
> Chris
>
>
> Am 29.05.20, 10:21 schrieb "Joris Suppers" <j....@sotec.eu>:
>
> Hey,
>
> sure thing it is:
> [triggeredscraper-executor-thread-4] INFO
> org.apache.plc4x.java.transport.tcp.TcpChannelFactory - Configuring
> Bootstrap with Configuration{local-rack=1, local-slot=1, remote-rack=0,
> remot-slot=1, pduSize=1024, maxAmqCaller=8, maxAmqCallee=8,
> controllerType='S7_1200'}
> [triggeredscraper-scheduling-thread-3] WARN
> org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperTask -
> Exception during scraping of Job ScheduleJob, Connection-Alias
> DeviceSource: Error-message: null - for stack-trace change logging to
> DEBUG
>
> this is using version 0.7.0
>
> Cheers
>
> On Fri, 29 May 2020 at 10:16, Christofer Dutz <
> christofer.dutz@c-ware.de>
> wrote:
>
> > Hi Joris,
> >
> > unfortunately images or binary attachments (I think attachments in
> > general) are removed on this list.
> > So we can’t see your image.
> >
> > Rgarding the versions:
> > I would suggest to use 0.7.0 or 0.8.0-SNAPSHOT as 0.7.0-SNAPSHOT
> became
> > the 0.7.0 release and development is proceeding on 0.8.0-SNAPSHOT.
> >
> > If you could post the error in a textual form, perhaps we can help
> you
> > better.
> >
> > Chris
> >
> >
> >
> > Von: Joris Suppers <j....@sotec.eu>
> > Antworten an: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
> > Datum: Freitag, 29. Mai 2020 um 10:11
> > An: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
> > Cc: CloudPlug Development <cl...@sotec.eu>
> > Betreff: S7 DATA_BLOCKS error
> >
> > Hey Everyone,
> >
> > We are currently testing the Siemens S7 connector (S7_1200) using the
> > scrapper, and have come into an issue.
> >
> > When testing the values as shown in the "Getting Started" page (
> > https://plc4x.apache.org/users/plc4j/gettingstarted.html) we can
> > successfully read the following values:
> > builder.addItem("value-1", "%Q0.4:BOOL");
> > builder.addItem("value-2", "%Q0:BYTE");
> > builder.addItem("value-3", "%I0.2:BOOL");
> >
> > However when testing:
> > builder.addItem("value-4", "%DB.DB1.4:INT");
> > There is a Connection-Alias error:[cid:ii_karwzil70]
> >
> > I have also tried the other syntax shown in "
> > https://plc4x.apache.org/users/protocols/s7.html" However, no luck.
> >
> > We are using a 0.7.0-SNAPSHOT version, I have also tested with 0.7.0.
> >
> > Is there something that still needs to be done? Any suggestions or
> > comments would be appreciated.
> >
> > Many thanks,
> > Joris
> >
> >
> >
> >
> > --
> > Joris Suppers | SOTEC | j.suppers@sotec.eu<ma...@sotec.eu>
> | T
> > +49 7033 5458 72
> >
> >
> > www.sotec.eu<http://www.sotec.eu/>
> >
> > SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG
> >
> > Calwer Straße 11, D-75395 Ostelsheim
> >
> > Sitz Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664,
> > Geschäftsführer: Florian Holz
> >
>
>
> --
> Joris Suppers | SOTEC | j.suppers@sotec.eu | T +49 7033 5458 72
>
> --
>
>
>
>
>
>
> www.sotec.eu <http://www.sotec.eu/>
>
> SOTEC Software Entwicklungs GmbH
> + Co Mikrocomputertechnik KG
>
> Calwer Straße 11, D-75395 Ostelsheim
>
> Sitz
> Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664,
> Geschäftsführer:
> Florian Holz
>
>
>
>
>
--
Joris Suppers | SOTEC | j.suppers@sotec.eu | T +49 7033 5458 72
--
www.sotec.eu <http://www.sotec.eu/>
SOTEC Software Entwicklungs GmbH
+ Co Mikrocomputertechnik KG
Calwer Straße 11, D-75395 Ostelsheim
Sitz
Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, Geschäftsführer:
Florian Holz
Re: S7 DATA_BLOCKS error
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Joris,
could you please set the logging to DEBUG?
Usually this is done by adding a logback.xml in your application and setting the log level there.
This one even sets it to "TRACE" which should log even more than DEBUG.
https://github.com/apache/plc4x/blob/develop/plc4j/examples/hello-world-plc4x/src/main/resources/logback.xml
Chris
Am 29.05.20, 10:21 schrieb "Joris Suppers" <j....@sotec.eu>:
Hey,
sure thing it is:
[triggeredscraper-executor-thread-4] INFO
org.apache.plc4x.java.transport.tcp.TcpChannelFactory - Configuring
Bootstrap with Configuration{local-rack=1, local-slot=1, remote-rack=0,
remot-slot=1, pduSize=1024, maxAmqCaller=8, maxAmqCallee=8,
controllerType='S7_1200'}
[triggeredscraper-scheduling-thread-3] WARN
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperTask -
Exception during scraping of Job ScheduleJob, Connection-Alias
DeviceSource: Error-message: null - for stack-trace change logging to DEBUG
this is using version 0.7.0
Cheers
On Fri, 29 May 2020 at 10:16, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hi Joris,
>
> unfortunately images or binary attachments (I think attachments in
> general) are removed on this list.
> So we can’t see your image.
>
> Rgarding the versions:
> I would suggest to use 0.7.0 or 0.8.0-SNAPSHOT as 0.7.0-SNAPSHOT became
> the 0.7.0 release and development is proceeding on 0.8.0-SNAPSHOT.
>
> If you could post the error in a textual form, perhaps we can help you
> better.
>
> Chris
>
>
>
> Von: Joris Suppers <j....@sotec.eu>
> Antworten an: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
> Datum: Freitag, 29. Mai 2020 um 10:11
> An: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
> Cc: CloudPlug Development <cl...@sotec.eu>
> Betreff: S7 DATA_BLOCKS error
>
> Hey Everyone,
>
> We are currently testing the Siemens S7 connector (S7_1200) using the
> scrapper, and have come into an issue.
>
> When testing the values as shown in the "Getting Started" page (
> https://plc4x.apache.org/users/plc4j/gettingstarted.html) we can
> successfully read the following values:
> builder.addItem("value-1", "%Q0.4:BOOL");
> builder.addItem("value-2", "%Q0:BYTE");
> builder.addItem("value-3", "%I0.2:BOOL");
>
> However when testing:
> builder.addItem("value-4", "%DB.DB1.4:INT");
> There is a Connection-Alias error:[cid:ii_karwzil70]
>
> I have also tried the other syntax shown in "
> https://plc4x.apache.org/users/protocols/s7.html" However, no luck.
>
> We are using a 0.7.0-SNAPSHOT version, I have also tested with 0.7.0.
>
> Is there something that still needs to be done? Any suggestions or
> comments would be appreciated.
>
> Many thanks,
> Joris
>
>
>
>
> --
> Joris Suppers | SOTEC | j.suppers@sotec.eu<ma...@sotec.eu> | T
> +49 7033 5458 72
>
>
> www.sotec.eu<http://www.sotec.eu/>
>
> SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG
>
> Calwer Straße 11, D-75395 Ostelsheim
>
> Sitz Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664,
> Geschäftsführer: Florian Holz
>
--
Joris Suppers | SOTEC | j.suppers@sotec.eu | T +49 7033 5458 72
--
www.sotec.eu <http://www.sotec.eu/>
SOTEC Software Entwicklungs GmbH
+ Co Mikrocomputertechnik KG
Calwer Straße 11, D-75395 Ostelsheim
Sitz
Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, Geschäftsführer:
Florian Holz
Re: S7 DATA_BLOCKS error
Posted by Joris Suppers <j....@sotec.eu>.
Hey,
sure thing it is:
[triggeredscraper-executor-thread-4] INFO
org.apache.plc4x.java.transport.tcp.TcpChannelFactory - Configuring
Bootstrap with Configuration{local-rack=1, local-slot=1, remote-rack=0,
remot-slot=1, pduSize=1024, maxAmqCaller=8, maxAmqCallee=8,
controllerType='S7_1200'}
[triggeredscraper-scheduling-thread-3] WARN
org.apache.plc4x.java.scraper.triggeredscraper.TriggeredScraperTask -
Exception during scraping of Job ScheduleJob, Connection-Alias
DeviceSource: Error-message: null - for stack-trace change logging to DEBUG
this is using version 0.7.0
Cheers
On Fri, 29 May 2020 at 10:16, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hi Joris,
>
> unfortunately images or binary attachments (I think attachments in
> general) are removed on this list.
> So we can’t see your image.
>
> Rgarding the versions:
> I would suggest to use 0.7.0 or 0.8.0-SNAPSHOT as 0.7.0-SNAPSHOT became
> the 0.7.0 release and development is proceeding on 0.8.0-SNAPSHOT.
>
> If you could post the error in a textual form, perhaps we can help you
> better.
>
> Chris
>
>
>
> Von: Joris Suppers <j....@sotec.eu>
> Antworten an: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
> Datum: Freitag, 29. Mai 2020 um 10:11
> An: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
> Cc: CloudPlug Development <cl...@sotec.eu>
> Betreff: S7 DATA_BLOCKS error
>
> Hey Everyone,
>
> We are currently testing the Siemens S7 connector (S7_1200) using the
> scrapper, and have come into an issue.
>
> When testing the values as shown in the "Getting Started" page (
> https://plc4x.apache.org/users/plc4j/gettingstarted.html) we can
> successfully read the following values:
> builder.addItem("value-1", "%Q0.4:BOOL");
> builder.addItem("value-2", "%Q0:BYTE");
> builder.addItem("value-3", "%I0.2:BOOL");
>
> However when testing:
> builder.addItem("value-4", "%DB.DB1.4:INT");
> There is a Connection-Alias error:[cid:ii_karwzil70]
>
> I have also tried the other syntax shown in "
> https://plc4x.apache.org/users/protocols/s7.html" However, no luck.
>
> We are using a 0.7.0-SNAPSHOT version, I have also tested with 0.7.0.
>
> Is there something that still needs to be done? Any suggestions or
> comments would be appreciated.
>
> Many thanks,
> Joris
>
>
>
>
> --
> Joris Suppers | SOTEC | j.suppers@sotec.eu<ma...@sotec.eu> | T
> +49 7033 5458 72
>
>
> www.sotec.eu<http://www.sotec.eu/>
>
> SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG
>
> Calwer Straße 11, D-75395 Ostelsheim
>
> Sitz Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664,
> Geschäftsführer: Florian Holz
>
--
Joris Suppers | SOTEC | j.suppers@sotec.eu | T +49 7033 5458 72
--
www.sotec.eu <http://www.sotec.eu/>
SOTEC Software Entwicklungs GmbH
+ Co Mikrocomputertechnik KG
Calwer Straße 11, D-75395 Ostelsheim
Sitz
Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, Geschäftsführer:
Florian Holz
Re: S7 DATA_BLOCKS error
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Joris,
unfortunately images or binary attachments (I think attachments in general) are removed on this list.
So we can’t see your image.
Rgarding the versions:
I would suggest to use 0.7.0 or 0.8.0-SNAPSHOT as 0.7.0-SNAPSHOT became the 0.7.0 release and development is proceeding on 0.8.0-SNAPSHOT.
If you could post the error in a textual form, perhaps we can help you better.
Chris
Von: Joris Suppers <j....@sotec.eu>
Antworten an: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
Datum: Freitag, 29. Mai 2020 um 10:11
An: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
Cc: CloudPlug Development <cl...@sotec.eu>
Betreff: S7 DATA_BLOCKS error
Hey Everyone,
We are currently testing the Siemens S7 connector (S7_1200) using the scrapper, and have come into an issue.
When testing the values as shown in the "Getting Started" page (https://plc4x.apache.org/users/plc4j/gettingstarted.html) we can successfully read the following values:
builder.addItem("value-1", "%Q0.4:BOOL");
builder.addItem("value-2", "%Q0:BYTE");
builder.addItem("value-3", "%I0.2:BOOL");
However when testing:
builder.addItem("value-4", "%DB.DB1.4:INT");
There is a Connection-Alias error:[cid:ii_karwzil70]
I have also tried the other syntax shown in "https://plc4x.apache.org/users/protocols/s7.html" However, no luck.
We are using a 0.7.0-SNAPSHOT version, I have also tested with 0.7.0.
Is there something that still needs to be done? Any suggestions or comments would be appreciated.
Many thanks,
Joris
--
Joris Suppers | SOTEC | j.suppers@sotec.eu<ma...@sotec.eu> | T +49 7033 5458 72
www.sotec.eu<http://www.sotec.eu/>
SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG
Calwer Straße 11, D-75395 Ostelsheim
Sitz Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, Geschäftsführer: Florian Holz
Re: S7 DATA_BLOCKS error
Posted by Joris Suppers <j....@sotec.eu>.
Thanks!
That works "%DB4.DB1.4:INT", we were trying the short syntax
"DB{Data-Block-Number}.{Start-Byte-Address}:{Data-Type-Code}[{Count}]"
which did not seem to work, but if I add a simple DB before
{Start-Byte-Address}
it works :).
Thanks for your speedy response.
Cheers
On Fri, 29 May 2020 at 10:38, Julian Feinauer <j....@pragmaticminds.de>
wrote:
> Hi,
>
>
>
> sorry for being late (ist still morning, right).
>
> But @Joris Suppers <j....@sotec.eu> you are missing the DB Number.
>
> And I think we handle that pretty poorly with our exception.
>
>
>
> It should be builder.addItem("value-4", "%DB{DB-Number}.DB1.4:INT");
>
>
>
> Cheers!
>
> Julian
>
>
>
>
>
> *Von: *Joris Suppers <j....@sotec.eu>
> *Antworten an: *"dev@plc4x.apache.org" <de...@plc4x.apache.org>
> *Datum: *Freitag, 29. Mai 2020 um 10:11
> *An: *"dev@plc4x.apache.org" <de...@plc4x.apache.org>
> *Cc: *CloudPlug Development <cl...@sotec.eu>
> *Betreff: *S7 DATA_BLOCKS error
>
>
>
> Hey Everyone,
>
>
>
> We are currently testing the Siemens S7 connector (S7_1200) using the
> scrapper, and have come into an issue.
>
>
>
> When testing the values as shown in the "Getting Started" page (
> https://plc4x.apache.org/users/plc4j/gettingstarted.html) we can
> successfully read the following values:
>
> builder.addItem("value-1", "%Q0.4:BOOL");
> builder.addItem("value-2", "%Q0:BYTE");
> builder.addItem("value-3", "%I0.2:BOOL");
>
>
>
> However when testing:
>
> builder.addItem("value-4", "%DB.DB1.4:INT");
>
> There is a Connection-Alias error:
>
>
>
> I have also tried the other syntax shown in "
> https://plc4x.apache.org/users/protocols/s7.html" However, no luck.
>
>
>
> We are using a 0.7.0-SNAPSHOT version, I have also tested with 0.7.0.
>
>
>
> Is there something that still needs to be done? Any suggestions or
> comments would be appreciated.
>
>
>
> Many thanks,
>
> Joris
>
>
>
>
>
>
>
>
>
> --
>
> *Joris Suppers | SOTEC | *j.suppers@sotec.eu* | *T +49 7033 5458 72
>
>
>
> *www.sotec.eu* <http://www.sotec.eu/>
>
> SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG
>
> Calwer Straße 11, D-75395 Ostelsheim
>
> Sitz Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664,
> Geschäftsführer: Florian Holz
>
--
Joris Suppers | SOTEC | j.suppers@sotec.eu | T +49 7033 5458 72
--
www.sotec.eu <http://www.sotec.eu/>
SOTEC Software Entwicklungs GmbH
+ Co Mikrocomputertechnik KG
Calwer Straße 11, D-75395 Ostelsheim
Sitz
Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, Geschäftsführer:
Florian Holz
Re: S7 DATA_BLOCKS error
Posted by Julian Feinauer <j....@pragmaticminds.de>.
Hi,
sorry for being late (ist still morning, right).
But @Joris Suppers<ma...@sotec.eu> you are missing the DB Number.
And I think we handle that pretty poorly with our exception.
It should be builder.addItem("value-4", "%DB{DB-Number}.DB1.4:INT");
Cheers!
Julian
Von: Joris Suppers <j....@sotec.eu>
Antworten an: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
Datum: Freitag, 29. Mai 2020 um 10:11
An: "dev@plc4x.apache.org" <de...@plc4x.apache.org>
Cc: CloudPlug Development <cl...@sotec.eu>
Betreff: S7 DATA_BLOCKS error
Hey Everyone,
We are currently testing the Siemens S7 connector (S7_1200) using the scrapper, and have come into an issue.
When testing the values as shown in the "Getting Started" page (https://plc4x.apache.org/users/plc4j/gettingstarted.html) we can successfully read the following values:
builder.addItem("value-1", "%Q0.4:BOOL");
builder.addItem("value-2", "%Q0:BYTE");
builder.addItem("value-3", "%I0.2:BOOL");
However when testing:
builder.addItem("value-4", "%DB.DB1.4:INT");
There is a Connection-Alias error:[cid:ii_karwzil70]
I have also tried the other syntax shown in "https://plc4x.apache.org/users/protocols/s7.html" However, no luck.
We are using a 0.7.0-SNAPSHOT version, I have also tested with 0.7.0.
Is there something that still needs to be done? Any suggestions or comments would be appreciated.
Many thanks,
Joris
--
Joris Suppers | SOTEC | j.suppers@sotec.eu<ma...@sotec.eu> | T +49 7033 5458 72
www.sotec.eu<http://www.sotec.eu/>
SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG
Calwer Straße 11, D-75395 Ostelsheim
Sitz Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, Geschäftsführer: Florian Holz