send file to serial port using comfromfile

[VikramShetty_p]

I dont think so it is configuration issue..because I had crosschecked the manual for controller settings and all other commands working fine without any issues..only the issue with the seding bin file..

I am also guessing this function may be one issue IOCTL_SERIAL_SET_TIMEOUTS..

[RobertoBozzolo]

---

Julien_2831 ha scritto:

You're right.

Another point is "IOCTL_SERIAL_SET_TIMEOUTS" lines in CVI log, between each character sent. It is not visible in HYP log. Don't you think it could be the reason why it doesn't work ?

---

Unless I'm missing something, that line is present in all logs Vikram has posted. I'm not sure on what does it mean but I see no difference between Hyperterminal and CVI in that.

@Vikram: which transmission speed are you using? Unless it's very slow (say 2400 baud or so) that 80 char/sec speed does not match with character spacing, so it seems that in Hyperterminal too there is some delay added (I seem to remember it can be set in some ASCII settings screen).

Can you check it and verify whether you can send with HT with different delays? If not then transmission timing seems to be critical and you must match it exactly in CVI app too.

[VikramShetty_p]

Please find the attachement for hypertermial settings and below my code configuration settings..

There is no issues in reading the configuration settings..

<rs232conf>
  <port1>
  <portnum>1</portnum>
  <portname>com1</portname>
  <baudrate>19200</baudrate>
  <startbit>1</startbit>
  <stopbits>2</stopbits>
  <databit>7</databit>
  <parity>1</parity>
  <xonxoff>1</xonxoff>
  <micbaclatency>50</micbaclatency>
  <rs232timeout>100</rs232timeout>
  </port1>

[Julien_31]

About IOCTL_SERIAL_SET_TIMEOUTS : It is not visible at the beginning of both files (Hyperterminal Log.LOG and Hyperterminal Log New.LOG) that Vikram has sent. Both files start as follow :

0 4:00:43 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: Q
1 4:00:44 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
2 4:00:44 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1:
3 4:00:44 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
4 4:00:44 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: X
5 4:00:45 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
6 4:00:45 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
7 4:00:46 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
8 4:00:46 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
9 4:00:46 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
10 4:00:46 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
11 4:00:47 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
12 4:00:47 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
13 4:00:47 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1:
14 4:00:47 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
15 4:00:48 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
16 4:00:48 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
17 4:00:48 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
18 4:00:49 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
19 4:00:49 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
20 4:00:49 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: F
21 4:00:50 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: 0
22 4:00:50 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1:
23 4:00:56 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: `
24 4:00:56 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1: @
25 4:00:56 PM hypertrm.exe IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS
26 4:00:56 PM hypertrm.exe IRP_MJ_WRITE Serial0 SUCCESS Length 1:
27 4:00:56 PM hypertrm.exe IOCTL_SERIAL_GET_COMMSTATUS Serial0 SUCCESS

...

I agree with Roberto : this assumption is not very convincing. ^^ But I think it can be worth sweeping away this assumption by doing some test without IOCTL_SERIAL_SET_TIMEOUTS.