Applied Motion ST5si vi

[Highland_Controls]

Glad to help.

[UoB_Hoss]

Resurrection apology.

I've just been using this code to talk to a Applied Motion TSM 23Q over RS485.

I also have the timeout error, how did you solve that? termination?

[Highland_Controls]

So it was working and now it isn't?  Only a specific command?

[UoB_Hoss]

HI, I'm not the original poster. Dave last reported that he had a timeout error and solved it by 'termination' whatever that means. I've been trying your VI's and have the same timeout error.

[UoB_Hoss]

Hi Highland Controls.

I'm using your Send Serial to talk to a TSM23 motor. (Many thanks, great work)

But i'm getting a timeout error 1073807339. Now usually that beacuse its waiting for bytes that a'rent there.

In your .vi you've made a read of a constant 100 bytes, which would seem to be more than the drive sends.

Why have you done it this way and not a bytes at port?

Any ideas on the timeout?

[Highland_Controls]

If the termination character is enabled when opening the com port(and my Applied Open Com Port VI does this), then the byte count is just a maximum.  Is any command working?  Post a screenshot of your code.

[UoB_Hoss]

I seem to have at least one read before it times out. I'm just in the process of hooking up a scope to have a look at the data. But perhaps before i do that i'll check out the termination char. I must admit i thought the previous poster was talking about RS485 line termination.
I have had your Open, close & send serial working in a small test app, before putting into my main vi, so was thinking it was a timing or clashing. Hence everything moved to a sequential, and some delays put in places (Applied HCR calls for 30ms between most writes, but 'I' commands can be done with 1ms. Hence the fast/slow command delay waits.

...haha found it mid typing. 

Looks like your Open vi has a bug, it specifies 'D' as the termination rather than '0D', that would be what the previous poster was refering to in a rather oblique way.

 

[UoB_Hoss]

ah no, me being stupid, that was just it stripping the 0 in the constant. Still have the timeout.