Posted by: SteveyD
« on: October 23, 2011, 10:08:25 pm »No, just a simple bi-directional Serial port interface.
I built a new interface and the errors are gone.
I built a new interface and the errors are gone.
News:
Thank you for using this forum as the technical support base for your device.
● You can format the text and attach screenshots, photos and RDS Spy records
● Faster reply: 50 % of questions are answered within 30 minutes
● You don't need to register (but registration is possible)
● The members represent a wide range of experts
● The resolution will be helpful to other users
● You'll be notified by email about new post
Posted by: Jan
« on: October 23, 2011, 09:37:56 pm »Is it a USB to RS232?
Posted by: SteveyD
« on: October 23, 2011, 06:33:54 pm »Error was found
my Serial adapter cable was at fault.
my Serial adapter cable was at fault.
Posted by: Jan
« on: October 18, 2011, 09:06:35 am »This kind of error may occur if you use USB to RS232 converter and if you remove the converter from the USB before the connection is closed in the application. (But for example FTDI drivers are well written and do not raise this error.)
The cable wiring has no effect on it. It may be a driver issue. There's something more you can test:
http://pira.cz/rds/TinyRDS_Setup.exe - This is the minirds control software based on mrdsio.dll
http://pira.cz/rds/minirds.zip - This is an older minirds control software that accesses the port directly (but using the same VaComm component).
The cable wiring has no effect on it. It may be a driver issue. There's something more you can test:
http://pira.cz/rds/TinyRDS_Setup.exe - This is the minirds control software based on mrdsio.dll
http://pira.cz/rds/minirds.zip - This is an older minirds control software that accesses the port directly (but using the same VaComm component).
Posted by: SteveyD
« on: October 18, 2011, 02:11:45 am »Jan
I've tested my Serial (with 2K resistor replacement) version and it consistently returns the error.
My LPT version is functioning fine in both Delphi and C#.
I will rebuilding my Serial interface cable and will test again.
Steve
I've tested my Serial (with 2K resistor replacement) version and it consistently returns the error.
My LPT version is functioning fine in both Delphi and C#.
I will rebuilding my Serial interface cable and will test again.
Steve
Posted by: Jan
« on: October 17, 2011, 03:49:19 pm »The Disconnect procedure is pretty simple:
Could you confirm that the error occurs also if you connect to some COM port previously?
Code: [Select]
procedure TDM1.Disconnect;
begin
Connected:=false;
try
VaComm1.Close;
sleep(200);
except
end;
end;
Could you confirm that the error occurs also if you connect to some COM port previously?
Posted by: SteveyD
« on: October 17, 2011, 02:33:28 pm »Yes, even the most recent zip package from 4 posts above.
It occurs on your example.exe in Delphi as well as my C# conversion.
It occurs on your example.exe in Delphi as well as my C# conversion.
Posted by: Jan
« on: October 17, 2011, 11:59:50 am »Is your example file actual too?
Posted by: SteveyD
« on: October 17, 2011, 10:38:37 am »Yes, I'm using Dll version 0.98
Application Error
Exception EAccessViolation in module mrdsio.dll at 000038C4,
Access violation at addres 075938C4 in module 'mrdsio.dll'.
Read of address 00000000.
Application Error
Exception EAccessViolation in module mrdsio.dll at 000038C4,
Access violation at addres 075938C4 in module 'mrdsio.dll'.
Read of address 00000000.
Posted by: Jan
« on: October 17, 2011, 09:29:38 am »Make sure you have the latest version http://pira.cz/rds/mrdsio.zip
This works stable for me using any combination of OS or settings.
This works stable for me using any combination of OS or settings.
Posted by: SteveyD
« on: October 17, 2011, 09:15:20 am »Jan
I've been encountering application crashes when I use the "Disconnect" button on your example.exe
This occurs in WinXP Sp3, as well as Win7 Sp1.
The error always occurs in the same memory location on the mrdsio.dll
I'm trying to get a screen shot to post.
Has anyone else reported this problem?
Steve
I've been encountering application crashes when I use the "Disconnect" button on your example.exe
This occurs in WinXP Sp3, as well as Win7 Sp1.
The error always occurs in the same memory location on the mrdsio.dll
I'm trying to get a screen shot to post.
Has anyone else reported this problem?
Steve
Posted by: SteveyD
« on: September 19, 2011, 01:19:06 am »Solved!
I had a Bool declaration backwards
I had a Bool declaration backwards
Posted by: SteveyD
« on: September 14, 2011, 05:39:24 pm »Has anyone come up with a working example for using the Receive function in VB or C#?
I've converted and tested all the functions except Receive. Its still giving me problems.
function Receive (Adr, Len : Integer); TData; stdcall;
I've converted and tested all the functions except Receive. Its still giving me problems.
function Receive (Adr, Len : Integer); TData; stdcall;
Posted by: Jan
« on: July 30, 2011, 03:26:49 pm »You may take the example sources and modify them as required.
Posted by: SteveyD
« on: July 30, 2011, 02:46:51 pm »I see, Bi-directional operation is REQUIRED.
therefore the trap is correct, and the CheckBox1 must be checked.
The error is the message;
StatusBar1.SimpleText:="Bidirectional operation not allowed"
should be
StatusBar1.SimpleText:= "Bidirectional operation required"
On another note, Which is returned in the Receive function, TData as a byte array or Result: Output as a string?
therefore the trap is correct, and the CheckBox1 must be checked.
The error is the message;
StatusBar1.SimpleText:="Bidirectional operation not allowed"
should be
StatusBar1.SimpleText:= "Bidirectional operation required"
On another note, Which is returned in the Receive function, TData as a byte array or Result: Output as a string?