Display Driver issues (info enclosed)

[hydrolisk1792]

Hi, this will be meh second post about the NCR 5972 AND the WD-202 Customer displays. These are RS232 and are 2x20 displays. VFD type. My issues are that Smartie will only talk to them "Properly with no scrambled junk and no constant reseting of the display" with the test driver with them in the 1x40 mode. This makes absoultly no sence what's so ever. Has there been any research done on these displays to make a driver in smartie? I've done all the foot work I can with datasheets and all so contact me if you need more information reguarding any of the two mentioned customer displays. I have information on the HEX commands and all that, so yeah, please reply to this.

These displays are on a machine running WIN XP SP3

[dperrow]

Okay,
I've modified one of my other display drivers for these so see how it goes. You need to set the COM port etc. to match what you are using in LCDSmartie

The WD-202 needs to be in CD5220 mode (using it's switch settings)

Obviously I don't have either of these displays so there's every chance these plugins may not work at all. Unzip them to the LCDSmartie\Displays folder then select the appropriate one from the settings screen in Smartie.

NCR5972.zip

WD-202.zip

Let me know how it goes.

Good luck,
Dave

[hydrolisk1792]

Okay,
I've modified one of my other display drivers for these so see how it goes. You need to set the COM port etc. to match what you are using in LCDSmartie

The WD-202 needs to be in CD5220 mode (using it's switch settings)

Obviously I don't have either of these displays so there's every chance these plugins may not work at all. Unzip them to the LCDSmartie\Displays folder then select the appropriate one from the settings screen in Smartie.

NCR5972.zip

WD-202.zip

Let me know how it goes.

Good luck,
Dave

Okay, thanks for the help. I have my WDs already set for that mode About to try the drivers now. *crossing meh fingers lol*

[hydrolisk1792]

Okay,
I've modified one of my other display drivers for these so see how it goes. You need to set the COM port etc. to match what you are using in LCDSmartie

The WD-202 needs to be in CD5220 mode (using it's switch settings)

Obviously I don't have either of these displays so there's every chance these plugins may not work at all. Unzip them to the LCDSmartie\Displays folder then select the appropriate one from the settings screen in Smartie.

NCR5972.zip

WD-202.zip

Let me know how it goes.

Good luck,
Dave

Mkay, the WD-202's dont respond, for example I get an error upon opening smartie on that port (Failed to open device: DLL Initilize Error: Serial port does not exist: The system coul not find the file specified. The parameters are correct, (COM18,9600,8,N,1) Yes, COM18 I have 46 of them for different stuff and about thirty screens.

The NCR one reacts the same in the 2x20 mode, just scrambles the messages. When in 1x40 mode, it scrolls as normal, from bottom to top. . .

Now remember, these screens seem to react to the Testdriver.dll the best, just only when setting it for 1x40 even though their 2x20s. Let me know if you need any more information on these screens. I have the full DAtasheets on both types And thanks for taking the time to make a driver for something you don't even own

BTW, how hard is it to make a driver for Smartie? Like how do you edit the .dll file and all that?

[dperrow]

A few questions:

1. Can you send me a copy of the config.ini files you used with the testdriver.dll for these two displays please?
2. Would it be possible to try one of the WD-202's on COM1,2 or 3?
3. Are you certain COM18 exists, can you have a look in control panel/device manager and check it.
4. What port is the NCR display on?

To develop a display dll you need to be able to program. I use the C programming language and a development tool called CodeBlocks. There are a predefined set of functions that need to be written but once you have done a first one doing others is much easier. These two took about an hour to create (although they may take much longer to debug without a display

Regards,
Dave

[hydrolisk1792]

A few questions:

1. Can you send me a copy of the config.ini files you used with the testdriver.dll for these two displays please?
2. Would it be possible to try one of the WD-202's on COM1,2 or 3?
3. Are you certain COM18 exists, can you have a look in control panel/device manager and check it.
4. What port is the NCR display on?

To develop a display dll you need to be able to program. I use the C programming language and a development tool called CodeBlocks. There are a predefined set of functions that need to be written but once you have done a first one doing others is much easier. These two took about an hour to create (although they may take much longer to debug without a display

Regards,
Dave

Yes, I will get you the required information tomorrow after I get home Thanks for all the help.

[hydrolisk1792]

A few questions:

1. Can you send me a copy of the config.ini files you used with the testdriver.dll for these two displays please?
2. Would it be possible to try one of the WD-202's on COM1,2 or 3?
3. Are you certain COM18 exists, can you have a look in control panel/device manager and check it.
4. What port is the NCR display on?

To develop a display dll you need to be able to program. I use the C programming language and a development tool called CodeBlocks. There are a predefined set of functions that need to be written but once you have done a first one doing others is much easier. These two took about an hour to create (although they may take much longer to debug without a display

Regards,
Dave

Okay, here is your answers

1. Files attached

Configs.rar

2. I can try the WD displays on the port 3 if needed, but I'm not able to keep them on that port because of the wiring setup that I have on this particular machine.
3. Yes, the diplay works on that port, ports 17 - 22 are USB to RS232.
4. The NCRs are all reserved for the bus RS232s which are ports 1 - 4

Hope this info helps

[dperrow]

Hi,
after a bit of trial and error I discovered that for COM ports above COM9 you need to reference them as \\.\COMx so I've modified the code to do this and checked it on a serial port emulator.

NCR5972.zip

WD-202.zip

Give these a try and let me know. The other thing to double check are the switch settings on the displays themselves.

Regards,
Dave

[hydrolisk1792]

Hi,
after a bit of trial and error I discovered that for COM ports above COM9 you need to reference them as \\.\COMx so I've modified the code to do this and checked it on a serial port emulator.

NCR5972.zip

WD-202.zip

Give these a try and let me know. The other thing to double check are the switch settings on the displays themselves.

Regards,
Dave

Okay, the WD-202 is working next to perfect. There is one flaw though, the cursor is flashing in the top left corner. . . It is fine with me though Imma see if I can disable it via HEX codes in the datasheet.

The NCR dll just blanks out the screen. . . That is amazing how you can make a driver work like that without the hardware there to test it on Second try and you got it on the WD-202 on the second try lol.

[hydrolisk1792]

Hi,
after a bit of trial and error I discovered that for COM ports above COM9 you need to reference them as \\.\COMx so I've modified the code to do this and checked it on a serial port emulator.

NCR5972.zip

WD-202.zip

Give these a try and let me know. The other thing to double check are the switch settings on the displays themselves.

Regards,
Dave

Also something to add to the last post is that when on a screen that updates but doesn't scroll EX. CPU usage precentage, the cursor glitches all over the screen on the WD-202. It does operate as a 2x20 now though Tried to get rid of it with the hex as well, but nothing
Thanks for the help.

[dperrow]

Hi,
for the WD-202 there is a conflict between the two data sheets I have regarding the value to switch on/off the cursor. The one you have uses ESC 5F 01, I've created another with ESC 5F 00 so try this and let me know.

WD-202.zip

for the NCR I suspect that the reset command is doing something horrible so I've replaced it with a clear screen command.

WD-202.zip

Cheers,
Dave

[hydrolisk1792]

Hi,
for the WD-202 there is a conflict between the two data sheets I have regarding the value to switch on/off the cursor. The one you have uses ESC 5F 01, I've created another with ESC 5F 00 so try this and let me know.

WD-202.zip

for the NCR I suspect that the reset command is doing something horrible so I've replaced it with a clear screen command.

WD-202.zip

Cheers,
Dave

OMFG dude, they both are working flawlessly! I can't believe that you made drivers for hardware that you didn't even have, and make it work this perfect. I can't thank you enough. I've been after this for about two years now! I would love to know how you did this. Also, I have a question, how many ports did you make the .dlls go up to? For instance, if I add more prots, can it go up to port 50 or higher?

[dperrow]

Excellent, Excellent

The port numbers in the version you have will go up to 99. I've tidied up the code and the attached versions just read an integer so will go way beyond this.

NCR5972.zip

WD-202.zip

I'd love to know what you are going to do with 50 displays on a single machine????? and does this mean you are running multiple copies of LCDSmartie? If so how do you get them to automatically start up at boot time as I've found that it mixes up the entries in the startup folder?

I've also attached another plugin I've been working on and using which allows multiple displays from a single LCDSmartie.

Multi.zip

Restrictions are that all the displays must be the same size (i.e 4x16 or 4x20 etc.) and will all display the same thing. You also need a separate copy of the dll for each display. It will cope with up to 99 displays. If you want to try it then copy multi.dll to the displays folder and create a file called Multi.cfg containing something like:

Code: Select all

//
// set Debug to 1 if you want traces
Debug=0
// Total number of dlls to run
NumDLLs=3
// Dll for display 1
DLL1=desktop.dll
// init string for display1
INIT1=None1
// etc
DLL2=desktop2.dll
INIT2=None2
DLL3=desktop3.dll
INIT3=None3
//

should be fairly self explanatory. // indicates a comment line. Setting debug to 1 will create traces in a log file in the smartie/logs folder.
You need to copy and rename the dll for each display but you can mix and match the display types (e.g WD-202 and NCR).

Not sure if there will be an upper limit to the number of displays it can drive (it might get slower) but overall it will use less processor than multiple copies of smartie running.

Let me know how you get on if you try it.

Regards,
Dave

[hydrolisk1792]

Excellent, Excellent

The port numbers in the version you have will go up to 99. I've tidied up the code and the attached versions just read an integer so will go way beyond this.

NCR5972.zip

WD-202.zip

I'd love to know what you are going to do with 50 displays on a single machine????? and does this mean you are running multiple copies of LCDSmartie? If so how do you get them to automatically start up at boot time as I've found that it mixes up the entries in the startup folder?

I've also attached another plugin I've been working on and using which allows multiple displays from a single LCDSmartie.

Multi.zip

Restrictions are that all the displays must be the same size (i.e 4x16 or 4x20 etc.) and will all display the same thing. You also need a separate copy of the dll for each display. It will cope with up to 99 displays. If you want to try it then copy multi.dll to the displays folder and create a file called Multi.cfg containing something like:

Code: Select all

//
// set Debug to 1 if you want traces
Debug=0
// Total number of dlls to run
NumDLLs=3
// Dll for display 1
DLL1=desktop.dll
// init string for display1
INIT1=None1
// etc
DLL2=desktop2.dll
INIT2=None2
DLL3=desktop3.dll
INIT3=None3
//

should be fairly self explanatory. // indicates a comment line. Setting debug to 1 will create traces in a log file in the smartie/logs folder.
You need to copy and rename the dll for each display but you can mix and match the display types (e.g WD-202 and NCR).

Not sure if there will be an upper limit to the number of displays it can drive (it might get slower) but overall it will use less processor than multiple copies of smartie running.

Let me know how you get on if you try it.

Regards,
Dave

Hello and thank you for taking intrest in meh screens :

The resoning for so many displays and com port equipment on a single machine is for home/control center automation. Each screen does something completely different and there are tons of screens all over the building alond with in the control room. I have some of those USB to 20 buttons from desktopaviator.com which work perfect for custom number pads and other hot buttons to do all sorts of things. For instance, someone hits a buton in lets say the game room, the button is ran thru Xpadder, than that button thru Xpadder turns into a hot key combo, (EX. ctrl+F12). That command than is picked up by smartie to run a batch file, and go to the winamp screen set (EX. Theme 10) Batch file runs winamp with the approate play list loaded as well. Then there are more buttons for the Winamp global hotkeys which are also ran thru Xpadder.

Plus to add something, I use the shit out of the LPT ports as well for external control as output. . .

On to instances. At the start up of the Command PC, nothing happeneds, everything is individually started up one by one. . . For the simple fact of having to send soem hex commands to each and every port on the machine for the screens and special RS485 POS keyboards. Each instance is in it's own folder, EX:
C:/CONTROL/LCD-SMARTIE/LCD-SMARTIE-COM(001)/LCDSMARTIE.EXE
C:/CONTROL/LCD-SMARTIE/LCD-SMARTIE-COM(002)/LCDSMARTIE.EXE
C:/CONTROL/LCD-SMARTIE/LCD-SMARTIE-COM(003)/LCDSMARTIE.EXE
And so on. . .
C:/CONTROL/LCD-SMARTIE/LCD-SMARTIE-COM(050)/LCDSMARTIE.EXE
C:/CONTROL/LCD-SMARTIE/LCD-SMARTIE-COM(051)/LCDSMARTIE.EXE
C:/CONTROL/LCD-SMARTIE/LCD-SMARTIE-COM(052)/LCDSMARTIE.EXE

Some of the ports in the main smartie DIR are skipped because of RS485 ports and RS232 card swipers.
Everything to do with control center equipment is in that CONTROL folder, so even programs are changed from standard DIRs and into there.
Plus I have a massive shortcuts folder right on the desktop organized by port number, lol.
EX.
(COM001)(MAINDOOR)LCDSMARTIE.EXE
(COM002)(CONTROL-ROOM-DOOR)LCDSMARTIE.EXE
and so on.
I know, all this seems a bit elaborate, lol

Did you read up on how the WD202's can be pigibacked to a reciept printer? Well I have them duplicating displays for the displays around the building, so this way I can see what is being displayed on those screens from in here and save an instance of Smartie, along with another port I shouldn't have to worry about going past port 100 with screens, because I can put the rest of the gear past 99 for the simplicity of the screens and drivers. But you sdid say to use the dll's that you just posted insted of the ones that were posted yesterday? You said you cleaned up the code a bit, so yeah.

So the code you posted, is that part of the Milti plug in, or is that part of the screen dll's?

[dperrow]

Sounds Complicated. What's the control centre for?

Yes you should use the latest version of the dll's just because the error checking is better and the program is cleaner. Check they work okay first before deploying them accross all your displays.

The code example I supplied is only for the multi.dll if you choose to use it.

Regards,
Dave

[hydrolisk1792]

Sounds Complicated. What's the control centre for?

Yes you should use the latest version of the dll's just because the error checking is better and the program is cleaner. Check they work okay first before deploying them accross all your displays.

The code example I supplied is only for the multi.dll if you choose to use it.

Regards,
Dave

The reason for the control center is classified under contract. . . Sorry bout that.
Yes the new DLLs work perfectly, I ran them thru all the approate tests on another machine supporting 10 displays and 400 USB buttons, and all commands and such work perfectly Thank you for all the help you have given and you can keep in touch with me if you like on here or via my email.
anubis1792@aol.com

[hydrolisk1792]

Sounds Complicated. What's the control centre for?

Yes you should use the latest version of the dll's just because the error checking is better and the program is cleaner. Check they work okay first before deploying them accross all your displays.

The code example I supplied is only for the multi.dll if you choose to use it.

Regards,
Dave

The reason for the control center is classified under contract. . . Sorry bout that.
Yes the new DLLs work perfectly, I ran them thru all the approate tests on another machine supporting 10 displays and 400 USB buttons, and all commands and such work perfectly Thank you for all the help you have given and you can keep in touch with me if you like on here or via my email.
anubis1792@aol.com

Also there is one more issue with the NCR dll. When I shut down smartie on the NCR displays the data is lost, like the screen goes blank. On thje dw drivers, the last data that was sent to the screen (shutdown message) is displayed. Is there a way to make the NCR display do that?

[dperrow]

Actually there was a mistake in the WD-202 driver and it was meant to clear the display too.

I've removed the clear code from both of these so they should retain what's on display when Smartie is closed down.

WD-202.zip

NCR5972.zip

let me know how it goes.

Regards,
Dave

[hydrolisk1792]

Actually there was a mistake in the WD-202 driver and it was meant to clear the display too.

I've removed the clear code from both of these so they should retain what's on display when Smartie is closed down.

WD-202.zip

NCR5972.zip

let me know how it goes.

Regards,
Dave

Works flawlessly Thanks again for all the help in this endevor

[hydrolisk1792]

Actually there was a mistake in the WD-202 driver and it was meant to clear the display too.

I've removed the clear code from both of these so they should retain what's on display when Smartie is closed down.

WD-202.zip

NCR5972.zip

let me know how it goes.

Regards,
Dave

Hey, I just realized that maleware bytes says that these are Trojan.backdoor viruses? That is odd, any idea why? I still am using them and put it in the ignore list obvously lol. Just curious of why it is saying that. . .

[dperrow]

I use Microsoft security essentials and i've not had any viruses shown on these. I downloaded your versions and rescanned them just to be sure. dont know why maleware bytes thinks different?

[hydrolisk1792]

I use Microsoft security essentials and i've not had any viruses shown on these. I downloaded your versions and rescanned them just to be sure. dont know why maleware bytes thinks different?

Yeah, I use essentials as well, it is just Malewarebytes that is saying it. It is fine, I put it in the ignore list so it don't mess anything up lol. Yeah I found it out when I was doing a curiousity scan to prove that my machines were virus/maleware/randsomware free to someone. Hee hee, it was a bit messed up becase those poped up, but I explained everything and that was the only thing on my machines lol. Cheers

[hydrolisk1792]

I don't mean to surface this topic again and again lol, however, would it be possible to have the Brightness slider in the Smartie GUI control the brightness of the WD-202 and the NCR 5972 displays? And would this work for having an action in smartie change the brightness automatically once the code is in the dlls? I have the string commands here, which are in HEX:

NCR 5972:

Code: Select all

Format: 1B 17 nn

Range: 01 < nn < 05

Description: Adjusts the brightness of the entire display, on powerup the default brightnes setting is 5 (100%)

01  20%
02  40%
03  60%
04  80%
05  100%

And here is the command lines for the WD-202 brightness:

Code: Select all

1B 2A n

1 < n < 4

You may have to add a "0" in front of the brightness number, I have to do that in Hercules to make the brightness change.

If you would like me to send you the datasheets I found these commands in, let me know, or maybe you still have them from when you made the original DLL files Could you add these to the most recent versons of the dlls that you made and I'll give them a go? Thanks Dave

[dperrow]

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.

[hydrolisk1792]

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.

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?