we had bought one of your line counters probably 2 years ago.
I’m having an issue of it reading Feet accurately . it takes about a full turn and a half on the wheel to register a foot . If i pull cable till the counter read a foot. Ive pulled 18 inches
Is there a setting to adjust that?
Also what is the string outputting on UDP? I need it to be ASCII. When I start up the counter I am inputting { #cable nothing nothing and } and 50 on the interval. Is this correct?
The Counter string config is only used to connect directly to 3rd party software and allows to change the string to match your software input. It should be set to mm if used with “Oceavault - Cable counter” .
Then in “Oceavault - Cable counter” you should set it to feet.
What seems to be happening here is that you are converting twice and getting 0.01 feet not 1 foot.
When selecting the units in Oceanvault Cable counter to Feet, it takes the mm value and multiply by 0.00328083989501
For outputting UDP string:
Delta String = {,#CABLE,x.xx,}
Eva String = 1:x.xxCRLF
Then setting to feet should not be an option.
You can connect the Cable counter directly to your software and use the String configurator to output $XX.X,METER
What does the string configuture out put to if i am only runing it to my device? Or do i use the other on to the device? My device can except serial or udp.
Please show me an exsample set up for meters out put to a devise.
there is a virus on the download i finally downloaded it and scanned the file and there is a Trojan on the file. don’t email it. please look at your file and repair or advise on how to move fwd.
i got the file. evidently i was wrong. on the UDP input it needs the #cable input to the DT360xi i am using 1.010 version the latest. i still cant get it into the program. can the delta program output to serial? if so that output needs to be the $ sting .
i am not seeing the output in netstat -an when running the counter in udp i see it if i open the imagenex program but if i close it i dont see the ports 1261 source or 25103.