Jump to content


Photo
- - - - -

Eclipse cabs bellfruit


  • Please log in to reply
12 replies to this topic

#1 kensplace2

kensplace2

    Member

  • New Members
  • PipPip
  • 501 posts

Posted 08 August 2005 - 10:27 PM

Any one got any tech info on the vfd's used in these cabs?

BELLFRUIT VFD DISPLAY 31 - 821 - 001 ISS 1

Just bought 15 of them, have not arrived yet, hoping to be able to google it when they arrive from part-no's but just wondering if anyone had any info from a manual or whatever.

(reason I bought 15 is they were 99p each, but I would have bought 45 but was skint!, actually seriously I want to sell em on with a circuit to make em display whatever you want, so ideal for custom case mods, car displays, shop-displays, whatever)

#2 Bencrest

Bencrest

    The furniture

  • New Members
  • PipPipPipPipPip
  • 7446 posts

Posted 08 August 2005 - 11:59 PM

Custom case-mods eh?

You've got my attention, make it fit into drive bay and display CPU temp and I'll take one :)
Ben
 
Hopefully recovering from years of compulsive gambling and wanting to be gamble free forever.
 
Recommended reading - http://www.gamblersaloud.com/ (yes, I bought the book, very happy with it!)

#3 kensplace2

kensplace2

    Member

  • New Members
  • PipPip
  • 501 posts

Posted 09 August 2005 - 12:48 AM

:) It would have to fit either on top, or on the side of a pc, as its to wide to fit in a drive bay......

But I reckon I could do allsorts with it, as long as I can get some info on it, they are serially driven in general so should have no probs.

If I get one working, if you cover postage, I will send you one free of charge, so you can test it for me, as long as you write a glowing review if its any good ;)

#4 kensplace2

kensplace2

    Member

  • New Members
  • PipPip
  • 501 posts

Posted 09 August 2005 - 12:58 AM

Ps, Can do custom case mods electronically, but if someone in the fme scene knows anyone that can make the plastics to make it look nice for drive bay stuff then were sorted ;)

All I can do is the actual item, making it fit somewhere is upto the end punter... If I could supply fittings as well then I could retire!

Untill then, I do it for fun :)

#5 khards

khards

    Member

  • New Members
  • Pip
  • 172 posts

Posted 09 August 2005 - 12:27 PM

You should be able to drive it with the following code:

/**************************************************************************
File VFD.c
Send to VFD display
**************************************************************************/
#define direct_VFD 1 // enable if req'd, i.e. direct to VFD
//#define buffer_VFD 1 // enable if using i.f. p.c.b 130-714

/* Include Files */
#include
#include
#include
#include "Macros.h" // I.O. & Soft Timer Macros

#include "IOassign.h" // I.O. Assignments
#include "IOvars.h" // I.O. previous-present states
#include "SoftTmrs.h" // Soft-timer variables Definitions
#include "VFDdef.h" // V.F.D. Character set

// Declared here for global access
unsigned char xdata vfdbuf[16+1]; // +1 for NULL at end of sprintf()

unsigned char uc;

// CODE STARTS HERE...

#ifdef direct_VFD
void Reset_VFD(void)
{
set(VFD_CLK); clr(VFD_DAT); set(VFD_RST);
for(uc=0; uc<32; uc++) { eight_microsec(); }
clr(VFD_RST);
for(uc=0; uc<32; uc++) { eight_microsec(); }
}

void Send_VFD(unsigned char d_chr)
{
unsigned char bit_cnt;
for(bit_cnt=0; bit_cnt<8; bit_cnt++) {
if(d_chr & 0x80) { clr(VFD_DAT); } else { set(VFD_DAT); }
d_chr <<= 1;
eight_microsec(); eight_microsec(); eight_microsec(); eight_microsec();
clr(VFD_CLK);
eight_microsec(); eight_microsec(); eight_microsec(); eight_microsec();
set(VFD_CLK);
eight_microsec(); eight_microsec(); eight_microsec(); eight_microsec();
}
}

#else // buffer_VFD

void Send_VFD(unsigned char d_chr)
{
unsigned char bit_cnt;
for(bit_cnt=0; bit_cnt<8; bit_cnt++) {
if(d_chr & 0x80) { set(VFD_DAT); } else { clr(VFD_DAT); }
d_chr <<= 1;
eight_microsec(); eight_microsec(); eight_microsec(); eight_microsec();
set(VFD_CLK);
eight_microsec(); eight_microsec(); eight_microsec(); eight_microsec();
clr(VFD_CLK);
eight_microsec(); eight_microsec(); eight_microsec(); eight_microsec();
}
}


