J Ascii
Dallas Themshirts
I am struggling to convert (modified) ASCII files to rasters (examples attached, zipped + image of error message). Original ASCII files (which I don't have) were delimited using Excel after which they are tab delimitted, as attached. Now it looks like ArcGIS can't convert them back to rasters.
It is you path to the files that is throwing an error. Since your path isn't raw encoded something is amiss. Spaces in the path are not good and any folder beginning with a \t \a and a bunch of others will cause failure.
It has something to do with the modified ascii file structure, because when I convert some random raster to ascii, by using the same tool, and then perform opposite process (ascii to raster) over the same ascii file, then it works. And both the path and file name are default \Documents\ArcGIS\Default1.gdb\ASCIITo_txt18.
Is there any compression going on? Resampling based on the raster environment? The one on the right looks resampled (the edges are a different shape). Make sure the environment extent and cell size are set to the input before converting.
Thanks for the reply. Unfortunately, this has made no difference. The input raster is in fact a resampled file itself as I have converted what was originally WGS1984 to OSGB1936 and have resampled the cell size using the 'Resample' tool (Cubic). Could this be a problem?
Update: The underlying files are actually identical and displaying accordingly when opened in Desktop 10.5. This problem only occurs in Pro, which is incredibly frustrating as I'm deliberately trying to move away from Desktop but Esri are making it hard to do so.
There is nothing in the ascii to raster tool that would account for a change in values. Is there something in the Raster environments that might point to issues? The latter would depend on the raster type you are saving to.
I'm assessing the difference by looking at the raster statistics under 'Properties', which show me that the minimum, maximum, standard deviation etc. are the same. I think the difference in visual display is a bug in Pro 2.0 as this problem does not occur in Desktop 10.5.
I'm working to install an ethernet enabled EZAutomation LED display for use on the plant floor. I called the vendor to ask some questions regarding their product's capatability with Ignition. The vendor said that the displays facilitate a Modbus TCP protocol with ASCII controlling what prints on the display.
I solved the problem by using a ViewMarq Marquee and writing the ascii string to an OPC tag in Ignition. A gateway script would poll tags in Ignition to gather the information. The gateway script would then assemble the ascii string in accordance with what the ViewMarq would expect. Teh gateway scripts would update the OPC tags that were addressed to the holding registers in the ViewMarq resulting in the message displaying.
One pitfall is that the ViewMarq would only take 150 characters therefore I would have to write to 3 OPC tags to create the entire 450 character message. Also, each string had to be an exact length to work therefore I would have to pad the strings with spaces as needed. Python string manipulation worked for this.
Hello all, I've been having troubles with Maya in general, most of the issues I have resolved, however, I've encountered an issue with my files that are Ascii. If I open an Ascii file in the file viewer, do some animation etc. I use the shortcut to save scene, when doing so I am prompted to "Save as" even though the document already exists and the project is set correctly. This issue also appears when I try to close the document without saving and it prompts "Do you want to save changes to Untitled" even though the document name and location is shown at the top of the window. I have done many un-installs and re-installs as well as cleared as much data as I could before doing so - ( -service/download-install/remove-products/remove-windows-prod...), I have also changed the preferences folder many times as well. Though I can save using the .mb files, because I cannot save the ASCII files I am concerned they may be other features I am unable to use. I am reliant on the software for my university course so it is something I am rather concerned about if it were to impede my ability to work. I would also like to say that it was working fine previously, however I wanted to move the location of some files and tried to uninstall it and accidentally cancelled it mid way, it was from that point I had my issues occur. Thank you.
You said you can't save ASCII files. Does this mean that when you hit CTRL+S for example, it'll open the file window as if you did Save as and then still won't let you save? What happens when you try to save the file?
When I hit CTRL+S it opens the window prompting to "Save as" rather than do a regular save, it will let me save, however, it has to overwrite the previous file and warns me when I do so, unlike when I use Maya Binary in which when I press CTRL+S it recognises the file location and saves as it should, automatically overwriting the data from before the save. Before the issue had occured I had no update package enabled and it was working as it should, much like on my laptop, however when the issues first started occurring I did update to the latest software package of Maya, but it unfortunately did not make a difference to the issue. Thank you
Yes, when the files were deleted and re-created, it didn't change the issue with saving. I've tried doing the clean uninstall/reinstall a few times now as well as clear the registry of former data of any autodesk product and the issue is still present. Thank you.
I think so too, I'm tempted to at this point factory resetting my computer to see if that works. I just created one and the same problem is there unfortunately. I believe so, there are some lines of error code that appear, however I'm not sure if they are related to the issue. Thank you
If the only thing going wrong is the window appearing every time when you try to save in ascii format that isn't really a problem. As long as the file is saving properly and you're able to open it then you can keep working.
I'm sorry, I just worry if that feature is unavailable something else may be at a later point if I need it for my work, but that is completely true. I may try a reset as I have some holiday time approaching meaning I won't need to use it for a few weeks. Thank you again for all that you've to help me out, I really appreciate it. I'll leave this as answered. Once again, many thanks.
2- I'm using a local datastore created previously with Python39 and some queries do not return anything. I think queries that use built-in indexes are ok, but if the query requires a composite index where one of the properties is a String property it just doesn't return anything. If I were to re-load those entities to the datastore using the newer Python version (3.11) then it's all good. I could be wrong, but I think this behavior could be related to that warning.
The good news is that in production all works well, but to avoid surprises I would like to run things in dev. as they are in prod. That is, running dev_appserver with 'ascii' as the default encoding.
The way the CAN data is sent is in packages of 4 bytes (out of my hand, cannot change this). So for example when i want to send the device an ASCII command for example: "RETURN STATE?" i need to receive following HEX data over CAN bus:
What i'm struggling with now is what is the correct way to add up these bytes to form the required single ASCII string? This should be easy to do i think but I cannot find the required functions, probably because my PLC programming knowledge is limited.
sry, I don't understand via which system you receive that 4 bytes packet one by one, as after each some timeout or what system you're use for this? Simply in case of long enough timeout for recv condition and long enough defined recv buffer, your each packets can fill your recv buffer one after each other in my opinion. After complete receive I expect that CAN with some idle timeout for other next reasons (your business) so this must be enough in my opinion, you can have all packets in array of byte structure f.ex.
The customer uses CAN bus to control all his machinery. I am supplying a new piece of machinery to this customer. I'm supplying a new piece of machinery which needs to be integrated into the existing CAN network.
DINT tags is not what I would have expected. DWORD would be expected to indicate the data is yet unformatted.It is not clear what you want as an outcome. An array of BYTEs would be expected. Not seeing the code that already works makes this a guessing game.
Thank you for the code suggestion. Now you mention DWord i'm not sure anymore about my tags. I don't have access to the program right now but i will make some screenshots to clear things up when i can.
The rs232 screen shows the function block i created for the RS232 communication to the device. The string sCommando is the string command i want to send to the rs232 device. I tested this side of the communication by just filling in this string in a watch table. For example one of the commands of the device is "STOP OPERATION". So i tested this by typing in the string into a watch table, and the FB correctly sent it to the device as i could see the devices reaction to the command (it stopped its operation..)
My second step was integrating the CAN bus side of the communication. Here i am very limited in my choices. The data i receive through the PN/CAN link (see network view for topology) is received as seperate DWords.
Becaue the RS232 device has some quite long ascii commands i need more than a single DWord to form the corresponding HEX code for the ascii characters. See screenshots for the DWords (not double ints as i mentioned before, was a mistake) for the incoming receive messages.
What i need to do now is convert the HEX data into the corresponding ascii characters en paste them all together as a single string, so i can feed this to my RS232 sCommando string as input for that FB.
c80f0f1006