21
TinyDuino / Re: USB TinyShield and Bluetooth
« Last post by Chicadian on April 09, 2019, 06:24:22 PM »You're not alone. I'm having the same issue following the tutorial as suggested. Maybe there's a step missing that isn't listed?
Recent Posts
22
User Projects / Code Examples / Re: Viobyte (Pac-Man Clone)
« Last post by dulsi on April 06, 2019, 01:37:45 PM »Someone emailed me asking for the binary so I figured I'd post the latest here. It adds another level map. The map was created with tiled. There is a convert in the source repository to allow you to convert maps into header files that can be added to viobyte.
23
General Discussion / Re: Problem Initializing BMP280 Sensor after SD Card Insertion
« Last post by wendolw on March 29, 2019, 09:49:20 PM »I am publishing a solution to the above "pressure sensor initializing" problem that I initially posted here on 3-1-2019. I hope that this solution and the references/citations listed, will help others who wish to build the TinyCircuits Rocket Altimeter as a fully functioning unit using late model MacBook laptops running on macOS Sierra operating systems with versions 10.9, and up (my MacOS Sierra was version 10.12.6).
Rocket Altimeter Build Using MacOS Sierra Version 10.12.6 3-29-2019
BUILD SEQUENCE
• Initializing Stack Hierarchy (Bottom to Top)
1. Lithium Battery
2. TinyDuino Processor
3. TinyShield USB
4. TinyShield Barometric Pressure Sensor
5. TinyShield Micro SD
• Step One: Charge the Lithium Battery
1. Charge the Lithium Ion battery by connecting the TinyDuino Processor to the USB TinyShield and plug in the USB chord to your computer.
2. A yellow LED will turn on showing that the battery is charging.
a. When the LED turns off, the battery is fully charged.
• Step Two: Load the Drivers
1. Before starting, the proper drivers must be installed to detect the COM ports. These drivers must be installed before downloading any codes from the codebender plugin (https://codebender.cc/).
2. Go to http://www.ftdichip.com/Drivers/VCP.htm
a. The page contains VCP drivers currently available for FTDI devices.
b. Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC.
c. Application software can access the USB device in the same way as it would access a standard COM port.
3. Open VCP Drivers for Mac OS X 10.9 and above, for 64-bit functionality, listed as 2.4.2, click on icon, and follow installation instructions.
• Step Three: Disable the Apple USBFTDI Drivers
1. Go to Applications Folder/Utilities folder. Select Terminal.
o PROBLEM:
FTDI devices are not instantly usable in MacOS High Sierra. There may be trouble connecting FT231R chip devices to a 2018 MacBook Air with C-Ports. The devices appear in the USB device tree (System Information -> Hardware -> USB), but do not show up as a serial device using Arduino.
o SOLUTION:
2. Download the 2.4.2 drivers from FTDI's website http://www.ftdichip.com/Drivers/VCP.htm and install. The install will succeed, but due to Apple's built-in FTDI drivers, they will not work.
3. Reboot computer and enter recovery mode via powering down and, then holding down CMD + R on reboot.
4. In Recovery Mode, open terminal from utilities at the top of the screen and type the following command to temporarily disable System Integrity Protection:
csrutil disable
The computer will then prompt you to reboot to make the changes take effect.
5. On reboot, we now will disable the Apple FTDI drivers, which can be reversed later if desired.
6. Open Terminal and type the following code:
sudo touch /library/extensions
sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
Now you will have successfully disabled Apple's built-in FTDI drivers and replaced them with FTDI v2.4.
7. Restart your computer in recovery mode. Shutdown, hold Command + R and open terminal in the Utilities tab. Enter the following to “re-enable” Apple's System Integrity Protection.
csrutil enable
8. One final restart and then the USB serial devices should all be loading properly.
• Step Four: Download Code
1. Before starting, the proper drivers must be installed to detect the COM ports. These drivers must be installed before downloading any codes from the codebender plugin (https://codebender.cc/).
2. To reiterate, and as noted in the Tiny Circuits’ instruction published on their website, titled Rocket Altimeter (https://tinycircuits.com/blogs/learn/130916679-rocket-altimeter-logger), “once the drivers are successfully installed, the program below can be downloaded to your computer or directly uploaded to your TinyDuino processor.”
3. You now have to navigate to the main codebender sketch page to access their serial monitor (https://codebender.cc/sketch:145121#Altimeter_DataLogger.ino)
4. “The sensor used for the barometric pressure shield is the BMP280 from Bosch.
5. The first sample of code shows the data coming from the sensor in the COM port while the second code logs the data to the microSD card.
6. In order for the data to be logged, the SD card must be inserted before the TinyDuino is switched on.
7. When the device logs a data point, a green LED on the processor will flash on and off.
8. The code is setup to export the data points as a .csv file so it can be opened directly into Microsoft Excel.”
• References & Attributions:
1. https://superuser.com/questions/1135730/how-to-release-reset-serial-port-ftdi-devices-mac-osx
2. Garrett Johnson/Superuser Forum (excellent post on drivers & MacOS)
3. Alain O’Dea/Superuser Forum (helpful addendum to the G. Johnson post)
4. Tiny Circuits Staff [Ben Rose – timely response with excellent technical advice]
Rocket Altimeter Build Using MacOS Sierra Version 10.12.6 3-29-2019
BUILD SEQUENCE
• Initializing Stack Hierarchy (Bottom to Top)
1. Lithium Battery
2. TinyDuino Processor
3. TinyShield USB
4. TinyShield Barometric Pressure Sensor
5. TinyShield Micro SD
• Step One: Charge the Lithium Battery
1. Charge the Lithium Ion battery by connecting the TinyDuino Processor to the USB TinyShield and plug in the USB chord to your computer.
2. A yellow LED will turn on showing that the battery is charging.
a. When the LED turns off, the battery is fully charged.
• Step Two: Load the Drivers
1. Before starting, the proper drivers must be installed to detect the COM ports. These drivers must be installed before downloading any codes from the codebender plugin (https://codebender.cc/).
2. Go to http://www.ftdichip.com/Drivers/VCP.htm
a. The page contains VCP drivers currently available for FTDI devices.
b. Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC.
c. Application software can access the USB device in the same way as it would access a standard COM port.
3. Open VCP Drivers for Mac OS X 10.9 and above, for 64-bit functionality, listed as 2.4.2, click on icon, and follow installation instructions.
• Step Three: Disable the Apple USBFTDI Drivers
1. Go to Applications Folder/Utilities folder. Select Terminal.
o PROBLEM:
FTDI devices are not instantly usable in MacOS High Sierra. There may be trouble connecting FT231R chip devices to a 2018 MacBook Air with C-Ports. The devices appear in the USB device tree (System Information -> Hardware -> USB), but do not show up as a serial device using Arduino.
o SOLUTION:
2. Download the 2.4.2 drivers from FTDI's website http://www.ftdichip.com/Drivers/VCP.htm and install. The install will succeed, but due to Apple's built-in FTDI drivers, they will not work.
3. Reboot computer and enter recovery mode via powering down and, then holding down CMD + R on reboot.
4. In Recovery Mode, open terminal from utilities at the top of the screen and type the following command to temporarily disable System Integrity Protection:
csrutil disable
The computer will then prompt you to reboot to make the changes take effect.
5. On reboot, we now will disable the Apple FTDI drivers, which can be reversed later if desired.
6. Open Terminal and type the following code:
sudo touch /library/extensions
sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
Now you will have successfully disabled Apple's built-in FTDI drivers and replaced them with FTDI v2.4.
7. Restart your computer in recovery mode. Shutdown, hold Command + R and open terminal in the Utilities tab. Enter the following to “re-enable” Apple's System Integrity Protection.
csrutil enable
8. One final restart and then the USB serial devices should all be loading properly.
• Step Four: Download Code
1. Before starting, the proper drivers must be installed to detect the COM ports. These drivers must be installed before downloading any codes from the codebender plugin (https://codebender.cc/).
2. To reiterate, and as noted in the Tiny Circuits’ instruction published on their website, titled Rocket Altimeter (https://tinycircuits.com/blogs/learn/130916679-rocket-altimeter-logger), “once the drivers are successfully installed, the program below can be downloaded to your computer or directly uploaded to your TinyDuino processor.”
3. You now have to navigate to the main codebender sketch page to access their serial monitor (https://codebender.cc/sketch:145121#Altimeter_DataLogger.ino)
4. “The sensor used for the barometric pressure shield is the BMP280 from Bosch.
5. The first sample of code shows the data coming from the sensor in the COM port while the second code logs the data to the microSD card.
6. In order for the data to be logged, the SD card must be inserted before the TinyDuino is switched on.
7. When the device logs a data point, a green LED on the processor will flash on and off.
8. The code is setup to export the data points as a .csv file so it can be opened directly into Microsoft Excel.”
• References & Attributions:
1. https://superuser.com/questions/1135730/how-to-release-reset-serial-port-ftdi-devices-mac-osx
2. Garrett Johnson/Superuser Forum (excellent post on drivers & MacOS)
3. Alain O’Dea/Superuser Forum (helpful addendum to the G. Johnson post)
4. Tiny Circuits Staff [Ben Rose – timely response with excellent technical advice]
24
Tiny Arcade / Mini joystick replacement on neo Geo mini clone?
« Last post by vetteguy112233 on March 24, 2019, 01:35:36 AM »I have a Neo Geo mini clone (rs-07) that I would like to try and replace the joystick on but can't seem to find anything at all.
I wondered if you guys might have any suggestions on a good 8 way replacement?
I wondered if you guys might have any suggestions on a good 8 way replacement?
25
TinyDuino / Re: USB TinyShield and Bluetooth
« Last post by digital1440 on March 22, 2019, 07:48:10 PM »I am having the same problem from the same tutorial
https://tinycircuits.com/blogs/learn/bluetooth-low-energy-tinyshield-st-tutorial
The serial monitor is spitting out garbage content.
I have baud rates that match. Tried 9600 and 115200. Same problem.
Tried the return control and that did not seem to fix it either.
Any other thoughts?
https://tinycircuits.com/blogs/learn/bluetooth-low-energy-tinyshield-st-tutorial
The serial monitor is spitting out garbage content.
I have baud rates that match. Tried 9600 and 115200. Same problem.
Tried the return control and that did not seem to fix it either.
Any other thoughts?
26
TinyDuino / Re: Initial serial output is lost on new TinyZero
« Last post by Ben Rose on March 18, 2019, 11:58:16 AM »Hi, great to hear you like TinyZero as an upgrade to TinyDuino! One of the major differences in use is the SerialUSB virtual serial port and the fact that opening the serial monitor does not reset the processor like with TinyDuino. However, now you can test if the virtual serial port is open or not, so you can put something like this before any SerialUSB output in your setup:
while (!SerialUSB && millis() < 5000); //On TinyScreen+/TinyZero, this will wait until the Serial Monitor is opened or until 5 seconds has passed
Then you will get all output messages after that. We've updated some of our examples, but it's still a work in progress.
Thanks,
Ben
while (!SerialUSB && millis() < 5000); //On TinyScreen+/TinyZero, this will wait until the Serial Monitor is opened or until 5 seconds has passed
Then you will get all output messages after that. We've updated some of our examples, but it's still a work in progress.
Thanks,
Ben
27
Tiny Arcade / Re: CHARGING/AUDIO ISSUES?
« Last post by Ben Rose on March 18, 2019, 11:48:53 AM »Thanks for supporting us in the Kickstarter! Sorry about the current issues. My simple guess would be a loose battery connector and maybe a damaged flex cable to the speaker- are you able to pop it open and take a look? Sending it here is definitely an option as well, let me know.
28
TinyLily / Re: USB board getting super hot
« Last post by Ben Rose on March 18, 2019, 11:32:46 AM »I'm not sure what happened, but it sounds like you should set that particular board aside! The board is damaged if it's hot enough to smell bad. Was it maybe plugged into the processor board the wrong way? Either way, please contact info@tinycircuits.com so we can try to figure out what happened and replace your board.
Thanks,
Ben
Thanks,
Ben
29
User Projects / Code Examples / Re: Tinyduino load cell to display on tinyduino matrix led
« Last post by Ben Rose on March 18, 2019, 11:27:09 AM »Hi- we've used the HX711 with a TinyDuino before. SparkFun has a great basic breakout with a very good tutorial: https://www.sparkfun.com/products/13879 Their code can be used with any Arduino including TinyDuino, and you should just need to pick two open IO pins(maybe A0 and A1, since the Matrix board uses 2 through 9). These could be connected through one of our proto boards.
Thanks,
Ben
Thanks,
Ben
30
TinyDuino / Initial serial output is lost on new TinyZero
« Last post by PSch on March 14, 2019, 01:33:07 PM »Hi,
I just started to play with my new Tinyzero (with the accelerometer) board (impressive to get 3 or even 4 (with the RTC) boards in one now!!!).
After updating the Board manager (to get the tinyzero board option) I got my code to work. However, I noticed that with my code (written for the old t board system) as well as with the linked example code from Github (https://github.com/TinyCircuits/TinyCircuits-TinyZero-ASM2021/tree/master/examples/TinyZero_BMA250), I do never get the initial serial output from the setup section (i.e. all the initialisation messages e.g. "Initializing BMA..." in the example code). (I changed the Serial.print to SerialUSB.print, but still no success...).
The output from the main section of the code is then displayed OK.
Cheers!
PS: Could you also add an example on how to use the RTC on the new Tinyzero board? Does this work with the same libraries as for the previous RTC shield?
I just started to play with my new Tinyzero (with the accelerometer) board (impressive to get 3 or even 4 (with the RTC) boards in one now!!!).
After updating the Board manager (to get the tinyzero board option) I got my code to work. However, I noticed that with my code (written for the old t board system) as well as with the linked example code from Github (https://github.com/TinyCircuits/TinyCircuits-TinyZero-ASM2021/tree/master/examples/TinyZero_BMA250), I do never get the initial serial output from the setup section (i.e. all the initialisation messages e.g. "Initializing BMA..." in the example code). (I changed the Serial.print to SerialUSB.print, but still no success...).
The output from the main section of the code is then displayed OK.
Cheers!
PS: Could you also add an example on how to use the RTC on the new Tinyzero board? Does this work with the same libraries as for the previous RTC shield?