Thanks Terry, I'm tracking the issue and hoping it can be done sooner.

Hi, guys. I've tested this new version in Mango 2.7, but not sure I was using it by the right way.
The module seems to process only one character after the escape one. So I can get HEX value 00 by typing \0 as read command, and HEX value 01 by typing \1 .
When it comes to complicated HEX value like FD, \253 cannot work because it is treated as three characters, as in HEX value 02 35 33 .
The job is to send and receive strings in HEX format, and the commands may be like 01 00 00 FD AE CA 5C. Using escape characters is one way to input these strings on Mango pages, maybe there are other ways, please let me know.

Quick question: how to input HEX value like FD or CA?
I was writing this in a hurry, any mistakes, please correct me.
Thank you guys.

Thanks to your reply, Terry.
I'm tracking your issue at github and have seen your fix about write command. I can't wait to see all codes fixed and try out the new version of TCP/IP module.

This TCP/IP data source is really handy.
Yet it seems to send and receive data as strings as always, despite of escape characters like '\' .
Is there a way to send and receive HEX data using this data source? @administrators

Solved.

There is a SQL grammer error in Line 18 of the "createTables-MYSQL.sql" file, which is in the "m2m2-reports-2.0.7.zip" module.
There is a dot character where there should be a comma in SQL.

There are some problems that stop a new mango 2.4.2 installation from starting on a Windows 7 machine.

There are some problems that stop a new mango 2.4.2 installation from starting on a Windows 7 machine.

Hello, Joel. This is Marc working with Mebius.
We have acknowladged all alarms and then deleted all from EVENTS table using the SQL statement.
Unluckily it didn't work much. Maybe our trouble comes elsewhere.

We did find something. As you and your colleague Phil know, we are using combinations of scripting data source, serial test data source and meta data source to send and receive messages through serial ports.
There are more than 20 combinations of these data sources in our mango system now.

1. When these 20+ combinations are disabled, other 100+ data sources and publishers can work at a normal speed.
2. When these 20+ combinations are enabled, with periods of 20 seconds on scripting data sources, the whole mango system slow down. All 120+ data sources updates slowly. And all publishers become slower and slower until they stop to publish any data.
3. After we change the periods to 5 mins on scripting data sources, the publishers can work normally, but data sources are still slow. We got stuck when opening the "datasources.shtm" page, several minutes after enabling them.

We need a way that provides both shorter periods and normal speed updates.
Also we see a very high memory usage of mango, up to 1.4G. Is that because the total number of data sources, or something else?

@JoelHaggar said:

I see you have a lot of unacknowledged events. I would recommend purging your events table and see if that speeds things up. I seem to be sharing this thread a lot lately:
http://forum.infiniteautomation.com/forum/posts/list/1796.page

If you can use the SQL statement to delete everything in the events table. Go through your settings and turn things to Do Not Log that you don't need to minimize the number of events that are being created.

Let me know if that helps,
Joel.

Thanks, Philips.
Learned more about the response. It's like "0DH [X1] [X2] xxxxxxx 20H 20H 0DH 4CH 32H xxxxxxx 20H 20H 0DH 4CH 33H xxxxxxx 20H 20H 0DH", in which [X1] may be letter 'A','B' or 'C', and [X2] is a single digit.

Tryed to split it into 3 parts using 3 data points, each of which ended with "20H 20H 0DH". A sample of the first part is in the screenshot attached.
But "patternMismatch" alarms showed up.
Screenshots of Serial Data Source Configuration, alarm, and event in Mango database are attached.

As may not be seen directly in the screeshot, there are two spaces in both message terminator and message regex. Whole strings are written below:
Message Terminator: [space][space]\r
Message Regex: (?s)([A-CL][0-9].*)[space][space]\r

Embbeded flag expression (?s) is used because there are several single '0DH' in the "xxxxxxxx" part of the response. So the ".*" can match them.

I took out the piece of "messageMatcher" java code from SerialDataSourceRT.java, and tested it with sample message and regex above. It was a match. And I got to find the problem elsewhere.

Now it seems to me there is only one space left in the message and the regex, seen from the highlighted parts of the screenshots. Not sure that is a display issue or really a clue.
What do you see, Philips?

@phildunlap said:

The difference from what you'd expect in the resulting terminator using the \s is because Java escape characters are different than regular expression escape characters (spaces are okay with Java). This is unclear, I should probably add that to the documentation.

Unfortunately no, the serial data source wasn't written for protocols that are length dependent or have ambiguous terminators. I think the existing solution is to use the same trick and buffer the serial data into a meta point, then shuffle it to the right point from a script.

Attachment: download link

Thanks, Philips. I've tested this version.
First of all, I was wrong about the protocol. It's a "20H 20H 0DH" at the end of the message, not a "0DH 0DH 0AH" as I thought before.
So I tried "\s\s\r" at first, and something about escape was wrong. On saving data source properties, this version lost the first two \ charactors and turned "\s\s\r" into "ss\r". You may want to look into that.

"[space][space]\r" seems not so well-formed to me, yet it got a correct command message to send.
Then again, the protocol, which is definitely not my favourite, has this response like "0DH 41H xxxxxxx 20H 20H 0DH xxxxxxx 20H 20H 0DH xxxxxxx 20H 20H 0DH".

"20H 20H 0DH" is the end of response, but it also shows up in the middle, twice. Is it still OK to use it as the message terminator?
@phildunlap said:

Hi Marc,

It looks like that restriction was improper. I removed it and tried to read around to validate it, but my serial cables have seemingly grown legs and I can't test as thoroughly as I'd like. Let me know!