Author Topic: Feature Requests (and don't suggest buying something else:) and Question  (Read 3897 times)

polarlight

  • Newbie
  • *
  • Posts: 1
    • View Profile
hi,

with a heavy embedded sw development background (of automation and
communication related embedded devices) I would like to suggest
the following:

1) I request and vote for the same basic feature as  HB9AZT did (feb-2011)
  On the http URL it would be very handy to be able to give
  a delay/timer value as a URL parameter that would say how
  many seconds the ON or OFF-drive should last (== giving a pulse
  instead of changing state until otherwise written)

2) is it really that you can't read back the current state (last written state)
  of relays, and that you can only read the inputs ? If so, then this is a feature request.
  Sometimes devices boot for many reasons. To allow good software behavior
  you should enable reading the values of ALL signals, including outputs-signals
  back. That way a remote device (assume it just booted) could read
  back the situation (for example the state of relays) and decide it that
  situation should continue (and for how long).

3) Is there any other communication protocol available than the http ?
  (I mean this HTTP URL-protocol is very good invention  and should be
   supported by all this kind of devices, but support for some other
  more M2M oriented protocol such as MODBUS would be a plus)





Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1800
    • View Profile
    • Email
1/
Do you mean this:
Quote
New commands added in version 1.21:

Pulse a relay high(on) for a selectable duration in seconds:
http://[webswitch address]/relaycontrol/pulse/high/[relay/Nexa name/number]/[duration in secs]
See above for [relay/Nexa name/number]

Pulse a relay low(off) for a selectable duration in seconds:
http://[webswitch address]/relaycontrol/pulse/low/[relay/Nexa name]/[duration in secs]
See above for [relay/Nexa name/number]
which can be found on this page:
http://www.remoterig.com/wp1216/?page_id=342
?

2/
Existing firmware versions don't support reading back current relay states. That it mostly due to the fact that if the Webswitch reboots it restores the previous relay states, including Nexa remotes. But support for reading current states will be added in coming firmware versions as it might be handy to get the states when for ex. starting the controlling program.

3/
Only HTTP is currently supported.
Always include type of hard/software and version when asking for support.

ON4AOI

  • Sr. Member
  • ****
  • Posts: 295
    • View Profile
    • Email
Hi Jan,
pse have a look also on the automatic Antenna Switch, maybe for some users the bandselection is enough now
but in my case and probably others it sure isn't.
1) only 1 relay can be set for a band or part of it this should be more
2) 01=160M this should be extended
In my case I have to switch on 1820, 1830,1840 & 1850 to cover 1810-1860
3) 35,36,37,38 (3A) are for 80M band should also be extended or more relays available
RTTY on 80M is between ~3590 and 3610
I can set 35 for CW and 37,38 for SSB but for RTTY I can't set 35,36 (only 36 is possible)
maybe it would be an option that the customer can define its own selection bandselection
for example
3500 to 3580 = relay1
3580 to 3620 = relay2
3620 to 3700 = relay3
3700 to 3800 = relay4

Guy ON4AOI

ON4AOI

  • Sr. Member
  • ****
  • Posts: 295
    • View Profile
    • Email
Jan,
I also forgot the following,
When CAT is not available anymore for a certain time (5 minutes or so) because you switch off the rig etc
the relay that was in use (high) should go LOW, now you have to switch it off manualy

Guy ON4AOI

Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1800
    • View Profile
    • Email
I've added your requests to the to-possible-do-if-possible-list  ;)
Always include type of hard/software and version when asking for support.

ON4AOI

  • Sr. Member
  • ****
  • Posts: 295
    • View Profile
    • Email