Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
blocks:app-note:nexmosphere [2021-04-21 09:46] mattias |
blocks:app-note:nexmosphere [2023-10-05 15:30] mattias [Use Nexmosphere sensors and actuators with Blocks] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======Use Nexmosphere | + | ======Use Nexmosphere |
- | This is an application note that describes how to get started using Nexmosphere sensors and actuators with experiences managed by Blocks. | + | |
+ | This is an application note that describes how to get started using Nexmosphere sensors and actuators with experiences managed by Blocks. | ||
+ | |||
+ | :!: The method in this application note is useful if connecting a Nexmosphere controller with a 3.5mm serial connector using a serial network server such as Moxa N-Port. From Blocks version 6.1 it is possible to connect a Nexmosphere with built in serial to usb contoller directly to Pixilab Players USB port. Please consult the manual for more details about serial devices in blocks. | ||
=====Hardware requirements====== | =====Hardware requirements====== | ||
Line 7: | Line 10: | ||
In the examples we use the following hardware: | In the examples we use the following hardware: | ||
- | Nexmosphere | + | * [[https:// |
- | + | | |
- | XN-180 Experience controller | + | |
- | + | | |
- | XT-EF650 Gesture sensor | + | |
- | + | | |
- | XR-DR1 RFID Pick up sensor | + | |
- | + | ||
- | XW-L9 X-WAVE animating led strip | + | |
- | + | ||
- | + | ||
- | Moxa | + | |
- | + | ||
- | [[https:// | + | |
- | + | ||
- | 3.5mm to dsub cable that connects the XN-180 to the Moxa Nport. | + | |
Line 130: | Line 123: | ||
- | =====Change settings on the controller or sensors===== | + | =====Change settings on the controller or a sensor===== |
Some sensors have settings that must be set from Blocks. There is no persistence in the Nexmosphere controller so typically all settings must be set after reboot of the controller. One way of doing this is to run a task that does just that every time the controllers connected property becomes true. | Some sensors have settings that must be set from Blocks. There is no persistence in the Nexmosphere controller so typically all settings must be set after reboot of the controller. One way of doing this is to run a task that does just that every time the controllers connected property becomes true. | ||
Line 143: | Line 136: | ||
+ | =====Program RFID tags to be used with Nexmosphere RFID sensors===== | ||
+ | |||
+ | Nexmoshpere uses MIFARE Classic tags and can provide software available for Windows computers that can be used to program tags. This software can be obtained from their support once you got the hardware. | ||
+ | |||
+ | It is also possible to program tags using a mobile phone. I use an Sony phone with Android OS and NFC enabled. | ||
+ | Using softare such as MIFARE Classic Tool as in my example it is possible to write any tag ID to your tags. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | A valid tag ID has to be between 1-255, 01-FF in hex. | ||
+ | In the screenshot below where i read a tag already programmed as tag ID 3, 03 in hex is repeated in all 16 bytes in sector 1 block 0. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | If I want to program a new tag with no 255 I would set the application to write tag mode with the following settings and press the write tag button while holding the tag to the mobiles NFC sensor: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | This should be the final result from reading the tag with ID 255. | ||
+ | {{: |