Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: rgweber on March 25, 2021, 10:45:21 AM
-
Are there any issues with using the internal Ethernet port for both Modbus/TCP to a device via MRX/MWX and a custon protocol to a printer via OPENTCP and STREAMOUT
in the same Project but in separate Tasks/Programs?
-
Are there any issues with using the internal Ethernet port for both Modbus/TCP to a device via MRX/MWX and a custon protocol to a printer via OPENTCP and STREAMOUT
in the same Project but in separate Tasks/Programs?
Not a problem.
-
The sample code(SampleForSendingDataToAPrinter.dmd) for sending to a printer worked just fine by itself in a bench setup. However when that same code was added to an existing program with the Modbus/TCP code working with a scale, it does not appear to work. The PRINT program executes as we can see from the Print.RunCounter. The OPENTCP command appears to execute showing the status in the ladder instruction as Open & Connected highlighted, yet the Device Status window shows State Close. The sample code has a CLOSE command which is executed upon completion of the program regardless of success or error. As the sample code uses the success/err of the instructions to set the next appropriate stage, and we cannot see any stage except SG0 even blink in the Data View, are there any Error registers/codes we can monitor to troubleshoot the issue?