Hi Everyone,
I am currently working on a feature where we want to show the label names from a matrix interface in DataMiner. The device documentation said this information can be retrieved by sending a command to the device but the device will return the information one label at a time until it is done, we can verify that all the information is received if there is a 5 second window with no messages.
The connector is currently using a serial connection to retrieved information about the matrix crosspoints, due to the nature of how the response is handle we assume that a smart serial connection might be the best way to handle the response. Based on DataMiner Docs a Serial and Smart-Serial cannot exist within a connector that is linked to the same IP and Port, since this is the case, the recommendation is to convert the connector to a smart-serial connection.
When attempting commands over the smart-serial connection the element is not receiving any response. We have a pair that only contains the command and a response that have a single param that is other-next param which should read any incoming response. We have added the headertrailerlink to the header and trailer of the command. We have any IP address with the corresponding port with the IP of the device in the accepted IP Address in the element wizard.
- Are we wrong to assume that any serial connector can be converted to a smart-serial connector?
-
- If not, based on what I mentioned above what could be the possible issue on why I am not receiving responses from the device?
- Even in the case where the connector can handle smart-serial connection, is this the best approach to handle a response like this or there is an easier way?
Note: When making the call over standard serial the only way to get the desire result is to have a response with only a other next param, that will read until timeout which is not ideal.
Hi Aldrick,
Did you try creating a new element? Changing the port type of an existing element can have undesired side effects.
Did you confirm via a tool like Wireshark that the device is responding?
Do you check the stream viewer and SLPort log for any suspicious logs?
Is the connector using the Read action on the response with the "next param"?
Have you tried removing the header-trailer link? This feature is intended for matching responses and shouldn't have any effect on commands. Either you use the "next param" approach or the header-trailer link approach to match responses, but combining can have undesired effects.
Hi Thomas,
I did create a new element because originally it was working and I was suspicious. No I did not monitor the traffic using Wireshark I can try this. No, I did not see anything strange in the Stream Viewer or SLPort logs. The connector has the before trigger on each response to read the response. Initially i did it without the headertrailerlink and i did not have any success so i added after to see if it would help but it did not.