December 3, 2015 - 3:53pm, 2883 views
Are there any limitations on detecting a change of one of the GPIO ports when using the InPortListener? E.g. when the Java application is very busy or the pulse is very short?
What I mean to ask:
When using InPortListener to receive notifications on a change of on of the GPIO pins, is the delivery of such notifications guaranteed or are there situations where a short pulse on the GPIO pin is missed due to timing?
Generally Java is not the real time system so there may be some delays that may depend on system load and application logic.
But the notifications should be delivered if only detected by the underlying hardware and system.
Please pay attention that the processing code for the port value change leaves the listener context as soon as possible (by running a new thread for example). While the callback method does not return it cannot be called again if changes occur.
Still are there hardware limitations?
Nothing has changed here. Notifications for GPIO stare changes may depend on system load but should be delivered. For ******** pulses only the pulse *****er should be used and it can ***** up to 1000 pulses per second. The rest of GPIO's should be used for state changes.
© 2013-2023 Thales DIS AIS Deutschland GmbH - a Telit Cinterion Company