Hello,
I'm using a DL310 datalogger with the intention of setting up communication via Ethernet as the primary mode and RS232 as a secondary mode, acting as a backup. This backup communication mode is particularly useful in case of communication loss.
I've already conducted separate tests for each communication mode, and they've proven to be reliable.
In my specific configuration:
To configure this feature, if supported by the datalogger, could you please guide me on the steps to set it up?
Thank you in advance.
Hi All,
Let me clarify my previous request:
When I collect data with the Radio modem and communication has failed, how do I configure the LoggerNet software to switch automatically to collect data with the GSM modem ?
Have a nice day
It is possible, but a little bit complicated to set up. You need to use the scripting language of Loggernet called Cora Command. There is a document describing the scripting language in the Loggernet installation folder. Usually you find cora_cmd.pdf in C:\Program Files (x86)\Campbellsci\LoggerNet\
In Task Master, set the script command to run after failed communication. The particular command to use is "set-alt-partent". In Loggernet Setup, you will have both communication paths set up, but the datalogger only once. The script command will move the datalogger from one Pakbus port to another. Give both Pakbus ports in the list for set-alt-parent if communication failed.
That task triggered on failed communication will leave the station on the cell modem if the radio network failed. It won't automatically switch back to the radio network until the cellular connection fails. I suggest a scheduled task to move the station back to the radio network. To move the station back to the radio network, use set-alt-parent with only the radio network Pakbus port as an option in the list.
Hi Davis,
Thank you for sharing this procedure.
With my first use of the Cora Command script, I find it very interesting, several additional features are available.
The task 1 ran successfully, it's amazing to see the Datalogger switch from the Ethernet Port to the COM Port root in Setup > Standard View :D
Here's my Task 1 configuration in Task Master:
- How Task 1 Starts: after premary retries failed
- Command Line in What Task 1 Does : --input={connect localhost; set-alt-parent CR310_Radio PakBusPort PakBusPort_2;}
To return the Datalogger to Radio Mode as mentioned in your answer I tried to create a Task 2 with this configuration:
- How Task 2 Starts : Schedule interval
- Command Line in What Task 2 Does : --input={connect localhost; set-alt-parent CR310_Radio PakBusPort ;}
Apparently This command didn't work with me.
I tried this command:
--input={connect localhost; set-alt-parent CR310_Radio PakBusPort_2 PakBusPort;}
With this command the Datalogger switched to Radio Mode after Scheduled interval, That's fine! but I noticed that at each interval, the Datalogger changed its epmlacement and move to other root.
Can you help me to find the right command to execute ?
Best Regards
I figured it out. List the same PakBusPort twice. Based on the documentation, I thought the command could take a list of just one PakBus port.
--input={connect localhost; set-alt-parent CR310_Radio PakBusPort PakBusPort;}
Hint: if you did not know, you can manually test tasks on the Status tab of Task Master.
hi,
Just adding our experience as we had the same issue but a slightly different solution
We run dual comms at our flood warning sites for resilience and typically have a combination of Hytera radio and IP comms, either cell modem or direct internet or microwave link. mix of loggers from cr800, 1000 and 310's now the standard .
Our solution works around a load balancer (fortigate 30E)
we configure out comms paths in the load balancer as a virtual server that then has an assigned local IP which we reference in LoggerNet. We simply run retries on loggerent and let the load balancer change paths if needed. The load balancer can be set in a variety of modes but typically set to first alive and have health checks to routinely ping the assigned paths.
our radio system is managed via a Moxa Nport RS232 device server that has the bonus of IP address and 8 rs232 outputs assigned by ports, this can be setup in the load balancer but has the limitation of only one loggernet connection at a time that does cause some conflicts if call sequencing is not managed. retries tend to sort.
Our next iteration is to upgrade the load balancer and look for more reporting to improve identifing falied comms paths but system has be operating and stable for a number of years
Can provide more detailed config and mapping if anyone intereted
This post is under review.