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 2 3 ... 24
1
Thumby / Re: Invader Test
« on: October 21, 2021, 01:27:42 PM »
Best picture my phone could manage, which is probably the only way to get a good sense of how it looks!

2
Thumby / Re: Font size
« on: October 21, 2021, 01:11:32 PM »
@acedent- I thought that would be a quick answer! I've been playing around with a bunch of stuff in MicroPython for the last day or two, and I think the answer is that blits with the built in FrameBuffer object are just a bit slow. It's extremely general purpose and can handle tons of use cases outside of our simple 1bpp need. The arduboy2 font section looks like a very reasonable C/C++ implementation for 1bpp, I've written(adapted?) similar stuff for TinyScreen etc. After a while, I was able to do something similar in a MicroPython Viper code block, and it actually runs faster than the built in stuff for this very specific need.. I'll see if I can get something far enough along for other people to take a look at.

3
Thumby / Re: Invader Test
« on: October 18, 2021, 12:53:58 PM »
Very cool to see that you're able to work on this with the emulator!  I tested it on hardware quickly and it seems to work as intended, keep us updated if you do any more before you have hardware!

4
Thumby / Re: Font size
« on: October 15, 2021, 07:16:43 PM »
Hi- the answer for 'eventually' is definitely. We'd like 5x7 default, with maybe some smaller options. Right now we're testing out implementation in pure MicroPython, but it's pretty slow and we'll probably need to implement it within the firmware, so that will delay initial availability of it for testing etc- if anyone has input on that, let us know!

Thanks,
ben

5
Thumby / Re: Thumby / RPi RP2040 specs
« on: October 07, 2021, 12:58:37 PM »
Hi Kieron,

With how we plan to ship Thumby, the MicroPython interpreter will eat plenty of RAM as well as possibly some minimal assets leftover in memory from the main menu, however the menu essentially runs and then completely exits to the game(power off/soft reset to get back to the menu, for now).  I don't currently have a number for what's used- I've read things like 16-32KB for the interpreter. Let me know if you need a better answer.

I'll admit that during development of our little game examples, we haven't worried about memory, it's a lot more than we're used to!

Thanks,
Ben

6
Thumby / Re: 'Mazogs' game scaled for Thumby Screen
« on: October 04, 2021, 07:08:17 PM »
Very cool! If you run it at 72x40 on your Arduboy, it will be pretty close to what you'd see on a Thumby, except about 25% larger pixels still! Keep us updated- not sure if the scaling is a mockup or functional, maybe we could test the code here?

Thanks,
Ben

7
Thumby / Re: Thumby / RPi RP2040 specs
« on: October 04, 2021, 06:58:51 PM »
Hi- the 2MB flash is a QSPI flash chip, the same one as used on the Raspberry Pi Pico. By default we plan to have the standard Pi Pico MicroPython interpreter loaded, which I believe is about half a MB, leaving about 1-1.5MB available.

There's 264KB RAM, no crpyto acceleration hardware that I'm aware of. Full specs at:

https://datasheets.raspberrypi.org/rp2040/rp2040-datasheet.pdf

Thanks for the interest!
Ben

8
Thumby / Re: Thumby Display Controller, Arduino Examples
« on: October 04, 2021, 06:50:55 PM »
Meant to respond last week, sorry- yep, lib/thumby.py will get you most of what you need until we have things documented. Thumby works fine in the Arduino IDE equivalent to the Raspberry Pi Pico, so it should be pretty easy to adapt the Arduboy library functionality, aside from the tough part of adapting games to the lower resolution.

Thanks,
Ben

9
Wirelings / Re: imu 9 dof wireling sampling rate
« on: January 20, 2021, 03:13:58 PM »
Hi Phil, thanks for using our products. Right, RTIMU is pretty old, but works pretty well. I haven't found anything more appropriate.

The software can get a lot more complex when reading multiple IMUs at once and recording, so there are a lot of potential causes. Have you timed any particular sections of code to determine what's slow? It could be some 'simple' stuff like I2C clock, non-optimized SD card writes, etc.