void Reset_VFD(void)
{
clr(VFD_CLK); set(VFD_DAT); clr(VFD_RST);
for(uc=0; uc<32; uc++) { eight_microsec(); }
set(VFD_RST);
for(uc=0; uc<32; uc++) { eight_microsec(); }
}
#endif

/*
void Clear_VFDbuf(void)
{
for(uc=0; uc<16; uc++) vfdbuf[uc]=' ';
}

void Put_String_VFDbuf(unsigned char *s)
{
clear_vfdbuf();
uc=0;
while((uc<16) && (s[uc]!=0)) {
vfdbuf[uc]=s[uc];
uc++;
}
}
*/

void Send_VFDbuf(void)
{
bit vfd_end;

vfd_end=0;
Reset_VFD();
Send_VFD(DIGITS_16); Send_VFD(POSITION_0); Send_VFD(BRIGHT_31);
for(uc=0; uc<16; uc++) {
if (vfdbuf[uc]==0) vfd_end=1;
if (vfd_end) { vfdbuf[uc]=' '; Send_VFD(' '); } else Send_VFD(vfdbuf[uc] & 0x3F);
}
}

/*************************************************************************
End file VFD.c
*************************************************************************/

/**************************************************************************
Include File VFDdef.h
Character definitions for VFD display
**************************************************************************/

#define TESTMODE 0x80
#define DIGITS_1 0xc1
#define DIGITS_2 0xc2
#define DIGITS_3 0xc3
#define DIGITS_4 0xc4
#define DIGITS_5 0xc5
#define DIGITS_6 0xc6
#define DIGITS_7 0xc7
#define DIGITS_8 0xc8
#define DIGITS_9 0xc9
#define DIGITS_10 0xca
#define DIGITS_11 0xcb
#define DIGITS_12 0xcc
#define DIGITS_13 0xcd
#define DIGITS_14 0xce
#define DIGITS_15 0xcf
#define DIGITS_16 0xc0
#define POSITION_0 0xaf
#define POSITION_1 0xa0
#define POSITION_2 0xa1
#define POSITION_3 0xa2
#define POSITION_4 0xa3
#define POSITION_5 0xa4
#define POSITION_6 0xa5
#define POSITION_7 0xa6
#define POSITION_8 0xa7
#define POSITION_9 0xa8
#define POSITION_10 0xa9
#define POSITION_11 0xaa
#define POSITION_12 0xab
#define POSITION_13 0xac
#define POSITION_14 0xad
#define POSITION_15 0xae
#define BRIGHT_0 0xe0
#define BRIGHT_1 0xe1
#define BRIGHT_2 0xe2
#define BRIGHT_3 0xe3
#define BRIGHT_4 0xe4
#define BRIGHT_5 0xe5
#define BRIGHT_6 0xe6
#define BRIGHT_7 0xe7
#define BRIGHT_8 0xe8
#define BRIGHT_9 0xe9
#define BRIGHT_10 0xea
#define BRIGHT_11 0xeb
#define BRIGHT_12 0xec
#define BRIGHT_13 0xed
#define BRIGHT_14 0xee
#define BRIGHT_15 0xef
#define BRIGHT_16 0xf0
#define BRIGHT_17 0xf1
#define BRIGHT_18 0xf2
#define BRIGHT_19 0xf3
#define BRIGHT_20 0xf4
#define BRIGHT_21 0xf5
#define BRIGHT_22 0xf6
#define BRIGHT_23 0xf7
#define BRIGHT_24 0xf8
#define BRIGHT_25 0xf9
#define BRIGHT_26 0xfa
#define BRIGHT_27 0xfb
#define BRIGHT_28 0xfc
#define BRIGHT_29 0xfd
#define BRIGHT_30 0xfe
#define BRIGHT_31 0xff

/*************************************************************************
End include file VFDdef.h
*************************************************************************/

#6 mythicos

mythicos

    Member

  • New Members
  • PipPip
  • 553 posts

Posted 09 August 2005 - 01:13 PM

The eclipse use the dot alphas if Im not mistaken, f***in gorgeous they are :)

Theyre very very big tho, I mean my Crazy Fruits has a normal alpha and its at least 8 inches wide so I think Ken's got it nailed, it's either in the side or the top (or small custom box and external)

:)

#7 Bencrest

Bencrest

    The furniture

  • New Members
  • PipPipPipPipPip
  • 7446 posts

Posted 09 August 2005 - 09:30 PM

I've got a fecking huge case with a big window, so could just mount it on the window.

