Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Problem receiving data with ET200S 1SI ASCII

Created by: F. Barbosa at: 12/6/2013 3:38 PM (17 Replies)

Rating (0)

Thanks 2

Result pages:: |; 1 | 2; |

18 Entries

Entries per page: 10 | all

12/6/2013 3:38 PM	Rate (0)
F. Barbosa Posts: 9 Rating: (1)	Hello. I am using 1SI ASCII card (6ES7138-4DF01-0AB0) with an IM151-8 (6ES7151-8AB01-0AB0) so I can read values from Buhler weighting scales with RS-485 protocol. The problem is that whenever I configure the hardware of 1SI ASCII with the option "End detection of a receiving frame" as "On expiration of character delay time" or "On receipt of end-of-text character", it won't receing anything, just gives error. If I use the option "On receipt of fixed number of characters", I can read the answer, but I need to get several data, which do not have the same length, so this option isn't good for this case. To send and receive data, I am using FB3 (S_SEND) and FB2 (S_RCV). Do any of you had already any issue like this one? Any tip on how to solve this? Thanks in advance.
F. Barbosa Posts: 9 Rating: (1)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Rakesh Sangle

12/6/2013 4:30 PM	Rate (0)
Owei Gold Member Joined: 10/1/2013 Last visit: 3/21/2025 Posts: 605 Rating: (71)	Hi, to help we need more information. To start with you could tell us, what exact error code is delivered by the S-blocks?

Suggestion To thank Quote Answer

12/6/2013 4:45 PM	Rate (0)
F. Barbosa Posts: 9 Rating: (1)	Most of the time, it's 0811 (which the manual defines as character frame error). But this error is also present even when I read data successfully. With the options "character delay time" or "end-of-text character" the error is 0806, which is defined as charater delay time excedeed". Thanks for your help.
F. Barbosa Posts: 9 Rating: (1)
Suggestion To thank Quote Answer

12/11/2013 2:32 PM	Rate (0)
Fafner Silver Member Joined: 3/20/2013 Last visit: 3/21/2025 Posts: 676 Rating: (44)	As far as it concerns me i got not an error like this and had no problems with different end-terminations. do you know exactly which frames the buhler scales are sending? you can set there the end-of-text charachters? do you have to sniff with a sth. like hyperterminal? the characters you are receiving with "fixed numbers of charakters" are the same you are expecting? you have the right cabling (manual) and the right transmission rate?
	Best Regards, Fafner
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users mmkhan

12/12/2013 4:38 PM	Rate (0)
F. Barbosa Posts: 9 Rating: (1)	Hi. I know which frames I am supposed to receive, and if I use fixed-number character reception, I receive exactly what I am expecting and wha the manual says it sends. Although I have'nt solve this problem, I managed to get all the information I need in one single frame, which I then decompose into what I need. However, the communication is still pretty unstable: I noticed today that when I receive a frame - with proper data - the Error and NDR bits of S_RCV_SI (FB2) are triggered (I suppose that this not happens in the same cycle). Anyone already has seen this scenario?
F. Barbosa Posts: 9 Rating: (1)
Suggestion To thank Quote Answer

12/13/2013 12:32 AM	Rate (0)
F. Barbosa Posts: 9 Rating: (1)	I was analysing this situation and came to the conclusion that, for my hw configuration, which I describe below, I receive two errors and one NDR for each request. When errors come, status change its value to 0806 and then to 1E0D. I have 1 SI ASCII V1.3 (32 B) configured to RS485 at 4800bps, 8 data bits, 1 stop bit and no parity (this was deducted from manufacturer's manual). The end detection is made by receipt of fixed number of characters (for my case, it's 21 characters, with the termination character included), and 8ms of character delay time. Any help will be much appreciated :) .
F. Barbosa Posts: 9 Rating: (1)
Suggestion To thank Quote Answer

12/20/2013 4:08 PM	Rate (0)
Fafner Silver Member Joined: 3/20/2013 Last visit: 3/21/2025 Posts: 676 Rating: (44)	hm, there i have nothin produtive to say, sry. guess you read the helps to the error codes. to you already tried to communicate with a pc to your modul? to see if the error is more likely at 1SI side or more likely on device side? (you can use something like hyperterminal)
	Best Regards, Fafner
Suggestion To thank Quote Answer

12/20/2013 4:10 PM	Rate (0)
Fafner Silver Member Joined: 3/20/2013 Last visit: 3/21/2025 Posts: 676 Rating: (44)	P.S. the hyperterminal out of Win XP (for in Win7 it is not any more 'on board') @moderator: am i allowed to upload this here? if not pls delete post. Attachment hyperterminal.zip (359 Downloads)
	Best Regards, Fafner
Suggestion To thank Quote Answer

12/23/2013 1:30 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (324)	F. Barbosa I was analysing this situation and came to the conclusion that, for my hw configuration, which I describe below, I receive two errors and one NDR for each request. When errors come, status change its value to 0806 and then to 1E0D. I have 1 SI ASCII V1.3 (32 B) configured to RS485 at 4800bps, 8 data bits, 1 stop bit and no parity (this was deducted from manufacturer's manual). The end detection is made by receipt of fixed number of characters (for my case, it's 21 characters, with the termination character included), and 8ms of character delay time.. Hello Barbosa, 1E0D means that something with the data destination is wrong. The common user error is, that the receive DB has not got a sufficent length. The character delay time is used to monitor the received characters. If the communication partner has gaps between the characters of one telegram, error 0806 is reported. In this case the character delay time must be exeeded. But this also affects the end detection "on expiration of character delay time". When using this end detection, the communication partner must "keep quiet" for at least this time before starting the next telegram. Which end character did you use? Can this end character be part the the telegram data as well? Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer

1/9/2014 10:12 AM	Rate (0)
F. Barbosa Posts: 9 Rating: (1)	I've been analysing more deeply this situation and re-wrote the software. But every time I read the devices (scales), I got two errors: when I send a request to a scale that is disconnected, I receive the error 0806 (which I suppose it's correct because since it's disconnected it does not replies), and when I send a request to a scale that's connected, I receive one successful answer, but I get also two errors: 0806 and 0811. However, I get the values correctly, so this would not upset me if the 1SI card would not stop receiving data every 15 minutes or so. If I wait for about five minute, the reception of values unlocks and continues to receive values, and then it stops receiving again and so on. It's been three weeks I'm struggling with problems on this card. Does anyone ever faced something like this?
F. Barbosa Posts: 9 Rating: (1)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on