LCD Smartie

Posted: **June 20th, 2014, 7:41 pm**

Okay,
I assumed the range was 0-100 but it must be 0-255 so i've updated it in the attached.

WD-NCR2.zip

Good Luck.

Posted: **June 20th, 2014, 7:45 pm**

Not a problem.
two things though:

1. Can't remember what the range of the slider value is for the function 100 or 255)
2. Can't remember what the direction of the slider value is for the function (0-100 or 100-0)

so if it works backwards or tops out too early let me know.

Anyway they are both in the attached zip file:

wd-NCR.zip

BTW I don't think you can set the brightness from an action.[/quote]

Blimey, you are the fastest one to reply on here, lol. Nice website BTW, I found that the other day lol. The NCR file is correct, however the screen is at max brightness when the slider is in the middle lol. This is also the case with the WD-202 Displays. The slider is going in the correct direction as well. Testing them whilst I'm typing this lol. Thanks for doing this for me, it is really appreciated mate!

Also as a side quest, would it be possible to have the screens go into powersave mode when the backlight command is accessed via an action? This command is already in Smartie's actions tab under the output list of commands, "BacklightToggle, Backlight(0/1), and Backlight flash (5). I have the commands for each of the screens here:

NCR 5972:

Code: Select all


Enable Power Save Mode 1B 06

And to bring it out of powersave mode it is 1B 05

And the WD-202 Screen codes are:

Code: Select all


I can't find any code in the CD5220 command list that supports a power save mode :(  It is okay, I may be able to do a bit of soldering and have a switch between the connection for the heaters. . .

Furthermore, I tried to use your Multi.dll, however I can't get it to work properly. It will only display on one screen, and when I close Smartie and re-open it, the screens don't do anything. Also how do I set which com port the screens are on?

Posted: **June 20th, 2014, 8:02 pm**

They work flawlessly

Also as a side quest, would it be possible to have the screens go into powersave mode when the backlight command is accessed via an action? This command is already in Smartie's actions tab under the output list of commands, "BacklightToggle, Backlight(0/1), and Backlight flash (5). I have the commands for each of the screens here:

NCR 5972:

Code: Select all


Enable Power Save Mode 1B 06

And to bring it out of powersave mode it is 1B 05

And the WD-202 Screen codes are:

Code: Select all


I can't find any code in the CD5220 command list that supports a power save mode :(  It is okay, I may be able to do a bit of soldering and have a switch between the connection for the heaters. . .

Furthermore, I tried to use your Multi.dll, however I can't get it to work properly. It will only display on one screen, and when I close Smartie and re-open it, the screens don't do anything. Also how do I set which com port the screens are on?

Posted: **June 20th, 2014, 8:34 pm**

Hadn't read the rest of your post!

The attached dll's have the backlight functions included. for the WD202 backlight off sets the brightness to 1 and backlight on sets it to whatever it was previously set to.

WD-NCR4.zip

For multi you specify the com port etc. in the cfg file on the init line in the same way you would in the smartie setup screen.

Posted: **June 20th, 2014, 8:52 pm**

Blimey, those work really well. Thanks for doing that. That was pretty brilliant making the WD-202's brightness change, that is actually very usefull

For the Multi.dll, It is acting very strangely lol, I can only get one screen to work, specifically I'm using the NCR5972.dll for this. It only displays on COM2. . . Also on that one screen, only the second line of text is displaying on both the top and bottom of the display. I'm guessing that the Multi.cfg file is supposed to be in the displays folder, right?

Here is the code I'm using in the config. . .

Code: Select all


//
//
Debug=0
NumDLLs=2
DLL1=NCR5972.dll
INIT1=COM2,9600,8,N,1
DLL2=NCR5972.dll
INIT2=COM3,9600,8,N1
//
//
//

Cheers

Posted: **June 20th, 2014, 9:20 pm**

very strange. Could you maybe set debug to 1 and let me see the log file?

Posted: **June 20th, 2014, 9:25 pm**

dperrow wrote:very strange. Could you maybe set debug to 1 and let me see the log file?

Okay, I did that and here is the contents of the log file:

Code: Select all


13:22:37 20/06/14 Loading library NCR5972.dll
13:22:37 20/06/14 Dll loaded NCR5972.dll
13:22:37 20/06/14 Loading library NCR5972.dll
13:22:37 20/06/14 Dll loaded NCR5972.dll
13:22:37 20/06/14 All Dlls Loaded - nr. displays 0x00000002 (2)
13:22:37 20/06/14 Initialising Dll 1 dll=NCR5972.dll x=20, y=2, init=COM2,9600,8,N,1 ok=0, handle=0x65F40008, init code at 0x65F41398
13:22:37 20/06/14 Initialised Dll 1 ok=1, returned NCR5972 v1.0.61.324
13:22:37 20/06/14 Initialising Dll 2 dll=NCR5972.dll x=20, y=2, init=COM3,9600,8,N,1 ok=1, handle=0x65F40008, init code at 0x65F41398
13:22:37 20/06/14 Initialised Dll 2 ok=1, returned NCR5972 v1.0.61.324
13:22:37 20/06/14 Init Complete
13:22:45 20/06/14 Entered Done
13:22:45 20/06/14 Exit Done

