I think my idea the "font table" would be stored in the modified PIC code. I'm very new to all of this. So I'm not even sure it's at all possible. It was just an idea of how to get many out of a few. This was my idea of how to record the text as Dirk was talking about..
chelmuth wrote:I think my idea the "font table" would be stored in the modified PIC code. I'm very new to all of this. So I'm not even sure it's at all possible. It was just an idea of how to get many out of a few. This was my idea of how to record the text as Dirk was talking about..
That could work, too -- (stream of consiousness thinking here...) so if you sent a 41 (decimal 65, for the letter A) to the pic, it could print the letter A. That's an okay idea, but IMO it would be tedious to set exact values into multiple Vixen cells like that, and I'd be impossible to read on the Vixen screen. I'm also not sure how exactly those values are stored, recalled, recalculated, and transmitted in real time and then decoded at the PIC when the Renard protocol is asynchronous... there's no error-checking/redundancy going on to ensure that the character transmitted was the character received, and the message could easily become garbled.
That's why the concept I'm working on it essentially binary -- a cell is either on or off (value 127) so there's a lot more leeway for evaluating a pixel's value which I would think for an asynchronous protocol would make the transmission/reception/decoding process more secure and predictable.
I may be talkin' through my hat on this whole concept, but in my feeble pea-brain, it seems like it ought to work. I like your idea of flashing the pic with the footprint for the letters because it makes good sense. I just think it requires a more exact communication environment that we have for blinky-flashy.
I was thinking it could be configured roughly as follows and the attached picture is what "Hello World!" would look like in Vixen.. Obvisouly other characters would need to be programmed like "." etc. I'm not sure of the memory capabilities of the PICs as far as font tables. Just throwing ideas at the wall. You were talking originally about an Add-in anyway so I was thinking readability in Vixen wasn't super important. Just have to make sure you get the 8 channels sent to the right pic. otherwise it would look weird when your arches started blinking morse code. LOL. There's another way you could program the pics.. Via Morse Code.. Only need one channel.. CQCQ DE Dirk . Display Hello World! Stop. LOL
BIT|CH|0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ!(Space)
---|-------------------------------------------------------------------------
1 |D1|101010101010101010101010101010101010101010101010101010101010101 1
2 |D2|011001100110011001100110011001100110011001100110011001100110011 1
4 |D3|000111100001111000011110000111100001111000011110000111100001111 1
8 |D4|000000011111111000000001111111100000000111111110000000011111111 1
16 |D5|000000000000000111111111111111100000000000000001111111111111111 1
32 |D6|000000000000000000000000000000011111111111111111111111111111111 1
64 |D7|000000000000000000000000000000000000000000000000000000000000000 1
chelmuth wrote:I was thinking it could be configured roughly as follows and the attached picture is what "Hello World!" would look like in Vixen.. Obvisouly other characters would need to be programmed like "." etc. I'm not sure of the memory capabilities of the PICs as far as font tables. Just throwing ideas at the wall. You were talking originally about an Add-in anyway so I was thinking readability in Vixen wasn't super important. Just have to make sure you get the 8 channels sent to the right pic. otherwise it would look weird when your arches started blinking morse code. LOL. There's another way you could program the pics.. Via Morse Code.. Only need one channel.. CQCQ DE Dirk . Display Hello World! Stop. LOL
I like your idea... although the vision of my plugin would be that you'd type the text into it and it would paint the pixels on the screen for you -- WYWISYG. When the display ran, it'd look like this out on the TRIKS, and the only difference inside Vixen would be that the background colors would be white:
There should be plenty of room in the PICs under discussion for a font table. Figuring 8 bits per column, 5 columns per character, and 96 characters, it would require 480 locations. The PIC16F688 has room for 2048 instructions and the PIC16F627A has 1024 instructions. The current Renard firmware is around 250-300 instructions, so there would be plenty of room for a 5x7 font table with 96 characters.
Ok I can see that. So basically you set the control channel on and then stream how ever many columns into the PIC then set the control channel off and it repeats streamed data either scrolling or something.. until control channel is triggered again.
chelmuth wrote:Ok I can see that. So basically you set the control channel on and then stream how ever many columns into the PIC then set the control channel off and it repeats streamed data either scrolling or something.. until control channel is triggered again.
Yep, that's essentially it. It's a very simple concept, and with a 595 chip for each column of 7 LEDs (ch 1 unused) it should be pretty easy to scroll them across the screen using the shift register design of the chips themselves. Only need one PIC to pump out the channels to the first 595 and from there, it's just simple replication for the number of columns in the display, which would be a flashed value in the PIC's firmware. Since there's no font profile and it just mimics the pixel in Vixen, one could draw very simple graphics or use it free-hand, coloring-in pixels at random. It's WYSIWYG. Designing the display and firmware first, I can leave the plug-in for later development and get this working right away. Then if I don't finish the plugin for the coming season, people can still get the job done manually. I could even provide a sample vixen sequence that had words and numbers pre-defined and one could just copy/paste them into a sequence as needed... a REAL lazy-man's way to the solution of programming the display... (and cheap, plus it'd be software version independent, too!)
A 16F688 has 256 bytes of memory and plenty of programming space for this so it could easily handle a display that was 50-100 columns at one byte/column, and at 5 columns + a space between each letter, a 96-column display could display 16 letters (672 LEDs). But I'm thinking that only about 36 columns and letting the viewer's brain and persistence of vision assemble the moving display of 6 viewable characters should work pretty well. The column limitation is the number of 595 chips that can logically be connected to the clock/latch signals, and I don't know what that is yet... The other limitation is power for the LEDs, which isn't rocket science... (well, maybe it IS rocket science, but we'll leave NASA to figure out its own problems...)
We're talking DUMB triks here... and DUMB is a word I can relate to (and do nearly every day of my life...:lol:) But this should give you a pretty good outline of how this thing would work...
Phil, I know you're watching this thread, any insight into the number of 595 chips I can hang on the same clock/latch signal?
The limits due to DC loading are probably might higher than any practical number, perhaps up in the hundreds. The AC loading (i.e. capacitive and transmission line effects) are another factor, but I don't really know what that would be (this would also depend on the amount of trace/wire between the 595 chips). This AC limit is a function of the rise and fall times of the signals coming out of the PIC and not the clock rate. The limit can be calculated, but it has been so long since I've done so that I'm not prepared to do this now.
Just as a starting point, I estimate that the fall and rise time of the PIC outputs would be around 10 ns, or so, with load. If you have 36 595 chips out there, the physical length of the line would be perhaps 36 inches. The propagation delay (round trip) over this line is about 12 ns (perhaps a bit longer). This propagation time is long enough (compared to the signal rise/fall times) that I would be concerned about ringing, false triggering, etc., so it would be worthwhile to look into this further.
Skunberg wrote:bump
Uhhhhh.... what's the dealio with all the bumps?
budude wrote:Uhhhhh.... what's the dealio with all the bumps?
I think he is trying to move the spammer off the top page. Of course a moderator will come and get rid of the spam if we just wait

