You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/documentation/providers/_index.md
+5-23Lines changed: 5 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,19 +4,11 @@ weight: 90
4
4
tags: ["GpioD", "LinuxFS", "PiGpio"]
5
5
---
6
6
7
-
Providers are extensible service modules responsible for the concrete implementation of a specific I/O type.
8
-
The providers also allow to separate the internal logic of the Pi4J core from the concrete implementation of the board
9
-
on which they are used.
7
+
Providers are extensible service modules responsible for the concrete implementation of a specific I/O type. The providers also allow separating the internal logic of the Pi4J core from the concrete implementation of the board on which they are used.
10
8
11
-
Pi4J 2.0 - 2.4: Multiple providers for the same I/O type can be loaded into a Pi4J context concurrently. For example a
12
-
"RaspberryPi-DigitalInputProvider" and "GertBoard-DigitalInputProvider" could both be loaded and both providing digital
13
-
inputs at the same time.
9
+
As of Pi4J 2.5 multiple providers for the same I/O type is no longer supported. During the Context initialization it will ensure only a single provider for an I/O type is loaded. In addition, the Mock Providers are not loaded unless expressly requested when creating the Context. [See Create Context](../create-context/)
14
10
15
-
As of Pi4J 2.5 multiple providers for the same I/O type is no longer supported. During the Context initialization it will
16
-
ensure only a single provider for an I/O type is loaded. In addition the Mock Providers are not loaded unless
17
-
expressly requested when creating the Context. [See Create Context](../create-context/)
18
-
19
-
Current supported providers:
11
+
## Available Providers
20
12
21
13
*[FFM](/documentation/providers/ffm/)
22
14
* Was introduced in Pi4J 4.0.0
@@ -51,19 +43,9 @@ Current supported providers:
51
43
* Needs to run as `sudo`
52
44
* 03/22/2024 Does not support Raspberry Pi 5
53
45
54
-
Possible future providers:
55
-
* Pi5 SPI, under construction.
56
-
* Pi5 Serial. At present the intent is no Pi4j Serial provider on Pi5. As an alternative see [jSerialComm](http://fazecast.github.io/jSerialComm/).
57
-
* RemoteProvider to control the I/O from a remote device e.g. through websockets
58
-
59
-
Pi4J 2.5 Provider not found
60
-
* Pi4J 2.5 ensuring a single provider for an I/O type is loaded may result in the provider your code references not being
61
-
found because it was replaced by a higher priority provider.
62
-
If you encounter this case, you can remove the unwanted provider plugin from your pom.xml file dependencies. Then after a clean
63
-
and rebuild of your program the unwanted provider will no longer be loaded.
64
-
46
+
## Check Loaded Providers
65
47
66
-
* PrettyPrint loaded providers. After creating the Context the following code will print the currently loaded provider for each I/O type.
48
+
After creating the `Context` the following code will print the currently loaded provider for each I/O type.
0 commit comments