Posted: **June 20th, 2014, 10:10 pm**

You need a separate copy of the NCR5972.dll for each device. Just copy the dll and rename it e.g. NCR5972a.dll

Took me a while to remember this! It does say so in the doc but it's not very explicit.

Posted: **June 21st, 2014, 4:16 am**

dperrow wrote:You need a separate copy of the NCR5972.dll for each device. Just copy the dll and rename it e.g. NCR5972a.dll

Took me a while to remember this! It does say so in the doc but it's not very explicit.

Blimey, right after I read your post, I noticed that bit in the release notes. I made sure to add your post to those release notes for future refrence. There is a problem whilst using the sandr.dll plugin on the WD-202 displays, but I'm working that out now, and I know it has nothing to do with your plugin because the sandr.dll plugin works just fine on the NCR displays. I'm probably not going to use it on the WD-202 screens anyways becasue I can piggieback them with the "screen duplicate command" which before I start the screens I go into my favorite com port access program and send them the correct command to duplicate the screens, then run smartie and all is well

Code: Select all


This is the code I send to the WD-202 screens before startup in HEX:

1B 3D 03

This is a really cool function of these displays, and I like the fact I can do it with any display now with your Multi.dll plugin, has to be in my top favorite LCD Smartie Plugins!!

Thanks again for all your help with this, I know it is probably a small thing for you to program these .dll files, but it is a big thing for me lol. The extent of my programming skills are web development only, "Javascrit, html, php, css, and so on"

I use the sandr.dll plugin to make all the bars, spectrum analyzers, and so on look right on these displays because the characters are a different hex/ASCII code between the two types of displays lol. I'm just glad that they are installed already in the character sets of the displays and I can access them via $Chr(###) code sttring in Smartie and in the omit files for sandr.dll.

Posted: **June 22nd, 2014, 2:37 pm**

I've modified the attached to include commands to be sent before and after the initialisations for both drivers.

WD-NCR5.zip

It works like this. Create a file in the displays folder with the same name as the dll and an extension of .cfg e.g. WD-202.cfg (or WD-202a.cfg if you copied and renamed the dll for multi for example) as a text file.

In that file put:

Code: Select all

//
// WD-202 optional initialisation strings INIT1 is sent before init and INIT2 sent after
// format is:
//INIT1=<space>hh<space>hh<space>hh<return>
// where hh is a 2 digit hex number. You can have up to 20 numbers. Note DO NOT put a space after the last character on the line
// example below
INIT1= 1B 3D 03
//

Hope this is useful.

Posted: **June 24th, 2014, 12:00 pm**

dperrow wrote:I've modified the attached to include commands to be sent before and after the initialisations for both drivers.

WD-NCR5.zip
It works like this. Create a file in the displays folder with the same name as the dll and an extension of .cfg e.g. WD-202.cfg (or WD-202a.cfg if you copied and renamed the dll for multi for example) as a text file.

In that file put:
Code: Select all
//
// WD-202 optional initialisation strings INIT1 is sent before init and INIT2 sent after
// format is:
//INIT1=<space>hh<space>hh<space>hh<return>
// where hh is a 2 digit hex number. You can have up to 20 numbers. Note DO NOT put a space after the last character on the line
// example below
INIT1= 1B 3D 03
//
Hope this is useful.

Blimey, that is a really good idea doing this to the display drivers

you just made them more modular, which is a really good thing. However, for some reason, it doesn't work. I did exactly as described, but it doesn't work

Posted: **June 24th, 2014, 2:29 pm**

Oops, My Bad, Schoolboy error, forgot to call the function to read the configuration file!!

fixed that - hopefully this one will be better

WD-NCR6.zip

Posted: **June 25th, 2014, 1:46 am**

dperrow wrote:Oops, My Bad, Schoolboy error, forgot to call the function to read the configuration file!!

fixed that - hopefully this one will be better

WD-NCR6.zip

LOL, Schoolboy error, Nice. For some reason this verson crashes Smartie

I think it has to do with a typo in the dll files acording to what I can gather from the error code:

Code: Select all


Problem signature:
  Problem Event Name:	BEX
  Application Name:	LCDSmartie.exe
  Application Version:	5.4.0.5
  Application Timestamp:	2a425e19
  Fault Module Name:	StackHash_8680
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	00000000
  Exception Offset:	50737913
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7600.2.0.0.256.1
  Locale ID:	1033
  Additional Information 1:	8680
  Additional Information 2:	868025873020f321084fbdb34a7689b5
  Additional Information 3:	5ffb
  Additional Information 4:	5ffbf063dc0b38b7ca4e74e7a7bb679a

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Right at the top of the error report it says that the problem event name is BEX, maybe you accidently typed a "B" insted of a "H"? LOL, just a newbie guess lol.

Posted: **June 25th, 2014, 6:29 am**

Put that down to a bad day

Hopefully this is better.

WD-NCR7.zip

Posted: **June 25th, 2014, 9:54 am**

dperrow wrote:Put that down to a bad day Hopefully this is better.

WD-NCR7.zip

Blimey, that one works! It is alright, we all have those days, I hope that your day gets better mate

And thanks again for all the work you have put into this project with me

Cheers

LCD Smartie

Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)

Re: Display Driver issues (info enclosed)