News:

  • February 10, 2025, 11:19:10 PM

Login with username, password and session length

Recent Posts

Pages: [1] 2 3 ... 10
1
Done
2
Good morning BobO, I'm open to whatever you would need done to drill down into this.

Hit us at support@hosteng.com and I'll give them heads up.
3
Good morning BobO, I'm open to whatever you would need done to drill down into this.
4
Certain hardware cannot roll back because there were hardware changes that require newer firmware. Yet another pain caused by the supply chain crisis.

This error happens when all of the packet buffers are used, generally with packets the PLC isn't sure what to do with. Sometimes it is transient due to a massive broadcast packet burst, but sometimes stuff is hung in the stack. There may be things we can do to mitigate it if we could determine what's getting stuck. There are some network diagnostics in 2.10 (BRX) that might give us some insight into what's happening. If it is pretty repeatable, we can talk you through what it takes to get the diagnostic dump.
5
Do-more CPUs and Do-more Designer Software / Odd network problem with OS 2.10
« Last post by stoic-one on February 09, 2025, 09:08:16 PM »
When connected to my network, I'm getting ST145 and ST146 comm warnings.
I've replicated this with the following CPU's:
BX-DM1E-M-D manufactured 08/24 shipped with 2.10.3, the software will not let me roll this unit back to an earlier version.
BX-DM1E-M manufactured 03/24 updated from 2.9.8 to 2.10.3
BX-DM1E-36ER3-D manufactured 05/24 updated from 2.9.9 to 2.10.3

If I alternate back and forth between 2.9.x and 2.10.x, in the above cases, when 2.10.x OS is installed I get a network error. I can still connect with the processor, but it's slower than normal.

It's an all gigabit home network, but needless to say there's a fair amount of non-industrial stuff going on in the background. I've isolated it to HDMI over Ethernet device. When I disconnect it the error clears when using 2.10.x.

I also tried this with a T1H-DM1E manufactured 06/19
Which did NOT have this problem after being updated from 2.9.6 to 2.10.2, it's a Do-More, but it's not a BRX.

I'm not saying there's a problem Host necessarily needs to fix here as I've never observed this in an actual installation at a customer site. Of course 2.10 is also relatively new, so who knows...

I am however curious what might be the differences between 2.9.x and 2.10.x on the BRX platform that would cause this.
6
Do-more CPUs and Do-more Designer Software / Re: BRX to Davis Weather Station Comms
« Last post by Kristjan on February 08, 2025, 06:04:28 PM »
Look for the angle brackets at the right edge of the Postman application, see attached screenshot.

You may already have seen that API data access is very different between systems. Both in terms of syntax and authentication. Some don't require any authentication while others do. And the authentication methods are different. I found a case where the BRX couldn't handle the authentication because the JSON Web Token was too big for the BRX to handle.
7
Do-more CPUs and Do-more Designer Software / Re: Modbus Port Forward Fails
« Last post by BobO on February 07, 2025, 02:19:28 PM »
Okay, I will update when the opportunity arises. Do you have a list of registers I should check before triggering the REBOOT instruction next time?

There are two bits, ST300 and ST301, that trigger diagnostic dumps. ST300 dumps info about the network packet frames in use. The critical data gets dumped to a long range of DSTs. DST98 and DST99 contain the number of frames currently in use, DST100-DST199 contains a table that is a distillation of the types, source/dest ports, and counts of everything in the stack. DST200 contains the raw contents of one of the frames, but I don't recall the details of it. Generally the best things to do is create a data view with ST300, DST98 and DST99 in decimal, and DST100-DST1?? in hex. Enabling DST300 will start dumping.

DST301 just dumps some resource usage info, memory stuff and socket counts, into DST200-DST205. Viewing that in decimal is easiest.

I'll tend to check ST301 first, then do the network dump ST300. Since they share some registers, you can't do both at the same time.
8
Do-more CPUs and Do-more Designer Software / Re: Modbus Port Forward Fails
« Last post by Bolt on February 07, 2025, 01:49:18 PM »
Okay, I will update when the opportunity arises. Do you have a list of registers I should check before triggering the REBOOT instruction next time?
9
Do-more CPUs and Do-more Designer Software / Re: Modbus Port Forward Fails
« Last post by BobO on February 06, 2025, 03:56:20 PM »
I don't think the best diags are in that firmware version. If you were to update to 2.10.x and this happens again, there are definitely some things we'd love to see.
10
Do-more CPUs and Do-more Designer Software / Re: Modbus Port Forward Fails
« Last post by Bolt on February 06, 2025, 12:55:15 PM »
I guess I probably should have checked ModbusTCPServer.ActiveSessions? The system is set to a max of 16 connections, 1800 seconds timeout. OS is 2.9.5.
Pages: [1] 2 3 ... 10