I believe the Wireling library has a delay in it that is not totally necessary, and could cause a significant slowdown in this type of application.

With the amount of math RTIMU does, I believe it can run the algorithm at around 250Hz with the default settings on TinyZero. So I think 50Hz or better is achievable for four IMUs as long as the SD writing is optimized. This assumes that the fusion algorithm needs to run on the microcontroller.

Thanks,
Ben

10
General Discussion / Re: ZOE GPS proto board / ZOE setup with examples
« on: December 18, 2020, 06:04:46 PM »
Thanks for the feedback, really appreciate it. Based on this and some review here, I think we will try to make this a 20x20mm TinyShield compatible with all processor boards, and use the ZOE-M8Q with UART as well as I2C if I can route it. The origins of the TinyScreen+ format board were a pretty specific use case. I'll update here, we'll build a few extra prototypes.

11
General Discussion / Re: ZOE GPS proto board / ZOE setup with examples
« on: December 10, 2020, 05:56:11 PM »
Hi Willem,

I've just had time to fully read the post. This is great work and thanks for posting it. I've only skimmed the code, but it looks very helpful- I seem to recall finding very little Arduino example code to interface with the uBlox module, although maybe I just missed it. Like you say, the documentation is all 'there', but it's not easy to get started creating the commands. The method of listening to the u-center commands is a good workaround.

Somewhat unfortunately we decided to do a quick test with the ZOE-M8Q, which is only a minor hardware difference, before producing hardware. I'll update here with progress on that.

Thanks,
Ben

12
General Discussion / Re: HW UART for GPS logging with TinyZero
« on: October 02, 2020, 11:56:25 AM »
Hi Willem,

Great, glad the hardware serial is working.

Regarding the USB TinyShield, it doesn't work directly in that application because the TX/RX are the same as the GPS and not inverted as when compared to the processor board. Wiring it in for that application is probably too much effort. However software on the TinyZero can easily implement a low throughput 'adapter' from hardware to virtual serial in the main loop- look up the "SerialPassthrough" example to get an idea of how to do so.

Thanks,
Ben

13
General Discussion / Re: GPS TinyShield does not provide actual altitude
« on: October 01, 2020, 04:35:27 PM »
Willem,

Got it. I don't think we will have a backup battery on the PCB, but otherwise the TinyScreen+ can act as a serial relay and should(but I have never tried/tested) work with the u-center software, and we have used the ubx setup strings with success as well, so I think there are workarounds for setting up the GPS at startup. Glad to hear the size is suitable. If you'd like to test one of the new boards, can you contact me through email on the forum or just send a message on our contact form? Thanks.

John,

Glad to hear your interest. Along with a board for Willem I will see if we have parts to build up another prototype.

14
General Discussion / Re: GPS TinyShield does not provide actual altitude
« on: September 24, 2020, 06:37:02 PM »
Sorry about the lack of response here. I think you did some good research on the JF2, and it's an older chipset with default firmware aimed at primarily 2D navigation applications. Unfortunately we're not a big volume customer with access to the alternate firmware, as far as I'm aware. However more fortunately, we have a new TinyScreen+ board that we've been working on with a ZOE-M8B module, LSM9DS1, BME280, and microSD slot. Overall size is approximately 26x25x6.5mm, with ~3mm of microSD sticking out on one side. Is this small enough for the rockets you want to test on?

Thanks,
Ben

15
General Discussion / Re: HW UART for GPS logging with TinyZero
« on: September 24, 2020, 06:21:34 PM »
Hi Willem- Sorry, there's probably a lack of documentation on this for TinyZero. Hardware serial on pins 0/1 on our boards should be 'Serial', we use 'SerialUSB' for the virtual serial over USB. I think some Arduino Zero derivatives use 'Serial' for the virtual and 'Serial1' as the primary hardware port, so it gets confusing. Let me know if this is working properly. RX on IO0, TX on IO1 is correct from the processor point of view.

Sorry about the poor response on your other post, I think Laveréna was waiting on some input from me and it got lost in my inbox.

Thanks for your patience,
Ben

Pages: 1 2 3 ... 24
SMF spam blocked by CleanTalk