Recent Posts

Wirelings / Re: .42" OLED usage with Arduino UNO?
« Last post by lennevia on May 05, 2020, 02:33:44 PM »
Hey there Steve,

The random white bits mean that the screen is not correctly being initialized.

The Arduino UNO will supply 5V, when the 0.42" Wireling is meant to be used with 3.3V - so there is a possibility that the power difference could be causing issues.

There are a couple of solutions to output 3.3V from the Arduino UNO:

It is, however, possible that the 0.42" Screen could be damaged. If you have a Wireling Adapter Shield or other Wireling-specific hardware, I would advise you to test with this before moving forward so that you can make sure the screen is still functioning.

I hope that helps!

Thank you,

Wirelings / .42" OLED usage with Arduino UNO?
« Last post by steve_eo on May 04, 2020, 11:56:22 PM »
Hi there.
I have the 0.42" display and an UNO.
I have downloaded the examples and wired the display as:
J1.1 to GND on the Arduino board
J1.2 to 3.3 on the Arduino board
J1.3 to A5 on the Arduino board
J1.4 to A4 on the Arduino board
J1.5 to A0 on the Arduino board
BTW, to make these connections, I disconnected one end of the 5 pin Wireling cable and soldered on pins that fit correctly into the UNO sockets.
The result of running the example code from 0.42-Screen-Text-Example is a screen with a bunch of random white bits.
Perhaps I'm connecting something wrong?
Can anyone please comment if they see something I'm doing wrong.
Thank you!

TinyDuino / Re: I2C communication reliability
« Last post by lennevia on May 04, 2020, 12:50:00 PM »
Hello Luke,

Welcome to the forum! I'll try to answer your questions and provide information where I can!

In addition if the I2C did suddenly lose connection mid way through sending data what would the 328P processor do?  does it simply hang waiting for the ACK and the STOP command or does it just take whatever data it has received and assume the rest is value 0 and ends communication?

"Acknowledge bit is a ninth bit of every byte sent. The receiver always has to confirm successful receive with ACK by pulling SDA low or in case receiver cannot accept data it will leave SDA high (NACK), so master could stop transmitting and do another scenario if needed." This page some more information that picks apart the bits in each I2C signal.

Some things can definitely go wrong when using I2C, but these issues usually only occur when you are using a lot of different devices with different addresses - since I2C uses mainly two wires for communication, things could get a little hectic in a scenario with 20 I2C devices and trying to pull data from each device as quickly as possible.

That being said, while it is possible, it is unlikely you will have any issues. It sounds like you are using only one I2C device (the RTC). And while there is a small chance some signals could be lost - the RTC will continue to send and be read correctly for the time originally set. So while a signal could be lost, correct signals will continuously be sent - which should effectively correct any issues along the way.

All in all, I wouldn't worry too much! To put your mind at ease, I would recommend doing some tests with the hardware you have. You could set a time in respect to a trustworthy clock - like your phone - and then leave it over night or for a few days to see if there is any difference in the time.

I hope that helps!


General Discussion / Re: TinyZero Problems
« Last post by jgavlik on May 04, 2020, 12:01:37 PM »

Thanks for the USB related suggestion, but I've been "successfully" programming TinyScreen+ units on a Win 10 machine (circa 2019) for sometime now. 

Even though - schematically - the TinyZero is the same as the TinyScreen+ in terms of the processor, something else is going on and I don't think it's USB related.

I think the problem is on my end, but I can't be sure.

Again, any help is appreciated.

General Discussion / Re: TinyZero Problems
« Last post by WillemH on May 04, 2020, 06:27:43 AM »
Hello John,

after several successful uploads to a TinyDuino I experienced big problems with upload to a TinyZero.

Looking for a solution to a completely different problem, i.e. reading out a modern digital recorder, I found that the USB channels of the computer platform I worked with are relatively slow.

After using another computer platform with faster (more modern) USB channels I have got no problems anymore with upload to TinyZero.

Did you check if the USB channel you use for upload is fast enough?

General Discussion / TinyZero Problems
« Last post by jgavlik on May 03, 2020, 02:47:00 PM »
I purchased two (2) TinyZero Processors and neither of them work correctly. I've tried them both per below.

Most times the Bootloader won't allow me to upload the code even after following the directions on the NOTES for the TinyZero.

But once in a while the code gets uploaded.

However, even when the code loads, the COM port won't be active after the loading sequence (see attached).

I did have another TinyZero (3rd one) that did work at one point, but the fragile bootloader button broke (tore off)

To confirm things....I've reloaded the Arduino IDE, changed USB ports, changed USB cables but still no luck.

Am I missing an #include <TinyZero.h> if there is such thing??

Any help will be appreciated.


TinyDuino / I2C communication reliability
« Last post by luke1i1 on May 03, 2020, 12:38:19 PM »
Hi all

This is my first post so please be kind!  I'm completely new to programming but trying my best to learn :)

Apologies if this is in the wrong section, I'll move the post if an admin can advise.

I'm currently designing a watch using the TinyDuino LED Matrix and the 1339 RTC module connected via I2C.  In short I'm concerned with the reliability of I2C (purely due to seeing other posts on various forums claiming lost data packets etc.) which has set my paranoia going!

I am using the wire.h library, in combination with the DSRTCLib.h RTC library.  I have programmed my board and it works really well (much better then I expected in fact).  However it concerns me that if the I2C does lose communication or data packets somewhere down the line I'm not going to know.  I've read up on I2C and have a reasonable grasp of it's functioning but I'm by no means an expert in it's operation. 

I suppose what I'm looking for is some way of knowing that the I2C has successfully transmitted all data packets so the time displayed on the LED Matrix is accurate. 

In addition if the I2C did suddenly lose connection mid way through sending data what would the 328P processor do?  does it simply hang waiting for the ACK and the STOP command or does it just take whatever data it has received and assume the rest is value 0 and ends communication?

Sorry for the long post, I'm really close to finishing my project but I'm concerned that I'll never know if the time displayed on my watch is accurate - obviously a pretty important thing for a watch!

Many thanks

Wirelings / Re: Wireling Interrupt specifics
« Last post by lennevia on May 01, 2020, 11:47:32 AM »
Hello Mike,

What board are you looking at?

Is there something specific you are aiming to accomplish with interrupts?

Wirelings / Wireling Interrupt specifics
« Last post by Cyborg84 on April 30, 2020, 05:02:55 PM »
I noticed on the schematic that there are two options for an I2C interrupt from the wireling board to either IO2 or IO3, but I cant tell which resistor is which (R17 and R18) on the board.

Please clarify which one is present by default - (maybe provide an annotated picture of the board).

Also, it looks like all 4 of the interrupt signals from the connectors are connected to AD0 - AD3 by default, is that correct?
- Mike
Hello Réna,

Many thanks for pushing the code fix.
The updated BMP280 Arduino Library now gives stable results for both TinyZero and TinyDuino with comparable output for two different shields with BMP280.
So issue has been solved.

SMF spam blocked by CleanTalk