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
As it stands, in order to communicate with the SparkFun Simultaneous RFID Reader - M6E Nano, via the RX/TX pins (the only way to communicate with that board) you must use 5V logic. This is nice if you are using the standard Arduino board to do that, but a lot of other products (if not most) use 3V logic making communicating with the RFID board unnecessarily complex (having to use voltage shifters / resistors to lower the voltage etc, solutions that have been known to be problematic).
Given that the M6E uses 3V on the RX/TX pins by design, it would be nice if those pins where exposed directly to the outside world (via header pins). This would make it very easy for devices such as the Raspberry Pi (and many others) to easily and directly communicate with the RFID board using the RX/TX pins without needing anything in between.
Its important to keep in mind that the Mercury API (the code that is used to communicated with the M6E and used by the URA application) is supported in most operating system, also, keep in mind that the Mercury API is supported in Java, .NET Core, etc. This basically means that creating apps that run in Raspberry Pi boards that communicate with the M6E is very, very, easy. In other words, the Arduino board is not the only game in town when it comes to communicating with the M6E. As a matter of fact (this is my personal opinion) creating apps for the M6E in Linux / Raspberry Pi boards is much more attractive than the Arduino board with all its limitations (the Java / .NET Mercury API usable from Linux / Windows runs circles around the current Arduino library), just my thoughts.
Thanks.
The text was updated successfully, but these errors were encountered:
As it stands, in order to communicate with the SparkFun Simultaneous RFID Reader - M6E Nano, via the RX/TX pins (the only way to communicate with that board) you must use 5V logic. This is nice if you are using the standard Arduino board to do that, but a lot of other products (if not most) use 3V logic making communicating with the RFID board unnecessarily complex (having to use voltage shifters / resistors to lower the voltage etc, solutions that have been known to be problematic).
Given that the M6E uses 3V on the RX/TX pins by design, it would be nice if those pins where exposed directly to the outside world (via header pins). This would make it very easy for devices such as the Raspberry Pi (and many others) to easily and directly communicate with the RFID board using the RX/TX pins without needing anything in between.
Its important to keep in mind that the Mercury API (the code that is used to communicated with the M6E and used by the URA application) is supported in most operating system, also, keep in mind that the Mercury API is supported in Java, .NET Core, etc. This basically means that creating apps that run in Raspberry Pi boards that communicate with the M6E is very, very, easy. In other words, the Arduino board is not the only game in town when it comes to communicating with the M6E. As a matter of fact (this is my personal opinion) creating apps for the M6E in Linux / Raspberry Pi boards is much more attractive than the Arduino board with all its limitations (the Java / .NET Mercury API usable from Linux / Windows runs circles around the current Arduino library), just my thoughts.
Thanks.
The text was updated successfully, but these errors were encountered: