-
Notifications
You must be signed in to change notification settings - Fork 413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated DataIo Template (And working on the Siemens S7 L-types as well as Temporal types) #1376
Conversation
feat: Added support for 'BCD' formatted unsigned numbers in read- and write-buffer.
…n the new Profinet driver Also tried getting the old driver working with my Adam devices.
…working for S7-1500
… match the previous refactoring of the complex-types and enums.
… data-types working and all but the last two L-types for S7-1500
...n/language-java/src/main/java/org/apache/plc4x/language/java/JavaLanguageTemplateHelper.java
Outdated
Show resolved
Hide resolved
...n/language-java/src/main/java/org/apache/plc4x/language/java/JavaLanguageTemplateHelper.java
Outdated
Show resolved
Hide resolved
… the "all-types" test.
...ata/src/main/java/org/apache/plc4x/java/firmata/readwrite/protocol/FirmataProtocolLogic.java
Show resolved
Hide resolved
@@ -71,12 +71,22 @@ public void onConnect(ConversationContext<FirmataMessage> context) { | |||
LOGGER.debug("Sending Firmata Reset Command"); | |||
FirmataMessageCommand resetCommandMessage = new FirmataMessageCommand(new FirmataCommandSystemReset()); | |||
context.sendRequest(resetCommandMessage) | |||
.onTimeout(e -> { | |||
LOGGER.info("Timeout during Connection establishment, closing channel..."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the closing implicit or is there missing a close call here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Öhm ... from where I copied it from, it was commented out ;-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe @splatch added that? :D. Anyway maybe it is better to name it channel will be closed
as there is no immediate close call there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The onTimeout
is not propagated well across stack, from what I remember in the past onTimeout
had to specified at first, otherwise it was ignored/swallowed by lower part of engine. Not sure if that's true nowadays.
only combines those 2 and makes the code a bit more readable
Ok ... pulled in all changes from develop ... time to merge |
Please review especially the changes to generated DataIo types ... I know that at least in the Can driver I could see that now the encoding seems to be passed to the parser (which previously was not)
fixes #1379