konsultnisse's dashboard

i have a similar problem..
i can't upload appl. from serial and from appl. i can't send/recive anything.. any help please?

Regards, Lorenzo

p.s. i have already tried without debug mode

Hi Max,

Just to make sure I understand your problem...

1. You can upload firmware using the serialport ?

2. upload of your appl. works when using Eth (eg. UDP or TCP) but not working when using the serialport ?

3. serial upload of your appl. works, but your appl. can not send or receive anything using the serialport ?

If 1 & 2 = yes
- try to turn off "debug mode" if on. (found under "project - settings"
and try again.

Best regards
/Anders

Hi,

I tryed to change the network & subnet to a full C net on my normal PC and then it works, however then I'm not connected to my "company" network anymore..:-((

Today I also find out that this problem/bug has something to do with "debug mode". (small subnet + debug mode)

As I said previously, If I upload app. (not debug mode) on a PC with a full C net and then moves it to a PC & net with a smaller subnet I can upload app's without any problem unlit I check the debug mode box. after this the DS202 continious rapidly flashes the green led and the IDE indicates "no contact" (red dot). In this state the DS explorer can't find the DS.

Also in this state the serial upload of app. fails(eg. says "loading") but nothing happens.

Best regards
/Anders

Yea, I tried the same settings as you did above, still was able to see and upload!!! Very intriguing indeed! What if you took your work PC off the network and just assign different subnet mask to it and connect the DS202 directly to the PC. Would this work?

Also, any possibilities for network sniffing to see if there were responses from the DS202 when the Device Explorer is trying to search for devices? If you need a software to use, you can try our IO Ninja software : http://www.tibbo.com/ninja.php

Hi,

T-bone !

I tested the new IDE release.. same problem..

I did some more testings, it looks like it has someting to do with
the size on the PC's network subnet.
If I use a pc with a full C subnet eg. netmask=255.255.255.0
everything works just fine.
My normal PC at work is using a netmask=255.255.255.128
and here it just won't work.

My conclution is that the IDE has an issue with not handeling
smaller subnet's than a full C net in a correct way.

There might also be a problem in the DS/EM202 firmware with
"small" subnet's. It did'nt work in my first test, but I'll do some more testing to be sure. If I use a full C net in the 202 it works OK.

Best regards
Anders Fromell

Thanks Mike! :) – ezuk, on July 30, 2008 06:19

Thanks :) – vovkos, on July 30, 2008 05:40

We also plan to include WinPCap into Ninja installer package for convenience.
But you are right, error message should not be there even if no wincpap is installed (for users that are not interested in network sniffing)
We will fix that in future revisions. – vovkos, on July 30, 2008 05:38

Let me add some clarification regarding this topic.

For the time being, we are not planning to charge for our TIDE software, even when we take it out of beta (which is to happen soon). We will do our best (but do not undertake) to keep this policy in the future. We can afford to do so because we also sell related hardware.
Ninja is a different story. It simply has no related hardware, and we at least need to cover the the process of turning a set of separated internal utilities into a finished product, right?

Now to rather confusing topic of relations between Ninja and existing packet sniffers.

Originally Ninja (which was not called Ninja at that time ;) was meant to be an advanced terminal emulation program with support of multiple transports (TCP/UDP/PIPE/Serial), client & server modes, UDP broadcasts and ability to handle binary data.
But the resulting modular and asynchronous I/O architecture and -- more importantly -- the beautiful logging engine were simply too good to stop just here :)
So we decided to add monitoring capabilities as well (serial sniffer is definitely coming in the future releases) -- to turn advanced terminal emulation program into a well-rounded communication debugging tool.

The difference between Ninja Network Sniffer plug-in and existing packet sniffers such as WireShark -- is in the representation of captured packets.
For example, WireShark simply cannot show the contents of 2 packets at once -- you have to switch from packet to packet to see the contents.
Our log engine lets us show all the packet contents side-by-side in a single view, making it much easier to follow the actual data flow.
Of course current protocol parsing capabilities of Ninja Network Sniffer plug-in could not match those of WireShark -- which has been in development for over a decade.
Currently we only have support for basic internet protocols such as TCP and UDP, but if there is demand from customers we will work to improve that.

BTW Ninja has another approach to sniffing TCP/UDP/PIPE connections, and that is Socket Proxy plug-in.
Being proxy, it redirects the connection between 2 endpoint and all the data they exchange -- logging it in the process.
That means you also get the contents of data flow, but this time you get it in an even clearer representation, avoiding "packet" notation.
Not to mention that regular network sniffers (WireShark included) simply do not fit into certain scenarios.

Wrapping up, Ninja is not trying to replicate functionality of WireShark and other packet sniffers.
Instead, it introduces a different approach to viewing captured data.
But even if you decide to stick with your favorite tried-and-true packet sniffer, other Ninja plug-ins still can offer functionality useful in the fight against issues in communication area.

I'm hopeTibbo is making lots of money, their tools are terrific!

I'm not quite sure I'm following...

There are no plans to charge for TIDE... This is a different product. You have nothing to worry about re TIDE. :)

And I do apologize if anyone was offended - that was not my intent! – ezuk, on July 29, 2008 10:59

Please be not offend, but he seems me that this is the bad politics of the firm, such tools guilty free. I'm worries a fact that Tide has the postscript "This software can be used free of charge for as long as it remains in BETA".

This marks that he will be paid in the future (Tide), and stops then to be worth while from solutions Tibbo.
He stays us to have hopes only that he will not happen so and tide is in the version beta eternally ;]

Right -- it only means the sniffer won't work (other plug-ins work). To try the sniffir, get WinPCap - http://www.winpcap.org/ – ezuk, on July 29, 2008 10:44

Yup. Ours is different -- simpler to use, and you can clearly see (and even search) beyond packet boundaries.

And we use the same base DLL like Wireshark.

yes I have it installed on my computer, and when I run the program the warning box appear :



after I press OK, the ninja program could still running (seems ok)

For sniffing IP..
It's free......

http://www.wireshark.org/

/Anders

I'm using XP Pro SP2

I tried what you said using the latest version of TIDE (2.6.25).

1. I loaded the 202 with the EM202-1.00.01 firmware, and I was able to see it in Device Explorer
2. Loaded with EM202-02.05.01 and I was still able to see it in Device Explorer.

I am unsure why it is happening the way it is with your system over there. What OS are you using? I am using XP SP2.