Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Jan (Microbit)

Pages: 1 ... 113 114 [115] 116 117
1711
General discussion forum / Re: Insanity
« on: 2010-11-16, 20:37:25 »
This feels contradictory somehow. You say you are able to upgrade to new firmware in the RRC and at the same time it can't reboot on settings submission any more? Updating the firmware requires the device being able to reboot in the same way as submitting settings does.

Also, are you using the PC client right now when HRD doesn't work or are you using some other configuration?

1712
What is the symptom of HRD not being able to connect? Can you check Window's Event Viewer, Application/System, and see if the virtual com port logs something there(Source "1274Serial")? And finally, run a session with the PC Micro Client's debug option set, close the Micro Client and send the created log file to me? (jan.andersson at microbit.se)

1713
Then I have a question: when DynDNS returns an error, does it continue to
try at the defined intervals, or does it give-up and stop at that point?
Just checked this and it continues reattempting updating at the defined intervals. We are considering extending the status information regarding both DynDNS and dns in order to make it easier to diagnose problems like this.

1714
I am not 100% updated myself when it comes to all possible combinations of settings. But I do know that if you set "Program mode" to 5, then setting Com 2 to parallel isn't allowed, and that is why you see it go back to inactive. I would think that you should have Com 2 in mode 4 and match that with similar settings in the PC program. Mikael isn't here for the moment, so if this doesn't help then we have to wait for him.

1715
Which "Hardware" version do you see on the "Info" page? Which "Program mode" are you using?

1716
Guy,

I still can't get it to work after lowering the baud rate. I must be missing
some setting. It would be great if you and Thom were to provide a list of
correct settings.

Thanks & 73,
Mitch DJ0QN / K7DX
I might have lost track of what your problem is, so asking what is that that doesn't work? The audio, HRD, something else?

1717
Hello,

I am using the Telstra 3G network to access my remote device. The access device is a 3G wireless router which is able to update my remote IP address to DynDNS if the remote wireless device is reset. (the remote IP address is public but not static).

If I ping my DynDNS host name the remote IP address is resolved. Pinging vk3oexxxx.xxxxx.net [132.209.3.131] with 32 bytes of data.

If I use this IP address [132.209.3.131] as the SIP contact in the radio settings on the control device then I can easily connect to the remote device.

If I use the DynDNS host name instead (vk3oexxxx.xxxxx.net ) for the SIP contact then the control device is not able to resolve the remote IP address from DynDNS and I get a SIP Error and 5 sets of increasing tones.

Software is 2.26. I have not tried to use the remote rig device to update DynDNS.

This seems to be at the root of the problem.

73,
Andrew.
Just to be 100% sure: You have entered a valid "Dns server" IP address in "IP Settings"?  ;)

/Jan

1718
Ja tyvärr var det samma - eller nästan samma. Förut har jag inte sett fenomenet att bara halva, eller 25% av sidan kommer fram.

Får försöka med en annan router då. Någon som har tips på en bra stabil router? Kör nu Linksys wrt54gl...
Det du erfar är nog egentligen samma fenomen, bara olika grader av det. I de fall du inte alls får fram nån webbsida så är webbswitchens förmåga att få sänt data till webbläsaren allvarligt försämrad, i de fall du ser delar av sidorna går det lite bättre för den att få iväg datat.

Du behöver väl inte byta hela routern. Testa med en vanlig nätverksswitch mellan routern och webbswitchen.

1719
Du får alltså samma/liknande fenomen med den nya webbswitchen?

Det fenomen du ser beror mest troligt på att webbswitchen inte lyckas skicka tillbaka all nödvändig data för att visa hela webbsidan. Det i sin tur verkar vara en sak som kan uppstå när webbswitchen ansluts mot vissa specifika routrar/switchar.

Om möjligt kan du testa att:

1/
Om inte redan gjort så, byt inställning på "Ethernet" till "Auto" eller nått 100 Mbit-läge.

2/
Sätta in en annan nätverksswitch mellan webbswitchen och den nu trilskande.

1720
I would check to see if it does indeed continue retrying, since that
is the only plausible explanation of why I had this problem, but no
one else did.
We will give it a check, but I would say based on experience that there are often more reasons for a failure than one can imaging ;)

Yes, I was one of the guys that reported the web page accessibility
problem with 2.25 (and only with 2.25!). 2.26 has definitely
solved this, it hasn't died once since I installed 2.26.
That is even more strange! Can't think of any reason 2.25 would have been different than all other versions, including the older ones. (But the previous mentioned more reasons for a failure than imaginable might apply here too, hehe!)

1721
Then I have a question: when DynDNS returns an error, does it continue to
try at the defined intervals, or does it give-up and stop at that point?
......
Since 2.26 solved the stability issue with the web page accessibility, I had
no reason to recycle the power since installing it.
It should continue retrying at the defined intervals. At least that is the intention ;)

You mean that 2.26 has fixed the web page accessibility?! We haven't actually found what has caused some of you having such problems, though one minor thing was spotted during the search for it, and fixed in 2.26. If that "fixed" that problem then it really is great news! From which version did you upgrade?

1722
OK, I see. But I don't see how deactivating and reactivating it could have helped. I would have better understood if a power reset had helped. Also it seems strange if 2.26 is like that in general, demanding deactivation and reactivation for the DynDNS to work.

1723
Although I find 2.26 to be stable and a good improvement, I noticed that
the DynDNS update no longer works, and returns an error message.
Which error message did you get? And where did you see it?

1724
I would be more than glad to allow you to log in my remote and try to access the radio and serial port.  Let me know when your ready and you can try it to your hearts content.
Log into what "remote"? A computer? If so it sure would be great to be able to do that. If not then maybe you are able/willing to try out a fresh rewritten com port driver which is able to log information to Window's log system? The logging function would help track down where it fails.

1725
General discussion forum / Re: firmware 2.21 - unstable?
« on: 2010-10-22, 20:35:59 »
I'm using auto for all sets. I miss an over problem, if i use the ptt switch for long time (15s) the trx stay often on tx. I need to push again the ptt to go back to rx...
The problem is the same with 2.25 so I'll return to 2.15.
If it's possible I would like to have 2.10 again to download.

73''
You are using "Auto" and still have network related problems? Which speed does the switches/hubs/routers you have the RRCs connected to? 10 Mbit, 100 Mbit or even faster?

Pages: 1 ... 113 114 [115] 116 117