Creating RIC files
Creating RIC files
*I didnt know where to post such a topic
**I know the name of the program, i downloaded it.
Hello.
I need help in creating RIC files. [Help in the program]
Thanks.
**I know the name of the program, i downloaded it.
Hello.
I need help in creating RIC files. [Help in the program]
Thanks.
B2O productions are the best for the best.
-
- Posts: 346
- Joined: 27 Sep 2010, 03:05
- Contact:
Re: Creating RIC files
The best place to start is by editing an existing one.
Steve
Steve
---> Link to lots of MINDSTORMS stuff under my picture --->
Re: Creating RIC files
I'm assuming you downloaded nxtriceditv2 from Andreas Dreier's website. If so, there are also several example RIC's there that you could use to see how it's all done. That is how I learned most of how it works.
The difficulty level really depends whether you intend creating static pictures, or whether you want to get into the more advanced paramaterized RIC features. Static pictures are quite straightforward to create - but the easiest way to create static pictures is to use the older version of Andreas's program (nxtriceditV1). Static pictures can also be created using the editor built in to NXT-G V2.0.
Dynamic pictures can only be created using nxtriceditV2. If you load a pre-existing dynamic RIC file then in the editor window you can simulate parameter values in the area at the top left of the screen and then watch how those values affect what would get displayed on the NXT screen.
When first playing with RIC files, the questions I had were "what are sprites" and "how are they used". The answer is that sprites are scratchpad areas of pixels that contain complete or partial graphic images that will likely get copied onto the screen at some point. Exactly what areas of what sprites do actually get displayed is all controlled by the copybits commands, which copies blocks of pixels from the scratchpad into the actual NXT screen memory area. What each copybits command actually does is determined by the parameter values, either statically, or via a varmap, or as a parameter from your program.
RIC files are quite an impressive, powerful and fun concept. It's like a whole new programming language.
Ron.
The difficulty level really depends whether you intend creating static pictures, or whether you want to get into the more advanced paramaterized RIC features. Static pictures are quite straightforward to create - but the easiest way to create static pictures is to use the older version of Andreas's program (nxtriceditV1). Static pictures can also be created using the editor built in to NXT-G V2.0.
Dynamic pictures can only be created using nxtriceditV2. If you load a pre-existing dynamic RIC file then in the editor window you can simulate parameter values in the area at the top left of the screen and then watch how those values affect what would get displayed on the NXT screen.
When first playing with RIC files, the questions I had were "what are sprites" and "how are they used". The answer is that sprites are scratchpad areas of pixels that contain complete or partial graphic images that will likely get copied onto the screen at some point. Exactly what areas of what sprites do actually get displayed is all controlled by the copybits commands, which copies blocks of pixels from the scratchpad into the actual NXT screen memory area. What each copybits command actually does is determined by the parameter values, either statically, or via a varmap, or as a parameter from your program.
RIC files are quite an impressive, powerful and fun concept. It's like a whole new programming language.
Ron.
Re: Creating RIC files
I still don't get why they couldn't use modified versions of GIFs. (Black And White, one bit. *)
*Doesn't storing 8 pixels/byte (Screen Memory) kill speed? 1 pixel/byte increases memory usage, but that can be easily remedied by adding more RAM. (Doesn't cost much to go from ~50KB to ~57KB.)
*Doesn't storing 8 pixels/byte (Screen Memory) kill speed? 1 pixel/byte increases memory usage, but that can be easily remedied by adding more RAM. (Doesn't cost much to go from ~50KB to ~57KB.)
Last edited by muntoo on 11 Dec 2010, 02:18, edited 1 time in total.
Commit to LEGO Mindstorms Robotics Stack Exchange:
bit.ly/MindstormsSE
Commit to LEGO Stack Exchange: bit.ly/Area51LEGOcommit
-
- Posts: 323
- Joined: 29 Sep 2010, 05:03
Re: Creating RIC files
What RAM are you thinking of when you talk about increasing it from 50Kb to 57Kb?
Re: Creating RIC files
Changing the hardware.gloomyandy wrote:What RAM are you thinking of when you talk about increasing it from 50Kb to 57Kb?
Have any arguments in support of LEGO? (Besides the fact that RAM has gotten cheaper over the years.)
(I fixed up the post above. The change is in bold:
)muntoo wrote:*Doesn't storing 8 pixels/byte (Screen Memory) kill speed? 1 pixel/byte increases memory usage, but that can be easily remedied by adding more RAM. (Doesn't cost much to go from ~50KB to ~57KB.)
Commit to LEGO Mindstorms Robotics Stack Exchange:
bit.ly/MindstormsSE
Commit to LEGO Stack Exchange: bit.ly/Area51LEGOcommit
-
- Posts: 323
- Joined: 29 Sep 2010, 05:03
Re: Creating RIC files
The problem is that changing the hardware is not easy. The RAM used in the NXT is built into the same chip that provides the cpu and many of the I/O devices. There is not a simple upgrade that just provides more RAM. The chip selected by Lego for the NXT is already pretty much at the top of the range for that device. The following table:
http://www.atmel.com/dyn/products/param ... ection=ASC
Gives you a view of what is available. The current device is the AT91SAM7S256 and as you can see very few of the available chips offer more RAM along with flash and other peripherals and the only ons that do (like the AT91SAM7X512) have a different package (100 pins v 64) and so would require a redesign of the PCB and probably other changes...
Going back to your original question I suspect that the current format is also designed to allow a correctly aligned image to be drawn directly to the LCD without any processing, which would actually be faster than the processing required for a 1pixel per byte image...
http://www.atmel.com/dyn/products/param ... ection=ASC
Gives you a view of what is available. The current device is the AT91SAM7S256 and as you can see very few of the available chips offer more RAM along with flash and other peripherals and the only ons that do (like the AT91SAM7X512) have a different package (100 pins v 64) and so would require a redesign of the PCB and probably other changes...
Going back to your original question I suspect that the current format is also designed to allow a correctly aligned image to be drawn directly to the LCD without any processing, which would actually be faster than the processing required for a 1pixel per byte image...
Re: Creating RIC files
Very helpful, Random, this is how it works.ronmcrae wrote:I'm assuming you downloaded nxtriceditv2 from Andreas Dreier's website. If so, there are also several example RIC's there that you could use to see how it's all done. That is how I learned most of how it works.
The difficulty level really depends whether you intend creating static pictures, or whether you want to get into the more advanced paramaterized RIC features. Static pictures are quite straightforward to create - but the easiest way to create static pictures is to use the older version of Andreas's program (nxtriceditV1). Static pictures can also be created using the editor built in to NXT-G V2.0.
2Labz.com, My Website
Re: Creating RIC files
Thanks, I got it. I made a picture too =)
-
- Posts: 125
- Joined: 29 Sep 2010, 18:07
- Contact:
Re: Creating RIC files
umm, hey, I've got nxtricedit (version 1) but can't find the website for the new version.... can someone help? It's kinda embarrassing because I was their at one time, but I can't even find it via Google. Please Help!
- Stryker AKA Jordan
http://nxtbystryker.wordpress.com
http://nxtbystryker.wordpress.com
Who is online
Users browsing this forum: No registered users and 0 guests