Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Ben Rose

Pages: 1 ... 3 4 5 6 7 ... 27
61
Looking through the code, I do see a delay being used in 'moveAllServos'- hard to say exactly how long the delay is(it looks like it's 0 if the servos don't change position but may be 10s or 100s of ms on large changes), but any blocking delay like that should be avoided to keep the main loop running frequently, especially variable delays. Let us know if removing that changes what you are seeing.

Thanks,
Ben

62
General Discussion / Re: volume not consistent when using tone()
« on: November 28, 2018, 11:20:25 AM »
Yep- this was an unusual one.

We are definitely interested in adding your games! I need to go post in one of the Tiny Arcade section topics where you have mentioned the updates.

63
TinyLily / Re: What are the two PWM pins on the Tinilily?
« on: November 28, 2018, 11:16:05 AM »
Sorry this sat so long! Yes, pin 3 is the only easily accessible PWM pin, MOSI/11 is one as well and seems to be labeled correctly in the image!

64
Glad to hear it fixes the HTTP issue as well! We are now updating the firmware here as part of the test procedure.

65
TinyDuino Processors & TinyShields / Re: Serial.read baud-rate issues...
« on: November 28, 2018, 11:00:19 AM »
Just saw this one- For future reference, this is effectively a hardware limitation for the processor. The 8MHz ATmega(any that I've used) have a significant error in the baud rate generation when trying to do 115200. Why does it work one way? The FTDI chipset is 'smarter' and allows for receiving the significant error, but does not apply it back to what it sends to the TinyDuino.

There's another thread referencing the Arduino WiFi firmware updater tool not working. Same issue. I was able to modify the tool to run at 250K baud- much faster, but a rate that the 8MHz processor can generate exactly, so it works fine.

Unfortunately a lot of our older example code used 115200 since it was output only and worked fine. I'm switching things to 9600 as they need updates(when I remember!).

66
We were able to determine a couple things through email about this issue:

1. The TSV converter had an error with 8 bit output! This should be corrected now along with handling GIFs better.
2. The 8 bit/no audio setting needs to be used with TinyDuino example code.

Hopefully anybody else using TinyDuino/TinyScreen can mention if this is working correctly or has issues, then we can update the older tutorials to point to the new one.

67
Hi Tom,

We're hearing about some issues with the firmware updater on TinyDuino. This is due to the 115200 baud rate chosen for the IDE tool. This rate is fairly inaccurate on 8MHz Arduino boards, and will often work for sending text(ASCII characters) but can result in errors when sending lots of binary data. I was able to modify the firmware updater tool and change the baud to 250000 which does not have the large error rate. You can add this version by creating a ‘tools’ folder inside your Arduino sketch folder(similar to the ‘libraries’ folder) and unzipping this file inside it:
 
https://cdn.shopify.com/s/files/1/1125/2198/files/WiFi101.zip?11858682129905299368
 
Then, in the ‘FirmwareUpdater.ino’ example, replace:
 
Serial.begin(115200);
 
With:
 
WiFi.setPins(8,2,A3,-1);
Serial.begin(250000);
 
Under ‘Tools’ in the IDE, you should see two different ‘WiFi101 Firmware Updater’ tools, the new one should be the second one, and you should be able to get a positive result when testing the connection. Let me know what you see.

Hopefully the update fixes your other problem- there are some bugfixes that could be relevant.

Thanks,
Ben

68
TinyDuino Processors & TinyShields / Re: GPS Tracker
« on: November 20, 2018, 02:45:48 PM »
Hi- sorry about the problem! Can you test with the latest GPS code example at: https://cdn.shopify.com/s/files/1/1125/2198/files/GPSLogger.zip?8357215698240317466 and let me know if it initializes properly?

Thanks,
Ben

69
General Discussion / Re: volume not consistent when using tone()
« on: November 20, 2018, 02:35:43 PM »
Sorry about the long delay! I did figure out what's going on though- the DAC is still running! So the digital pin driver is fighting the analog output and you get 'something' in between. You should be able to use:

DAC->CTRLA.bit.ENABLE = 0x00; // Disable DAC

To ensure the DAC is off. Alternatively, it looks like you can use the Arduino analogRead(A0) which will turn the DAC off as well. Let me know if you still have issues.

70
Tiny Arcade & Pocket Arcade / Re: Send voltage to expansion shield pin?
« on: November 20, 2018, 02:09:44 PM »
Hi- VCC is the best way to power external sensor boards. On TinyScreen+ it will output 3.3V when TinyScreen+ is switched on. You should be able to connect this to either the VIN or 3VO(bypassing the boards 3.3V regulator) on the Adafruit board, along with ground and necessary IO pins.

71
General Discussion / Re: volume not consistent when using tone()
« on: October 31, 2018, 11:21:23 AM »
Can you post a really basic test case that results in this behavior? I think I remember seeing this when using tone, but don't remember the cause so I'll have to reinvestigate.

Thanks,
Ben

72
General Discussion / Re: TincyCircuits used in Viacom #seeher campaign
« on: October 31, 2018, 11:18:49 AM »
Just saw this topic- somebody linked the video to us on some social media platform a little while ago and we were pretty surprised to see it! Very fun that they picked our board, we had no idea. Too bad they blocked our logo and my silkscreen work :) we like the campaign!

73
TinyDuino Processors & TinyShields / Re: TinyScreen+ vsync
« on: October 25, 2018, 06:03:50 PM »
Hi- great job finding that in the SSD1331 datasheet. I took a look into this in the past, unfortunately the signal isn't brought out in the flex tail so we're stuck with "send as fast as possible", which does seem to work acceptably- are you using DMA to transfer the data? We have a couple examples of this.

74
TinyDuino Processors & TinyShields / Re: TinyScreen+ Physical dimensions
« on: October 25, 2018, 04:30:58 PM »
Sorry this doesn't have a response, for future reference: https://www.buydisplay.com/download/manual/ER-OLED0.95-2C_Datasheet.pdf this has the dimensions of the glass and active area of the screen.

75
Sorry about the problem- it sounds like you might have a TinyScreen and TinyDuino but are looking at the TinyScreen+ instructions? Have you looked at the tutorial at https://tinycircuits.com/blogs/learn/124803655-tinyduino-setup-tutorial ? Have you tried another USB cable? The computer should recognize something is plugged in, even if it's just the USB TinyShield on its own.

Pages: 1 ... 3 4 5 6 7 ... 27
SMF spam blocked by CleanTalk