Lovely to see some engineering types in here as well :)
Ben
 
Hopefully recovering from years of compulsive gambling and wanting to be gamble free forever.
 
Recommended reading - http://www.gamblersaloud.com/ (yes, I bought the book, very happy with it!)

#8 kensplace2

kensplace2

    Member

  • New Members
  • PipPip
  • 501 posts

Posted 10 August 2005 - 08:26 PM

Thanks for the replies, Im hoping to get the info, they are the dot matrix alphas, and they are as nice as described earlier :)

Problem is, they are not marked in any way as to what pin is what, even blew my pie factory mux board up trying to interface it drunk (why do I NEVER learn... Good job I had a spare :) )

I have emailed Bell Fruit asking if they have any data (which obviously they will do) and had a read reciept from then, just waiting to see if Bell Fruit is helpful, or ignores me like barcrest would.........

Getting info from some companies is like getting blood out of a stone, JCM were VERY helpful with the note acceptor problem I had, which I still thank them for, I have tried starpoint for reel info, but they just wasted my time asking me for more info and then ignored me (translation ... lets get the ideas from him, feck him off, remember them for the future then steal them probably.....)

Any one got a eclipse cab service manual, or access to the board to see if the display pinouts are marked on it, its serial I guess but dont even know the voltage, or which pin does what..


ps duplu just ignore me and the post about emails, drink amplifies my depression/paranoia sometimes, sorry if I came across a bit of a twat

#9 Sarky

Sarky

    Junior Member

  • New Members
  • 94 posts

Posted 11 August 2005 - 02:23 AM

What is the configuration of the socket? Is it one row of pins or two? I think you'll be lucky to get a full datasheet from Bellfruit as it's customed designed.

As for Starpoint all of their datasheets are online here

#10 kensplace2

kensplace2

    Member

  • New Members
  • PipPip
  • 501 posts

Posted 11 August 2005 - 03:00 AM

Thanks sarky, as for starpoing I was after decent ramp data which is not in the data sheets, they say they can supply it, but only sometimes, so asked me for details, in effect wasting my time without the decency to even reply.....

Bellfruit should have the pinouts at the least (barcrest would not give me pinouts for the note acceptor, but when one of the JCM head bosses asked them on my behalf I got a copy, even though barcrest probably didnt know it was for me). Dont worry Mr Barcrest, I wont spoil your secret pinouts.

I should be getting them tommorow hopefully as another source has volunteered info, but at the end of the day, I cant see why companies refuse to help, saying that, Im jumping the gun with BFM as its to early to say they wont come back with lots of info (which they do have.......)
edit - plus if I have to find the info out myself, or obtained elsewhere without help from the company, then its there problem if I release the info I made up myself on the net....... Would never happen if they communicated in the first place :)

#11 kensplace2

kensplace2

    Member

  • New Members
  • PipPip
  • 501 posts

Posted 11 August 2005 - 03:06 AM

ps its one row of pins 123 4missing 5 6
(reverse the numbers, so its actually 12 3missig 456)
looks like end pins 1 and 6 are power from what I can make out from circuit traces. ITs nothing like the barcrest alpha, its probably similar, but its different...

#12 Guest_system80_*

Guest_system80_*
  • Guests

Posted 11 August 2005 - 06:34 PM

i dont suppose you want to tell us where these displays come from? :)

they are probably made by noritaka but they wont talk to you - they are bastards.

best you can do is get the datasheet for the chip, or id some other display with that chip on.

that's what i did years ago to get the info to use the barcrest displays,
i got the datasheet for the riockwell microcontroller on them instead. :)

#13 kensplace2

kensplace2

    Member

  • New Members
  • PipPip
  • 501 posts

Posted 13 August 2005 - 11:27 PM

Got some info, bfm came through with pinouts, got info from some others, so got it working now to display basic text, still got a lot more to do though, like the scrolling, dimming, and whatever other features it has built in.

The displays I picked up cheap on ebay, they are futuba displays, the vfd itself is a 16-md-07gryk with a interface board that uses a nec 780204 micro controller, custom program job by the looks of it.

So I guess for the unknown commands, I will just try banging data at it until something happens, and eventually I will get some of them. Seems to nice a display to just get trashed, when they can be put to good use.

Think im on the way to getting the dimming worked out, just need to re-hook up a lcd or a serial port to the pic so I can make a note of which commands did what as I cycle through a load of them in loops.

They run *scarily* hot though, lots of them appear to have scorch marks around the big resistor on the back, looks like they were designed in a hurry!
But they still work, so cant complain at the price I got them for.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users