Hi
I have a yellow (amber) LED on the bottom row of my Log40m. There is a GREEN LED next to it---I don't seem able to find any information on this LED---any help would be appreciated
Bill, W5UY in Las Cruces
LED color
- VK7XX
- Old Man
- Posts: 442
- Joined: 24 Jan 2013, 04:07
- Location: Planet Earth on Tasmania Island
- Contact:
Re: LED color
Bill, what is the text label adjacent to the 'LED' ?? I have 8 of these indicators across the bottom of my Log4om window and all have a text label.w5uy wrote:Hi
I have a yellow (amber) LED on the bottom row of my Log40m. There is a GREEN LED next to it---I don't seem able to find any information on this LED---any help would be appreciated
Bill, W5UY in Las Cruces
John
VK7XX
Re: LED color
John
Thanks for the response.
You are quite correct in there are eight LED along the bottom
Here is what mine indicate
Far Left
Green Led --- Cat Status
Red Led --- HRD Log, etc
Yellow/Green --- Comm Services <------- This is the one I have questions about
Green Led--- Cluster
Red Led--- Super Cluster
Red Led --- Win Keyer
It may be that these LED's may return to one when problem resolved
Bill, W5UY
Thanks for the response.
You are quite correct in there are eight LED along the bottom
Here is what mine indicate
Far Left
Green Led --- Cat Status
Red Led --- HRD Log, etc


Green Led--- Cluster
Red Led--- Super Cluster
Red Led --- Win Keyer
It may be that these LED's may return to one when problem resolved
Bill, W5UY
- IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: LED color
You have communicator services not fully started. Left bullet is for WCF, right is for TCP connection to Communicator
This is not an issue if you're not using external integrations with WCF.
Yellow means your WCF services are started but not working correctly. It's probably related to running Log4OM not as administrator.
This is not an issue if you're not using external integrations with WCF.
Yellow means your WCF services are started but not working correctly. It's probably related to running Log4OM not as administrator.
Daniele Pistollato - IW3HMH