Konica Minolta AccurioPress C14000 Plockmatic SD-350/SD-500 USB to RS-232 Adap - Page 26

Device can write but cannot read, Bytes missing or data corrupt, Driver isn't sending or receiving

Get Konica Minolta AccurioPress C14000 PDF manuals and user guides View all Konica Minolta AccurioPress C14000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

5. Device can write but cannot read If the hardware does not work correctly under Windows 2000 or Windows XP then the problem is most likely a hardware issue. Windows CE is not very tolerant of noisy hardware, so even "good" designs for Windows 2000 and XP may experience problems with Windows CE. Another issue that has arisen with Windows CE is that different host devices support different bulk transfer sizes. One method to attempt to resolve this is to reduce In Transfer Size to 64. This is the smallest possible transfer size and will have a severe effect on performance, but should resolve most other issues. Larger values may be tried to improve performance. If a USB host CF card is being used, it may help to set the Raton bit in the configuration settings. 6. Bytes missing or data corrupt This can occur when a host driver fails to send vendor commands properly which can result in the device running at a different Baud rate to the one intended. The Baud rate can be verified easily by transferring data from PDA/target to HyperTerminal. Some host device drivers have been seen to lose packets of data which would also cause this problem. 7. Driver isn't sending or receiving any data Sending and receiving data can be tested with an application such as VCPTest. However, this will not highlight problems due to incorrect Baud rates. To check for the wrong Baud rate being set, try to transfer data from the PDA/target to and from HyperTerminal. 26-51

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
26-51
5. Device can write but cannot read
If the hardware does not work correctly under Windows 2000 or Windows XP then the problem is most likely a
hardware issue. Windows CE is not very tolerant of noisy hardware, so even "good" designs for Windows 2000
and XP may experience problems with Windows CE.
Another issue that has arisen with Windows CE is that different host devices support different bulk transfer sizes.
One method to attempt to resolve this is to reduce In Transfer Size to 64. This is the smallest possible transfer size
and will have a severe effect on performance, but should resolve most other issues. Larger values may be tried to
improve performance.
If a USB host CF card is being used, it may help to set the Raton bit in the configuration settings.
6. Bytes missing or data corrupt
This can occur when a host driver fails to send vendor commands properly which can result in the device running at
a different Baud rate to the one intended. The Baud rate can be verified easily by transferring data from PDA/target
to HyperTerminal.
Some host device drivers have been seen to lose packets of data which would also cause this problem.
7. Driver isn't sending or receiving any data
Sending and receiving data can be tested with an application such as VCPTest. However, this will not highlight
problems due to incorrect Baud rates. To check for the wrong Baud rate being set, try to transfer data from the
PDA/target to and from HyperTerminal.